en_alt:api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en_alt:api [2026/08/10 14:23] – Image heights, wording and section cleanup (review feedback) hajo | en_alt:api [2026/08/10 18:57] (current) – removed hajo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Using the data ====== | ||
| - | |||
| - | Everything OpenTrafficMap collects is meant to be usable for your own analysis, not just for our map. There are two levels at which you can get at it. | ||
| - | |||
| - | ===== Reading your own node ===== | ||
| - | |||
| - | This works today and needs nothing from us beyond credentials. Subscribe to your node on the MQTT broker and you get its raw frames live, which you can record, decode and process however you like. See [[en_alt: | ||
| - | |||
| - | ===== The map and history API ===== | ||
| - | |||
| - | **TODO:** This section is a placeholder. A public API for the collected data — map data, historical signal timings, statistics — has been promised and demonstrated (the Grazer Linuxtage talk showed Grafana dashboards of historical traffic-light data), but it is not documented anywhere yet. | ||
| - | |||
| - | What this page should eventually cover: | ||
| - | |||
| - | * **Overview** — what data is available, and over what time range | ||
| - | * **Endpoints** — the actual URLs | ||
| - | * **Data formats** — GeoJSON, JSON | ||
| - | * **Access and limits** — whether a key is needed, and what rate limits apply | ||
| - | |||
| - | If you know the endpoints, please document them here rather than leaving this page empty. Until then, the MQTT route above is the reliable way to get data. | ||
en_alt/api.1786364584.txt.gz · Last modified: by hajo
