Stadia Maps

530 posts

Stadia Maps banner
Stadia Maps

Stadia Maps

@StadiaMaps

Location APIs Without Compromise Stop battling legacy pricing, forced telemetry, and black-box billing. Engineered for privacy, scale, and developer sanity.

🌍🌏🌎 Katılım Ekim 2017
42 Takip Edilen537 Takipçiler
Stadia Maps
Stadia Maps@StadiaMaps·
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: stadiamaps.com/blog/why-osm-r…
English
0
0
1
30
Stadia Maps
Stadia Maps@StadiaMaps·
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 stadiamaps.com/news/75-millio…
Stadia Maps tweet media
English
0
0
0
60
Stadia Maps
Stadia Maps@StadiaMaps·
📦 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. stadiamaps.com/news/75-millio…
English
0
0
1
61
Stadia Maps
Stadia Maps@StadiaMaps·
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.
English
1
0
0
61
Stadia Maps
Stadia Maps@StadiaMaps·
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.
English
1
0
0
35
Stadia Maps
Stadia Maps@StadiaMaps·
@andrew_carles Thank you for blurring the addresses. We're not going to pretend this isn't embarrassing. It was a sending error: recipient addresses were in the To field instead of BCC. No other data or user information was affected. We are making process changes so it can't happen again.
English
0
0
0
33