[{"data":1,"prerenderedAt":219},["ShallowReactive",2],{"blog-\u002Fblog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding\u002F":3,"related-blog-\u002Fblog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding\u002F":180},{"id":4,"title":5,"abstract":6,"author":6,"body":7,"description":164,"excerpt":6,"extension":165,"head":6,"image":6,"keywords":166,"meta":172,"modified":6,"navigation":173,"path":174,"proficiencyLevel":6,"published":175,"rawbody":176,"schemaOrg":6,"schemaType":6,"seo":177,"stem":178,"__hash__":179},"blog\u002Fblog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding.md","Bulk Geocoding API Is Now Available",null,{"type":8,"value":9,"toc":155},"minimark",[10,14,27,32,47,50,53,57,65,69,89,93],[11,12,5],"h1",{"id":13},"bulk-geocoding-api-is-now-available",[15,16,17,18,26],"p",{},"Since we launched our geocoding product,\nwe've learned a lot about what developers need to build applications that convert addresses, places, and more to coordinates.\nWhile we've always supported forward, reverse, and structured queries,\none thing we haven't supported is making multiple queries in one request.\nBulk (also known as batch) geocoding makes it faster and simpler to geocode many addresses at once.\nWhether supporting a batch job or improving performance of multiple simultaneous requests,\nour new ",[19,20,25],"a",{"href":21,"rel":22,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement&utm_content=bulk_intro",[23],"external","_blank","Bulk Geocoding API"," helps developers build more efficient solutions based on the same, high-quality Geocoding API they already know.",[28,29,31],"h2",{"id":30},"make-up-to-5000-queriessimultaneously","Make up to 5000 Queries—Simultaneously",[15,33,34,35,40,41,46],{},"With the new API, you can make up to 5,000 geocoding queries with a single HTTP request.\nBoth ",[19,36,39],{"href":37,"rel":38,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement",[23],"forward geocoding","\nand ",[19,42,45],{"href":43,"rel":44,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement",[23],"structured geocoding","\nare supported. You can even combine multiple requests types in a single bulk request!",[15,48,49],{},"By using the bulk endpoint instead of individual requests, your queries will be faster.\nThe endpoints' internal parallelization will simultaneously improve throughput, reduce total latency, and simplify the calling code.\nThis new endpoint is useful in environments without easy access to lightweight concurrency and connection pooling,\nwhere each request incurs the connection establishment overhead.\nOlder web frameworks, lower-level code, and shell scripts will especially benefit from opting for the bulk endpoint over the standard endpoints.",[15,51,52],{},"For particularly latency sensitive applications, you can also process the results as they are produced.\nThe endpoint streams the results back as a JSON body, enabling much lower time-to-first-result if required.",[28,54,56],{"id":55},"the-same-simple-affordable-pricing","The Same Simple, Affordable Pricing",[15,58,59,60,64],{},"Bulk geocoding is available for all accounts subscribed to our Standard and Professional plans.\nEach request consumes credits as if you made a request to underlying endpoint directly,\nso there's no additional fees or credits used.\nYou can find how many credits each API call consumes in our ",[19,61,63],{"href":62},"\u002Fpricing\u002F#credit-schedule","credit schedule",".",[28,66,68],{"id":67},"available-in-our-sdks-curl-and-everything-in-between","Available in our SDKs, cURL, and Everything In-Between",[15,70,71,72,77,78,82,83,88],{},"As usual, our official ",[19,73,76],{"href":74,"rel":75,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement#apis",[23],"SDKs"," are already updated with support for the new API.\nYou can access it from JavaScript, Python, Kotlin, Swift or PHP without writing any new network or parsing code!\nYou can even find a ",[79,80,81],"code",{},"curl"," example in our ",[19,84,87],{"href":85,"rel":86,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement&utm_content=available_everywhere",[23],"API documentation"," so your shell scripts aren't left behind.",[28,90,92],{"id":91},"learn-more-next-steps","Learn More & Next Steps",[94,95,96,105,113,128],"ul",{},[97,98,99,104],"li",{},[19,100,103],{"href":101,"rel":102,"target":24},"https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_medium=blog&utm_campaign=bulk_geocoding_accounement",[23],"Create an account"," to get an API key. You can start building today without a credit card!",[97,106,107,108,64],{},"Read the ",[19,109,112],{"href":110,"rel":111,"target":24},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement&utm_content=bulk_next_steps",[23],"bulk geocoding API documentation and sample code",[97,114,115,116,121,122,127],{},"Join our community on ",[19,117,120],{"href":118,"rel":119,"target":24},"https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT",[23],"Discord"," or ",[19,123,126],{"href":124,"rel":125,"target":24},"https:\u002F\u002Fslack.openstreetmap.us\u002F",[23],"Slack"," to share what you're working on or get help.",[97,129,130,131,136,137,142,143,148,149,154],{},"Follow us on ",[19,132,135],{"href":133,"rel":134,"target":24},"https:\u002F\u002Fen.osm.town\u002F@stadiamaps",[23],"Mastodon",", ",[19,138,141],{"href":139,"rel":140,"target":24},"https:\u002F\u002Ftwitter.com\u002F@stadiamaps",[23],"Twitter",", or\n",[19,144,147],{"href":145,"rel":146,"target":24},"https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F",[23],"LinkedIn",", or sign-up for our ",[19,150,153],{"href":151,"rel":152,"target":24},"https:\u002F\u002Feepurl.com\u002Fgs51fD",[23],"mailing list"," to stay up to date.",{"title":156,"searchDepth":157,"depth":157,"links":158},"",4,[159,161,162,163],{"id":30,"depth":160,"text":31},2,{"id":55,"depth":160,"text":56},{"id":67,"depth":160,"text":68},{"id":91,"depth":160,"text":92},"Announcing Bulk Geocoding: we're making it easier to geocode large datasets with our bulk geocoding API.","md",[167,168,169,170,171],"Bulk Geocoding","Batch Processing","Address Lookup","Geocoding API","Data Processing",{},true,"\u002Fblog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding","2024-08-23","---\ndescription: \"Announcing Bulk Geocoding: we're making it easier to geocode large datasets with our bulk geocoding API.\"\npublished: \"2024-08-23\"\nkeywords:\n  - Bulk Geocoding\n  - Batch Processing\n  - Address Lookup\n  - Geocoding API\n  - Data Processing\n---\n\n# Bulk Geocoding API Is Now Available\n\nSince we launched our geocoding product, \nwe've learned a lot about what developers need to build applications that convert addresses, places, and more to coordinates. \nWhile we've always supported forward, reverse, and structured queries, \none thing we haven't supported is making multiple queries in one request.\nBulk (also known as batch) geocoding makes it faster and simpler to geocode many addresses at once.\nWhether supporting a batch job or improving performance of multiple simultaneous requests,\nour new [Bulk Geocoding API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement&utm_content=bulk_intro){ target=\"_blank\" } helps developers build more efficient solutions based on the same, high-quality Geocoding API they already know.\n\n## Make up to 5000 Queries—Simultaneously\n\nWith the new API, you can make up to 5,000 geocoding queries with a single HTTP request. \nBoth [forward geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement){ target=\"_blank\" }\nand [structured geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement){ target=\"_blank\" }\nare supported. You can even combine multiple requests types in a single bulk request!\n\nBy using the bulk endpoint instead of individual requests, your queries will be faster. \nThe endpoints' internal parallelization will simultaneously improve throughput, reduce total latency, and simplify the calling code.\nThis new endpoint is useful in environments without easy access to lightweight concurrency and connection pooling, \nwhere each request incurs the connection establishment overhead. \nOlder web frameworks, lower-level code, and shell scripts will especially benefit from opting for the bulk endpoint over the standard endpoints.\n\nFor particularly latency sensitive applications, you can also process the results as they are produced. \nThe endpoint streams the results back as a JSON body, enabling much lower time-to-first-result if required.\n\n## The Same Simple, Affordable Pricing\n\nBulk geocoding is available for all accounts subscribed to our Standard and Professional plans.\nEach request consumes credits as if you made a request to underlying endpoint directly,\nso there's no additional fees or credits used.\nYou can find how many credits each API call consumes in our [credit schedule](\u002Fpricing\u002F#credit-schedule).\n\n## Available in our SDKs, cURL, and Everything In-Between\n\nAs usual, our official [SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement#apis){ target=\"_blank\" } are already updated with support for the new API.\nYou can access it from JavaScript, Python, Kotlin, Swift or PHP without writing any new network or parsing code!\nYou can even find a `curl` example in our [API documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement&utm_content=available_everywhere) so your shell scripts aren't left behind.\n\n## Learn More & Next Steps\n\n- [Create an account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_medium=blog&utm_campaign=bulk_geocoding_accounement) to get an API key. You can start building today without a credit card!\n- Read the [bulk geocoding API documentation and sample code](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=bulk_geocoding_accounement&utm_content=bulk_next_steps).\n- Join our community on [Discord](https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT) or [Slack](https:\u002F\u002Fslack.openstreetmap.us\u002F) to share what you're working on or get help.\n- Follow us on [Mastodon](https:\u002F\u002Fen.osm.town\u002F@stadiamaps), [Twitter](https:\u002F\u002Ftwitter.com\u002F@stadiamaps), or\n  [LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F), or sign-up for our [mailing list](https:\u002F\u002Feepurl.com\u002Fgs51fD) to stay up to date.\n",{"title":5,"description":164},"blog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding","9QlY8hF8wAh1471jY5wPoKPTWrLX5qsPyYlfQsGWlCk",[181,195,207],{"title":182,"description":183,"path":184,"published":185,"keywords":186,"rawbody":194},"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",[187,188,189,190,191,192,193],"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":196,"description":197,"path":198,"published":199,"keywords":200,"rawbody":206},"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",[201,202,203,204,205],"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",{"title":208,"description":209,"path":210,"published":199,"keywords":211,"rawbody":218},"75 Million More Addresses: Expanding Geocoding Precision","Our largest geocoding dataset expansion yet: 75 million new addresses from OpenAddresses, 3 million new POIs from Foursquare OS Places, smarter intent recognition, and new structured address fields (house_number, street, unit) on the v1 search API.","\u002Fblog\u002F75-million-more-addresses-geocoding-precision",[212,213,214,215,216,217],"Geocoding","Addresses","OpenAddresses","Foursquare OS Places","Structured Search","Points of Interest","---\ndescription: >-\n  Our largest geocoding dataset expansion yet: 75 million new addresses from OpenAddresses,\n  3 million new POIs from Foursquare OS Places, smarter intent recognition, and new\n  structured address fields (house_number, street, unit) on the v1 search API.\npublished: 2026-04-27\nkeywords:\n  - Geocoding\n  - Addresses\n  - OpenAddresses\n  - Foursquare OS Places\n  - Structured Search\n  - Points of Interest\n---\n\n# 75 Million More Addresses: Expanding Geocoding Precision\n\nInaccurate geocoding breaks the user experience. If your query returns a street-level guess instead of a rooftop coordinate, a user might be on the right street but the wrong block, or a delivery driver gets routed to an approximate centroid instead of a front door. The coordinates are \"close enough\" until they aren't, and your application takes the blame.\n\nWe continuously update our geocoding dataset as new address and POI data becomes available. This release is our largest expansion yet: 75 million new addresses, 3 million new points of interest, improved intent recognition, and a new way to query with structured address fields.\n\n## Rooftop-Level Accuracy at Scale\n\nThe bulk of this expansion comes from OpenAddresses, one of the largest open datasets of address-level coordinates. These aren't interpolated guesses along a road segment. They're rooftop-level points tied to individual parcels, which matters for any application that depends on precise placement: routing, last-mile logistics, property lookup.\n\nThe gains aren't spread evenly. France and the US lead with roughly 25 million new addresses each, followed by Germany with 3 million and notable expansions across Brazil, Australia, and Mexico. If you've been hitting street-level fallbacks in these regions, you should see noticeably better results.\n\n## Fresher Points of Interest\n\nPOI data goes stale quickly. A restaurant opens, a shop closes, a business moves across the street, and suddenly your search results are sending users to the wrong place. We've added 3 million POIs from Foursquare OS Places, bringing our dataset more in line with what's actually on the ground. Better coverage for the kinds of searches your users actually run: finding a specific restaurant, locating the nearest pharmacy, or navigating to a business that opened last month.\n\n## Smarter Search, Fewer Misses\n\nBeyond raw data, we've improved how our [\u002Fsearch APIs](https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002Fgeocoding-search\u002Fgeocoding\u002F) interpret what users actually mean. The changes focus on intent recognition: better handling of queries for larger geographic areas, complex or compound place names, and cases where the most obvious textual match isn't the right result.\n\nYour users should find more of what they're looking for on the first try.\n\n## Structured Address Input, Now on v1\n\nFor developers working with structured address data, this release adds `house_number`, `street`, and `unit` as first-class fields on the geocoding API. Previously, structured queries supported country, region, and postal code, but the address itself arrived as a single text field that we had to parse before running a match.\n\nIf your dataset is already structured that way, you can now pass it through directly. This is common for shipping, CRM, and property data. Queries with the new fields skip the parsing step entirely, which typically means better match quality and faster responses.\n\nThe free-text `address` field isn't going anywhere. If you only have a single string, we'll still parse it for you. The new fields are available on v1 today. Adopt them at your own pace.\n\n## No Tracking Required\n\nA common assumption in the industry is that better geocoding requires more user data: search history, device location, behavioral signals. We don't work that way. These improvements come from better source data and smarter algorithms, not from profiling your end users. Your users' queries are yours, not ours.\n\nAs with everything we build, these updates are available through standard APIs and SDKs, including MapLibre and Leaflet. Technical precision, fair pricing, and privacy are baked in from the start.\n\n## Get Started\n\nThe expanded dataset, structured address fields, and search improvements are live now for all Stadia Maps customers. New here? [Create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) and start geocoding.\n",1778676026040]