Importing map data

Review your source file and map its groups, fields and coordinate system.

Last updated: 10 November 2026

Supported files

Import in the top toolbar uploads map data. Editing permission and the relevant destination module are required.

The general upload allowance is 300 MB and 400,000 total features per file. Divide large or complex data into meaningful sections. Compressed files are also checked for expanded size and compression characteristics.

For independent-unit tables without coordinates, use Unit import instead. Uploading a .sosogis project package follows a separate restore workflow.

Preview the file

1. Select Import.
2. Upload through Drop the file here or select it.
3. Check the detected format, group count and feature count.
4. Verify Source coordinate system. estimated; please check means the selection is uncertain.
5. Select Destination for each source group.

Basemap layer (reference) creates geometry retained only for reference. A type under Network feature turns suitable geometry into an editable project record. Selecting Transfer excludes that group.

Apply suggestions restores the system's suggested types. Use all as basemap and Import none help with bulk selection. Suggestions do not confirm the accuracy of your source data.

Map fields

Use Name field to choose the column supplying record names. For network feature destinations, open Field mapping and map fields such as fiber count, tube count, diameter or status to source columns. For a reference destination, edit the layer name.

Calculations assume 12 fibers where a cable's fiber count is unmapped or blank. Always map this field when the source contains the actual fiber count; review missing-field warnings in the result.

Numeric values are interpreted in the destination field's unit. Compatible units may be converted; ambiguous or incompatible values are rejected. Source attributes are also retained for network features. Reference-layer import may not retain every source column; keep the source file separately.

Import and check the result

1. Review group selections, field mappings and the coordinate system once more.
2. Select Import.
3. Read the created-record results and reasons for excluded features. Invalid attributes, invalid geometry, empty mapped fields and geometry incompatible with the destination are reported separately.
4. Use Show on map to check locations and inspect numeric values in a representative feature card.
5. If the coordinate system or mapping was wrong, use Undo transfer and upload again with the correction.

The import is recorded as a single history operation. Later edits to the same features may need to be resolved before undoing it. See Change history and undo.

Connect cable endpoints during import

For cable destinations, Endpoint connection associates cable endpoints with node records. It does not create fiber splices or patch connections to equipment ports.

1. Set the group's Destination to a cable type.
2. Select Connect endpoints.
3. Check Tolerance (m) for location-based matching.
4. Map A endpoint key and B endpoint key if the source contains node keys.
5. Set Create node if missing if you want new nodes at unmatched locations; otherwise leave Creation selected.
6. Review endpoint connection results and warnings after import.

Save a source and retain field corrections

Use Save as source to identify a dataset received regularly. Choose the same stable Key field across all imported groups in that source. Keys in subsequent files are used to compare differences against existing records.

1. On the first import, select New source under Source, enter Source name and check Key.
2. Upload the updated file through Import and select the same entry in Source.
3. Use Show differences to open Source differences.
4. Review Source changed, Keep local, Conflict, Moved and Absent from source. Details compare Legacy source, New source and Local values.
5. Select Keep local version on the relevant class or row to preserve field corrections. Use Apply source where a change is required; separately choose Release or Delete for a record absent from the source.
6. Under Destination, select Apply in a design branch (recommended) and Apply. Put the resulting design through review and publication.

An authorised administrator may also use Apply directly. If the displayed example list is shortened, remember that class-level decisions also affect rows not shown.

Data sources in Project shows source names, key fields and import history. Changing the key field may produce new and absent-from-source rows in the next file; keep the key scheme consistent for a source.