[{"data":1,"prerenderedAt":229},["ShallowReactive",2],{"blog-\u002Fblog\u002Fopen-data-geocoding-global-search\u002F":3,"related-blog-\u002Fblog\u002Fopen-data-geocoding-global-search\u002F":182,"blog-author-\u002Fblog\u002Fopen-data-geocoding-global-search\u002F":217},{"id":4,"title":5,"abstract":6,"author":7,"body":8,"description":140,"excerpt":6,"extension":141,"head":142,"image":164,"imageAlt":165,"keywords":166,"meta":171,"modified":6,"navigation":172,"path":173,"proficiencyLevel":6,"published":174,"rawbody":175,"schemaOrg":6,"schemaType":6,"section":155,"seo":176,"stem":180,"__hash__":181},"blog\u002Fblog\u002Fopen-data-geocoding-global-search.md","The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos",null,"ian-wagner",{"type":9,"value":10,"toc":131},"minimark",[11,15,22,25,28,42,47,50,72,76,79,82,86,100,104,107,121,123],[12,13,5],"h1",{"id":14},"the-open-data-superpower-why-global-search-is-moving-beyond-proprietary-silos",[16,17,18],"blockquote",{},[19,20,21],"p",{},"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.",[23,24],"hr",{},[19,26,27],{},"Legacy 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.",[19,29,30,31,35,36,41],{},"At Stadia Maps, we solve this by building ",[32,33,34],"strong",{},"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 ",[37,38,40],"a",{"href":39},"\u002Fproducts\u002Fgeocoding-search\u002F","geocoding and search APIs",".",[43,44,46],"h2",{"id":45},"rapid-turnaround-and-the-fix-it-loop","Rapid Turnaround and the \"Fix-it\" Loop",[19,48,49],{},"Proprietary 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.",[51,52,53,60,66],"ul",{},[54,55,56,59],"li",{},[32,57,58],{},"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.",[54,61,62,65],{},[32,63,64],{},"Global Localization:"," We collaborate on an open-source set of address templates that respect how people actually write addresses in their home countries.",[54,67,68,71],{},[32,69,70],{},"Rapid Geocoding Updates:"," We refresh our geocoding data at least monthly to match our maps and routing services.",[43,73,75],{"id":74},"localization-without-the-friction","Localization Without the Friction",[19,77,78],{},"Search 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).",[19,80,81],{},"While 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.",[43,83,85],{"id":84},"precision-reverse-geocoding-down-to-the-feature","Precision Reverse Geocoding, Down to the Feature",[19,87,88,95,96,41],{},[37,89,94],{"href":90,"rel":91,"target":93},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F",[92],"external","_blank","Reverse geocoding"," 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 ",[37,97,99],{"href":98},"\u002Fproducts\u002Fon-prem-embedded\u002F","on-premise usage",[43,101,103],{"id":102},"whats-next","What's Next?",[19,105,106],{},"We are currently planning and building features that make the switch to Stadia Maps a no-brainer for enterprise teams:",[51,108,109,115],{},[54,110,111,114],{},[32,112,113],{},"Revamped Categorical Search:"," Expect more granular detail in specialized searches, such as \"Sushi restaurants,\" ranked by distance and relevance.",[54,116,117,120],{},[32,118,119],{},"Deeper Internationalization:"," Our team is expanding English-name search to include road names globally, bridging the gap for international logistics.",[23,122],{},[19,124,125,126,130],{},"Want to learn more about what we're working on? ",[37,127,129],{"href":128},"mailto:entsales@stadiamaps.com","Contact our engineering team"," to discuss your specific enterprise requirements.",{"title":132,"searchDepth":133,"depth":133,"links":134},"",4,[135,137,138,139],{"id":45,"depth":136,"text":46},2,{"id":74,"depth":136,"text":75},{"id":84,"depth":136,"text":85},{"id":102,"depth":136,"text":103},"Stadia Maps builds geocoding & search on continuous open data streams — rapid updates, community fix-it loops, multilingual search, and precision reverse geocoding.","md",{"meta":143},[144,147,150,153,156,158,160,162],{"property":145,"content":146},"og:image:width","1200",{"property":148,"content":149},"og:image:height","630",{"property":151,"content":152},"og:image:type","image\u002Fpng",{"property":154,"content":155},"article:tag","Geocoding",{"property":154,"content":157},"Open Data",{"property":154,"content":159},"Reverse Geocoding",{"property":154,"content":161},"Localization",{"property":154,"content":163},"Location Search","\u002Fimages\u002Fog\u002Fglobal-search-proprietary-silo-og.png","The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos — Stadia Maps",[155,167,159,157,168,169,161,170,163],"Geocoding API","OpenStreetMap","Multilingual Search","On-Premise Geocoding",{},true,"\u002Fblog\u002Fopen-data-geocoding-global-search","2026-07-08","---\ntitle: \"The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos\"\ndescription: Stadia Maps builds geocoding & search on continuous open data streams — rapid updates, community fix-it loops, 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 & search APIs ingest continuous open data for rapid updates, multilingual search, and precision reverse geocoding — no proprietary black box.\n---\n\n# The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos\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](\u002Fproducts\u002Fon-prem-embedded\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":177,"ogTitle":178,"description":179},"Open Data Geocoding API: Global Search, Rapid Updates","The Geocoding Engine Built on Open Data, Not Black Boxes","Stadia Maps geocoding & search APIs ingest continuous open data for rapid updates, multilingual search, and precision reverse geocoding — no proprietary black box.","blog\u002Fopen-data-geocoding-global-search","po9OO0XcSdry93Scr9OtV3lD_aA85SmprvogEaATkFI",[183,196,208],{"title":184,"description":185,"path":186,"published":187,"keywords":188,"rawbody":195},"Precision Meets Privacy: Elevating the Consumer Search Experience","Stadia Maps geocoding API delivers structured search, reverse geocoding, and autocomplete across 1B+ locations — no user tracking, no ad-network bias.","\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience","2026-06-17",[155,159,189,190,191,192,193,168,194,163],"Structured Geocoding","Autocomplete","Address Search","Privacy","GDPR","Foursquare","---\ntitle: \"Precision Meets Privacy: Elevating the Consumer Search Experience\"\nauthor: ian-wagner\ndescription: Stadia Maps geocoding API delivers structured search, reverse geocoding, and autocomplete across 1B+ locations — no user tracking, no ad-network bias.\nimage: \u002Fimages\u002Fog\u002Fprecision-meets-privacy-consumer-search-experience.png\nimageAlt: \"Precision Meets Privacy: Geocoding API With Global Coverage and No Tracking — Stadia Maps\"\nkeywords:\n  - Geocoding\n  - Reverse Geocoding\n  - Structured Geocoding\n  - Autocomplete\n  - Address Search\n  - Privacy\n  - GDPR\n  - OpenStreetMap\n  - Foursquare\n  - Location Search\nmodified: 2026-07-02\npublished: 2026-06-17\nsection: Geocoding\nseo:\n  title: \"Geocoding API: Structured Search, Global Coverage, No Tracking\"\n  ogTitle: The Geocoding API That Doesn't Track Your Users\n  description: Stadia Maps geocoding API delivers structured search, reverse geocoding, and autocomplete across 1B+ locations — no user tracking, no ad-network bias.\n---\n\n# Precision Meets Privacy: Elevating the Consumer Search Experience\n\n> Developers often hit a ceiling when moving from a search prototype to a production-ready global product. Stadia Maps delivers more reliable [structured geocoding](https:\u002F\u002Fstadiamaps.com\u002Fblog\u002Fopen-data-geocoding-global-search\u002F) by aggregating open datasets from across the globe, applying freshness signals to POI data, and providing structured endpoints that eliminate the black box guesswork of single-string search. All while maintaining a strict no-tracking policy.\n\n---\n\nBuilding a location-aware application often starts with a simple goal: helping users find where they need to go. Let's look at the specific gaps in the current geocoding landscape and how we've built a more reliable path forward.\n\n## Coverage and Data Quality\n\n[Our geocoding API](\u002Fproducts\u002Fgeocoding-search\u002F) surfaces three core capabilities: [fuzzy search and autocomplete](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) to resolve ambiguous input in under 100ms, [reverse geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) to convert coordinates into street-level addresses from a dataset of over 1 billion locations globally, and [structured data](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F) access for clean, parsed results that satisfy strict schema requirements. All three depend on the same thing: data you can trust.\n\nGeocoding quality isn't just about how often data updates. It's about how many sources you draw from and whether those sources tell you something meaningful. A single-provider dataset, no matter how frequently refreshed, will have gaps. [We aggregate open datasets from across the globe](\u002Fblog\u002F75-million-more-addresses-geocoding-precision\u002F), giving you broader coverage than any single source provides. For POI data specifically, we use Foursquare's freshness signals to reduce the likelihood that a result points to a location that closed years ago.\n\n## Move Beyond the Single-String Black Box\n\nFree-form single-string search is popular, but it's often an inefficient way to handle data. Most providers force you into a \"black box\" parser that guesses what your user meant, which works until it doesn't.\n\nStructured search shines when you already know something about your data, such as information from a shipping form or a registration profile. Structured geocoding endpoints let you pass postal codes, specific cities, and other clean facts directly to the engine. Removing ambiguity ensures better results and more reliable handling of local conventions, such as the wildly varying ways different countries format unit numbers.\n\n## Real Results in an Ad-Driven World\n\nIn an era when \"near me\" searches are auctioned off to the highest bidder, location infrastructure has effectively become an ad network. Unlike industry giants that harvest user behavior for profiling or bias results toward paid advertisers, our search APIs are built to be a transparent source of truth.\n\nOur no-tracking policy ensures that end-user searches don't get used to create behavioral profiles. Avoiding data harvesting leads to a more honest discovery experience. Users see what is actually there rather than what a platform was paid to show them.\n\n---\n\nReady to see the difference for yourself? [Create a free account](https:\u002F\u002Fclient.stadiamaps.com\u002Fsignup\u002F) and test our [Search API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) today.\n",{"title":197,"description":198,"path":199,"published":200,"keywords":201,"rawbody":207},"75 Million More Addresses: Expanding Geocoding Precision","75 million new rooftop-accurate addresses from OpenAddresses, 3 million Foursquare POIs, and structured address fields (house_number, street, unit) on the v1 API.","\u002Fblog\u002F75-million-more-addresses-geocoding-precision","2026-04-27",[155,167,202,203,204,205,206],"Rooftop Geocoding","OpenAddresses","Foursquare OS Places","Structured Search","Points of Interest","---\ntitle: \"75 Million More Addresses: Expanding Geocoding Precision\"\ndescription: 75 million new rooftop-accurate addresses from OpenAddresses, 3 million Foursquare POIs, and structured address fields (house_number, street, unit) on the v1 API.\nseo:\n  title: \"Geocoding Update: 75M New Addresses, Rooftop Accuracy\"\n  description: 75 million new rooftop-accurate addresses from OpenAddresses, 3 million Foursquare POIs, and structured address fields (house_number, street, unit) on the v1 API.\nsection: Geocoding\nkeywords:\n  - Geocoding\n  - Geocoding API\n  - Rooftop Geocoding\n  - OpenAddresses\n  - Foursquare OS Places\n  - Structured Search\n  - Points of Interest\nauthor: luke-seelenbinder\npublished: 2026-04-27\nmodified: 2026-07-02\n---\n\n# 75 Million More Addresses: Expanding Geocoding Precision\n\n> Stadia Maps' largest geocoding dataset expansion adds 75 million rooftop-accurate addresses from OpenAddresses (led by \\~25M each in France and the US), 3 million fresh POIs from Foursquare OS Places, smarter intent recognition, and new structured address fields — house\\_number, street, and unit — on the v1 search API. All improvements are live now with no migration required.\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\n[We continuously update our geocoding dataset](\u002Fblog\u002Fgeocoding-and-autocomplete-v2-updates-continue\u002F) 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## Where Do the 75 Million New Addresses Come From?\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## What Are the New Structured Address Fields?\n\nFor developers working with [structured address data](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F), 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",{"title":209,"description":210,"path":211,"published":212,"keywords":213,"rawbody":216},"Enriching Geocoding & Search: More Data, Smarter Deduplication, and Forward & Reverse v2","Geocoding v2 Forward and Reverse endpoints, smarter cross-source deduplication, multi-language fixes, and 8M more Foursquare OS Places POIs.","\u002Fblog\u002Fgeocoding-and-autocomplete-v2-updates-continue","2025-07-01",[155,159,214,190,215,194],"Forward Geocoding","Deduplication","---\ntitle: \"Enriching Geocoding & Search: More Data, Smarter Deduplication, and Forward & Reverse v2\"\ndescription: Geocoding v2 Forward and Reverse endpoints, smarter cross-source deduplication, multi-language fixes, and 8M more Foursquare OS Places POIs.\nseo:\n  title: \"Forward & Reverse Geocoding v2: More Data, Smarter Dedup\"\n  description: Geocoding v2 Forward and Reverse endpoints, smarter cross-source deduplication, multi-language fixes, and 8M more Foursquare OS Places POIs.\nsection: Geocoding\nkeywords:\n  - Geocoding\n  - Reverse Geocoding\n  - Forward Geocoding\n  - Autocomplete\n  - Deduplication\n  - Foursquare\nauthor: luke-seelenbinder\npublished: 2025-07-01\nmodified: 2026-07-02\n---\n\n# Enriching Geocoding & Search: More Data, Smarter Deduplication, and Forward & Reverse v2\n\n> This Geocoding & Search update ships v2 of the Forward and Reverse geocoding endpoints, smarter cross-source deduplication, multi-language query fixes, improved labels, and 8 million more Foursquare OS Places POIs (about 14 million total). All improvements are live for all customers.\n\nOn the heels of [our last geocoding update](\u002Fblog\u002Fintroducing-stadia-maps-geocoding-search-v2\u002F) for our Autocomplete and Place Details endpoints,\nwe're excited to announce another major update to [Geocoding & Search](\u002Fproducts\u002Fgeocoding-search\u002F):\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 the 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),\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#autocomplete-search)\n- [API Clients\u002FSDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F)\n- [v2 Migration Guide for Developers](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fv2-api-migration-guide\u002F)\n- [Geocoding Documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F)\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) 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",{"id":218,"bio":219,"extension":220,"jobTitle":221,"meta":222,"name":223,"sameAs":224,"slug":7,"stem":226,"twitterCreator":227,"url":6,"__hash__":228},"authors\u002Fauthors\u002Fian-wagner.yml","Ian is co-founder of Stadia Maps and leads engineering and operations. He works on routing, navigation, and the technical foundations that keep customer applications reliable at scale.","yml","Founder & President \u002F COO",{},"Ian Wagner",[225],"https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fian-w-wagner\u002F","authors\u002Fian-wagner","@ianthetechie","I3XDLabBF4Qu7lS862NuwOPtHhXe58zi7go2UmY9DOY",1783515182381]