Guide

Exporting road survey findings to GIS: KML, GeoJSON and CSV

KML, GeoJSON or CSV for Google Earth, QGIS and ArcGIS: coordinate systems, camera vs defect position, and the provenance fields every export needs.

Updated 29 October 20267 min read

Short answer: Use KML for Google Earth and quick client sharing, GeoJSON for QGIS, ArcGIS and web maps, and CSV for spreadsheets and audit. All three should use WGS 84 latitude and longitude. Keep the camera position and the defect or asset position as separate features, and include provenance fields such as finding ID, source file, source time, GPS quality and survey date so the GIS team can trace every record back to its evidence.

Choosing a format

GIS export formats compared
FormatUse it forNotes
KMLGoogle Earth, quick visual checksEasy to open; less suited to analysis
GeoJSONQGIS, ArcGIS, web mapsStandard GeoJSON uses WGS 84 longitude/latitude
CSVExcel, audit, import into other systemsKeep separate latitude and longitude columns
GPXRoutes and waypoints for GPS appsTracks and pins only
Evidence ZIPHandover with imagesFrames plus a manifest that lists every file

Camera position vs defect position

The GPS point is where the camera was, not where the pothole or sign is. A defect on the far verge can be several metres away. Good exports keep the two apart: one feature for the camera position at the source time, and one for the object’s own position when it has been placed. RouteLens exports them as separate features, and asset records keep their own location separate from the camera track.

Coordinate systems

KML, GPX and standard GeoJSON use WGS 84 (EPSG:4326). If your client works in a projected system such as a UTM zone, reproject in QGIS or ArcGIS after import rather than editing coordinates by hand. Keep the original WGS 84 values in the CSV for audit.

Fields every export should carry

  • Stable finding or asset ID (for example SGN-0142)
  • Type, severity and status
  • Survey date and source time (UTC where known, otherwise marked unknown)
  • Source file name
  • GPS quality: fix type and DOP
  • Chainage, marked as calibrated or travelling distance
  • Link or path to the evidence frame

Importing into QGIS

  1. GeoJSON: Layer → Add Layer → Add Vector Layer and pick the file.
  2. CSV: Add Delimited Text Layer, set X to longitude and Y to latitude, and EPSG:4326.
  3. Style by severity or status, and join to your asset layer on the asset ID.

Avoiding silent data loss

The most common export problem is a filter left on: a project-wide export quietly drops records. RouteLens runs a preflight that shows the full counts and IDs, warns about missing evidence, UTC or object location, and never lets a search filter silently remove records from a project-wide export.

Questions

Which format should I send to a GIS team?

GeoJSON for QGIS or ArcGIS, plus a CSV for audit. Both should use WGS 84 latitude and longitude and carry stable IDs.

Why are my defects plotted on the road centre line?

Because the camera position was exported instead of the defect position. Keep camera and object positions as separate features.

Can I open RouteLens exports in Google Earth?

Yes. Export KML for the route, start and end markers and pins.

RouteLens is built by UGAC. Where this guide describes RouteLens behaviour, it reflects the release status published on 29 October 2026; see the product overview for what is verified.

Next step

See RouteLens on your own footage.

Book a 30-minute walkthrough. Bring a recording and a sample report, and we will show you the map, video, findings and coverage working together.

Book a demo