Importing Layers
Mapit GIS can import feature data from several standard geospatial file formats into your active project. Imported data is stored as a new GeoPackage layer within the current project.
- Android
- iOS
Supported Formats
| Format | Extension | Notes |
|---|---|---|
| GeoJSON | .geojson | Full geometry and attribute support |
| ArcJSON | .json | Esri JSON format |
| Shapefile | .zip | Must be a ZIP archive containing at least .shp, .shx, and .dbf files |
| CSV | .csv | Requires coordinate columns; the app auto-detects latitude/longitude fields |
| KML | .kml | Google Earth format - points, lines, and polygons |
Starting an Import
- Open the Layers screen from the main menu or the map menu.
- Tap the + button (floating action button).
- A bottom sheet appears with options including Create New Layer and Import Layer.
- Tap Import Layer.
- Choose an import source:
| Source | Description |
|---|---|
| Device | Opens the Android file picker to select a file from local storage |
| Dropbox | Browse and download layer files from your Dropbox /Apps/Mapit GIS/ folder (see Export to Dropbox) |
The Dropbox option only appears if your Dropbox account is connected in Settings → Remote Connections → Dropbox.
Import Process
Once a file is selected, the import runs in the background with a progress dialog showing three phases:
- Reading file - the file is parsed and features are extracted
- Importing features - features are written to the GeoPackage database in batches
- Building index - a spatial index is created for the new layer
The progress dialog displays the number of features imported so far.
How Features Are Imported
- A new layer is created in the current project, named after the source file.
- The geometry type is determined from the source data (Point, LineString, Polygon, or their Multi equivalents).
- Attributes from the source file become columns in the new layer's feature table.
- If the source data uses a coordinate reference system other than WGS 84, geometry is automatically transformed to match the project's CRS.
- Features are inserted in batches of 128 for performance.
Importing into an Existing Layer
If you want to add features to an existing layer rather than creating a new one:
- The geometry type of the imported data must match the target layer.
- Attribute columns that exist in both the source and target are mapped automatically.
- Columns present in the source but not in the target are ignored.
If the geometry type of the import file does not match the target layer (for example, importing polygons into a point layer), incompatible features are skipped.
Validation and Error Handling
| Situation | Behaviour |
|---|---|
| Unsupported file format | Import is rejected with an error message |
| Empty file or no features found | Import completes with zero features |
| Mixed geometry types in source | Features are normalised to the dominant geometry type |
| Corrupt or malformed file | Import fails with an error message |
Feature Limits
On the Free tier, layers have a maximum feature count. If the source file contains more features than the limit allows, the import is truncated and a message indicates how many features were imported out of the total.
On Pro and Pro+ tiers, there are no feature limits.
For large imports (tens of thousands of features), GeoJSON and Shapefile formats perform best. KML is suitable for smaller datasets.
When importing Shapefiles, ensure all component files (.shp, .shx, .dbf, and optionally .prj) are inside a single ZIP archive.
Layer import requires the Import/Export entitlement, available on Pro and Pro+ tiers.
Supported Formats
| Format | Extension | Notes |
|---|---|---|
| GeoJSON | .geojson | Full geometry and attribute support |
| ArcJSON | .json | Esri JSON format |
| Shapefile | .zip | Must be a ZIP archive containing at least .shp, .shx, and .dbf files |
| CSV | .csv | Requires coordinate columns; the app auto-detects latitude/longitude fields |
| KML | .kml | Google Earth format - points, lines, and polygons |
Starting an Import
- Open the Layers screen from the main menu.
- Tap the + button.
- Tap Import Layer.
- The iOS file picker opens, allowing you to select a file from local storage, iCloud Drive, or other configured file providers.
The import process reads the file, creates a new layer in the current project, and builds a spatial index.
Dropbox import is not yet available on iOS (on the roadmap). Use the iOS Files app to access files from cloud storage providers instead.
Layer import requires the Import/Export entitlement, available on Pro and Pro+ tiers.