maps.mxd.codes

Self-hosted map tile server for Colota

Map tile server for the Colota GPS tracking app. Runs tileserver-gl on a VPS with a self-hosted planet .mbtiles file, plus a global terrain DEM cache for hillshade rendering.

Styles

https://maps.mxd.codes/styles/bright/style.json https://maps.mxd.codes/styles/dark/style.json

Vector-only styles. Use the /terrain/ endpoint below as a raster-dem source on the client side if you want hillshade.

Terrain / Hillshade Tiles

https://maps.mxd.codes/terrain/{z}/{x}/{y}.png

Terrarium-encoded raster DEM tiles, suitable for use as a raster-dem source with the MapLibre hillshade layer (or any client expecting Mapzen/Tilezen Terrarium encoding). Served for z0–z15. Low zooms are pre-seeded worldwide; anything above that is fetched on demand from the AWS-hosted Mapzen Terrain Tiles dataset and cached locally on first request.

Details

Planet .mbtiles sourced from OpenFreeMap, updated weekly
OSM edits may take a few days to appear
Terrain tiles served up to z15 — the underlying DEM (mostly ~30 m SRTM/GMTED/ETOPO) holds no real detail much past z13
Tile requests are rate-limited to 100 per second per IP; anything above that is answered with HTTP 429 and should be retried more slowly
Tiles are cached server-side after the first request

Terms of Use

Personal use is welcome. You can view maps, pan, zoom, and use offline map packs through the Colota app as intended.

We do not give guarantees for availability and reserve the right to implement changes without notice. If you have a larger number of requests to make, please consider setting up your own instance. It is as simple as downloading an .mbtiles file and starting tileserver-gl.

Bulk-downloading tiles, automated tile fetching outside of normal map usage, and scraping are not allowed.

Please send a User-Agent naming your app and giving a way to reach you, for example MyApp/1.2 (+https://example.com/myapp; you@example.com) — either half alone is fine. Nothing is logged in normal operation, so this is not tracking. It is what makes it possible to tell a well-behaved client apart from an abusive one if a problem ever forces logging on, and to get in touch with you instead of simply blocking you.

Privacy Policy

Last updated: August 19, 2026

When your device fetches tiles, the server sees your IP address as part of normal HTTP traffic. Tile requests are not logged, apart from a short-lived record of requests rejected by the rate limit. Full logging may be turned on temporarily to investigate abuse or issues, then turned off again.

No cookies. No analytics. No tracking. Tile requests carry no user identifiers.

Questions: GitHub or colota@mxd.codes.

Attribution

Map data

Geographic data (roads, places, water, land use, labels, boundaries, …) is © OpenStreetMap contributors, available under the Open Database License (ODbL).

Vector tile schema and distribution

Vector tile schema and styles are based on OpenMapTiles (CC-BY 4.0). Planet .mbtiles distribution courtesy of OpenFreeMap.

Terrain DEM

Terrarium-encoded DEM tiles courtesy of Mapzen Terrain Tiles, hosted via the AWS Open Data program. The Mapzen Terrain Tiles dataset is a composite of the following sources:

ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and funded under National Science Foundation awards 1043681, 1559691, and 1542736.
Canada terrain data contains information licensed under the Open Government Licence – Canada.
Europe terrain data produced using Copernicus data and information funded by the European Union – EU-DEM layers.
Global ETOPO1 terrain data: U.S. National Oceanic and Atmospheric Administration.
Mexico terrain data source: INEGI, Continental relief, 2016.
United States 3DEP (formerly NED), and global GMTED2010 and SRTM terrain data courtesy of the U.S. Geological Survey.