Spatial7 EAM Data & Migration SpecialistLesson 2 of 4 · 0% complete
Preparing asset data for Spatial7

Mapping to the Spatial7 taxonomy

Turning a source classification into the controlled Spatial7 taxonomy.

45 min

Map once, deliberately

The import wizard maps each source column to a master field, and remembers the mapping as a reusable profile. The work that matters is the classification mapping:

| Source value | Spatial7 class | Type | Subtype | | --- | --- | --- | --- | | RD - SEALED | Roads | Road Segment | Sealed carriageway | | SW PIPE | Drainage | Pipe | Stormwater pipe |

Values that do not map

A source class with no counterpart is not guessed at. The record is registered against Other Assets, the original value is kept in source_asset_class, and the row is flagged for review. That gives you a list of decisions to make rather than a silent reinterpretation.

Site and facility identifiers

Site IDs must be identifiers already registered in Spatial7. An unregistered site is reported so it can be created deliberately, rather than inventing a new identifier on import.

Create an Academy account to track your progress and resume where you stop.

Skip to Running a bulk import