GIS road inventory: from a drawn corridor to a maintainable register

A maintainable road inventory separates four concepts that are often mixed together: the stable corridor reference, administrative segments, located assets and dated observations. A bridge can then retain its identity when segmentation changes, while a new inspection does not erase previous evidence. GIS adds spatial relationships and query capabilities, but the inventory’s value depends on identifiers, dates and update rules.

The decision this guide supports

Before capturing assets, choose a linear reference that can be explained and repeated. Cartographic geometry does not always match operational direction, and administration may change within one route code. For the 45A04 demonstration, the correct reading is by segment and source: some sections are administered by ANI and others by INVÍAS, so the National Route designation does not prove a single administrator or a complete inventory. The SINC v6 methodology published by Colombia’s Ministry of Transport is the reference for structuring applicable information.

The stable unit is not always the corridor’s complete geometry. Design a section identifier that survives cartographic correction and links landmarks, assets, inspections, defects and interventions through linear location and validity dates. Keep administration as a time-dependent attribute: a change from ANI to INVÍAS, or the reverse, should not erase history. Define rules for overlaps, gaps, carriageway changes and non-monotonic kilometre references. The resulting register must let a reviewer reconstruct which network configuration was current when a measurement was taken or works were performed.

Recommended workflow

1. Agree. Create a stable corridor entity and relate geometry versions without losing history.
2. Structure. Model administrative segments with validity dates, owner and attribution source.
3. Check. Assign stable identifiers to bridges, signs, drainage and other observed assets.
4. Document. Store inspections as dated events separate from the asset and its base location.
5. Operate. Link planned and completed interventions without overwriting documented condition.

Minimum controls before publishing or delivery

A useful review combines automated checks with expert judgement. At minimum, record:

• stable identity across geometry changes.
• administration declared by segment.
• inspection date visible for every condition statement.
• photos and documents connected through traceable references.

Limits that must remain visible

A bridge record confirms that a source inventoried the asset; it does not establish safety, capacity or current condition. An undated photograph does not resolve that limitation. A professional viewer needs to show source, cutoff and scope, provide a fallback when WebGL fails, and let users distinguish loaded data, selection and calculation. Good publication preserves uncertainty instead of hiding it.

To apply this method to a concrete project, review the GeoSAT sector service and compare its dependencies with the related service. These links serve different intents: this guide explains the process, while the service pages define scope, evidence and the appropriate commercial next step.