Map of Errindlev in OruxMaps format
A map built from OpenStreetMap data, ready to download
Customize the map
Open this place's area in the constructor and adjust everything to your needs
Open in constructor →Map passport
What this map contains by default
This is how the map is built as-is — every setting can be changed in the constructor.
.sqlitedb
About OruxMaps
Map of Errindlev in OruxMaps — an export of real OpenStreetMap data for the selected area.
OruxMaps is an offline Android navigation app (hiking, outdoors). We ship a ZIP archive containing the SQLite tiles database (.otrk2.db) and the calibration XML (.otrk2.xml) — both files are required side-by-side on the device. Beta: one map layer, up to 50 000 tiles.
Which layers are in the file
This file for the selected area contains:
- Roads
- Buildings
- Greenery
- Points of interest
Coordinate systems
WGS 84 (EPSG:4326), selectable in the wizard
Units
Meters (projected in the chosen coordinate system)
| Category | GIS |
| File extension | .sqlitedb |
| Tier | Open Beta |
How to use OruxMaps for Errindlev
- OruxMaps (Android) — unpack the archive into the OruxMaps/mapfiles/OSM2CDR/ folder on the device, then open the map list in the app and refresh it: the new map appears among the offline sources.
- A file manager or a USB cable — move the whole unpacked folder over; make sure the .otrk2.db and .otrk2.xml stay together and share the same name.
- DB Browser for SQLite — if in doubt, open the database on a computer and check that the tiles were written.
Programs that open OruxMaps
FAQ: OruxMaps for Errindlev
How to install?
Unpack the ZIP into OruxMaps/mapfiles/OSM2CDR/ on the device.
Why are there two files in the archive?
That is how the format works: the .otrk2.db holds the tiles themselves, and the .otrk2.xml holds the calibration, that is the binding of tiles to coordinates and zoom levels. The app needs both files together, otherwise the map will not open.
How large an area can I take?
In beta mode one layer of up to 50,000 tiles is built. A district or a small town fits comfortably; for a large territory it is better to make several maps covering sections of the route.
How is this different from MBTiles and Locus Map?
The content is similar — ready raster tiles — but each app has its own storage schema. OruxMaps expects the .otrk2.db + .otrk2.xml pair, Locus expects its own .sqlitedb, and MBTiles is a universal container for GIS and the web.
