Local, not cloud
Imported offline data is stored in app-owned storage or at a file location you choose. There is no ArxSilex cloud sync for maps, POI, terrain or projects.
অফলাইন
মোবাইল নেটওয়ার্ক ছাড়াই ব্যবহারের জন্য মানচিত্র, POI, elevation model, raster overlay ও map style প্রস্তুত করুন।
সর্বশেষ আপডেট: ২৭ মে ২০২৬
Data center
Offline use is more than one map file on the device. A useful field view depends on matching maps, POI, elevation models, overlays, profiles and map styles.
Imported offline data is stored in app-owned storage or at a file location you choose. There is no ArxSilex cloud sync for maps, POI, terrain or projects.
The app uses the Android file picker. You select files deliberately; ArxSilex MapTools does not request broad storage access to the whole device.
Smart Import analyzes files by content and suggests a target: base map, layer, raster overlay, POI, terrain, render theme or project.
The offline status shows whether map, POI, elevation data, active profile and map style are available for a position or whether online tiles would still be needed.
Map profiles combine map, active layers, terrain, POI display and map style. This lets you switch between outdoor, field and specialist views.
OpenAndroMaps, OpenStreetMap, your own GIS data, authority maps or commercial data may have their own license terms. The app does not automatically bundle external map data.
Formats
The app treats maps, layers, POI, terrain and themes separately. The same file format can have different targets depending on its content.
| Area | Supported data | Important for use |
|---|---|---|
| Offline base maps | Mapsforge .map, MBTiles .mbtiles, GeoPackage .gpkg | Mapsforge files, for example from OpenAndroMaps, are intended for vector maps. MBTiles and GeoPackage are used as tile containers or map catalog data. GeoTIFF is not a directly renderable base map here. |
| Layers and overlays | GPX, GeoJSON, KML, KMZ, LOC, JSON, GeoPackage, GeoTIFF, Shapefile ZIP | Vector and raster data can be prepared as additional layers. Visual GeoTIFF belongs to raster overlays; DEM GeoTIFF belongs to terrain. |
| POI and offline search | .poi, .db, .sqlite, .geojson, .json, .csv, .tsv, .txt, .zip | Searchable POI must be imported separately. An offline map file alone does not yet provide a complete local POI search. |
| Terrain and elevation features | SRTM .hgt, DEM GeoTIFF .tif/.tiff/.geotiff, ESRI ASCII Grid .asc, DTED .dt0/.dt1/.dt2, terrain ZIP | Used for point elevation, route elevation profiles, hillshade, contours and viewrange. GeoPackage DEM is not intended for these elevation queries. |
| Render themes and map styles | Compatible Mapsforge/Elevate-like theme ZIP files | Map and map style remain separate. External themes must be obtained separately and follow their own license. |
| Projects and exchange data | ArxSilex projects, GPX, KML, KMZ, GeoJSON, CSV, PDF, ZIP | Project and exchange formats can be stored or shared offline. Shared files leave the app only through your action. |
Preparation
Check which region is really needed. Smaller, suitable datasets start faster and save battery and storage.
Import a Mapsforge .map file, MBTiles or a suitable GeoPackage. Then activate it in the map profile.
If you want offline search, import POI data in addition to the map and check categories, size and indexing.
Import HGT, DEM GeoTIFF, ASC or DTED for elevation profiles, hillshade, contours and viewrange in the area.
Use offline status, Layers & Visibility and map profiles before entering an area without coverage.
Limits
Offline data is reliable as long as coverage, format and quality fit. Some features intentionally depend on external data or user action.
The app displays and analyzes geodata, but it does not calculate automatic turn-by-turn routes along roads or trails like a routing service.
Elevation data and POI only work where the imported files actually cover the area.
Google or OSM online maps can still request tiles from external providers. Choose imported maps and data for local use.
Large maps, GeoTIFFs, terrain archives and POI databases need storage and can take time to import or index.
Imported maps, layers, POI, terrain and themes can be removed in the relevant data areas. App data can also be cleared through Android.
ArxSilex MapTools
Import/export describes exchange formats in more detail. Permissions and privacy explain when files, location, online maps or third parties matter.