Start with the person who will use the records
Imagine a maintenance team collecting street-light information. They need more than dots on a map. A useful record could include a stable lamp number, location, observed condition, photograph, and visit date. Those details help the team find the same asset on its next visit.
Ask the users what they need to search and update. Keep names and field meanings consistent. If one person records a material as unknown and another leaves the field blank, the difference should be intentional and understood.
Try the form before collecting everything
Test a small range of real situations first. Include an unreadable label, inaccessible equipment, and something that does not fit the proposed categories. It is easier to improve the form now than to repair hundreds of inconsistent records later.
A fixed list of choices can prevent spelling variations. Esri calls these controlled choices domains. They help with consistency, but the list must allow honest answers. A fieldworker should not have to select the wrong category just to finish a record.
Explain what the map position represents
Decide where each point belongs. Is it the centre of the cover, the equipment base, or the nearby identification label? Record how the position was measured and which coordinate system describes it, so the next team can reuse the location.
Keep measured positions separate from locations copied from old records or estimated from an image. Review duplicates, missing photographs, and unexplained gaps in coverage. A tidy map can still contain the wrong description or leave out a whole work area.
Where Geobiro can support the survey work
If your GIS project needs new site measurements or terrain information, Geobiro can help define that survey scope. Its surveying service connects field measurements with terrain data, drawings, and digital models.
Your GIS team should provide the area, required features, coordinate requirements, and the information its system needs. Share an example of the receiving format and explain how the data will be used. Agree the survey outputs with Geobiro before work begins. Database design, asset descriptions, and loading data into your GIS should have clearly agreed responsibilities.
Keep a data dictionary with the delivery: a short explanation of each field, its units, and permitted values. Also decide who will update the records. Even a good first survey becomes less useful if later changes are stored in unrelated spreadsheets.
Common questions
Is a spreadsheet enough to hand over the data?
It can work for a simple point list if coordinates, reference information, and field meanings are included. Lines, areas, connected networks, or photographs may need a different agreed format.
Should we delete the old asset records?
Usually, review and reconcile them first. Keep useful identifiers and history, add the new evidence, and flag conflicts. Silent replacement can break the connection to previous maintenance work.
Further reading
This article was rewritten in October 2026 around the subject of the original Geobiro post. The original publication date is retained; the update date identifies the current text.



