SEPM logo

GIS DATA WORKFLOW

From Smallworld toward modern GIS platforms.

Walk through matching, Auto Mapping, and export steps that help move Smallworld data into PostGIS, with Python as a possible downstream analysis stage — not a built-in X-Translator feature.

Explore X-Translator

The problem

Moving GIS data forward takes more than an export.

Organizations often need to transfer data from an established Smallworld environment into a modern platform while handling attribute mapping, identification, and subsequent analysis.

  • Understanding source and target data models
  • Matching source and target attributes
  • Exporting data to a modern database
  • Preparing exported data for further analysis

Why SEPM

A clearer path from source data to usable results.

SEPM products support structured steps — identification, mapping review, export — rather than a single opaque migration button.

  1. 01

    Connect-ID across systems

    Relate source and target entities where Connect-ID applies to your migration scenario.

  2. 02

    Auto Mapping with review

    Let Auto Mapping propose attribute pairs, then refine mappings yourself before export.

  3. 03

    Export to PostGIS

    Transfer prepared data into PostGIS as the modern storage target for your program.

  4. 04

    Python as downstream analysis

    Use Python scripts on exported data for validation or analytics — as a separate step from the transfer itself.

Demonstration

See the workflow in action.

Follow the process, from the initial data to the final result.

Workflow steps

  1. 01

    Connect the source and target

    Define the Smallworld source and PostGIS target involved in your migration scope.

  2. 02

    Identify corresponding data

    Apply Connect-ID where it fits to align records or features between environments.

  3. 03

    Map attributes

    Use Auto Mapping to suggest mappings, then review and adjust proposed attribute pairs.

  4. 04

    Export the data

    Run the export transfer to load prepared data into PostGIS.

  5. 05

    Continue with analysis

    Optional Python scripts can validate or analyse exported datasets outside the core transfer UI.

Products & technologies

Expected outcome

Legacy data on a modern footing

You gain a documented path from Smallworld through mapping and export into PostGIS — ready for open tooling and optional Python workflows, with human review at the critical steps.

Related workflows

Have a workflow in mind?

Tell us how your GIS data moves today. We'll help you explore a practical way to improve it.

Talk to SEPM