The Oruxmaps onlinemapsources.xml file functions as a configuration engine, allowing users to integrate custom online map layers via specific XML tags including url, projection, and server subdomains. Custom maps should be placed in oruxmaps/mapfiles/customonlinemaps/
To add new map sources, you must place the XML file in a specific directory on your device: oruxmaps/mapfiles/customonlinemaps/ .
For servers requiring custom HTTP headers (e.g., Referer ), Oruxmaps does not support header injection via XML alone. You would need to use a proxy or switch to a different map source. Oruxmaps Online Map Sources.xml
: 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.
Wrong URL pattern. Oruxmaps uses zoom , x , y . Some servers expect z , row , or col . Also, check zoom constraints – you may be zoomed out beyond the server’s min zoom. Fix: Compare your URL with working examples from the same tile service. Try the URL in a web browser first. The Oruxmaps onlinemapsources
Worse: Map servers change their URLs. Your lovingly curated XML file from 2019? Dead. All those $x requests now return 404 or a “forbidden” image. You have to manually hunt down new endpoints—a cartographic archeology project.
Sometimes you need a specific tile server not found in community packs. For instance, a local government’s orthophoto service or a private WMS server. You would need to use a proxy or
The file uses a standard XML format where each map source is wrapped in an tag. Key parameters within these tags include: : A unique identification number for each map.