Import GPX
- Data → Data Center → Import file
- Select the GPX file, review the detected waypoints, routes and tracks, then confirm.
- You can also open or share the file with MapTools from Android.
Formats
Supported import and export formats with notes on limits and recommended formats.
Files and services
File formats and map services have different destinations. These links lead to the matching step-by-step section in the Quickstart.
WMS is an online map service, not an import file. Setup requires the provider URL and, where applicable, credentials or licence information.
An ASMAPS archive holds one editable MapTools project and can include photos, PDFs and audio notes. MapTools accepts .asmaps and .asmaps.zip files up to 1 GiB for import.
Open Data → Data Center → Import file, select the archive and confirm the destination.
The extracted project can take up more space than the archive. MapTools checks for free space before unpacking and importing. If there is too little space, free up storage and retry. You can cancel until MapTools starts adding the contents to the destination.
If that step fails, MapTools can restore the previous state of the destination project. TIFF, ordinary ZIP and MAP files each follow their own import rules.
Import
ArxSilex MapTools analyzes files by extension and content. Depending on the file, several import targets may be offered.
| Format | Extension | Detected content | Typical use | Status |
|---|---|---|---|---|
| .asmaps project | .asmaps | App project with objects and metadata | Backup, restore, sharing | Supported |
| MapTools app backup | .asmaps.backup | Backup archive with manifest, checksums and selected app content | Restore, merge or selective import | Supported |
| GPX | .gpx | Routes, tracks, waypoints · Sensor data | Outdoor and GPS exchange | Supported |
| FIT | .fit | GPS track and sensor data | Recorded outdoor activity | Supported |
| KML / KMZ | .kml, .kmz | Placemarks, lines, polygons, GroundOverlays | GIS, Google Earth, raster overlays | Supported |
| GeoJSON / ArcGIS JSON | .geojson, .json | Vector layers with points, lines, polygons, multi-geometries, GeometryCollections and Esri features | Open data, web GIS, GIS exchange, developer data | Pro / content- and CRS-dependent |
| CSV / TSV / TXT | .csv, .tsv, .txt | Tabular POI or measurement data | Lists and structured point data | Yes (Free and Pro) / depends on content |
| Mapsforge | .map | Offline vector map | Base maps without mobile coverage | Supported |
| MBTiles | .mbtiles | Tile container | Offline raster maps; vector MBTiles (MVT/PBF) are not rendered | Supported |
| GeoPackage | .gpkg | Maps, vector layers or tile containers | GIS data and map packages | Pro / content-dependent |
| Elevation data / terrain | .hgt, .tif, .tiff, .geotiff, .asc, .dt0, .dt1, .dt2 | Elevation data from HGT, DEM GeoTIFF, ASC or DTED | Elevation profile, point elevation, hillshade, contours | Supported / Pro depending on format |
| Raster overlay | .tif, .tiff, .geotiff, .kml, .kmz | Georeferenced images or GroundOverlays | Aerial imagery, special maps, field overlays | Pro / content-dependent |
| POI database | .poi, .db, .sqlite | Searchable POI data | Offline search | Content-dependent |
| LOC | .loc | Waypoints | Geocaching and point lists | Supported |
| ZIP package | .zip | Elevation data archive, map style, POI or suitable vector layer container | Bundled imports | Content-dependent |
FIT stores recorded activities and sensor measurements. MapTools imports one outdoor activity with at least two usable GPS positions per file. Courses, training plans, multisport files and activities without a GPS track are not supported.
GPX exchanges waypoints, routes and tracks, without a background map. Recognized Garmin extensions can also carry heart rate, cadence, power and temperature. These values must be present in the file.
Choose the FIT or GPX file in Import, review the detected track and destination project, and confirm the import. Select the saved track, open its summary and expand Sport & sensor data. This section appears only when supported activity data is available.
TCX import and FIT export are not supported. Live heart rate is available locally over Bluetooth LE or ANT+.
Import
ArxSilex MapTools supports GeoJSON, ArcGIS/Esri JSON, GPX, KML/KMZ, CSV, Shapefile ZIP, GeoPackage, MBTiles, Mapsforge data, HGT, GeoTIFF and MapTools project files.
During import, content is assigned as editable map objects, vector layers, POI data, offline maps, elevation sources or raster overlays.
Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon and GeometryCollection stay structured. Properties, bounding boxes and available metadata are considered.
Feature data with Points, MultiPoints, Polylines and Polygons is processed. spatialReference and wkid are evaluated; known CRS are converted to WGS84.
Terms
ArxSilex MapTools uses these terms deliberately. They make it clear whether a file is used as a base map, editable geometry, image overlay or elevation data source.
| Term | Short definition | Examples |
|---|---|---|
| Maps | Base maps used as the main working view. | OpenStreetMap, OpenAndroMaps, offline .map, MBTiles as a base map |
| Vector layers | Additional object, line or polygon data above the map. The content consists of points, lines or areas and can often be displayed or evaluated individually. | GPX, KML, GeoJSON, Shapes, KML polygons, GeoJSON areas, GPX tracks as overlays |
| Raster overlays | Georeferenced image or tile data above the map. They are placed as a finished image surface and are not interpreted as individual objects. | GeoTIFF, MBTiles, image maps, aerial imagery, scanned maps, georeferenced plans |
| Elevation data / terrain | Data sources for elevation values and terrain analysis. They are not a visible map in the narrow sense, but provide height information. | HGT, DEM GeoTIFF, ASC, DTED |
| Map style | Rendering rules for vector maps. The style defines colors, symbols, paths, POIs, contour lines and other map elements. | OpenAndroMaps render theme, Elevate Theme |
| POI data | Search and display data for places and points of interest. | OpenAndroMaps .poi, custom POI files |
Vector layers contain individual geometries. They are useful for planning data, boundaries, search areas, routes, tracks and imported project information.
Raster overlays are finished image surfaces above the map. They are useful for aerial imagery, historical maps, scans or special map views. Opacity is often adjusted so the base map remains visible below.
Maps, vector layers and raster overlays can be shown on the map. Elevation data is usually used by tools: point elevation, elevation profile, hillshade, contour lines and viewrange.
Vector layers
ArxSilex MapTools imports GeoJSON and ArcGIS/Esri JSON files as vector layers. .geojson is recommended; .json is recognized by content inspection.
| Format | Support |
|---|---|
| GeoJSON | Points, lines, polygons, multi-geometries and GeometryCollections |
| ArcGIS/Esri JSON | Points, MultiPoints, Polylines, Polygons/Rings and FeatureSets |
| Properties | Attributes/properties are preserved |
| Styles | Simple GeoJSON styles such as line color, fill color, opacity and line width are preserved |
| Polygon inner rings | Supported, for example areas with holes |
| Elevation / Z values | Read when present |
| File extensions | .geojson recommended; .json is recognized by content inspection |
CRS / EPSG
Unsupported or unknown coordinate systems are not placed incorrectly; they are safely rejected during import.
| CRS / EPSG | Meaning |
|---|---|
| EPSG:4326 / 4269 | WGS84 / geographic coordinates |
| EPSG:3857 / 102100 / 102113 | Web Mercator |
| EPSG:25832 / 25833 | ETRS89 / UTM zones 32N and 33N |
| EPSG:32632 / 32633 | WGS84 / UTM zones 32N and 33N |
| EPSG:3035 | LAEA Europe |
| EPSG:31466-31469 | DHDN / Gauss-Krueger zones 2 to 5 |
GeoTIFF and CRS
MapTools uses the same central CRS engine for GeoTIFF, coordinates and online maps. The deciding factor is whether the file consistently identifies a registered, transformable and raster-enabled CRS.
ProjectedCSTypeGeoKey or GeographicTypeGeoKey is evaluated as an EPSG code. Model type, units, ellipsoid and additional GeoKeys must not contradict the definition.
Geographic and projected rasters are transformed through the central engine into the WGS 84 map view. This supports many more curated CRS than the former small list.
Unknown CRS, missing required grids, contradictory metadata or non-raster definitions are rejected instead of placing an image in the wrong location.
Even with a matching CRS, tie points or transformation matrix, pixel interpretation, bands, bit depth, compression and raster dimensions must be supported. A GeoTIFF without unambiguous CRS metadata is not a reliable basis for positionally accurate rendering.
Current functionality
ZIP archives are checked as a list of data sets: vector, raster, POI, terrain and project data remain separately selectable. Multiple GPX, KML, KMZ, GeoJSON and LOC files can become individual layers; mixed imports are prepared and rolled back without visible partial imports if an error or cancellation occurs.
Import
Directly selected GeoPackages now use the correct container key and reliably select their feature tables; an empty layer selection no longer rolls back the complete import.
Detailed guides
Queued, running, completed, failed and cancelled imports are shown as separate tasks.
The × hides up to the three most recent visible rows but does not stop work. A new task makes the panel visible again; use the task's Cancel action when available.
Up to two non-conflicting tasks can run in parallel; tasks using the same resource wait. Duplicate submissions are rejected. Wait for the final status and inspect recovery notices after interruption.
Classification
GeoPackage remains supported for maps, tile containers and vector layers. GeoPackage DEM is currently not recommended for terrain; use HGT, DEM GeoTIFF, ASC or DTED for elevation features.
Export
.asmaps projects are suited for exchanging individual projects. For broader safekeeping, ArxSilex MapTools can create .asmaps.backup app backups, optionally encrypt them with a password and restore them later as a new project, replacement, merge or selective import.
| Format | Extension | Content | Use |
|---|---|---|---|
| MapTools app backup | .asmaps.backup | Selected app content, manifest, checksums and optionally encrypted data | Complete app backup and restore |
| .asmaps project | .asmaps | App project with objects and metadata | Complete backup and exchange |
| GPX | .gpx | Routes, tracks and waypoints · Sensor data | GPS devices and outdoor apps |
| KML / KMZ | .kml, .kmz | Placemarks, lines, areas and possibly overlays | Google Earth, GIS and map tools |
| GeoJSON / JSON | .geojson, .json | Geometries and properties | Web GIS, development and archiving |
| CSV | .csv | Tabular data | Spreadsheet analysis |
| ZIP | .zip | Bundled exchange or backup file | Multi-format export and backups |
| Reports or summaries | Documentation | ||
| Remote ID | .kml, .geojson, .csv | Received Remote ID history with positions and optional operator fields | Documentation and analysis |
Heart rate is stored locally without a cloud or manufacturer account. You can explicitly include pulse values from saved tracks in supported exports or backups. Without such a backup, these measurements cannot be restored after uninstalling the app or losing the device. Pulse values are excluded by default. Include them only if you want recipients of this file to see them. GPX, ASMAPS, JSON and ZIP support this option; original activity files and sensor pairing remain excluded. Pulse values from saved tracks are optional and excluded by default. Unassigned pulse recordings, sensor pairing and original import files remain excluded. Normalized project data and other supported sports measurements remain included.
Filenames
Suggested filenames begin with the date, followed by the type and the name of the object or project. Sharing uses the same order; content and file format are unchanged.
GIS / GPS
The provider alone does not determine compatibility. File format, content, CRS, licence and its role as map, layer, overlay, POI or elevation source all matter.
.shp + .dbf + .shx
XML / ZIP
QR
TXT / PDF
XYZ, TMS, WMTS, WMS, OGC API Features and WFS are configured through HTTPS endpoints. Service metadata, layer selection, licences and credentials therefore remain separate from imported offline files.
InfoTap
The point report combines information from the active map slot: coordinates and terrain, local Mapsforge data, WMS/WMTS FeatureInfo and OGC API Features or WFS hits when the source provides them.
TXT
TXT
TXT
Before export, MapTools sanitises control and bidirectional characters, limits oversized content and redacts recognisable passwords, tokens, API keys, cookies, Authorization values and sensitive URL parameters. Still review reports before sharing because unknown provider-specific field names cannot always be identified.

Remote ID
Remote ID data is read from public broadcasts and processed locally. The optional history can be exported as map, GIS or spreadsheet data.
| Format / source | Supported content | Typical use |
|---|---|---|
| Open Drone ID / ASTM F3411 | Basic ID, Location Vector, System, Operator ID, Self ID, Authentication, Message Pack | Live display of received Direct Remote ID broadcasts |
| ASD-STAN / EU Direct Remote ID | EU profile, classification, operator and system data when present in the broadcast | EU-compatible Remote ID evaluation |
| BLE, Wi-Fi NAN, Wi-Fi Beacon | Service data, manufacturer data, vendor-specific information elements and valid Remote ID payloads | Reception through the Android device's available radio paths |
| KML (.kml) | Drone points, tracks and optional operator/pilot positions | Viewing in map tools and Google Earth |
| GeoJSON (.geojson) | FeatureCollection with drone points, LineString tracks and optional operator features | GIS analysis and further processing |
| CSV (.csv) | Schema version, timestamp, drone ID, coordinates, altitude, height, speed, heading, status, source, protocol, profile, RSSI, flags, Self ID, classification, auth hash and optional operator fields | Spreadsheets, field documentation and analysis |
Working model
The three paths serve different purposes: exchange formats, a portable project or restoration of app areas.
GPX, KML/KMZ, GeoJSON and other formats exchange supported object types with other programs.
.asmaps preserves project structure, metadata and supported MapTools objects for project-based exchange.
.asmaps.backup can store several app areas, optionally password-protected, and provides controlled restore options.
The assistant blocks empty sources and shows warnings about unsupported properties before writing.
MapTools validates file type, content, sizes and names. You should still verify the origin and rights of imported or exported data.
Import data
Depending on the export selection, photos, PDFs and audio notes belonging to the project or selected objects are embedded in the project file.
Images, PDFs and audio notes are embedded in the .asmaps project file only when that option is selected, and are assigned back to the matching objects or project during import.
Complete MapTools projects with app-specific objects, collections and metadata.
Images, PDFs and audio notes are embedded in the .asmaps project file only when that option is selected, and are assigned back to the matching objects or project during import.
Attachments can contain private images, documents, voices and location metadata. Include them only deliberately.
Attachments are managed locally in private app storage. Camera and microphone operate only during a capture explicitly started by the user; export and sharing require a deliberate selection.
MapTools checks the file first and then shows suitable contents and import targets. Nothing is imported without confirmation.
Android filters by reported file type. The file extension and content are checked again before import.
Attachments can contain private images, documents, voices and location metadata. Include them only deliberately.
Backup
A .asmaps.backup can contain selected app areas, such as projects, recovery data, settings, profiles, import batches, POI databases, groups, offline maps, layers, terrain and map styles. During restore you decide whether the content is imported as a new project, replacement, merge or selective import. For conflicts, existing data can be skipped, copied or replaced.