Location APIs Without Compromise
Stop battling legacy pricing, forced telemetry, and black-box billing. Engineered for privacy, scale, and developer sanity.
8 styles for any use case: Clean, dark, satellite, terrain, Stamen watercolor, and more. All on our free tier. Custom styles too.
https://t.co/0kMkdl2jS2
We shipped a lot since mid-2024 and let the changelog slide. That's on us. It's current now: traffic-influenced routing, Geocoding v2, a 37M km² sat imagery update, new mobile SDKs, and an RSS feed to stay current.
https://t.co/Sofiz9jzvF
weeklyOSM 827 is out. We think it's one of the best places to go for everything happening in the OpenStreetMap world. Data, tools, community, all in one place.
https://t.co/AmMiXA17Eq
Most routing APIs weren't built for cars by accident. It's a design assumption baked into the graph. How we fixed it: https://t.co/ga25bPtkmJ
#routing#maps
https://t.co/ga25bPtkmJ
Kicking off a series on our most popular docs.
First up: Interactive Web Maps. React, Vue, or Vanilla JS, every stack has a quickstart and a recommended library.
Free signup & free tier to get started.
https://t.co/Jy9pBStGlc
For the first time, HDX is releasing disaster-specific OSM datasets with HOT. 440+ downloads during Madagascar and Mozambique disasters, including from within affected countries. Open data, real human impact.
https://t.co/CEiw0DqjsO
Our blog now has an RSS feed 📡
https://t.co/NjevgKTSZF
Recent ships you may have missed:👇
➡️ Traffic-influenced routing (public preview)
➡️ 75M new rooftop-accurate addresses
➡️ 30cm satellite imagery + global freshness refresh
Details: https://t.co/EeTe0VhrSG
Predicting traffic for Tuesday at 8 am by knowing what usually happens Tuesdays at 8 am.
That's predictive routing built on historical profiles. OSM alone can't deliver it.
Here's how:
https://t.co/E34Y8PfqvY
OSM is designed for stable ground truth, not live conditions.
That works for routing engines until it doesn't.
How we layered TomTom traffic on top.
#OpenStreetMap
https://t.co/E34Y8PfqvY
@openstreetmap just opened bidding for State of the Map 2027. Early bidders get first pick of dates. Submissions close 19 July 2026; 2027 venue announced at SotM Paris.
https://t.co/asKTpFh5Xi
#SotM2027#OpenStreetMap
https://t.co/asKTpFh5Xi
Our 2026 #SatelliteImagery update is live. Same tile endpoints, sharper, fresher data. No migration, no API changes.
And no end-user tracking sitting between your app and the tiles.
https://t.co/a2t3D5R7Dj
OSM way IDs just passed 1.5 billion, and the BCP 47 proposal for consistent Latin-script transliteration tags (name:<language>-Latn) closes voting today.
https://t.co/rU4qgGMZkV
#OpenStreetMap#Geospatial
https://t.co/rU4qgGMZkV
deck.gl-raster added a COG comparison slider. Two sources, client-side, no server needed. Good pattern for before/after imagery or dataset comparisons.
https://t.co/CLEja4HD0X
#deckgl#WebGIS
If your data is already structured, your geocoder shouldn't have to re-parse it.
house_number, street, and unit are now first-class fields on the v1 geocoding API. Skip the parsing step. Better matches, faster responses.
#OSM#geocoding
https://t.co/Ool0OWRhJe
30cm satellite imagery, scaled.
37 million km² of high-resolution coverage, plus new country-wide mosaics for Japan, Nigeria, Mexico, the UAE, and Eastern South Africa. No visible tile boundaries, no abrupt seasonal shifts.
#Geospatial#SatelliteImagery
https://t.co/7rfsbBGTlF
📦 Our largest geocoding dataset expansion yet:
- 75M new addresses from OpenAddresses (rooftop-level, not interpolated)
- 25M each in France and the US
- 3M new POIs
- New structured fields on the v1 search APINo user profiling required.
https://t.co/sR2xRs085K
Try Traffic-influenced routing today: two traffic tiers (adaptive and premium), multiple routing profiles, all built on the open road network you already know.
👉 https://t.co/8NodmAkRWl
#OpenStreetMap#Valhalla#Routing
https://t.co/HmegjRvoCQ
Most traffic-influenced routing solutions use the traffic provider's road network, because it's a lot easier. We kept OpenStreetMap and layered TomTom's data on top.
Why? Because our users can directly fix issues in OSM and routes stay perfectly aligned with our basemaps.
Traffic-influenced routing is in public preview!
Skip the enterprise contract negotiations, the surprise costs, and sacrificing your users' privacy.
Try it out today: https://t.co/8NodmAkRWl
#OpenStreetMap#Routing#PrivacyFirst#TrafficData
https://t.co/8NodmAkRWl
Built like we build everything: privacy-first, fair & transparent pricing, and on the flexible routing stack you already use. Instead of one opaque traffic profile, you get two traffic tiers and multiple routing profiles to choose from per request.
Devs deserve better choices.