Formats
Import & Export
Supported import and export formats with notes on limits and recommended formats.
Import
Importable File Formats
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.bak | Backup archive with manifest, checksums and selected app content | Restore, merge or selective import | Supported |
| GPX | .gpx | Routes, tracks, waypoints | Outdoor and GPS exchange | Supported |
| KML / KMZ | .kml, .kmz | Placemarks, lines, polygons, GroundOverlays | GIS, Google Earth, raster overlays | Supported |
| GeoJSON / JSON | .geojson, .json | Feature layers with points, lines and areas | Open data, web GIS, developer data | Pro / content-dependent |
| CSV / TSV / TXT | .csv, .tsv, .txt | Tabular POI or measurement data | Lists and structured point data | Pro / content-dependent |
| Mapsforge | .map | Offline vector map | Base maps without mobile coverage | Supported |
| MBTiles | .mbtiles | Tile container | Offline raster or vector maps | Supported |
| GeoPackage | .gpkg | Maps, feature layers or tile containers | GIS data and map packages | Pro / content-dependent |
| 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 | Terrain archive, render theme, POI or suitable layer container | Bundled imports | Content-dependent |
Export
Exportable Formats
.asmaps projects are suited for exchanging individual projects. For broader safekeeping, ArxSilex MapTools can create .asmaps.bak 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.bak | 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 | 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 |
Remote ID
Remote ID reception and export formats
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 |
Offline data
Download sources belong on the offline data page
The format overview explains what can be imported. Concrete hints for suitable download sources for maps, POI, terrain and overlays are kept centrally on the offline data page.
QR data format
QR import, export and sharing
QR codes are a compact exchange format for objects and groups. The specification describes URL structure, Base64URL-encoded JSON, privacy, size limits and validation rules.
Project format
Understand .asmaps and .asmaps.bak
A technical overview explains project files, backups, versioning, privacy and stable parsing rules for integrations.
Backup
App Backup and Restore
A .asmaps.bak can contain selected app areas, such as projects, recovery data, settings, profiles, import batches, POI databases, groups, offline maps, layers, terrain and render themes. 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.
Classification
Important Limitations
GeoPackage remains supported for maps, tile containers and feature layers. GeoPackage DEM is currently not recommended for terrain; use HGT, DEM GeoTIFF, ASC or DTED for elevation features.