[{"data":1,"prerenderedAt":106},["ShallowReactive",2],{"blog-\u002Fblog\u002Fwe-updated-our-changelog\u002F":3,"related-blog-\u002Fblog\u002Fwe-updated-our-changelog\u002F":68},{"id":4,"title":5,"abstract":6,"author":7,"body":14,"description":52,"excerpt":6,"extension":53,"head":6,"image":54,"imageAlt":6,"keywords":55,"meta":59,"modified":6,"navigation":60,"path":61,"proficiencyLevel":6,"published":62,"rawbody":63,"schemaOrg":6,"schemaType":6,"section":6,"seo":64,"stem":66,"__hash__":67},"blog\u002Fblog\u002Fwe-updated-our-changelog.md","We Updated Our Changelog (Yes, Really)",null,{"name":8,"slug":9,"jobTitle":10,"bio":11,"sameAs":12},"Luke Seelenbinder","luke-seelenbinder","Founder & CEO","Luke is co-founder of Stadia Maps and sets the company's product direction and growth strategy. His work also includes business development, partnerships, and making sure Stadia Maps stays focused on what developers and companies need from location APIs.",[13],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Flukeseelenbinder\u002F",{"type":15,"value":16,"toc":48},"minimark",[17,21,25,34,37,40],[18,19,5],"h1",{"id":20},"we-updated-our-changelog-yes-really",[22,23,24],"p",{},"We've shipped a lot since mid-2024. Traffic-influenced routing. Geocoding v2 and data updates, including hundreds of millions of new POIs and addresses. A 2026 satellite imagery update covering 37 million km². New SDKs, autocomplete UI components for SwiftUI and Jetpack Compose, and more.",[22,26,27,28,33],{},"None of it made it into our ",[29,30,32],"a",{"href":31},"\u002Fchangelog\u002F","changelog",".",[22,35,36],{},"That's on us.",[22,38,39],{},"We got heads-down building and let updating the changelog slide, which defeats the point of having one. We've gone back and filled in everything since June 2024. Go take a look.",[22,41,42,43,47],{},"Moving forward, we're committing to keeping it current. If you want updates without checking back manually, our changelog now has a long-overdue ",[29,44,46],{"href":45},"\u002Fchangelog\u002Frss.xml","RSS feed",", too.",{"title":49,"searchDepth":50,"depth":50,"links":51},"",4,[],"Catch up on everything Stadia Maps shipped since mid-2024 — traffic-influenced routing, Geocoding v2 with hundreds of millions of new POIs, a 37M km² satellite imagery update, and new mobile SDKs. Plus, subscribe via RSS to stay current.","md","\u002Fimages\u002Fcontent\u002Fchangelog-update-og.png",[56,57,58],"Changelog","Product Updates","RSS",{},true,"\u002Fblog\u002Fwe-updated-our-changelog","2026-06-02","---\ndescription: >-\n  Catch up on everything Stadia Maps shipped since mid-2024 — traffic-influenced\n  routing, Geocoding v2 with hundreds of millions of new POIs, a 37M km²\n  satellite imagery update, and new mobile SDKs. Plus, subscribe via RSS to stay\n  current.\nseo:\n  title: \"Stadia Maps Product Updates: Maps, Routing, Navigation, Geocoding, and more\"\nexcerpt: >-\n  We let our changelog fall behind while shipping. It's caught up now, with\n  everything since June 2024 and a long-overdue RSS feed.\npublished: \"2026-06-02\"\nimage: \u002Fimages\u002Fcontent\u002Fchangelog-update-og.png\nkeywords:\n  - Changelog\n  - Product Updates\n  - RSS\nauthor:\n  name: \"Luke Seelenbinder\"\n  slug: \"luke-seelenbinder\"\n  jobTitle: \"Founder & CEO\"\n  bio: \"Luke is co-founder of Stadia Maps and sets the company's product direction and growth strategy. His work also includes business development, partnerships, and making sure Stadia Maps stays focused on what developers and companies need from location APIs.\"\n  sameAs:\n    - \"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Flukeseelenbinder\u002F\"\n---\n\n# We Updated Our Changelog (Yes, Really)\n\nWe've shipped a lot since mid-2024. Traffic-influenced routing. Geocoding v2 and data updates, including hundreds of millions of new POIs and addresses. A 2026 satellite imagery update covering 37 million km². New SDKs, autocomplete UI components for SwiftUI and Jetpack Compose, and more.\n\nNone of it made it into our [changelog](\u002Fchangelog\u002F).\n\nThat's on us.\n\nWe got heads-down building and let updating the changelog slide, which defeats the point of having one. We've gone back and filled in everything since June 2024. Go take a look.\n\nMoving forward, we're committing to keeping it current. If you want updates without checking back manually, our changelog now has a long-overdue [RSS feed](\u002Fchangelog\u002Frss.xml), too.\n",{"title":65,"description":52},"Stadia Maps Product Updates: Maps, Routing, Navigation, Geocoding, and more","blog\u002Fwe-updated-our-changelog","ZYKfP0EnXroxiE-gigl4FBOAigvdW0wpvNKk1d2UdBw",[69,83,94],{"title":70,"description":71,"path":72,"published":73,"keywords":74,"rawbody":82},"Beyond the Car: Routing for the Other 90% of Transport","Car-first routing APIs fail trucks, e-bikes, and LSVs. See how Stadia Maps uses Valhalla and OpenStreetMap to deliver modal-specific routing that respects each vehicle's physical and legal constraints.","\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets","2026-05-26",[75,76,77,78,79,80,81],"Routing","Navigation","Valhalla","OpenStreetMap","Fleet Routing","Micromobility","Low-Speed Vehicles","---\ndescription: >-\n  Car-first routing APIs fail trucks, e-bikes, and LSVs. See how Stadia Maps\n  uses Valhalla and OpenStreetMap to deliver modal-specific routing that\n  respects each vehicle's physical and legal constraints.\npublished: \"2026-05-26\"\nimage: \u002Fimages\u002Fcontent\u002Fspecialized-routing-og.png\nimageAlt: \"Beyond the Car: Routing for the Other 90% of Transport — Stadia Maps\"\nsection: \"Routing\"\nkeywords:\n  - Routing\n  - Navigation\n  - Valhalla\n  - OpenStreetMap\n  - Fleet Routing\n  - Micromobility\n  - Low-Speed Vehicles\nauthor:\n  name: \"Ian Wagner\"\n  slug: \"ian-wagner\"\n  jobTitle: \"Founder & President \u002F COO\"\n  bio: \"Ian is co-founder of Stadia Maps and leads engineering and operations. He works on routing, navigation, and the technical foundations that keep customer applications reliable at scale.\"\n  twitterCreator: \"@ianthetechie\"\n  sameAs:\n    - \"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fian-w-wagner\u002F\"\n---\n\n# Beyond the Car: Routing for the Other 90% of Transport\n\n> Standard \"car-first\" routing APIs often fail to account for the unique legal and physical constraints of specialized fleets. Stadia Maps bridges this gap by leveraging the Valhalla routing engine and OpenStreetMap data to provide granular, modal-specific routing for everything from 10-ton trucks and e-bikes to low-speed vehicles (LSVs).\n\n## The Problem\n\nStandard consumer mapping apps are excellent at getting a passenger car from point A to point B, but the \"car-first\" default is a significant limitation for professional use cases. The moment a business needs to route a 10-ton truck, a delivery e-bike, or a neighborhood electric vehicle, most [Directions APIs](\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F) fall apart. Such platforms often lack the flexibility required for specialized fleets and fail to account for the unique legal and physical constraints these vehicles face.\n\n## The Logic Gap\n\nGeneric routing engines often treat a 10-ton semi-truck the same as an e-bike, leading to dangerous route suggestions or illegal maneuvers. Developers shouldn't have to build custom logic layers just to ensure a vehicle stays on a legal road.\n\nStadia Maps solves this by processing [OpenStreetMap (OSM) data](https:\u002F\u002Fwiki.openstreetmap.org\u002Fwiki\u002FRouting_profiles) into a specialized routing graph. Our engine extracts both implicit and explicit vehicle access rules, bridging the gap between raw map data and safe navigation.\n\nBy providing tailored routing profiles for diverse vehicle archetypes, we ensure that every calculation respects the physical and legal constraints of each asset. We leverage the open-source [Valhalla routing engine](https:\u002F\u002Fvalhalla.github.io\u002Fvalhalla\u002F), which allows you to customize desirability factors when you make an API request.\n\nSpecialized profiles for the 10-ton truck and the e-bike enable logistics platforms to automate fleet dispatch and [micromobility](https:\u002F\u002Fwww.mckinsey.com\u002Ffeatured-insights\u002Fmckinsey-explainers\u002Fwhat-is-micromobility) startups to provide riders with reliable, safe navigation.\n\n## The Stadia Maps Difference\n\n[Dynamic costing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F) gives you control over dozens of parameters on the fly, ensuring fleets navigate complex environments efficiently. Key capabilities include:\n\n- **Vehicle Subtypes:** Distinguish between mountain bikes and road bikes, or golf carts and other Low-Speed Vehicles (LSVs).\n- **Physical Preferences:** Configure the engine to avoid hills for scooters, disallow U-turns for long trucks, or avoid toll roads entirely.\n- **Precision Waypoints:** Specify that a waypoint must be visited from a particular side of the road, a critical feature for curb-side delivery and waste management.\n- **Direct Map Edits:** Map errors shouldn't take months to fix. Make your own edits directly. Updates can be live in our [routing engine](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fvalhalla\u002F) within days.\n\n## Specialized Mobility Solutions\n\nFlexibility enables business models that standard providers simply cannot support. A prime example is our work with municipalities such as [Peachtree City, GA](https:\u002F\u002Fpeachtree-city.org\u002F216\u002FPaths-Golf-Carts), and [The Villages, FL](https:\u002F\u002Fwww.districtgov.org\u002Frecreation\u002Ftrails.aspx).\n\nThese communities have extensive, legally regulated networks for golf carts and LSVs. Stadia Maps provided the only routing profile customizable enough to fit their local ordinances, such as prohibiting LSVs on roads with speed limits over 35 mph.\n\nWe support almost a dozen routing profiles out of the box, including bus, motorcycle, and pedestrian, with [matrix routing limits](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F) that are often orders of magnitude higher than those of our competitors. Whether you are optimizing a transit authority's bus training or dispatching a fleet of e-bikes, your routing engine should adapt to your vehicle, not the other way around.\n\n---\n\n[Create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) to explore our specialized routing profiles, or [contact our team](mailto:support@stadiamaps.com) to discuss a custom solution tailored to your unique vehicle constraints.\n",{"title":84,"description":85,"path":86,"published":87,"keywords":88,"rawbody":93},"Why Basic OpenStreetMap Routing Needs Real-Time Traffic","OpenStreetMap is a world-class road network, but without real-time traffic it's a static dataset. Here's why algorithmic ETAs fall apart in production logistics and how Stadia Maps closes the gap with TomTom-powered routing.","\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic","2026-05-12",[75,76,78,89,90,91,92],"Traffic Data","Matrix Routing","Logistics","TomTom","---\ndescription: >-\n  OpenStreetMap is a world-class road network, but without real-time traffic\n  it's a static dataset. Here's why algorithmic ETAs fall apart in production\n  logistics and how Stadia Maps closes the gap with TomTom-powered routing.\nexcerpt: >-\n  OpenStreetMap is great geography, but without real-time traffic it falls\n  short on ETAs. Stadia Maps closes the gap with TomTom-powered routing.\npublished: \"2026-05-12\"\nmodified: \"2026-05-27\"\nimage: \u002Fimages\u002Fcontent\u002Fosm-traffic-og.png\nsection: \"Routing\"\nkeywords:\n  - Routing\n  - Navigation\n  - OpenStreetMap\n  - Traffic Data\n  - Matrix Routing\n  - Logistics\n  - TomTom\nauthor:\n  name: \"Ian Wagner\"\n  slug: \"ian-wagner\"\n  jobTitle: \"Founder & President \u002F COO\"\n  bio: \"Ian is co-founder of Stadia Maps and leads engineering and operations. He works on routing, navigation, and the technical foundations that keep customer applications reliable at scale.\"\n  twitterCreator: \"@ianthetechie\"\n  sameAs:\n    - \"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fian-w-wagner\u002F\"\n---\n\n# Why Basic OpenStreetMap Routing Needs Real-Time Traffic\n\n> OpenStreetMap (OSM) provides a world-class geographic foundation, but it remains a static dataset. Without real-time traffic integration, routing engines must rely on algorithmic proxies—like road class and legal speed limits—which often lead to unreliable ETAs and logistics bottlenecks.\n\n## The Problem\n\n[OpenStreetMap (OSM)](https:\u002F\u002Fwww.openstreetmap.org\u002Fabout) is one of the world's leading road maps, but a persistent gap remains between fixed geographic data and a [live navigation experience](\u002Fproducts\u002Frouting-navigation\u002F). Without dedicated traffic data, Estimated Times of Arrival (ETAs) are essentially educated guesses. While OSM is excellent at mapping the world's road network, a static dataset cannot capture the actual driving conditions at this exact moment. In [enterprise-grade logistics](\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F), the lack of live data is often the first significant technical hurdle.\n\n## The Limits of Algorithmic Guesswork\n\nIn the absence of real-time data, a routing engine must estimate travel speeds based on tags and a few common proxies:\n\n- **Road Class:** Assuming a motorway is always faster than a residential street.\n- **Tagged Speed Limits:** Using the legal maximum as the baseline (when the tag even exists).\n- **Network Density:** Adjusting for urban vs. rural environments.\n- **Time of Day:** Using low-granularity buckets like \"daytime\" and \"nighttime.\"\n\nReal-world data show wild variances compared to these static estimates. Road class is a blunt instrument for predicting speed. Missing speed limit tags in open datasets force routing engines to rely on broad averages, resulting in unreliable ETAs and logistics delays. Rule-based algorithms are also notoriously bad at predicting choke points because open datasets don't account for traffic light timings, congestion near specific exits, or the \"invisible\" friction of a busy intersection.\n\n## The Stadia Maps Difference\n\nTo move from guesswork to precision, we integrated [TomTom's global traffic data](https:\u002F\u002Fwww.tomtom.com\u002Fproducts\u002Ftraffic-apis\u002F) directly into the [Stadia Maps routing engine](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F). High-resolution historical profiles and live feeds allow for accurate, real-time routing. We provide this through three key technical pillars:\n\n1. **Global Coverage:** Access to consistent data across more countries than almost any other vendor.\n2. **Rapid Updates:** A traffic latency of approximately two minutes allows our API to suggest alternate routes almost as soon as a wreck occurs.\n3. **Historical Profiles:** Deep granularity forms the backbone of predictive routing. High-resolution historical data enables accurate, time-dependent routing in advance, allowing you to plan a route for Tuesday at 8:00 AM based on what might happen on Tuesdays at 8:00 AM.\n\n## Fleet Intelligence at Scale\n\nFor dispatch, optimization, and fleet operations, [matrix routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F) (calculating the time and distance between many origins and destinations) is the engine's most critical function.\n\nThe Stadia Maps infrastructure supports matrix requests that are significantly larger than most competitors allow on standard plans. By integrating traffic data directly into these large-scale requests, we eliminate the need for developers to split requests into smaller chunks, reducing unnecessary complexity and latency.\n\nDevelopers maintain full agency over their implementation. We provide the fastest route based on live conditions, but the frequency of re-routing remains entirely in your control. Choice of revalidation frequency puts you in charge of the trade-off between real-time accuracy and [scaling costs](\u002Fpricing\u002F), ensuring your bills remain as predictable as your ETAs.\n\n---\n\n[Create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) to start building with real-time traffic and high-performance routing today. Our [documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F) provides everything you need to integrate TomTom-powered precision into your existing OSM workflow.\n",{"title":95,"description":96,"path":97,"published":98,"keywords":99,"rawbody":105},"2026 Satellite Imagery Update: 37 Million km² at 30cm Resolution","The 2026 Alidade Satellite update expands 30cm-resolution coverage to 37 million km², adds seamless country-wide mosaics for Japan, Nigeria, Mexico, the UAE, and Eastern South Africa, and refreshes our global 1.5m baseline from the latest SPOT data.","\u002Fblog\u002F2026-satellite-imagery-update","2026-04-27",[100,101,102,103,104],"Satellite Imagery","Aerial Photography","Map Update","High Resolution","Alidade Satellite","---\ndescription: >-\n  The 2026 Alidade Satellite update expands 30cm-resolution coverage to 37 million km²,\n  adds seamless country-wide mosaics for Japan, Nigeria, Mexico, the UAE, and Eastern\n  South Africa, and refreshes our global 1.5m baseline from the latest SPOT data.\npublished: 2026-04-27\nkeywords:\n  - Satellite Imagery\n  - Aerial Photography\n  - Map Update\n  - High Resolution\n  - Alidade Satellite\n---\n\n# 2026 Satellite Imagery Update: 37 Million km² at 30cm Resolution\n\nIf you've built anything on top of satellite imagery, you know the pain of inconsistent resolution. You zoom into one region and get crisp rooftops. Pan over to the next and it's a blurry patchwork from three years ago. That inconsistency isn't just cosmetic: it erodes trust in whatever you're building on top of it.\n\nWe regularly refresh our [Alidade Satellite](https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002Fmaps\u002Fmap-styles\u002Fsatellite-imagery\u002F) imagery as new high-resolution data becomes available from Airbus. This update is one of our most significant, expanding both the depth and freshness of our coverage.\n\n::cross-platform-map{id=\"map\" style=\"height: 400px;\"}\n---\ncenter: [139.6934, 35.6857]\nscroll-zoom: true\nzoom: 16.5\ntheme: alidade_satellite\nuse-theme-switcher: false\nuse-search: true\n---\n::\n\n## 30cm Coverage, Scaled\n\nWe now offer 37 million km² of 30cm-resolution satellite imagery, enough detail to distinguish individual vehicles, building footprints, and infrastructure at high zoom levels. For applications like urban planning tools, insurance assessments, or logistics platforms, this is the difference between useful and decorative.\n\nThis release also adds seamless 30cm country-wide mosaics for Japan, Nigeria, Mexico, the UAE, and Eastern South Africa. \"Seamless\" matters here: no visible tile boundaries, no abrupt shifts in color or season. Just consistent, high-resolution coverage across the entire country.\n\n## A Fresher Global Baseline\n\nBeyond the 30cm expansion, we've completed a full refresh of our 1.5m-resolution dataset covering the Earth's landmasses, derived from the latest SPOT Global layer. Even at lower zoom levels, you're working with current data rather than imagery that's aging out.\n\nFreshness matters as much as resolution. Across our entire dataset, the area-weighted average age is roughly 1.6 years. Nearly two-thirds of our coverage is less than a year old, and only 7% is older than three years. That share continues to shrink with each refresh.\n\nCombined with our [2025 satellite imagery refresh](https:\u002F\u002Fstadiamaps.com\u002Fblog\u002F2025-satellite-imagery-refresh\u002F), every pixel in our dataset is still 1.5m or better, with 37 million km² at 30cm and another 7 million km² at 50cm.\n\n## What This Means for Your Stack\n\nIf you're using Alidade Satellite, these updates are already live. No API changes, no migration. The same tile endpoints now serve fresher, sharper data. Integration works the same way it always has via MapLibre, Leaflet, OpenLayers, or any other mapping library that supports raster tiles.\n\nWe don't track or profile your end users. The imagery is delivered directly, with no behavioral tracking layer between your application and the tiles.\n\n## Try It\n\nThe updated satellite imagery is available now for all Stadia Maps customers. If you're new, [create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) and see the difference at zoom level 18.\n",1780407592734]