GeoJSON imports
Use GeoJSON for mapped municipal assets such as hydrants, valves, manholes, sewer mains, catch basins, water mains, and boundaries with point, line, or polygon geometry.
Imports
GIS and asset data imports for municipal operations
TraverseOps helps small municipal teams bring existing asset data into daily field operations with guided imports, field mapping, validation, duplicate detection, and honest rollback planning.
Start a municipal pilotCSV imports
Bring in spreadsheet asset lists when records include fields like asset ID, type, latitude, longitude, status, condition, and other operational properties.
Shapefile roadmap
Shapefile support is planned for teams that still receive GIS exports as zipped shapefile packages. Until implemented, convert to GeoJSON or CSV for pilot imports.
ArcGIS REST roadmap
ArcGIS REST source connections are on the roadmap for reading hosted layers. TraverseOps is intended to complement GIS systems, not replace authoritative GIS administration.
Validation checks
Preview import issues before committing data, including missing asset IDs, invalid geometry, unsupported file types, empty datasets, file size limits, and partial-import errors.
Field mapping
Map local column names to TraverseOps fields so municipal teams can keep existing asset IDs, asset types, statuses, coordinates, source IDs, and useful custom properties.
Duplicate detection
Flag duplicate asset IDs and repeated records so admins can decide whether to skip, update, or clean records before operational crews depend on the data.
Rollback planning
Import history can show what was committed and where rollback would require cloud import tracking. Rollback actions stay clearly marked until the backend supports them.
A focused pilot can start with one import, such as hydrants or manholes, then expand once the field team confirms the mapped records match daily work.