These examples, sourced from community forums, illustrate how adjusting the tile size projection is critical for readability on high-resolution screens.
The most common frustration with OruxMaps is that updates to the application often overwrite the default mapfiles/onlinemapsources.xml file, deleting user-added maps.
Let’s pop the hood.
Most modern apps hardcode their map sources. You get Google Maps, OpenStreetMap, maybe Bing—and you’re done. Oruxmaps, born in an era of limited storage and offline-first ethos (creator Jose Manuel Orux is a paraglider and mountain runner), took a different path:
What are you planning to navigate?
This flexibility cuts both ways. A malformed XML—a missing slash, a duplicate UID—will silently fail. No error message. Oruxmaps will just show a blank grid. Debugging means reading logcats or trial-and-error editing.
[Insert link to your XML file – Google Drive, Dropbox, or a pasted snippet] Oruxmaps Online Map Sources.xml
I can provide the exact XML code block ready for you to copy and paste. Share public link
: The endpoint for tile requests, typically wrapped in a section to handle special characters like & . It uses variables to dynamically fetch tiles: $x , $y : Tile coordinates. $z : Zoom level. Most modern apps hardcode their map sources
Every map source inside the XML file is wrapped in an tag. To add a custom map, you must understand the basic structure.