[{"data":1,"prerenderedAt":95},["ShallowReactive",2],{"blog-\u002Fblog\u002Fannouncing-simplified-account-level-billing\u002F":3,"related-blog-\u002Fblog\u002Fannouncing-simplified-account-level-billing\u002F":58},{"id":4,"title":5,"abstract":6,"author":6,"body":7,"description":44,"excerpt":6,"extension":45,"head":6,"image":6,"keywords":46,"meta":50,"modified":6,"navigation":51,"path":52,"proficiencyLevel":6,"published":53,"rawbody":54,"schemaOrg":6,"schemaType":6,"seo":55,"stem":56,"__hash__":57},"blog\u002Fblog\u002Fannouncing-simplified-account-level-billing.md","Announcing Simplified Account-Based Billing",null,{"type":8,"value":9,"toc":40},"minimark",[10,14,18,26],[11,12,5],"h1",{"id":13},"announcing-simplified-account-based-billing",[15,16,17],"p",{},"At Stadia Maps, we're always trying to make maps more accessible. Since launching, we have required a subscription for\neach property in your Stadia Maps account. However, over time, we recognized this approach added unnecessary complexity\nand confusion (it is the top support question we receive). So starting today, we’re making your life easier by\nbilling per account rather than per property.",[15,19,20,21,25],{},"Properties are still a useful way that many of our customers track usage of individual applications, so they are not\ngoing away. In fact, you can still create as many of them as you like! The difference is that your account only needs a\nsingle subscription that covers the ",[22,23,24],"em",{},"combined"," usage of all your properties. We’ve added an account-level\noverview to the client dashboard so that you can see the aggregate usage against your plan limit.\nIf you previously had multiple subscriptions, we’ve got you\ncovered! We have already canceled any extra subscriptions and\nemailed you with the good news.",[15,27,28,29,34,35,39],{},"Of course, our ",[30,31,33],"a",{"href":32},"\u002Fterms-of-service\u002F","terms of service"," still apply, and you will need multiple accounts to use maps\nacross multiple entities. See our ",[30,36,38],{"href":37},"\u002Ffaqs\u002F","FAQ"," to learn more about shared billing, and when you need multiple accounts.",{"title":41,"searchDepth":42,"depth":42,"links":43},"",4,[],"We've simplified billing by moving to a single subscription per account.","md",[47,48,49],"Billing","Account Management","Subscription",{},true,"\u002Fblog\u002Fannouncing-simplified-account-level-billing","2022-12-05","---\ndescription: \"We've simplified billing by moving to a single subscription per account.\"\npublished: 2022-12-05\nkeywords:\n  - Billing\n  - Account Management\n  - Subscription\n---\n\n# Announcing Simplified Account-Based Billing\n\nAt Stadia Maps, we're always trying to make maps more accessible. Since launching, we have required a subscription for\neach property in your Stadia Maps account. However, over time, we recognized this approach added unnecessary complexity\nand confusion (it is the top support question we receive). So starting today, we’re making your life easier by\nbilling per account rather than per property.\n\nProperties are still a useful way that many of our customers track usage of individual applications, so they are not\ngoing away. In fact, you can still create as many of them as you like! The difference is that your account only needs a\nsingle subscription that covers the _combined_ usage of all your properties. We’ve added an account-level\noverview to the client dashboard so that you can see the aggregate usage against your plan limit.\nIf you previously had multiple subscriptions, we’ve got you\ncovered! We have already canceled any extra subscriptions and\nemailed you with the good news.\n\nOf course, our [terms of service](\u002Fterms-of-service\u002F) still apply, and you will need multiple accounts to use maps\nacross multiple entities. See our [FAQ](\u002Ffaqs\u002F) to learn more about shared billing, and when you need multiple accounts.\n",{"title":5,"description":44},"blog\u002Fannouncing-simplified-account-level-billing","oaVKudPQLFtmC9JxTwnFN9_2koMy8mqR9dgSXikd0WA",[59,69,83],{"title":60,"description":61,"path":62,"published":63,"keywords":64,"rawbody":68},"New Plans & Pricing in 2023","Announcement: We've released new plans and pricing.","\u002Fblog\u002Fplan-updates-2023","2023-01-12",[65,66,67,47],"Pricing","Plans","Credits","---\ndescription: \"Announcement: We've released new plans and pricing.\"\npublished: 2023-01-12\nkeywords:\n  - Pricing\n  - Plans\n  - Credits\n  - Billing\n---\n\n# New Plans & Pricing in 2023\n\n## What’s Changing\n\nEffective today, we are updating our pricing policies and plans. We have identified some ways our current\npricing causes confusion, and we are updating how accounts are granted access to features.\n\n### Change #1: Account Usage\n\nThe biggest change is how account usage is calculated. First, plans will now have a monthly usage limit instead\nof a daily usage limit. Second, we are replacing \"map views\" and \"API requests\" with a single, simplified credit\nsystem.\n\nEach plan will come with an included amount of credits for each month, and each request you make to our APIs\nwill use a set number of credits (e.g., a raster map tile will count as 1 credit, a static map as 10 credits,\nand a route request as 10 credits).\n\nFor *new* paid plans, we will allow users to choose between the option to be hard limited (i.e.,\nadditional requests will be blocked) when the included credits are consumed or accruing additional usage fees.\nFree plans will continue being hard limited when the usage limit is reached.\n\n### Change #2: Available Features\n\nGoing forward, each plan will be granted access to a set of APIs. More advanced plans will have access to more\nfeatures; less advanced plans will have access to fewer features. For example, you will now need the Starter\nplan to gain access to our Static Maps API or the Standard plan for the new Satellite Basemap.\n\nLegacy plans will retain their existing feature set as of January 11th, but will need to upgrade to access new\nfeatures (ex: satellite basemaps). If you were a subscriber as of January 11th, we have emailed you with a\nlimited time upgrade offer to get a substantial discount on any of the new plans.\n\nYou can see all the details about our new pricing on our updated [pricing page](\u002Fpricing\u002F)",{"title":70,"description":71,"path":72,"published":73,"keywords":74,"rawbody":82},"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,77,78,79,80,81],"Routing","Navigation","OpenStreetMap","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\"\nkeywords:\n  - Routing\n  - Navigation\n  - OpenStreetMap\n  - Traffic Data\n  - Matrix Routing\n  - Logistics\n  - TomTom\nauthor:\n  name: \"Ian Wagner\"\n  jobTitle: \"Founder & President \u002F COO\"\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, 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":84,"description":85,"path":86,"published":87,"keywords":88,"rawbody":94},"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",[89,90,91,92,93],"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",1778676026174]