Import Data

Topologis imports data through the Data tab in the project editor.

Every import becomes an import job, so you can track progress, handle required configuration, and review failures without leaving the project.

Supported data sources

Topologis exposes three import entry points in the editor:

• File upload
• URL import
• Google Sheets

The upload control currently accepts GeoJSON, Shapefile, GeoPackage and CSV files. The URL import dialog is explicitly described as supporting GeoJSON, Shapefile, GeoPackage, and CSV. Google Sheets imports use a separate authenticated flow.

If you are looking for the quickest first-run path, start with a file upload. For a full beginner walkthrough, see Create Your First Map.

Upload a file

In the Data tab, use Upload File or drag a file into the project.

Topologis uploads the file first and then creates an import job for the project. The upload helper currently enforces a maximum file size of 1 GB.

For many files, this is the simplest way to get data into the project. It is local, direct, and does not depend on a remote endpoint or a connected Google account.

Import from a URL

If your data is hosted remotely, use From URL.

This flow lets you:

• Enter a data URL
• Choose GET or POST
• Add request headers
• Provide a request body for POST
• Test the connection before creating the import job

This is useful when the data already lives behind a stable endpoint and you want an import source that can also be scheduled later.

Import from Google Sheets

Google Sheets import is a guided flow with authentication, sheet selection, preview, and recipe configuration.

The flow works in three stages:

1. Authenticate with Google or reuse an existing refresh token.
2. Pick a spreadsheet and worksheet tab.
3. Create a recipe, preview the worksheet data, and confirm the import.

This path is useful when non-technical collaborators maintain tabular data in Sheets and you want that sheet to become map data inside a project.

Preview and configure your data

Not every import finishes in one step.

CSV and Shapefile imports can move into an Action required state before they are fully imported. When that happens, the import job stays visible in the sidebar and opens a configuration flow you need to confirm before processing can continue.

This is how Topologis handles cases where the data needs more structure before it can become usable layers. Instead of guessing, it pauses and asks you to confirm the recipe.

Map columns and geometry

The import configuration screens are where raw files become usable map data.

For CSV imports, the configuration flow includes:

• Parsing settings such as delimiter, quote, escape, encoding, newline, comments, and header handling
• Column preview and column inclusion
• Geometry mapping with None, XY Columns, or WKT Column
• Source CRS selection
• Import mode choices for geometry import, data enrichment, or time-series creation

When the import mode is data or time-series, you also map source keys to target keys so Topologis knows how to join incoming rows to an existing layer.

Google Sheets uses a similar preview-and-recipe model, but its current import modes are Import Geometries and Enrich Existing Layer.

Save and reuse import recipes

CSV and Shapefile configuration flows both support saved recipes.

You can save a recipe after you have configured it, then load it again later instead of rebuilding the same parsing or field-selection setup from scratch. These saved recipes are part of the workspace-level import library and are especially useful for repeat imports with a consistent schema.

Create refresh schedules

Topologis can schedule some imports to run again automatically.

Scheduling is available only for successfully completed import jobs created from:

• A URL
• Google Sheets

From the schedule dialog, you select a completed import job, choose an interval in minutes, and optionally enable layer overwrite behavior. This makes refresh schedules a continuation of an existing import job, not a separate import definition.

Troubleshooting imports

The import jobs list is the main place to understand what happened during an import.

Jobs can appear as:

• Waiting to start
• Processing
• Action required
• Completed
• Failed
• Canceled

If a job is in Action required, open it and complete the configuration it is asking for. If a job failed, review the error summary in the job details before retrying. If you are importing from a URL, use the connection test in the URL dialog before creating the job. If the problem is with the uploaded file itself, re-exporting the source data into one of the primary formats used by the importer can be the cleanest fix.