Map Tile Maths

Web Mercator and slippy-map tile maths: tile numbers, bounds, quadkeys, ground resolution, zoom for an extent, tile counts and scale.

payments ON MAINNET (real money) · 8 live endpoints

EndpointPriceWhat it answers
GET /ground-resolution$0.02Metres per pixel, map scale (1:N) and tile width on the ground for a zoom level and latitude.
GET /mercator-project$0.02Convert latitude/longitude to Web Mercator EPSG:3857 metres, or metres back to degrees, with scale distortion.
GET /quadkey$0.02Convert a tile x/y/z to a Bing Maps quadkey, or a quadkey back to x/y/z, with its parent and four children.
GET /tile-bounds$0.02Latitude/longitude and EPSG:3857 metre bounds of a slippy-map tile x/y/z, with its centre and ground size.
GET /tile-count$0.02Number of slippy-map tiles covering a lat/lon box for a zoom range, with a rough storage estimate at your average tile size.
GET /tile-from-coord$0.02Slippy-map tile x/y/z containing a latitude and longitude, plus the pixel position inside the 256 px tile.
GET /zoom-for-extent$0.02Highest map zoom level at which a lat/lon bounding box fits a viewport of given pixel size, with centre and tile span.
GET /zoom-table$0.02Zoom-level ladder 0 to 24: tiles per side, metres per pixel, map scale and typical use, at a chosen latitude.

GET /catalog returns this list as JSON. Activity hub · uptime.


Map projection and tile arithmetic computed locally from the numbers given, per the Web Mercator (EPSG:3857) and slippy-map conventions, provided as is. Web Mercator distorts size and distance away from the equator and is undefined beyond about 85.0511 degrees latitude. Tile servers have their own usage terms: this shelf never fetches tiles. Not survey-grade. Every paid response carries a disclaimer field.