Import and export data

Prepare city-scoped CSV, JSON and GeoJSON files and review changes before importing.

Import review dialog with a preview of new, updated and invalid crossing rows. — Review the row statuses and validation messages before importing. Actual application interface with illustrative records; no data was imported.

Supported file structures

Format	Structure
CSV	A header row using the app’s crossing field names, followed by records.
JSON	An array of records, or an object containing a crosswalks array.
GeoJSON	A FeatureCollection with crossing properties. Point coordinates provide longitude then latitude when those properties are absent.

Import with a preview

Open Import / Export in management and select the destination city you are authorised to edit.
Choose the file. The preview classifies rows as new, update or invalid and shows validation errors.
Review crossing IDs carefully. An existing ID in the same city is an update candidate. Duplicate IDs within the file and IDs belonging to another city are flagged as invalid.
Choose whether existing records should be updated or skipped, then confirm the import. Invalid rows are skipped.

Imports are written in batches of 100. If a later batch fails, earlier successful batches remain saved. Review the error and existing records before retrying; the whole file is not one atomic transaction.

Export for review or transfer

Choose a city or the available city scope and download CSV, JSON or GeoJSON. Use an export as a field-name reference when preparing imports. Verify record counts before treating a download as a complete backup, particularly for large datasets.

Open import and export