ForHosting KIT · Developer Utilities

Map tile to lat/lon

This map tile to lat lon calculator converts a slippy-map tile address — column X, row Y, and zoom Z — into the geographic latitude and longitude of that tile’s north-west corner under Web Mercator projection.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

The same XYZ numbering powers OpenStreetMap, Leaflet, Mapbox, and countless raster caches: at zoom zero a single tile covers the world; each zoom step doubles the grid on each axis so four children cover what one parent covered. The engine uses the classic closed-form formulas n equals two to the z, longitude equals x over n times three hundred sixty minus one hundred eighty, and latitude equals arctangent of sinh of pi times one minus two y over n, converted to degrees. Known checks include x zero y zero z zero near eighty-five point zero five degrees north and one hundred eighty west, and x one y zero z one at the same latitude with longitude zero. The path is pure finite arithmetic with no network tile fetches, no sampling, and no date-dependent shortcuts. Use it free in the browser for GIS homework, tile-debug sessions, and map-engine tests, or call the API at $0.002 per successful request when you need reproducible NW-corner fixtures in CI, offline pipelines, or teaching demos.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

How do I use this capability?

Complete the fields above and run it on this page. The form highlights anything that needs attention.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/geo/tile-to-latlon

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/geo/tile-to-latlon \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"x":0,"y":0,"z":0}'

const res = await fetch("https://api.kit.forhosting.com/geo/tile-to-latlon", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "x": 0,
    "y": 0,
    "z": 0
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/geo/tile-to-latlon",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "x": 0,
    "y": 0,
    "z": 0
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/geo/tile-to-latlon", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"x":0,"y":0,"z":0}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"x":0,"y":0,"z":0}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/geo/tile-to-latlon", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "x": 0,
  "y": 0,
  "z": 0
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "geo.tile_to_latlon",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

max_zoom 22

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →

Run — free