[{"data":1,"prerenderedAt":219},["ShallowReactive",2],{"blog-\u002Fblog\u002Finfrastructure-v2-improved-map-tiles-and-data\u002F":3,"related-blog-\u002Fblog\u002Finfrastructure-v2-improved-map-tiles-and-data\u002F":183},{"id":4,"title":5,"abstract":6,"author":6,"body":7,"description":168,"excerpt":6,"extension":169,"head":6,"image":6,"keywords":170,"meta":175,"modified":6,"navigation":176,"path":177,"proficiencyLevel":6,"published":178,"rawbody":179,"schemaOrg":6,"schemaType":6,"seo":180,"stem":181,"__hash__":182},"blog\u002Fblog\u002Finfrastructure-v2-improved-map-tiles-and-data.md","Mapping Infrastructure v2 Release",null,{"type":8,"value":9,"toc":154},"minimark",[10,14,18,21,24,29,34,37,41,46,49,86,89,93,97,100,103,106,110,114,117,121,124,138,141,145],[11,12,5],"h1",{"id":13},"mapping-infrastructure-v2-release",[15,16,17],"p",{},"After months of painstaking development, testing, data gathering,\ndeployment and a few seconds to flip the switch, we are pleased to\nannounce Stadia's mapping data infrastructure, version 2!",[15,19,20],{},"Shortly after starting Stadia Maps in 2017, we realized our method of\nprocessing, development, and deployment of mapping data was limited. We\ncould not deliver the quality maps our customers need or our inner\nperfectionists demand. We wanted to quickly deploy updates and iterate\non designs to make our maps more useful and beautiful. We wanted to add\nnew features without months of lag from testing to production.\nUltimately, we wanted a platform that would allow us to deliver an\nimproved mapping experience every single day. So last year, we began\ninvesting in a new mapping infrastructure that could deliver all the\nfeatures we hoped for (plus a few new ones we’ve discovered along\nthe way). To accomplish that, we needed to control the pipeline all the\nway from ingesting source data to displaying the maps for our users.",[15,22,23],{},"As of today, our dream is reality and your maps are getting loads of\nimprovements, all because our mapping data is delivered from a pipeline\n100% managed by us.",[25,26,28],"h2",{"id":27},"improvements","Improvements",[30,31,33],"h3",{"id":32},"data-updates","Data Updates",[15,35,36],{},"We are now delivering data from early August 2019, and plan to deliver at\nleast monthly updates to our underlying mapping data to allow you and your\ncustomers to have the latest data possible.",[30,38,40],{"id":39},"improved-language-support","Improved Language Support",[42,43],"content-twenty-twenty",{"afterSrc":44,"beforeSrc":45},"\u002Fassets\u002F2019-new-tiles-language.png","\u002Fassets\u002F2019-old-tiles-language.png",[15,47,48],{},"We’ve added support for many new languages in our themes, and we have\nplans to add another major source of data to extend our language coverage\nto as many places and languages as possible. We’ve added the following\nlanguages and scripts to our themes (in alphabetical order):",[50,51,52,56,59,62,65,68,71,74,77,80,83],"ul",{},[53,54,55],"li",{},"Armenian",[53,57,58],{},"Bengali",[53,60,61],{},"Devanagari",[53,63,64],{},"Ethiopian",[53,66,67],{},"Georgian",[53,69,70],{},"Hebrew",[53,72,73],{},"Khmer",[53,75,76],{},"Lao",[53,78,79],{},"Myanmar (Burmese)",[53,81,82],{},"Tamil",[53,84,85],{},"Thai",[15,87,88],{},"If you know of any language or script we don’t currently support, please\nlet us know!",[30,90,92],{"id":91},"extended-national-park-and-nature-reserve-coverage","Extended National Park and Nature Reserve Coverage",[42,94],{"afterSrc":95,"beforeSrc":96},"\u002Fassets\u002F2019-new-national.png","\u002Fassets\u002F2019-old-national.png",[15,98,99],{},"We believe our Outdoor theme is critical for our customers who focus on\neverything that happens outside the confines of a car or building. Until\ntoday, the Outdoor theme was missing a pretty critical piece of data:\nlabels for national parks and official nature reserves—the places we all\nenjoy hiking, biking, swimming, or just soaking in the aura of nature.",[15,101,102],{},"We also updated mountain peaks to include elevation data (where\navailable), and we made small tweaks to display mountain peaks more\noften and with somewhat better selection based on relative importance.\n(We believe there’s still room to improve this further in later\nupdates.)",[15,104,105],{},"Now you and your customers can go forth and enjoy nature—with\nfull awareness of what to call the place they are enjoying it.",[30,107,109],{"id":108},"improved-bay-and-water-label-visibility","Improved Bay and Water Label Visibility",[42,111],{"afterSrc":112,"beforeSrc":113},"\u002Fassets\u002F2019-new-water.png","\u002Fassets\u002F2019-old-water.png",[15,115,116],{},"Another important piece of location awareness is out to sea—more\nspecifically, bays and other smaller bodies of water. We’ve added\nlabels for smaller bays and waterways to make that favorite lagoon a bit\neasier to find.",[25,118,120],{"id":119},"whats-next","What’s next?",[15,122,123],{},"We have a lot of updates on the heels the new pipeline. Because it allows\nquick iteration, we plan to add the following data to our core data and\nthemes as appropriate over the next few months:",[50,125,126,129,132,135],{},[53,127,128],{},"Ocean Bathymetry",[53,130,131],{},"Contour lines",[53,133,134],{},"Hillshading",[53,136,137],{},"…and more!",[15,139,140],{},"We will soon be releasing our geospatial APIs (starting with elevation\nand time zones) and offer improved routing for bicycles based on the\nelevation data. We’re also hard at work developing our enterprise\nlevel plans to meet even the most demanding business needs.",[25,142,144],{"id":143},"talk-to-us","Talk to us!",[15,146,147,148,153],{},"And we want to hear from you! If there’s anything you need to make\nyour mapping experience more fantastic, just let us know. We’re\nalways ready to help and answer your questions at\n",[149,150,152],"a",{"href":151},"mailto:support@stadiamaps.com","support@stadiamaps.com"," or your\nfavorite social channel (links in footer).",{"title":155,"searchDepth":156,"depth":156,"links":157},"",4,[158,166,167],{"id":27,"depth":159,"text":28,"children":160},2,[161,163,164,165],{"id":32,"depth":162,"text":33},3,{"id":39,"depth":162,"text":40},{"id":91,"depth":162,"text":92},{"id":108,"depth":162,"text":109},{"id":119,"depth":159,"text":120},{"id":143,"depth":159,"text":144},"A revamped mapping data pipeline, improved map data and themes, and a look to the future.","md",[171,172,173,174],"Infrastructure","Map Data","Data Pipeline","Map Tiles",{},true,"\u002Fblog\u002Finfrastructure-v2-improved-map-tiles-and-data","2019-08-26","---\ndescription: A revamped mapping data pipeline, improved map data and themes, and a look to the future.\npublished: 2019-08-26\nkeywords:\n  - Infrastructure\n  - Map Data\n  - Data Pipeline\n  - Map Tiles\n---\n\n# Mapping Infrastructure v2 Release\n\nAfter months of painstaking development, testing, data gathering,\ndeployment and a few seconds to flip the switch, we are pleased to\nannounce Stadia's mapping data infrastructure, version 2!\n\nShortly after starting Stadia Maps in 2017, we realized our method of\nprocessing, development, and deployment of mapping data was limited. We\ncould not deliver the quality maps our customers need or our inner\nperfectionists demand. We wanted to quickly deploy updates and iterate\non designs to make our maps more useful and beautiful. We wanted to add\nnew features without months of lag from testing to production.\nUltimately, we wanted a platform that would allow us to deliver an\nimproved mapping experience every single day. So last year, we began\ninvesting in a new mapping infrastructure that could deliver all the\nfeatures we hoped for (plus a few new ones we’ve discovered along\nthe way). To accomplish that, we needed to control the pipeline all the\nway from ingesting source data to displaying the maps for our users.\n\nAs of today, our dream is reality and your maps are getting loads of\nimprovements, all because our mapping data is delivered from a pipeline\n100% managed by us.\n\n## Improvements\n\n### Data Updates\n\nWe are now delivering data from early August 2019, and plan to deliver at\nleast monthly updates to our underlying mapping data to allow you and your\ncustomers to have the latest data possible.\n\n### Improved Language Support\n\n::content-twenty-twenty\n---\nbeforeSrc: \"\u002Fassets\u002F2019-old-tiles-language.png\"\nafterSrc: \"\u002Fassets\u002F2019-new-tiles-language.png\"\n---\n::\n\nWe’ve added support for many new languages in our themes, and we have\nplans to add another major source of data to extend our language coverage\nto as many places and languages as possible. We’ve added the following\nlanguages and scripts to our themes (in alphabetical order):\n\n* Armenian\n* Bengali\n* Devanagari\n* Ethiopian\n* Georgian\n* Hebrew\n* Khmer\n* Lao\n* Myanmar (Burmese)\n* Tamil\n* Thai\n \nIf you know of any language or script we don’t currently support, please\nlet us know!\n\n### Extended National Park and Nature Reserve Coverage\n\n::content-twenty-twenty\n---\nbeforeSrc: \"\u002Fassets\u002F2019-old-national.png\"\nafterSrc: \"\u002Fassets\u002F2019-new-national.png\"\n---\n::\n\nWe believe our Outdoor theme is critical for our customers who focus on\neverything that happens outside the confines of a car or building. Until\ntoday, the Outdoor theme was missing a pretty critical piece of data:\nlabels for national parks and official nature reserves—the places we all\nenjoy hiking, biking, swimming, or just soaking in the aura of nature.\n\nWe also updated mountain peaks to include elevation data (where\navailable), and we made small tweaks to display mountain peaks more\noften and with somewhat better selection based on relative importance.\n(We believe there’s still room to improve this further in later\nupdates.)\n\nNow you and your customers can go forth and enjoy nature—with\nfull awareness of what to call the place they are enjoying it.\n\n### Improved Bay and Water Label Visibility\n\n::content-twenty-twenty\n---\nbeforeSrc: \"\u002Fassets\u002F2019-old-water.png\"\nafterSrc: \"\u002Fassets\u002F2019-new-water.png\"\n---\n::\n\nAnother important piece of location awareness is out to sea—more\nspecifically, bays and other smaller bodies of water. We’ve added\nlabels for smaller bays and waterways to make that favorite lagoon a bit\neasier to find.\n\n## What’s next?\n\nWe have a lot of updates on the heels the new pipeline. Because it allows\nquick iteration, we plan to add the following data to our core data and\nthemes as appropriate over the next few months:\n\n* Ocean Bathymetry\n* Contour lines\n* Hillshading\n* …and more!\n \nWe will soon be releasing our geospatial APIs (starting with elevation\nand time zones) and offer improved routing for bicycles based on the\nelevation data. We’re also hard at work developing our enterprise\nlevel plans to meet even the most demanding business needs.\n\n## Talk to us!\n\nAnd we want to hear from you! If there’s anything you need to make\nyour mapping experience more fantastic, just let us know. We’re\nalways ready to help and answer your questions at\n[support@stadiamaps.com](mailto:support@stadiamaps.com) or your\nfavorite social channel (links in footer).",{"title":5,"description":168},"blog\u002Finfrastructure-v2-improved-map-tiles-and-data","9E1NInDHqiwL5MBOe_DQkS0UKqlB-l98Wrg5tlPmwrk",[184,193,207],{"title":185,"description":186,"path":187,"published":188,"keywords":189,"rawbody":192},"Product Update: Improved Tiles, a New Tier, and Stadia Maps News","Product Update: improved map tiles, a new pricing tier, and more news from about the web.","\u002Fblog\u002Fproduct-updates-improved-tiles-new-tier","2020-07-02",[174,190,191],"Pricing","Product Update","---\npublished: 2020-07-02\ndescription: \"Product Update: improved map tiles, a new pricing tier, and more news from about the web.\"\nkeywords:\n  - Map Tiles\n  - Pricing\n  - Product Update\n---\n\n# Product Update: Improved Tiles, a New Tier, and Stadia Maps News\n\nIt’s been a few months since we last updated you on what\nwe’ve been doing around Stadia Maps, and we’ve been able to\naccomplish quite a lot.\n\n## New Tier: Stadia Growth\n\nAfter talking with customers and looking at our pricing, we realized there was a hole between our Starter and Standard\ntiers.\n\nEnter: *Stadia Growth*.\n\nA tier to help you grow, without growing your bills too much. Your $50 \u002F month goes a long way: 75k map views and API\nrequests \u002F day, with all the same great service you’ve learned to count on. Take a look at\nour [pricing page](\u002Fpricing\u002F) to see how it fits in.\n\n## Better Raster Tiles & Static Maps\n\nAt the beginning of this year, we knew our raster tiles had occasional\nedge-case performance issues, some cropped labels, and other minor\nquality concerns. So, starting in January, we began working towards\nfixing these issues.\n\nWe started by directly integrating our raster rendering library into our\ncustom-built tile server (it was previously a separate service). By doing\nthis, we’ve been able to almost completely eliminate our\nworst-case tail performance for raster tiles and static maps. After\nseeing promising results during the initial integration, we began tuning\nthe tile server against production loads, and have been able to eliminate\nmore performance bottlenecks. In terms of numbers, our worst-case raster\ntile rendering performance (the worst 0.1% of tile renders) dropped from\n8s to 2s—or 4x faster. At the same time, the 5% worst-case\nperforming requests improved from 512ms to 256ms—or 2x faster. We\nbelieve we have more progress to make, but this represents a significant\nstep towards eliminating too-slow tile renders.\n\nAs a very nice by-product, we’ve been able to drastically improve\nthe quality of our raster tiles (significantly fewer “cut\nlabels” and much better text layout). We are continuing to focus\non speed and reliability to ensure the best possible raster map\nexperience possible. Stay tuned for more updates regarding quality and\nperformance in the next few months.\n\n## Improved Outdoors Theme\n\nSince our last update, we’ve added the ability to display parks\nand nature reserves over water, sand and rock land cover types to give\nbeaches and mountain ranges more texture, and—a much requested\nfeature—trails and footpaths at lower zoom levels, all so that you can\nenjoy the great outdoors just a little bit more.\n\n## Newer Data, Better Depth\n\nAnother focus this year is to improve our processes for working with OSM\ndata. As a result, we’re on track to release new data each month this\nyear, with an improved schema each time. We’ve also increased the speed\nof our routing data updates, with new data being added every week.\n\nSince January, we’ve added a lot of updates to details of the\ntransportation layer (including the trails and footpaths at higher\nzoom), improved small details to the water and park layers, and improved\nvector tile performance for higher zoom levels (especially in complex\ncityscapes, such as Milan or Tokyo).\n\n## News from Around the Web\n\nOver the last few months, we’ve had the chance to read about how\nsome of our customers are\n\u003Ca href=\"https:\u002F\u002Fmedium.com\u002F@onthegomap\u002Fon-the-go-map-style-improvements-d24bfb5836e1\">\n  using Stadia Maps to improve their customers’ experiences\n\u003C\u002Fa>,\nthe opportunity to \u003Ca href=\"https:\u002F\u002Fwww.tfir.io\u002Fstadia-maps\u002F\">\n  chat with TFIR about how to build better open-source mapping services\n\u003C\u002Fa>, and\nexplore \u003Ca href=\"https:\u002F\u002Fwww.linode.com\u002Fspotlight\u002Fstadia-maps\u002F\">\n  how we deliver a quality experience for an affordable price\n\u003C\u002Fa> with our infrastructure provider, Linode.\n\n## What's Next?\n\nIn the next couple of months, we will continue to squash remaining\nperformance and quality issues with raster tiles. We are working to hone\nour data schema to allow for better display of data (specifically more\nupgrades to the road network to eliminate some holes in our data). We\nare also close to deploying a new set of geospatial APIs (a time zone API\nwith historical data), after a few setbacks delivering it to production.\n\n## Missing something? Have comments or concerns?\n\nWe’re always here to help. If you have any questions or concerns about\nour current services or our future roadmap, don’t hesitate to reach out\nto us with any of the channels listed in the footer. Of course, you can\nalways email us, we’ll get back to you lickety-split!\n\nThat’s all for now.\n\nStay well and be kind.\n\n:v:",{"title":194,"description":195,"path":196,"published":197,"keywords":198,"rawbody":206},"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",[199,200,201,202,203,204,205],"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":208,"description":209,"path":210,"published":211,"keywords":212,"rawbody":218},"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",[213,214,215,216,217],"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",1778676027771]