[{"data":1,"prerenderedAt":244},["ShallowReactive",2],{"footer-learn-links":3,"site-prefooter-cta":16,"blog-\u002Fblog\u002Fnovember-2026-newsletter\u002F":24,"related-blog-\u002Fblog\u002Fnovember-2026-newsletter\u002F":211,"blog-author-\u002Fblog\u002Fnovember-2026-newsletter\u002F":27},[4,7,10,13],{"title":5,"path":6},"What Is a Basemap?","\u002Flearn\u002Fwhat-is-a-basemap",{"title":8,"path":9},"What Is a Navigation SDK?","\u002Flearn\u002Fwhat-is-a-navigation-sdk",{"title":11,"path":12},"What Is a Distance Matrix API?","\u002Flearn\u002Fdistance-matrix-api",{"title":14,"path":15},"Can You Store Geocoding Results?","\u002Flearn\u002Fgeocoding-data-storage",{"id":17,"extension":18,"heading":19,"meta":20,"stem":21,"text":22,"__hash__":23},"site\u002Fsite\u002Fprefooter-cta.yml","yml","Business Outcomes That Fuel Your Growth",{},"site\u002Fprefooter-cta","With Stadia Maps, you build the solutions that matter. Logistics platforms provide accurate ETAs, fleet management apps reduce fuel costs, and emergency dispatch systems improve response times.","XztWiZDFyAC0XCoeYLLQrcyaVmP8uvGWALRS354c9I4",{"id":25,"title":26,"abstract":27,"author":27,"body":28,"description":189,"extension":190,"head":27,"image":191,"imageAlt":192,"keywords":193,"meta":200,"modified":27,"navigation":201,"path":202,"proficiencyLevel":27,"published":203,"rawbody":204,"schemaOrg":27,"schemaType":27,"section":205,"seo":206,"stem":209,"__hash__":210},"blog\u002Fblog\u002Fnovember-2026-newsletter.md","The Stadia Maps Newsletter №17 – November 2026",null,{"type":29,"value":30,"toc":173},"minimark",[31,35,44,47,50,58,61,68,71,78,81,83,87,109,115,117,124,127,129,133,141,144,151,154,161,164,166],[32,33,34],"p",{},"Thanks for building with us. Since our last newsletter, we've worked to deliver a more consistent map experience for you and your users. Boundaries and disputed markings now match across zoom levels. We also rebuilt the Static Maps API for faster, more scalable responses.",[32,36,37,38,43],{},"We'll keep shipping, and the ",[39,40,42],"a",{"href":41},"\u002Fchangelog\u002F","changelog"," lists every change as it goes live. Until next time.",[32,45,46],{},"— Luke, Ian, and the entire Stadia Maps team",[48,49],"hr",{},[51,52,54],"h2",{"id":53},"we-rebuilt-static-maps",[39,55,57],{"href":56},"\u002Fblog\u002Fwe-rebuilt-static-maps\u002F","We Rebuilt Static Maps",[32,59,60],{},"Every Static Maps request now uses a new rendering system built in Rust on MapLibre Native. Median response times halved, and the slowest 1% of requests went from up to 8s to about 1s.",[51,62,64],{"id":63},"redesigned-land-cover-layers-at-low-zoom",[39,65,67],{"href":66},"\u002Fblog\u002Fredesigned-land-cover-layers\u002F","Redesigned Land Cover Layers at Low Zoom",[32,69,70],{},"We recently added global land cover to our Outdoors style and paid closer attention to how we process and present it in Alidade Bright, Outdoors, and Stamen Terrain.",[51,72,74],{"id":73},"updated-boundary-layers-consistency-and-efficiency-across-all-zoom-levels",[39,75,77],{"href":76},"\u002Fblog\u002Fupdated-boundary-layers-across-zoom-levels\u002F","Updated Boundary Layers: Consistency and Efficiency Across All Zoom Levels",[32,79,80],{},"There were several inconsistencies in how we displayed boundaries across zoom levels. Now, every boundary is consistently marked as disputed or non-disputed at every zoom level.",[48,82],{},[51,84,86],{"id":85},"explore-our-platform","Explore Our Platform",[88,89,90,97,103],"ul",{},[91,92,93],"li",{},[39,94,96],{"href":95},"https:\u002F\u002Fdocs.stadiamaps.com\u002F","API Documentation",[91,98,99],{},[39,100,102],{"href":101},"\u002Fproducts\u002F","Platform Features & Overview",[91,104,105],{},[39,106,108],{"href":107},"\u002Fblog\u002F","Company Blog",[32,110,111],{},[39,112,114],{"href":113},"https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F","Don't have an account? Create one today.",[48,116],{},[51,118,120],{"id":119},"how-landsearch-uses-stadia-maps-satellite-imagery-to-show-millions-of-acres-of-land",[39,121,123],{"href":122},"\u002Fcustomer-stories\u002Flandsearch\u002F","How LandSearch Uses Stadia Maps Satellite Imagery to Show Millions of Acres of Land",[32,125,126],{},"LandSearch switched from Mapbox to Stadia Maps for satellite imagery, resulting in high-quality images at a lower cost. Our latest customer story explains why they decided to switch to Stadia Maps for high-quality satellite imagery and responsive customer support.",[48,128],{},[51,130,132],{"id":131},"latest-from-our-blog","Latest From Our Blog",[134,135,137],"h3",{"id":136},"revisiting-the-cartography-behind-stamen-terrain",[39,138,140],{"href":139},"\u002Fblog\u002Frevisiting-the-cartography-behind-stamen-terrain\u002F","Revisiting the Cartography Behind Stamen Terrain",[32,142,143],{},"We've been taking a fresh look at the cartographic decisions at every level of our map stack. Our recent water layer changes and water label updates visibly changed the Stamen Terrain style.",[134,145,147],{"id":146},"choosing-the-right-geocoding-endpoint",[39,148,150],{"href":149},"\u002Fblog\u002Fchoosing-the-right-geocoding-endpoint\u002F","Choosing the Right Geocoding Endpoint",[32,152,153],{},"Geocoding APIs fall into two categories: forward geocoding turns free text into coordinates, and reverse geocoding does the opposite. The distinction is straightforward, but the right endpoint and parameters can make a big difference.",[134,155,157],{"id":156},"how-to-build-a-custom-map-style-in-30-minutes",[39,158,160],{"href":159},"\u002Fblog\u002Fhow-to-build-a-custom-map-style-in-30-minutes\u002F","How to Build a Custom Map Style in 30 Minutes",[32,162,163],{},"This walkthrough forks a Stadia Maps style, recolors the background, water, road, and label layers in Maputnik, exports the JSON, and hosts it as a static file.",[48,165],{},[32,167,168,169],{},"Have feedback or questions? ",[39,170,172],{"href":171},"\u002Fsupport\u002F","We'd love to hear from you.",{"title":174,"searchDepth":175,"depth":175,"links":176},"",4,[177,179,180,181,182,183],{"id":53,"depth":178,"text":57},2,{"id":63,"depth":178,"text":67},{"id":73,"depth":178,"text":77},{"id":85,"depth":178,"text":86},{"id":119,"depth":178,"text":123},{"id":131,"depth":178,"text":132,"children":184},[185,187,188],{"id":136,"depth":186,"text":140},3,{"id":146,"depth":186,"text":150},{"id":156,"depth":186,"text":160},"We rebuilt Static Maps and redesigned land cover layers at low zoom. There's a new LandSearch customer story and the latest blog posts on geocoding endpoints, the cartography behind Stamen Terrain, and more.","md","\u002Fimages\u002Fog\u002Fnovember-2026-newsletter.png","The Stadia Maps Newsletter №17 – November 2026 — Stadia Maps",[194,195,196,197,198,199],"Stadia Maps Newsletter","Mapping Infrastructure","Static Maps","Stamen","Routing APIs","Geocoding",{},true,"\u002Fblog\u002Fnovember-2026-newsletter","2026-11-11","---\ntitle: The Stadia Maps Newsletter №17 – November 2026\ndescription: We rebuilt Static Maps and redesigned land cover layers at low zoom. There's a new LandSearch customer story and the latest blog posts on geocoding endpoints, the cartography behind Stamen Terrain, and more.\nimage: \u002Fimages\u002Fog\u002Fnovember-2026-newsletter.png\nimageAlt: The Stadia Maps Newsletter №17 – November 2026 — Stadia Maps\nkeywords:\n  - Stadia Maps Newsletter\n  - Mapping Infrastructure\n  - Static Maps\n  - Stamen\n  - Routing APIs\n  - Geocoding\npublished: 2026-11-11\nsection: Newsletter\nseo:\n  title: Stadia Maps Newsletter №17 | November 2026 Updates\n  description: \"Latest from Stadia Maps: more consistent map experience, LandSearch customer story, cartographic decisions at every level of our map stack, and more.\"\n---\n\nThanks for building with us. Since our last newsletter, we've worked to deliver a more consistent map experience for you and your users. Boundaries and disputed markings now match across zoom levels. We also rebuilt the Static Maps API for faster, more scalable responses.\n\nWe'll keep shipping, and the [changelog](\u002Fchangelog\u002F) lists every change as it goes live. Until next time.\n\n— Luke, Ian, and the entire Stadia Maps team\n\n---\n\n## [We Rebuilt Static Maps](\u002Fblog\u002Fwe-rebuilt-static-maps\u002F)\n\nEvery Static Maps request now uses a new rendering system built in Rust on MapLibre Native. Median response times halved, and the slowest 1% of requests went from up to 8s to about 1s.\n\n## [Redesigned Land Cover Layers at Low Zoom](\u002Fblog\u002Fredesigned-land-cover-layers\u002F)\n\nWe recently added global land cover to our Outdoors style and paid closer attention to how we process and present it in Alidade Bright, Outdoors, and Stamen Terrain.\n\n## [Updated Boundary Layers: Consistency and Efficiency Across All Zoom Levels](\u002Fblog\u002Fupdated-boundary-layers-across-zoom-levels\u002F)\n\nThere were several inconsistencies in how we displayed boundaries across zoom levels. Now, every boundary is consistently marked as disputed or non-disputed at every zoom level.\n\n---\n\n## Explore Our Platform\n\n- [API Documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002F)\n- [Platform Features & Overview](\u002Fproducts\u002F)\n- [Company Blog](\u002Fblog\u002F)\n\n[Don't have an account? Create one today.](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F)\n\n---\n\n## [How LandSearch Uses Stadia Maps Satellite Imagery to Show Millions of Acres of Land](\u002Fcustomer-stories\u002Flandsearch\u002F)\n\nLandSearch switched from Mapbox to Stadia Maps for satellite imagery, resulting in high-quality images at a lower cost. Our latest customer story explains why they decided to switch to Stadia Maps for high-quality satellite imagery and responsive customer support.\n\n---\n\n## Latest From Our Blog\n\n### [Revisiting the Cartography Behind Stamen Terrain](\u002Fblog\u002Frevisiting-the-cartography-behind-stamen-terrain\u002F)\n\nWe've been taking a fresh look at the cartographic decisions at every level of our map stack. Our recent water layer changes and water label updates visibly changed the Stamen Terrain style.\n\n### [Choosing the Right Geocoding Endpoint](\u002Fblog\u002Fchoosing-the-right-geocoding-endpoint\u002F)\n\nGeocoding APIs fall into two categories: forward geocoding turns free text into coordinates, and reverse geocoding does the opposite. The distinction is straightforward, but the right endpoint and parameters can make a big difference.\n\n### [How to Build a Custom Map Style in 30 Minutes](\u002Fblog\u002Fhow-to-build-a-custom-map-style-in-30-minutes\u002F)\n\nThis walkthrough forks a Stadia Maps style, recolors the background, water, road, and label layers in Maputnik, exports the JSON, and hosts it as a static file.\n\n---\n\nHave feedback or questions? [We'd love to hear from you.](\u002Fsupport\u002F)\n","Newsletter",{"title":207,"description":208},"Stadia Maps Newsletter №17 | November 2026 Updates","Latest from Stadia Maps: more consistent map experience, LandSearch customer story, cartographic decisions at every level of our map stack, and more.","blog\u002Fnovember-2026-newsletter","n4TluJ0WlmfmJKh0KFIF7BB2D6GQ6a5uV4lJu1J9Yrs",[212,221,236],{"title":213,"description":214,"path":215,"published":216,"keywords":217,"rawbody":220},"The Stadia Maps Newsletter №15 – June 2026","Two new leaders join Stadia Maps, updated changelog with RSS feed, and latest blog posts on water features, routing privacy, and transportation alternatives.","\u002Fblog\u002Fjune-2026-newsletter","2026-06-30",[194,195,198,218,199,219],"Basemaps","Developer Platform","---\ntitle: The Stadia Maps Newsletter №15 – June 2026\ndescription: Two new leaders join Stadia Maps, updated changelog with RSS feed, and latest blog posts on water features, routing privacy, and transportation alternatives.\nimage: \u002Fimages\u002Fog\u002Fjune-2026-newsletter.png\nimageAlt: The Stadia Maps Newsletter №15 – June 2026\nkeywords:\n  - Stadia Maps Newsletter\n  - Mapping Infrastructure\n  - Routing APIs\n  - Basemaps\n  - Geocoding\n  - Developer Platform\npublished: 2026-06-30\nsection: Newsletter\nseo:\n  title: Stadia Maps Newsletter №15 | June 2026 Updates\n  description: \"Latest from Stadia Maps: New leadership team, changelog RSS feed, improved water feature rendering, routing privacy, and multi-transport support.\"\n---\n\n---\n\n## Welcome to Our Growing Leadership Team\n\nBuilding a company around a conviction that maps are critical infrastructure, not an ad product, takes a particular kind of person, and two of them just joined Stadia Maps. Rob Yoegel and Rick Myers both spent years at Linode (now Akamai), building a developer-loved business in a market full of cynical alternatives. [Read the full announcement here.](\u002Fblog\u002Ftwo-leaders-join-stadia-maps\u002F)\n\n## Explore Our Platform\n\n- [API Documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002F)\n- [Platform Features & Overview](\u002Fproducts\u002F)\n- [Company Blog](\u002Fblog\u002F)\n\n---\n\n## We Updated Our Changelog (Yes, Really)\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\u002F), too.\n\n---\n\n## Latest From Our Blog\n\n### [How We Fixed Water Feature Rendering Across All Zoom Levels in Our Basemaps](\u002Fblog\u002Ffixing-missing-water-interactive-basemaps\u002F)\n\nWe shipped a significant update to the data pipeline behind our Interactive Basemaps. The change fixes a class of visual inconsistencies at low- and mid-zoom levels, such as missing rivers, shifting coastlines, islands that suddenly appear, and major water features that pop into detail abruptly rather than transitioning smoothly.\n\n### [The Invisible Costs of Routing: Privacy, Pricing, and Avoiding the \"MAU\" Trap](\u002Fblog\u002Finvisible-costs-of-routing-privacy-pricing-mau-trap\u002F)\n\nBeyond performance, the long-term viability of any motor vehicle routing project hinges on two \"invisible\" variables: data privacy architecture and billing predictability. Stadia Maps eliminates the risks of third-party data harvesting and \"MAU\"-based pricing traps by providing a private-by-design infrastructure and transparent, usage-only billing.\n\n### [Beyond the Car: Routing for the Other 90% of Transport](\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F)\n\nStandard \"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### [Why Basic OpenStreetMap Routing Needs Real-Time Traffic](\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F)\n\nOpenStreetMap (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---\n\n## What's Coming Next\n\nIn our next issue, we'll start a new blog series on Geocoding & Search and introduce a new feature highlighting some of our customers.\n\n*— Luke, Ian, and the entire Stadia Maps team*\n\n---\n\nHave feedback or questions? [We'd love to hear from you.](\u002Fsupport\u002F)\n",{"title":222,"description":223,"path":224,"published":225,"keywords":226,"rawbody":235},"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos","Stadia Maps geocoding and search APIs ingest continuous open data for rapid updates, multilingual search, and precision reverse geocoding.","\u002Fblog\u002Fopen-data-geocoding-global-search","2026-07-08",[199,227,228,229,230,231,232,233,234],"Geocoding API","Reverse Geocoding","Open Data","OpenStreetMap","Multilingual Search","Localization","On-Premise Geocoding","Location Search","---\ntitle: \"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos\"\ndescription: Stadia Maps geocoding and search APIs ingest continuous open data for rapid updates, multilingual search, and precision reverse geocoding.\nauthor: ian-wagner\nhead:\n  meta:\n    - property: og:image:width\n      content: \"1200\"\n    - property: og:image:height\n      content: \"630\"\n    - property: og:image:type\n      content: image\u002Fpng\n    - property: article:tag\n      content: Geocoding\n    - property: article:tag\n      content: Open Data\n    - property: article:tag\n      content: Reverse Geocoding\n    - property: article:tag\n      content: Localization\n    - property: article:tag\n      content: Location Search\nimage: \u002Fimages\u002Fog\u002Fglobal-search-proprietary-silo-og.png\nimageAlt: \"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos — Stadia Maps\"\nkeywords:\n  - Geocoding\n  - Geocoding API\n  - Reverse Geocoding\n  - Open Data\n  - OpenStreetMap\n  - Multilingual Search\n  - Localization\n  - On-Premise Geocoding\n  - Location Search\npublished: 2026-07-08\nsection: Geocoding\nseo:\n  title: \"Open Data Geocoding API: Global Search, Rapid Updates\"\n  ogTitle: The Geocoding Engine Built on Open Data, Not Black Boxes\n  description: Stadia Maps geocoding and search APIs ingest continuous open data for rapid updates, multilingual search, and precision reverse geocoding.\n---\n\n> Legacy mapping providers rely on static data captured during periodic drive-bys, creating a \"black box\" where errors can persist for years. Stadia Maps solves this by building living infrastructure that ingests continuous open and proprietary data streams, offering a transparent \"fix-it\" loop and rapid updates that proprietary silos cannot match.\n\n---\n\nLegacy mapping providers rely on data captured during periodic drive-bys, which can remain unverified for years. When the physical world changes, these APIs become a liability, leading to \"destination not found\" errors and broken logistics chains.\n\nAt Stadia Maps, we solve this by building **living infrastructure**. Instead of waiting for a fleet of sensor cars to pass through a neighborhood, we ingest continuous streams of open data for our [geocoding and search APIs](\u002Fproducts\u002Fgeocoding-search\u002F).\n\n## Rapid Turnaround and the \"Fix-it\" Loop\n\nProprietary datasets often feel like a black box. If an address is wrong or a new subdivision is missing, reporting the error can feel like shouting into a void. Stadia Maps changes this dynamic by leaning into the breadth of global contributors and open, official datasets.\n\n- **Data Corrections:** We include \"fix-it\" URLs for many records directly in our API responses. These links point users to datasets that accept contributions, enabling community-driven accuracy that commercial datasets can't match.\n- **Global Localization:** We collaborate on an open-source set of address templates that respect how people actually write addresses in their home countries.\n- **Rapid Geocoding Updates:** We refresh our geocoding data at least monthly to match our maps and routing services.\n\n## Localization Without the Friction\n\nSearch quality often takes a dive when switching between scripts. Handling non-Latin characters or searching for a Korean city using its English name are common pain points for global apps. Stadia Maps supports multilingual searching across all primary data layers, including Administrative Areas and Points of Interest (POIs).\n\nWhile we continue to refine partial matches in specific East Asian scripts, our current engine remains a benchmark for internationalization, helping global apps meet users where they are.\n\n## Precision Reverse Geocoding, Down to the Feature\n\n[Reverse geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) is the backbone of delivery and real estate apps. A \"close enough\" result isn't sufficient when an app needs to know exactly what's at a location — not just the nearest street. Because we ingest a massive variety of data sources, we identify extremely granular features. For enterprise teams with strict security or latency requirements, we even offer this entire geocoding engine for [on-premise usage](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F).\n\n## What's Next?\n\nWe are currently planning and building features that make the switch to Stadia Maps a no-brainer for enterprise teams:\n\n- **Revamped Categorical Search:** Expect more granular detail in specialized searches, such as \"Sushi restaurants,\" ranked by distance and relevance.\n- **Deeper Internationalization:** Our team is expanding English-name search to include road names globally, bridging the gap for international logistics.\n\n---\n\nWant to learn more about what we're working on? [Contact our engineering team](mailto\\:entsales@stadiamaps.com) to discuss your specific enterprise requirements.\n",{"title":237,"description":238,"path":239,"published":240,"keywords":241,"rawbody":243},"The Stadia Maps Newsletter №16 – September 2026","Billing alerts land in the dashboard, a new Shadowmap customer story, meetup sponsorships, and the latest blog posts on water labels, open data search, and routing.","\u002Fblog\u002Fseptember-2026-newsletter","2026-09-02",[194,242,195,198,199,219],"Billing Alerts","---\ntitle: The Stadia Maps Newsletter №16 – September 2026\ndescription: Billing alerts land in the dashboard, a new Shadowmap customer story, meetup sponsorships, and the latest blog posts on water labels, open data search, and routing.\nimage: \u002Fimages\u002Fog\u002Fseptember-2026-newsletter.png\nimageAlt: \"The Stadia Maps Newsletter #16 – September 2026\"\nkeywords:\n  - Stadia Maps Newsletter\n  - Billing Alerts\n  - Mapping Infrastructure\n  - Routing APIs\n  - Geocoding\n  - Developer Platform\npublished: 2026-09-02\nsection: Newsletter\nseo:\n  title: \"Stadia Maps Newsletter #16 | September 2026 Updates\"\n  description: \"Latest from Stadia Maps: billing alerts for API usage, the Shadowmap customer story, meetup sponsorships, and new posts on water labels and open data search.\"\n---\n\n---\n\n## Introducing Billing Alerts to Keep Your API Costs in Check\n\nYou can now set usage thresholds in your [Stadia Maps dashboard](https:\u002F\u002Fclient.stadiamaps.com\u002F) and get notified when you approach your chosen percentage of included credits. Billing alerts help you monitor your API consumption and stay informed about your usage patterns. Here's how it looks:\n\n![The billing alerts settings screen in the Stadia Maps dashboard, showing a usage threshold set as a percentage of included credits](\u002Fimages\u002Fcontent\u002Falerts-screenshot.png){style=\"display: block; margin-inline: auto; width: 100%; max-width: 900px;\"}\n\n## Explore Our Platform\n\n- [API Documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002F)\n- [Platform Features & Overview](\u002Fproducts\u002F)\n- [Company Blog](\u002Fblog\u002F)\n\n[Don't have an account? Create one today.](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F)\n\n---\n\n## How Shadowmap Powers Sunlight Simulation at Global Scale\n\nStarting from a thesis and a crisis, Georg Molzer built Shadowmap into a 3D sunlight simulation used by more than 700,000 people a month, and the engine behind Redfin's sunlight scores. [Our latest customer story explains how Stadia Maps helps.](\u002Fcustomer-stories\u002Fshadowmap\u002F)\n\n---\n\n## Let Us Sponsor Your Meetup\n\nRunning a meetup means covering the costs of the venue, food, WiFi, and more. Stadia Maps customers who organize a meetup can now get up to $200 toward whatever the event needs, and meetup attendees get a 14-day trial of Stadia Maps Professional. [Learn more.](\u002Fmeetup-sponsorships\u002F)\n\n---\n\n## Give Us 10 Minutes (or Less), Get Some Stickers\n\nReviews help people find and choose Stadia Maps. Write us a review (good or bad) on G2, then email a screenshot and your postal address to \u003Csupport@stadiamaps.com>, and we'll send you a pack of stickers anywhere in the world. If you already use a similar site that collects reviews, use that instead. You'll get stickers either way. [Leave a review.](https:\u002F\u002Fwww.g2.com\u002Fproducts\u002Fstadia-maps-location-platform\u002Freview_modalities\u002Fnew)\n\n---\n\n## Latest From Our Blog\n\n### [Water Labels Reworked: Cleaner Names, Smarter Placement, and Straits at Last](\u002Fblog\u002Fwater-labels-reworked-cleaner-names-smarter-placement\u002F)\n\nAround 71% of the Earth's surface is covered in water. It's not something everyone thinks about when they look at their maps, but bodies of water also provide important locational context. We're reworking our cartography from the ground up. Our chief architect, Ian Wagner, shares some details about our recent overhaul of water name labeling.\n\n### [The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos](\u002Fblog\u002Fopen-data-geocoding-global-search\u002F)\n\nLegacy mapping providers rely on static data captured during periodic drive-bys, creating a \"black box\" where errors can persist for years. We solve this by building living infrastructure that ingests continuous open and proprietary data streams, offering a transparent \"fix-it\" loop and rapid updates that proprietary silos can't match.\n\n### [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F)\n\nStructured search, reverse geocoding, and autocomplete across more than 1 billion locations, aggregated from open data. No user tracking, and no ad-network bias shaping which results come back first.\n\n### [Why Basic OpenStreetMap Routing Needs Real-Time Traffic](\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F)\n\nOpenStreetMap 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---\n\n## What's Coming Next\n\nIn our next issue, we'll continue to highlight our customers, provide updates to Stadia x Stamen Map Styles, and more.\n\n*— Luke, Ian, and the entire Stadia Maps team*\n\n---\n\nHave feedback or questions? [We'd love to hear from you.](\u002Fsupport\u002F)\n",1794385877450]