[{"data":1,"prerenderedAt":344},["ShallowReactive",2],{"blog-\u002Fblog\u002Fgeocoding-and-autocomplete-v2-updates-continue\u002F":3,"related-blog-\u002Fblog\u002Fgeocoding-and-autocomplete-v2-updates-continue\u002F":312},{"id":4,"title":5,"abstract":6,"author":6,"body":7,"description":296,"excerpt":6,"extension":297,"head":6,"image":6,"keywords":298,"meta":304,"modified":6,"navigation":305,"path":306,"proficiencyLevel":6,"published":307,"rawbody":308,"schemaOrg":6,"schemaType":6,"seo":309,"stem":310,"__hash__":311},"blog\u002Fblog\u002Fgeocoding-and-autocomplete-v2-updates-continue.md","Enriching Geocoding & Search: More Data, Smarter Deduplication, and Forward & Reverse v2",null,{"type":8,"value":9,"toc":279},"minimark",[10,14,18,37,42,45,57,61,64,76,79,82,86,96,102,106,109,126,130,141,145,148,152,164,168,171,201,204,207,212,221,224,228,231],[11,12,5],"h1",{"id":13},"enriching-geocoding-search-more-data-smarter-deduplication-and-forward-reverse-v2",[15,16,17],"p",{},"On the heels of our last geocoding update for our Autocomplete and Place Details endpoints,\nwe're excited to announce another major update to Geocoding & Search:",[19,20,21,25,28,31,34],"ul",{},[22,23,24],"li",{},"v2 of our Forward and Reverse geocoding endpoints,",[22,26,27],{},"label improvements for v1 endpoints,",[22,29,30],{},"enhancements to Autocomplete deduplication,",[22,32,33],{},"a collection of multi-language improvements,",[22,35,36],{},"and another significant Foursquare OS Places update.",[38,39,41],"h2",{"id":40},"new-address-delimiter-parsing-in-forward-geocoding","New Address Delimiter Parsing in Forward Geocoding",[15,43,44],{},"We've improved how we handle delimiters for house and building numbers, and their different ways they are represented around the world.",[15,46,47,48,52,53,56],{},"With this update,\nyou can now easily and more accurately search for addresses such as ",[49,50,51],"code",{},"Telliskivi 60a\u002F3, Tallinn"," or ",[49,54,55],{},"Kossuth Lajos utca 20. IV\u002F15, 1053 Budapest, Hungary",".",[38,58,60],{"id":59},"improved-regional-context-with-reverse-geocoding","Improved Regional Context with Reverse Geocoding",[15,62,63],{},"Full contextual hierarchy is now available in all Reverse Geocoding responses,\nproviding a straightforward path when you care about the context rather than a specific physical feature (e.g., in coarse lookups).",[15,65,66,67,70,71,75],{},"Previously,\nthe ",[49,68,69],{},"\u002Freverse"," endpoint behavior depended on which layers you explicitly included.\nWhen searching for an address, street, or venue (POI),\nwe served up the full context: locality, region, country, and so on.\nBut for a coarse lookup,\nthe API only included layers you ",[72,73,74],"em",{},"explicitly"," specified and dropped everything else (e.g., country code).",[15,77,78],{},"We have fixed this in both v1 and v2,\nand all responses include a complete contextual hierarchy,\nregardless of your search.\nThis response style matches the way our other search endpoints work and does not break any assumptions about result ordering.",[15,80,81],{},"With v2, just like v1, you'll receive the most granular layer result first based on your query.",[38,83,85],{"id":84},"better-label-responses-in-v1-endpoints","Better Label Responses in v1 Endpoints",[15,87,88,89,92,93,56],{},"Labels generated from the Who's on First source are now much more sensible for places across the globe.\nFor instance, where the API used to return ",[49,90,91],{},"Seoul, Yongsan-gu, Seoul, South Korea",",\nwe now simply return ",[49,94,95],{},"Seoul, South Korea",[15,97,98,99,56],{},"All v1 APIs now include this improvement except ",[49,100,101],{},"\u002Fv1\u002Fsearch\u002Fstructured",[38,103,105],{"id":104},"deduplication-and-more-relevance-in-autocomplete","Deduplication and More Relevance in Autocomplete",[15,107,108],{},"Our Autocomplete API enables seamless searching across many sources,\nincluding Foursquare OS Places, Geonames, OpenStreetMap, OpenAddresses, and Who's On First.\nWhile using such a broad range of sources ensures we have the best global coverage,\nit presents a deduplication problem when a location is present in multiple sources.\nWith our smarter deduplication process,\nwe’ve eliminated duplicate results across a range of location types:",[19,110,111,114,117,120,123],{},[22,112,113],{},"Tighter deduplication of addresses across our datasets;",[22,115,116],{},"Leveraging the ease of edits in OpenStreetMap, OSM addresses are now preferred over other sources when there is a collision;",[22,118,119],{},"More relevant results for focused searches, especially when searching for dense chains like 7-Eleven or Starbucks;",[22,121,122],{},"East Asian language deduplication improvements when comparing inconsistent naming between sources;",[22,124,125],{},"Better deduplication of place names with exotic Unicode representation (e.g., a stylized \"𝐀𝐂𝐌𝐄, 𝐈𝐍𝐂.\" is considered the same as \"ACME, Inc.\")",[38,127,129],{"id":128},"multi-language-query-improvements","Multi-Language Query Improvements",[15,131,132,133,136,137,140],{},"We updated the v1 and v2 ",[49,134,135],{},"\u002Fsearch"," endpoint to take into account the ",[49,138,139],{},"lang"," parameter when querying for POIs,\nimproving the quality of multilingual name searches.\nPreviously, if you were querying POI names in another language (e.g., the English name of a cafe whose primary name is Korean),\nyou would receive zero results when using Search.",[38,142,144],{"id":143},"foursquare-os-places-update","Foursquare OS Places Update",[15,146,147],{},"We have now included an additional 8 million places from Foursquare OS Places,\nbringing the total number of available POIs from Foursquare to about 14 million.",[38,149,151],{"id":150},"available-today","Available Today",[15,153,154,155,163],{},"All of these improvements are available for you today!\nIf you're using our ",[156,157,162],"a",{"href":158,"rel":159,"target":161},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement&utm_content=sdk_cta",[160],"external","_blank","SDKs",",\nupdate to the latest version.",[38,165,167],{"id":166},"learn-more-and-get-started","Learn More and Get Started",[15,169,170],{},"Ready to experience the power of Geocoding & Search v2?\nHere are some helpful resources to get you started:",[19,172,173,180,187,194],{},[22,174,175],{},[156,176,179],{"href":177,"rel":178,"target":161},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement#autocomplete-search",[160],"Autocomplete Search SDKs",[22,181,182],{},[156,183,186],{"href":184,"rel":185,"target":161},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement&utm_content=sdk_reference",[160],"API Clients\u002FSDKs",[22,188,189],{},[156,190,193],{"href":191,"rel":192,"target":161},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fv2-api-migration-guide\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement",[160],"v2 Migration Guide for Developers",[22,195,196],{},[156,197,200],{"href":198,"rel":199,"target":161},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement&utm_content=foursquare_beta_next_steps",[160],"Geocoding Documentation",[15,202,203],{},"We're confident Geocoding & Search v2 will significantly enhance your ability to build location-aware applications.\nWith more data and improved results,\nit's never been a better time to leverage the power of location with Stadia Maps.",[15,205,206],{},"Start exploring today and unlock the full potential of location search in your current or next project!",[208,209,211],"h3",{"id":210},"account-and-api-key","Account and API Key",[15,213,214,215,220],{},"If you don’t already have an account,\n",[156,216,219],{"href":217,"rel":218,"target":161},"https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement",[160],"create an account"," to start building today—no credit card is required.",[222,223],"hr",{},[38,225,227],{"id":226},"stadia-maps-community","Stadia Maps Community",[15,229,230],{},"Stay connected with Stadia Maps:",[19,232,233,247],{},[22,234,235,236,52,241,246],{},"Join our community on ",[156,237,240],{"href":238,"rel":239,"target":161},"https:\u002F\u002Fdiscord.gg\u002FqRBy6qqtdT",[160],"Discord",[156,242,245],{"href":243,"rel":244,"target":161},"https:\u002F\u002Fslack.openstreetmap.us\u002F",[160],"Slack"," to share what you're working on or get help.",[22,248,249,250,255,256,255,261,266,267,272,273,278],{},"Follow us on ",[156,251,254],{"href":252,"rel":253,"target":161},"https:\u002F\u002Fen.osm.town\u002F@stadiamaps",[160],"Mastodon",", ",[156,257,260],{"href":258,"rel":259,"target":161},"https:\u002F\u002Ftwitter.com\u002F@stadiamaps",[160],"Twitter",[156,262,265],{"href":263,"rel":264,"target":161},"https:\u002F\u002Fbsky.app\u002Fprofile\u002Fstadiamaps.com",[160],"BlueSky",", or ",[156,268,271],{"href":269,"rel":270,"target":161},"https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F",[160],"LinkedIn",", or sign up for our ",[156,274,277],{"href":275,"rel":276,"target":161},"https:\u002F\u002Feepurl.com\u002Fgs51fD",[160],"mailing list"," to stay up to date.",{"title":280,"searchDepth":281,"depth":281,"links":282},"",4,[283,285,286,287,288,289,290,291,295],{"id":40,"depth":284,"text":41},2,{"id":59,"depth":284,"text":60},{"id":84,"depth":284,"text":85},{"id":104,"depth":284,"text":105},{"id":128,"depth":284,"text":129},{"id":143,"depth":284,"text":144},{"id":150,"depth":284,"text":151},{"id":166,"depth":284,"text":167,"children":292},[293],{"id":210,"depth":294,"text":211},3,{"id":226,"depth":284,"text":227},"Our latest geocoding update includes v2 of Forward and Reverse endpoints, smarter deduplication, better multi-language support, and more Foursquare OS Places data.","md",[299,300,301,302,303],"Geocoding","Reverse Geocoding","Forward Geocoding","API Update","Foursquare",{},true,"\u002Fblog\u002Fgeocoding-and-autocomplete-v2-updates-continue","2025-07-01","---\ndescription: \"Our latest geocoding update includes v2 of Forward and Reverse endpoints, smarter deduplication, better multi-language support, and more Foursquare OS Places data.\"\npublished: \"2025-07-01\"\nkeywords:\n  - Geocoding\n  - Reverse Geocoding\n  - Forward Geocoding\n  - API Update\n  - Foursquare\n---\n\n# Enriching Geocoding & Search: More Data, Smarter Deduplication, and Forward & Reverse v2\n\nOn the heels of our last geocoding update for our Autocomplete and Place Details endpoints, \nwe're excited to announce another major update to Geocoding & Search:\n\n* v2 of our Forward and Reverse geocoding endpoints, \n* label improvements for v1 endpoints,\n* enhancements to Autocomplete deduplication, \n* a collection of multi-language improvements, \n* and another significant Foursquare OS Places update.\n\n## New Address Delimiter Parsing in Forward Geocoding\n\nWe've improved how we handle delimiters for house and building numbers, and their different ways they are represented around the world.\n\nWith this update, \nyou can now easily and more accurately search for addresses such as `Telliskivi 60a\u002F3, Tallinn` or `Kossuth Lajos utca 20. IV\u002F15, 1053 Budapest, Hungary`.\n\n## Improved Regional Context with Reverse Geocoding\n\nFull contextual hierarchy is now available in all Reverse Geocoding responses,\nproviding a straightforward path when you care about the context rather than a specific physical feature (e.g., in coarse lookups).\n\nPreviously, \nthe `\u002Freverse` endpoint behavior depended on which layers you explicitly included.\nWhen searching for an address, street, or venue (POI),\nwe served up the full context: locality, region, country, and so on.\nBut for a coarse lookup,\nthe API only included layers you _explicitly_ specified and dropped everything else (e.g., country code).\n\nWe have fixed this in both v1 and v2, \nand all responses include a complete contextual hierarchy,\nregardless of your search.\nThis response style matches the way our other search endpoints work and does not break any assumptions about result ordering.\n\nWith v2, just like v1, you'll receive the most granular layer result first based on your query.\n\n## Better Label Responses in v1 Endpoints\n\nLabels generated from the Who's on First source are now much more sensible for places across the globe.\nFor instance, where the API used to return `Seoul, Yongsan-gu, Seoul, South Korea`,\nwe now simply return `Seoul, South Korea`.\n\nAll v1 APIs now include this improvement except `\u002Fv1\u002Fsearch\u002Fstructured`.\n\n## Deduplication and More Relevance in Autocomplete\n\nOur Autocomplete API enables seamless searching across many sources,\nincluding Foursquare OS Places, Geonames, OpenStreetMap, OpenAddresses, and Who's On First.\nWhile using such a broad range of sources ensures we have the best global coverage,\nit presents a deduplication problem when a location is present in multiple sources.\nWith our smarter deduplication process,\nwe’ve eliminated duplicate results across a range of location types:\n\n* Tighter deduplication of addresses across our datasets;  \n* Leveraging the ease of edits in OpenStreetMap, OSM addresses are now preferred over other sources when there is a collision;  \n* More relevant results for focused searches, especially when searching for dense chains like 7-Eleven or Starbucks;  \n* East Asian language deduplication improvements when comparing inconsistent naming between sources;  \n* Better deduplication of place names with exotic Unicode representation (e.g., a stylized \"𝐀𝐂𝐌𝐄, 𝐈𝐍𝐂.\" is considered the same as \"ACME, Inc.\")\n\n## Multi-Language Query Improvements\n\nWe updated the v1 and v2 `\u002Fsearch` endpoint to take into account the `lang` parameter when querying for POIs,\nimproving the quality of multilingual name searches.\nPreviously, if you were querying POI names in another language (e.g., the English name of a cafe whose primary name is Korean),\nyou would receive zero results when using Search.\n\n## Foursquare OS Places Update\n\nWe have now included an additional 8 million places from Foursquare OS Places,\nbringing the total number of available POIs from Foursquare to about 14 million.\n\n## Available Today\n\nAll of these improvements are available for you today!\nIf you're using our [SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement&utm_content=sdk_cta),\nupdate to the latest version.\n\n## Learn More and Get Started\n\nReady to experience the power of Geocoding & Search v2?\nHere are some helpful resources to get you started:\n\n* [Autocomplete Search SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement#autocomplete-search)  \n* [API Clients\u002FSDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement&utm_content=sdk_reference)  \n* [v2 Migration Guide for Developers](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fv2-api-migration-guide\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement)  \n* [Geocoding Documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement&utm_content=foursquare_beta_next_steps)\n\nWe're confident Geocoding & Search v2 will significantly enhance your ability to build location-aware applications.\nWith more data and improved results,\nit's never been a better time to leverage the power of location with Stadia Maps.\n\nStart exploring today and unlock the full potential of location search in your current or next project!\n\n### Account and API Key\n\nIf you don’t already have an account,\n[create an account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=geocoding_v2_improvements_announcement) to start building today—no credit card is required.\n\n---\n\n## Stadia Maps Community\n\nStay connected with Stadia Maps:\n\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), [BlueSky](https:\u002F\u002Fbsky.app\u002Fprofile\u002Fstadiamaps.com), or [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":296},"blog\u002Fgeocoding-and-autocomplete-v2-updates-continue","beUtzdbAtu9GeBSvg2SvA62JIg59q6Lhy3GWpYFqCrM",[313,323,332],{"title":314,"description":315,"path":316,"published":317,"keywords":318,"rawbody":322},"Introducing Stadia Maps Geocoding & Search v2: Supercharge Your Search","Smarter, faster, cheaper Search is here!  We're adding 14M+ new places & addresses,  serving faster & more accurate results,  reducing autocomplete costs by 80%,  and making forward geocoding available for everyone.","\u002Fblog\u002Fintroducing-stadia-maps-geocoding-search-v2","2025-04-08",[299,319,302,320,321],"Autocomplete Search","Place Search","Address Search","---\npublished: \"2025-04-08\"\ndescription: >- \n  Smarter, faster, cheaper Search is here! \n  We're adding 14M+ new places & addresses, \n  serving faster & more accurate results, \n  reducing autocomplete costs by 80%, \n  and making forward geocoding available for everyone.\nkeywords:\n  - Geocoding\n  - Autocomplete Search\n  - API Update\n  - Place Search\n  - Address Search\n---\n\n# Introducing Stadia Maps Geocoding & Search v2: Supercharge Your Search\n\nAt Stadia Maps, we're dedicated to helping millions of users find their perfect starting point every month with our powerful Autocomplete Search.\nToday, we're thrilled to announce a significant upgrade: Geocoding & Search v2!\n\nThe latest version of [Stadia Maps Geocoding & Search](\u002Fproducts\u002Fgeocoding-search\u002F) isn't just an incremental update; \nit's a significant leap forward. \nWe've integrated millions more places and addresses, \nachieved faster API responses, \nand delivered better, more relevant results with enhanced language support—especially for non-English queries.\n\nAdditionally, we're introducing a new API and billing structure for Autocomplete, \ndesigned to make this essential feature even more accessible. \nThis new structure enables us to reduce the cost of a typical session by almost 80%, \nmaking it more affordable for everyone.\n\nAnd that's not all!\nWe're also making Geocoding & Search more accessible for everyone.\n[Forward Geocoding](\u002Fproducts\u002Fgeocoding-search\u002Fgeocoding\u002F) and\n[Place Details](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fplace-details\u002F?utm_source=marketing_site&utm_campaign=geocoding_v2_launch_announcement) \nare now available to all users, even if you're on the Free plan.\n\n## More Data, More Possibilities\n\nWe're all about providing you with the most comprehensive and accurate location data. \nWith Geocoding & Search v2, we've significantly expanded our horizons:\n\n* **Expanded address coverage:** We've added 4 million more addresses worldwide.\n  What does this mean for you? Simply put, more people will be able to find the exact addresses they're looking for.\n\n* **Foursquare integration:** \n  We've integrated [Foursquare's Places](https:\u002F\u002Fstadiamaps.com\u002Fblog\u002Fgeocoding-foursquare-beta\u002F) dataset, \n  adding over 10 million records to our existing robust sources (OpenStreetMap, OpenAddresses, and GeoNames). \n  By carefully integrating and deduplicating this massive dataset, \n  we're enriching our place information and ensuring you get the most comprehensive results.\n\n## Smarter Pricing for Autocomplete: Making It Even More Affordable\n\nWe understand that efficient and cost-effective tools are crucial. \nThat's why we've completely revamped our Autocomplete pricing model to better align with the value it delivers, \nmaking it a smart investment for your business.\n\n* **Nominal costs while typing:** While a user searches, each API call will now cost only 1 credit (down from 20\n  credits!). This means you can provide instant feedback to your users without worrying about high costs.\n\n* **Standard cost on selection:** Once the user selects a result, you can easily retrieve the full details using the\n  `\u002Fplace_details` endpoint, and the standard cost of 20 credits will apply.\n\nThis fundamental shift in pricing makes our powerful Autocomplete endpoints accessible to a wider range of users and\napplications, and—finally—the economics make sense.\n\n## Better Results: Improved Accuracy, Relevance, and Language Precision\n\nWe're committed to delivering the best possible search experience.\nWith Geocoding & Search v2, you'll notice significant improvements in result quality.\n\n* **Enhanced multilingual support:** We improved accuracy and relevance when searching in languages other than English,\n  ensuring a more inclusive and comprehensive search experience for all users.\n\n* **Smarter Deduplication:** We've tackled the tricky issue of deduplicating similar Points of Interest (POIs). \n  We've squashed bugs and implemented smarter logic, \n  resulting in a cleaner and more intuitive search experience for all searches.\n\n* **Reduced Bias for English:** We've removed the assumption of English as the default language, meaning requests\n  without a `lang` query parameter or an `Accept-Language` header will yield more accurate results in the relevant local\n  language.\n\n* **Foursquare Data Advantage:** Integrating Foursquare data provides us with richer information about each place,\n  allowing us to understand and conflate data from various sources better, ultimately leading to more relevant and\n  informative results.\n\n* **Better, Faster Responses**: The v2 autocomplete endpoint includes a streamlined response format with everything you\n  need to build the UI and an ID you can use to look up the full details.\n\n## What's Next?\n\nThis is just the beginning! We're excited about the future of Stadia Maps Geocoding & Search. \nHere's a sneak peek into what else we’re working on.\n\n* **Additional endpoints:** The rest of our Geocoding endpoints will also be upgraded to v2, benefiting from the new\n  infrastructure and improvements.\n\n* **Continued improvements for v1:** We're not forgetting our existing Geocoding & Search v1 users. We’ve already rolled\n  out many of the improvements to v1, and we will continue applying as many improvements as possible to the current\n  endpoints, ensuring everyone benefits from our enhanced data.\n\n* **Updated SDKs:** We have already updated our SDKs to use the new Autocomplete API.\n  Upgrade today to start saving!\n\n* **More datasets:** We're constantly exploring and integrating new datasets further to enhance the accuracy and\n  coverage of our services.\n\n## Learn More and Get Started\n\nReady to experience the power of Geocoding & Search v2? Here are some helpful resources:\n\n* [Autocomplete Search SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_campaign=geocoding_v2_launch_announcement#autocomplete-search)\n* [API Clients](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F)\n* [Transition Guide for Developers](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fv2-api-migration-guide\u002F?utm_source=marketing_site&utm_campaign=geocoding_v2_launch_announcement)\n\nWe're confident that Geocoding & Search v2 will significantly enhance how you build location-aware applications. \nWith more data, smarter pricing, and better results, it's never been a better time to leverage the power of Stadia Maps.\n\nStart exploring today and unlock the full potential of location search!",{"title":324,"description":325,"path":326,"published":327,"keywords":328,"rawbody":331},"Announcing Foursquare OS Places Beta","Our latest geocoding update includes more data, smarter searches, and better localization.","\u002Fblog\u002Fgeocoding-foursquare-beta","2025-02-19",[299,303,329,320,330],"POI Data","Location Data","---\ndescription: \"Our latest geocoding update includes more data, smarter searches, and better localization.\"\npublished: \"2025-02-19\"\nkeywords:\n  - Geocoding\n  - Foursquare\n  - POI Data\n  - Place Search\n  - Location Data\n---\n\n# Announcing Foursquare OS Places Beta\n\nOur geocoding and autocomplete search APIs provide fast and accurate place-to-coordinate matching.\nStarting today, with our latest geocoding update, we are including even more data, smarter searches, and better localization for our users.\n\n## Millions of new POIs with Foursquare OS Places data\n\nWe're excited to introduce Foursquare as a new data source,\nbringing even richer location data and improved search capabilities to all of our geocoding endpoints.\nWith this update, we have unlocked access to millions of new points of interest worldwide,\nmaking it easier for you to find the places you are looking for.\n\nSince we're launching this as beta data source, you'll need to opt in to participate.\nTo opt in, just add `foursquare` as a source in your request.\nAnd just like other open data sources, you can submit corrections if you find a mistake\n(we'll pick them up in our next update)!\nCheck out the Foursquare's [Placemaker program page](https:\u002F\u002Fopensource.foursquare.com\u002Fplacemaker\u002F) for details.\n\n## Expanded Localization\n\nOur geocoding and search APIs can return place names in dozens of languages.\nThis update expands our localized name coverage with more than 250,000 additional place names.\nWhichever language your users speak, they'll see better results.\n\n## Smarter Fuzzy Search and Interpolation\n\nWe fine-tuned our search capabilities to better handle house numbers with letters (e.g. 13L)\nand varied postal code spacing,\nensuring more accurate matches and prioritized results.\n\nSimilarly, we have also enhanced our address interpolation,\nmaking results even more precise when exact house numbers aren't available.\n\n## Available Today\n\nAll of these improvements are available immediately!\nIf you're using our [SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=foursquare_beta_announcement&utm_content=sdk_cta),\nupdate to the latest version to include the Foursquare source.\nAll other improvements are automatic without any further action.\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_campaign=foursquare_beta_announcement) to get an API key. You can start building today without a credit card!\n- Get started today by diving into the details in our [geocoding documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F?utm_source=marketing_site&utm_medium=blog&utm_campaign=foursquare_beta_announcement&utm_content=foursquare_beta_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), [BlueSky](https:\u002F\u002Fbsky.app\u002Fprofile\u002Fstadiamaps.com), 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":333,"description":334,"path":335,"published":336,"keywords":337,"rawbody":343},"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","2026-04-27",[299,338,339,340,341,342],"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",1778676026833]