Identify the CRS
ProjectedCSTypeGeoKey or GeographicTypeGeoKey is evaluated as an EPSG code. Model type, units, ellipsoid and additional GeoKeys must not contradict the definition.
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 / 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 | 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, 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 |
Vector layers
GeoJSON and ArcGIS/Esri JSON import
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
Coordinate systems
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 |
Coordinates and CRS
From file format to the correct spatial reference
The format lists show what can be imported and exported. The CRS matrix also explains which coordinate reference MapTools expects for input, GeoJSON, ArcGIS JSON, GeoTIFF, WMS, WMTS and map formats.
GeoTIFF and CRS
GeoKeys instead of a short EPSG allowlist
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.
Reproject locally
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.
Reject safely
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.
Import
Geodata import in project context
ArxSilex MapTools supports GeoJSON, ArcGIS/Esri JSON, GPX, KML/KMZ, CSV, Shapefile ZIP, GeoPackage, MBTiles, Mapsforge data, HGT, GeoTIFF and MapTools project files.
Targets, not just files
During import, content is assigned as editable map objects, vector layers, POI data, offline maps, elevation sources or raster overlays.
GeoJSON
Point, MultiPoint, LineString, MultiLineString, Polygon, MultiPolygon and GeometryCollection stay structured. Properties, bounding boxes and available metadata are considered.
ArcGIS/Esri JSON
Feature data with Points, MultiPoints, Polylines and Polygons is processed. spatialReference and wkid are evaluated; known CRS are converted to WGS84.
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 |
Terms
Separate maps, vector layers and raster overlays clearly
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
Vector layers contain individual geometries. They are useful for planning data, boundaries, search areas, routes, tracks and imported project information.
Raster overlays
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.
Show or use
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.
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 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.
Classification
Important Limitations
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.