[{"data":1,"prerenderedAt":422},["ShallowReactive",2],{"footer-learn-links":3,"site-prefooter-cta":16,"learn-\u002Flearn\u002Fgeocoding-data-storage\u002F":24,"related-learn-\u002Flearn\u002Fgeocoding-data-storage\u002F":394,"learn-org-author":410},[4,7,10,13],{"title":5,"path":6},"Can You Store Geocoding Results?","\u002Flearn\u002Fgeocoding-data-storage",{"title":8,"path":9},"What Does a \"Free\" Map API Actually Cost?","\u002Flearn\u002Fwhat-does-a-free-map-api-cost",{"title":11,"path":12},"What Is the Best Geocoding API?","\u002Flearn\u002Fbest-geocoding-api",{"title":14,"path":15},"What Is the Best Routing API?","\u002Flearn\u002Fbest-routing-api",{"id":17,"extension":18,"heading":19,"meta":20,"stem":21,"text":22,"__hash__":23},"site\u002Fsite\u002Fprefooter-cta.yml","yml","Business Outcomes That Fuel Your Growth",{},"site\u002Fprefooter-cta","With Stadia Maps, you build the solutions that matter. Logistics platforms provide accurate ETAs, fleet management apps reduce fuel costs, and emergency dispatch systems improve response times.","XztWiZDFyAC0XCoeYLLQrcyaVmP8uvGWALRS354c9I4",{"id":25,"title":5,"author":26,"body":27,"category":301,"description":378,"extension":379,"head":380,"image":382,"imageAlt":383,"keywords":384,"meta":385,"modified":384,"navigation":386,"path":6,"published":387,"rawbody":388,"schemaOrg":384,"seo":389,"stem":390,"term":391,"termDescription":392,"__hash__":393},"learn\u002Flearn\u002Fgeocoding-data-storage.md","Stadia Maps Team",{"type":28,"value":29,"toc":362},"minimark",[30,34,38,43,62,66,69,72,87,90,94,103,121,124,127,131,147,176,184,187,191,194,200,206,209,215,219,222,257,261,265,270,273,298,302],[31,32,5],"h1",{"id":33},"can-you-store-geocoding-results",[35,36,37],"p",{},"It depends on your provider, and the answer is often no, or yes at a significant surcharge. Geocoding storage rights are the contractual terms governing whether you can save a returned coordinate in your own database and for how long. Most teams do not discover the restriction until they are already at scale. On Stadia Maps, permanent storage is included on Standard plans and above with no per-request surcharge.",[39,40,42],"h2",{"id":41},"key-takeaways","Key Takeaways",[44,45,46,50,53,56,59],"ul",{},[47,48,49],"li",{},"Geocoding storage rights govern whether you can retain a returned coordinate in your own database, and for how long.",[47,51,52],{},"Per Stadia Maps' analysis, Mapbox, AWS, and ESRI often charge between 6x and 8x the cost of a regular query if you intend to store the result.",[47,54,55],{},"Google's restrictions generally forbid caching for anything other than a specific end-user session.",[47,57,58],{},"Stadia Maps allows permanent storage on Standard, Professional, and Enterprise plans with no extra fees and no per-user re-validation.",[47,60,61],{},"Temporary storage in the normal course of work is allowed on all Stadia Maps plans, including Free.",[39,63,65],{"id":64},"what-are-geocoding-storage-rights","What Are Geocoding Storage Rights?",[35,67,68],{},"When you geocode an address, the provider returns coordinates. The question of whether those coordinates are yours to keep is a licensing question, not a technical one. Nothing stops you from writing the response to a database. The terms of service determine whether you are allowed to.",[35,70,71],{},"Providers generally distinguish two cases:",[44,73,74,81],{},[47,75,76,80],{},[77,78,79],"strong",{},"Temporary storage."," Holding a result in memory or a short-lived cache during the normal course of a request or session.",[47,82,83,86],{},[77,84,85],{},"Permanent storage."," Writing a result to your own database and retaining it indefinitely.",[35,88,89],{},"Nearly every provider allows the first. The second is where terms diverge sharply, and where costs can appear that were not in your original estimate.",[39,91,93],{"id":92},"what-does-the-caching-tax-cost","What Does the Caching Tax Cost?",[35,95,96,97,102],{},"Stadia Maps published an analysis of this in ",[98,99,101],"a",{"href":100},"\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F","The Hidden Cost of Search",". Its findings on the industry:",[44,104,105,115],{},[47,106,107,110,111,114],{},[77,108,109],{},"Mapbox, AWS, and ESRI"," often charge between ",[77,112,113],{},"6x and 8x"," the cost of a regular query if you intend to store the result.",[47,116,117,120],{},[77,118,119],{},"Google"," employs complex restrictions that generally forbid caching for anything other than a specific end-user session.",[35,122,123],{},"The practical effect is that a cost model built on query volume can be off by a large multiple once storage enters the picture. A team that geocodes a million addresses once and stores the results is doing something very different, contractually, from a team that geocodes a million times and discards each result.",[35,125,126],{},"The same post notes a related constraint worth checking: Google often prevents displaying its geocoding results on a map from another provider. Storage rights and display rights are separate terms, and both can create lock-in.",[39,128,130],{"id":129},"what-does-stadia-maps-allow","What Does Stadia Maps Allow?",[35,132,133,134,141,142,146],{},"Per the ",[98,135,140],{"href":136,"rel":137,"target":139},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F",[138],"external","_blank","Stadia Maps geocoding documentation"," and the ",[98,143,145],{"href":144},"\u002Fpricing\u002F","pricing page",":",[44,148,149,159,169],{},[47,150,151,154,155,158],{},[77,152,153],{},"Temporary storage"," in the normal course of your work is allowed on ",[77,156,157],{},"all plans",", including Free.",[47,160,161,164,165,168],{},[77,162,163],{},"Permanent storage"," (for example, writing results to a database) requires an active ",[77,166,167],{},"Standard, Professional, or Enterprise"," subscription.",[47,170,171,172,175],{},"There is ",[77,173,174],{},"no per-request storage surcharge",", no per-user re-validation, and no permanent storage fee. Results can be cached as long as the subscription is active.",[35,177,178,179,183],{},"The governing language is in Section 8 of the ",[98,180,182],{"href":181},"\u002Fterms-of-service\u002F","Terms of Service",", which lists among prohibited uses \"permanently storing results for future use (e.g., as a database column), in part or in whole, from the Stadia Maps Geocoding APIs without an active Standard, Professional, or Enterprise subscription with appropriate permissions.\"",[35,185,186],{},"On the pricing page's feature comparison, storage rights appear directly in the plan table: Free and Starter show temporary storage, while Standard and Professional show persistent storage.",[39,188,190],{"id":189},"how-storage-rights-change-your-architecture","How Storage Rights Change Your Architecture",[35,192,193],{},"Storage terms are not just a line item. They shape how you can build.",[35,195,196,199],{},[77,197,198],{},"If permanent storage is allowed",", you can geocode once and reuse. Address normalization at signup, a one-time backfill of a customer table, or a nightly enrichment job all become straightforward. Your ongoing API cost tracks new addresses rather than total lookups.",[35,201,202,205],{},[77,203,204],{},"If permanent storage is restricted",", you have to re-geocode. That means either repeated API calls for the same addresses, or a session-scoped cache that gets discarded. Your cost tracks usage volume rather than unique addresses, and the gap between those two numbers grows as your product matures.",[35,207,208],{},"The difference compounds. A marketplace with a hundred thousand stable listings and heavy repeat browsing has wildly different bills under the two models.",[35,210,211,212],{},"Storage is one of several terms that only show up once you are past a free tier. For the others, see ",[98,213,8],{"href":214},"\u002Flearn\u002Fwhat-does-a-free-map-api-cost\u002F",[39,216,218],{"id":217},"where-this-gets-complicated","Where This Gets Complicated",[35,220,221],{},"A few things worth knowing before you architect around storage rights.",[44,223,224,230,236,242,251],{},[47,225,226,229],{},[77,227,228],{},"Terms change."," Provider pricing and licensing get revised. What is allowed today may carry a surcharge on renewal. Check the current terms rather than relying on a comparison written last year, including this one.",[47,231,232,235],{},[77,233,234],{},"Storage and display rights are separate."," A provider may allow you to store a coordinate but restrict where you can display it. Check both.",[47,237,238,241],{},[77,239,240],{},"Downgrading has consequences."," If permanent storage is tied to a plan tier, dropping to a lower tier may affect your right to retain data you already stored. Ask before you downgrade.",[47,243,244,247,248,250],{},[77,245,246],{},"This is a summary, not the contract."," The ",[98,249,182],{"href":181}," govern. If storage rights are material to your business, have someone read them.",[47,252,253,256],{},[77,254,255],{},"Other providers' terms are their own."," The figures above come from Stadia Maps' published analysis. Verify against each provider's current terms directly before making a decision.",[258,259],"faq-section",{":faqs":260},"[{\"question\":\"Can you store geocoding results in a database?\",\"answer\":\"It depends on the provider. On Stadia Maps, permanent storage of geocoding results in your own database is allowed with an active Standard, Professional, or Enterprise subscription, with no per-request surcharge. Temporary storage in the normal course of work is allowed on all plans including Free. Other providers commonly restrict permanent storage or charge a premium for it.\"},{\"question\":\"What is the geocoding caching tax?\",\"answer\":\"The caching tax refers to the premium some geocoding providers charge to store results long-term rather than discard them after use. According to Stadia Maps' published analysis, Mapbox, AWS, and ESRI often charge between 6x and 8x the cost of a regular query when results will be stored. Google's terms generally forbid caching outside a specific end-user session.\"},{\"question\":\"What is the difference between temporary and permanent geocoding storage?\",\"answer\":\"Temporary storage means holding a result in memory or a short-lived cache during the normal course of a request or session. Permanent storage means writing the result to your own database and retaining it indefinitely. Nearly every provider allows temporary storage. Permanent storage is where terms diverge and where surcharges typically apply.\"},{\"question\":\"Which Stadia Maps plans allow permanent geocoding storage?\",\"answer\":\"Permanent storage requires an active Standard, Professional, or Enterprise subscription. Temporary storage in the normal course of your work is allowed on all plans, including Free and Starter. There are no extra fees, no per-user re-validation, and no permanent storage surcharges on plans that include it.\"},{\"question\":\"Why do geocoding storage rights matter for cost?\",\"answer\":\"Storage rights determine whether your API cost tracks unique addresses or total lookups. If you can geocode once and store the result, ongoing cost scales with new addresses. If you must re-geocode, cost scales with usage volume. For products with stable data and heavy repeat access, the difference between those two models compounds significantly.\"}]",[39,262,264],{"id":263},"where-to-go-next","Where to Go Next",[266,267,269],"h3",{"id":268},"from-the-blog","From the Blog",[35,271,272],{},"More on geocoding costs and terms from the Stadia Maps blog:",[44,274,275,280,286,292],{},[47,276,277],{},[98,278,279],{"href":100},"The Hidden Cost of Search: Why Your Geocoding Bill Is Higher Than It Should Be",[47,281,282],{},[98,283,285],{"href":284},"\u002Fblog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding\u002F","Bulk Geocoding API Is Now Available",[47,287,288],{},[98,289,291],{"href":290},"\u002Fblog\u002Fopen-data-geocoding-global-search\u002F","The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos",[47,293,294],{},[98,295,297],{"href":296},"\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F","Precision Meets Privacy: Elevating the Consumer Search Experience",[266,299,301],{"id":300},"geocoding-search","Geocoding & Search",[44,303,304,310,317,324,331,339,345,351,357],{},[47,305,306,309],{},[98,307,11],{"href":308},"\u002Flearn\u002Fbest-geocoding-api\u002F"," for how storage rights compare against the other evaluation criteria",[47,311,312,316],{},[98,313,315],{"href":314},"\u002Flearn\u002Fgeocoding\u002F","What Is Geocoding?"," for how geocoding works and where the data comes from",[47,318,319,323],{},[98,320,322],{"href":321},"\u002Flearn\u002Freverse-geocoding\u002F","What Is Reverse Geocoding?"," for the coordinates-to-address direction",[47,325,326,330],{},[98,327,329],{"href":328},"\u002Flearn\u002Faddress-autocomplete\u002F","What Is Address Autocomplete?"," for search-as-you-type",[47,332,333,338],{},[98,334,337],{"href":335,"rel":336,"target":139},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F",[138],"Bulk Geocoding API reference"," for processing up to 5,000 addresses per request",[47,340,341],{},[98,342,344],{"href":136,"rel":343,"target":139},[138],"Forward Geocoding API reference",[47,346,347],{},[98,348,350],{"href":349},"\u002Fproducts\u002Fgeocoding-search\u002Fgeocoding\u002F","Geocoding product page",[47,352,353,356],{},[98,354,355],{"href":144},"Pricing and plan comparison"," for the storage rights table",[47,358,359,361],{},[98,360,182],{"href":181}," for the full legal terms",{"title":363,"searchDepth":364,"depth":364,"links":365},"",4,[366,368,369,370,371,372,373],{"id":41,"depth":367,"text":42},2,{"id":64,"depth":367,"text":65},{"id":92,"depth":367,"text":93},{"id":129,"depth":367,"text":130},{"id":189,"depth":367,"text":190},{"id":217,"depth":367,"text":218},{"id":263,"depth":367,"text":264,"children":374},[375,377],{"id":268,"depth":376,"text":269},3,{"id":300,"depth":376,"text":301},"Most geocoding providers restrict or surcharge storing results. Learn what geocoding storage rights are, what they cost, and which Stadia Maps plans allow it.","md",{"script":381},[],"\u002Fimages\u002Fog\u002Fcan-you-store-geocoding-results.png","Can You Store Geocoding Results? — Stadia Maps",null,{},true,"2026-09-15","---\ntitle: Can You Store Geocoding Results?\ndescription: Most geocoding providers restrict or surcharge storing results. Learn what geocoding storage rights are, what they cost, and which Stadia Maps plans allow it.\nauthor: Stadia Maps Team\ncategory: Geocoding & Search\nimage: \u002Fimages\u002Fog\u002Fcan-you-store-geocoding-results.png\nimageAlt: Can You Store Geocoding Results? — Stadia Maps\nhead:\n  script: []\npublished: 2026-09-15\nterm: Geocoding Storage Rights\ntermDescription: The contractual terms governing whether and for how long a developer may retain geocoding results in their own database.\n---\n\n# Can You Store Geocoding Results?\n\nIt depends on your provider, and the answer is often no, or yes at a significant surcharge. Geocoding storage rights are the contractual terms governing whether you can save a returned coordinate in your own database and for how long. Most teams do not discover the restriction until they are already at scale. On Stadia Maps, permanent storage is included on Standard plans and above with no per-request surcharge.\n\n## Key Takeaways\n\n- Geocoding storage rights govern whether you can retain a returned coordinate in your own database, and for how long.\n- Per Stadia Maps' analysis, Mapbox, AWS, and ESRI often charge between 6x and 8x the cost of a regular query if you intend to store the result.\n- Google's restrictions generally forbid caching for anything other than a specific end-user session.\n- Stadia Maps allows permanent storage on Standard, Professional, and Enterprise plans with no extra fees and no per-user re-validation.\n- Temporary storage in the normal course of work is allowed on all Stadia Maps plans, including Free.\n\n## What Are Geocoding Storage Rights?\n\nWhen you geocode an address, the provider returns coordinates. The question of whether those coordinates are yours to keep is a licensing question, not a technical one. Nothing stops you from writing the response to a database. The terms of service determine whether you are allowed to.\n\nProviders generally distinguish two cases:\n\n- **Temporary storage.** Holding a result in memory or a short-lived cache during the normal course of a request or session.\n- **Permanent storage.** Writing a result to your own database and retaining it indefinitely.\n\nNearly every provider allows the first. The second is where terms diverge sharply, and where costs can appear that were not in your original estimate.\n\n## What Does the Caching Tax Cost?\n\nStadia Maps published an analysis of this in [The Hidden Cost of Search](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F). Its findings on the industry:\n\n- **Mapbox, AWS, and ESRI** often charge between **6x and 8x** the cost of a regular query if you intend to store the result.\n- **Google** employs complex restrictions that generally forbid caching for anything other than a specific end-user session.\n\nThe practical effect is that a cost model built on query volume can be off by a large multiple once storage enters the picture. A team that geocodes a million addresses once and stores the results is doing something very different, contractually, from a team that geocodes a million times and discards each result.\n\nThe same post notes a related constraint worth checking: Google often prevents displaying its geocoding results on a map from another provider. Storage rights and display rights are separate terms, and both can create lock-in.\n\n## What Does Stadia Maps Allow?\n\nPer the [Stadia Maps geocoding documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F) and the [pricing page](\u002Fpricing\u002F):\n\n- **Temporary storage** in the normal course of your work is allowed on **all plans**, including Free.\n- **Permanent storage** (for example, writing results to a database) requires an active **Standard, Professional, or Enterprise** subscription.\n- There is **no per-request storage surcharge**, no per-user re-validation, and no permanent storage fee. Results can be cached as long as the subscription is active.\n\nThe governing language is in Section 8 of the [Terms of Service](\u002Fterms-of-service\u002F), which lists among prohibited uses \"permanently storing results for future use (e.g., as a database column), in part or in whole, from the Stadia Maps Geocoding APIs without an active Standard, Professional, or Enterprise subscription with appropriate permissions.\"\n\nOn the pricing page's feature comparison, storage rights appear directly in the plan table: Free and Starter show temporary storage, while Standard and Professional show persistent storage.\n\n## How Storage Rights Change Your Architecture\n\nStorage terms are not just a line item. They shape how you can build.\n\n**If permanent storage is allowed**, you can geocode once and reuse. Address normalization at signup, a one-time backfill of a customer table, or a nightly enrichment job all become straightforward. Your ongoing API cost tracks new addresses rather than total lookups.\n\n**If permanent storage is restricted**, you have to re-geocode. That means either repeated API calls for the same addresses, or a session-scoped cache that gets discarded. Your cost tracks usage volume rather than unique addresses, and the gap between those two numbers grows as your product matures.\n\nThe difference compounds. A marketplace with a hundred thousand stable listings and heavy repeat browsing has wildly different bills under the two models.\n\nStorage is one of several terms that only show up once you are past a free tier. For the others, see [What Does a \"Free\" Map API Actually Cost?](\u002Flearn\u002Fwhat-does-a-free-map-api-cost\u002F)\n\n## Where This Gets Complicated\n\nA few things worth knowing before you architect around storage rights.\n\n- **Terms change.** Provider pricing and licensing get revised. What is allowed today may carry a surcharge on renewal. Check the current terms rather than relying on a comparison written last year, including this one.\n- **Storage and display rights are separate.** A provider may allow you to store a coordinate but restrict where you can display it. Check both.\n- **Downgrading has consequences.** If permanent storage is tied to a plan tier, dropping to a lower tier may affect your right to retain data you already stored. Ask before you downgrade.\n- **This is a summary, not the contract.** The [Terms of Service](\u002Fterms-of-service\u002F) govern. If storage rights are material to your business, have someone read them.\n- **Other providers' terms are their own.** The figures above come from Stadia Maps' published analysis. Verify against each provider's current terms directly before making a decision.\n\n::faq-section\n---\nfaqs:\n  - question: Can you store geocoding results in a database?\n    answer: It depends on the provider. On Stadia Maps, permanent storage of\n      geocoding results in your own database is allowed with an active Standard,\n      Professional, or Enterprise subscription, with no per-request surcharge.\n      Temporary storage in the normal course of work is allowed on all plans\n      including Free. Other providers commonly restrict permanent storage or\n      charge a premium for it.\n  - question: What is the geocoding caching tax?\n    answer: The caching tax refers to the premium some geocoding providers charge to\n      store results long-term rather than discard them after use. According to\n      Stadia Maps' published analysis, Mapbox, AWS, and ESRI often charge\n      between 6x and 8x the cost of a regular query when results will be stored.\n      Google's terms generally forbid caching outside a specific end-user\n      session.\n  - question: What is the difference between temporary and permanent geocoding storage?\n    answer: Temporary storage means holding a result in memory or a short-lived\n      cache during the normal course of a request or session. Permanent storage\n      means writing the result to your own database and retaining it\n      indefinitely. Nearly every provider allows temporary storage. Permanent\n      storage is where terms diverge and where surcharges typically apply.\n  - question: Which Stadia Maps plans allow permanent geocoding storage?\n    answer: Permanent storage requires an active Standard, Professional, or\n      Enterprise subscription. Temporary storage in the normal course of your\n      work is allowed on all plans, including Free and Starter. There are no\n      extra fees, no per-user re-validation, and no permanent storage surcharges\n      on plans that include it.\n  - question: Why do geocoding storage rights matter for cost?\n    answer: Storage rights determine whether your API cost tracks unique addresses\n      or total lookups. If you can geocode once and store the result, ongoing\n      cost scales with new addresses. If you must re-geocode, cost scales with\n      usage volume. For products with stable data and heavy repeat access, the\n      difference between those two models compounds significantly.\n---\n::\n\n## Where to Go Next\n\n### From the Blog\n\nMore on geocoding costs and terms from the Stadia Maps blog:\n\n- [The Hidden Cost of Search: Why Your Geocoding Bill Is Higher Than It Should Be](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F)\n- [Bulk Geocoding API Is Now Available](\u002Fblog\u002Fquickly-geocode-thousands-of-addresses-with-bulk-geocoding\u002F)\n- [The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos](\u002Fblog\u002Fopen-data-geocoding-global-search\u002F)\n- [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F)\n\n### Geocoding & Search\n\n- [What Is the Best Geocoding API?](\u002Flearn\u002Fbest-geocoding-api\u002F) for how storage rights compare against the other evaluation criteria\n- [What Is Geocoding?](\u002Flearn\u002Fgeocoding\u002F) for how geocoding works and where the data comes from\n- [What Is Reverse Geocoding?](\u002Flearn\u002Freverse-geocoding\u002F) for the coordinates-to-address direction\n- [What Is Address Autocomplete?](\u002Flearn\u002Faddress-autocomplete\u002F) for search-as-you-type\n- [Bulk Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F) for processing up to 5,000 addresses per request\n- [Forward Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F)\n- [Geocoding product page](\u002Fproducts\u002Fgeocoding-search\u002Fgeocoding\u002F)\n- [Pricing and plan comparison](\u002Fpricing\u002F) for the storage rights table\n- [Terms of Service](\u002Fterms-of-service\u002F) for the full legal terms\n",{"title":5,"description":378},"learn\u002Fgeocoding-data-storage","Geocoding Storage Rights","The contractual terms governing whether and for how long a developer may retain geocoding results in their own database.","8C4kvi4oQzn_PdYpjBUE7BYIbleRJof6S9bmb5CvlKc",[395,400,405],{"title":329,"description":396,"path":397,"published":398,"category":301,"rawbody":399},"Address autocomplete suggests places, addresses, and points of interest as users type. Learn how it works and how to add it with Stadia Maps SDKs and API.","\u002Flearn\u002Faddress-autocomplete","2026-07-28","---\ntitle: What Is Address Autocomplete?\ndescription: Address autocomplete suggests places, addresses, and points of interest as users type. Learn how it works and how to add it with Stadia Maps SDKs and API.\nauthor: Stadia Maps Team\ncategory: Geocoding & Search\nimage: \u002Fimages\u002Fog\u002Fwhat-is-address-autocomplete.png\nhead:\n  script: []\npublished: 2026-07-28\nschemaOrg:\n  - \"@type\": FAQPage\n    mainEntity:\n      - \"@type\": Question\n        name: What is address autocomplete used for?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Address autocomplete is used to suggest places, addresses, and points of interest as a user types. It powers search-as-you-type experiences in checkout flows, store locators, ride-share pickup selection, and any interface where a user needs to find and select a real-world location quickly.\n      - \"@type\": Question\n        name: What is the difference between address autocomplete and forward geocoding?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Autocomplete is optimized for speed on partial input. Forward geocoding is optimized for accuracy on complete input and can interpolate addresses. Use autocomplete for interactive search-as-you-type; switch to forward geocoding when the user finalizes the query.\n      - \"@type\": Question\n        name: Which SDKs does Stadia Maps offer for address autocomplete?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: \"Stadia Maps offers three first-party SDKs for address autocomplete: the MapLibre GL JS Search Box plugin for the web, SwiftUI Autocomplete Search for iOS, and Jetpack Compose Autocomplete Search for Android. Each handles debouncing, caching, and result ordering out of the box. If none fit, the underlying HTTP API is available directly.\"\n      - \"@type\": Question\n        name: What are the default autocomplete timing and input settings on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: The Stadia Maps autocomplete SDKs default to a 100ms minimum wait period between requests (minWaitPeriodMs) and a 3-character minimum input length (minInputLength). The MapLibre GL JS Search Box plugin also defaults to 5 maximum results (maxResults). These defaults balance server load with responsiveness.\n      - \"@type\": Question\n        name: How is an address autocomplete request billed on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Autocomplete requests are billed from the unified Stadia Maps API credit pool, the same pool that covers forward geocoding, reverse geocoding, routing, and tiles. Each autocomplete request is a single billable request.\nterm: Address Autocomplete\ntermDescription: A search-as-you-type interface that suggests addresses, places, and points of interest as a user types, ranked by relevance and proximity.\n---\n\n# What Is Address Autocomplete?\n\nAddress autocomplete is a search-as-you-type interface that suggests addresses, places, and points of interest as a user types, ranked by relevance and proximity. Also called type-ahead search, place search suggestions, or predictive search, address autocomplete is what turns a slow, error-prone address form into a two-tap interaction. The [Stadia Maps Autocomplete Search API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) powers this experience through a fast, partial-input endpoint plus first-party SDKs for the web, iOS, and Android.\n\n## Key Takeaways\n\n- Address autocomplete suggests places as a user types, based on partial input and typically ranked by proximity or a focus point.\n- It is not a substitute for forward geocoding. Autocomplete is tuned for speed on partial input; forward geocoding is tuned for accuracy on complete input and can interpolate addresses.\n- Stadia Maps ships three first-party SDKs (MapLibre GL JS, SwiftUI, Jetpack Compose) that handle debouncing, caching, and result ordering out of the box.\n- The Stadia Maps SDKs default to a 100ms minimum wait period between requests and a 3-character minimum input length.\n- Each autocomplete request is billed as a single request from the unified Stadia Maps API credit pool.\n\n## How Address Autocomplete Works\n\nAutocomplete is a variant of forward geocoding tuned for speed on incomplete input. It follows this rough flow:\n\n1. **User types.** The client waits for a minimum number of characters (typically two or three) before firing the first request.\n2. **Debounce.** The client waits a short interval (roughly 100ms) after each keystroke before sending a request, so it does not overwhelm the server on fast typing.\n3. **Server searches.** The [Stadia Maps Autocomplete Search API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) matches the partial input against the geocoding database and returns ranked candidates.\n4. **Client renders results.** Suggestions appear under the search field, typically 3 to 5 at a time.\n5. **User selects one.** The application takes the selected feature (with its full coordinates, address components, and layer) and moves on to the next step.\n\nTwo implementation details that matter in production:\n\n- **Out-of-order responses.** Fast typing produces overlapping requests. The client must show the response for the most recent input, not the last one to arrive. Modern async frameworks and the Stadia Maps SDKs handle this automatically.\n- **Result caching.** Recent queries can be served from the local cache, which cuts perceived latency and reduces API calls.\n\n## Which Autocomplete SDK Should You Use?\n\nStadia Maps ships three first-party SDKs for address autocomplete, each purpose-built for its platform. All of them handle debouncing, caching, out-of-order responses, and result ordering by default.\n\n- **[MapLibre GL JS Search Box plugin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F)** for the web. Adds a search control to a MapLibre GL JS map. Configurable via options like `useMapFocusPoint`, `mapFocusPointMinZoom`, `minInputLength`, and `minWaitPeriodMs`. Available as an npm package or a CDN script tag.\n- **[SwiftUI Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fswiftui-autocomplete-search\u002F)** for iOS. A drop-in SwiftUI view for native iOS apps.\n- **[Jetpack Compose Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjetpack-compose-autocomplete-search\u002F)** for Android. A composable for native Android apps built with Jetpack Compose.\n\nIf none of the three fit your stack (React Native, Flutter, a custom UI framework, or a server-side integration), use the underlying HTTP API directly. The Stadia Maps [official SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F) also expose the endpoint from TypeScript, Python, Kotlin, Swift, and PHP.\n\n## Address Autocomplete Parameters That Matter\n\nThe [Autocomplete Search endpoint](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) takes one required parameter and several optional ones that tune the result set.\n\n- **`text`**: The partial user input. Required.\n- **`focus.point.lat` \u002F `focus.point.lon`**: Bias results toward a focus point. Typically the map center or the user's known location.\n- **`boundary.rect.*`, `boundary.circle.*`, `boundary.country`, `boundary.gid`**: Hard limits on where results can appear. Use these when your product only operates in specific regions.\n- **`layers`**: Restrict to specific layers (`address`, `venue`, `poi`, `street`, `locality`, and more). Fewer layers means faster, more relevant results. `layers=coarse` is the fastest option when you do not need addresses or POIs.\n- **`sources`**: Restrict to specific data sources (`openstreetmap`, `openaddresses`, `whosonfirst`, `geonames`, `foursquare`).\n- **`size`**: Maximum number of results to return. Default is 10; most autocomplete UIs display 3 to 5.\n- **`lang`**: A BCP47 language tag for localized results.\n\n## Autocomplete Defaults Worth Knowing\n\nThe [Stadia Maps SDKs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F#ready-to-go-integrations) enforce a set of defaults documented in the API and SDK references. Each one exists to balance API cost, server load, and interaction responsiveness.\n\n- **Minimum input length.** The [Autocomplete Search docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) recommend waiting for two or three characters of user input before sending a query. The [MapLibre GL JS Search Box plugin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F) defaults `minInputLength` to 3.\n- **Debouncing.** The MapLibre plugin defaults `minWaitPeriodMs` to 100ms, meaning it waits 100ms between requests as the user types. The docs recommend throttling or debouncing for interactive applications; the ready-to-go integrations handle it automatically.\n- **Result caching.** The MapLibre plugin caches recent results to avoid duplicate calls.\n- **Out-of-order response handling.** The docs call this out explicitly: \"network requests might arrive out of order... our frameworks handle it automatically.\" Take care if you build your own low-level integration.\n- **Maximum results.** The MapLibre plugin defaults `maxResults` to 5.\n- **Layer selection.** Specifying only the [layers](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Flayers\u002F) you need improves relevance and performance. `layers=coarse` is especially useful when POIs and addresses are not needed.\n\n## How Do You Add Address Autocomplete?\n\nHere is what a direct call to the Stadia Maps Autocomplete Search API looks like. This example searches for a partial query in Tallinn, Estonia.\n\n```http\nGET https:\u002F\u002Fapi.stadiamaps.com\u002Fgeocoding\u002Fv2\u002Fautocomplete?text=Union+Squa&lang=en\n```\n\nThe response is a GeoJSON `FeatureCollection`. Each feature includes coordinates, parsed address components, layer, confidence score, and source attribution. Full response format details are in the [Common Response Format docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fapi-response-format\u002F).\n\nFor most applications, the [MapLibre GL JS Search Box plugin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F), [SwiftUI Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fswiftui-autocomplete-search\u002F), or [Jetpack Compose Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjetpack-compose-autocomplete-search\u002F) will be faster than building a UI on top of the raw API. For runnable code against the HTTP endpoint in TypeScript, Python, Kotlin, Swift, PHP, or cURL, see the [Autocomplete Search API docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F).\n\n## Where Address Autocomplete Falls Short\n\nAutocomplete is not the right tool for every search interaction. Real limits worth knowing:\n\n- **Autocomplete does not interpolate addresses.** If a specific house number does not exist in the underlying data, forward geocoding can estimate it from surrounding addresses. Autocomplete cannot. Fall back to [forward geocoding](\u002Flearn\u002Fgeocoding\u002F) once the user finalizes their query.\n- **Very short queries are noisy.** A one-character query returns hundreds of matches. The Stadia Maps SDKs default to a 3-character minimum. Lowering that produces bad UX.\n- **Ranking is context-dependent.** Without a `focus.point` or a boundary, \"Springfield\" could match any of dozens. Provide a focus point or country hint whenever possible.\n- **Layer choice affects results.** If you only need addresses and POIs, exclude administrative layers to speed things up. If you only need administrative context, use `layers=coarse` for the fastest possible search.\n- **Two providers rarely agree exactly.** Different providers use different data, different scoring, and different ranking logic. Standardize on one provider to keep your product consistent.\n\n## Address Autocomplete vs. Forward Geocoding: Which Do You Need?\n\nBoth convert human-readable place input into coordinates. They optimize for different phases of the user interaction.\n\n- Use **[address autocomplete](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F)** while the user is still typing. Fast responses, partial input, ranked suggestions.\n- Use **[forward geocoding](\u002Flearn\u002Fgeocoding\u002F)** once the user finalizes their query (for example, by pressing Enter or submitting a form). Better accuracy on complete input, and forward geocoding can interpolate house numbers that autocomplete cannot.\n\nThe MapLibre GL JS Search Box plugin can automatically switch to the forward geocoding endpoint on Enter via the `searchOnEnter` option, if your plan includes the forward geocoding endpoint. See the [Stadia Maps pricing page](\u002Fpricing\u002F) for plan details.\n\n## Common Address Autocomplete Use Cases\n\nAutocomplete appears wherever a product asks a user to enter a real-world place.\n\n- **Checkout and shipping forms.** Users select their delivery address from suggestions instead of typing the full string. Fewer errors, faster completion, and higher form conversion.\n- **Ride-share and delivery pickup.** Rider or customer picks their pickup or drop-off from a search field. Focus point is set to the current GPS location so nearby options rank first.\n- **Store locator and site finder.** User types a city or zip code and the map centers on the selected result.\n- **Map-based search interfaces.** Real estate, travel, and outdoor apps let users search for places directly on the map.\n- **Data entry and CRM lookup.** Sales and support tools use autocomplete to attach a canonical place to a record.\n- **Point-of-interest discovery.** Restaurants, hotels, landmarks, and businesses surface as venues the user can select without knowing the full name.\n\n## Frequently Asked Questions\n\n### What is address autocomplete used for?\n\nAddress autocomplete is used to suggest places, addresses, and points of interest as a user types. It powers search-as-you-type experiences in checkout flows, store locators, ride-share pickup selection, and any interface where a user needs to find and select a real-world location quickly.\n\n### What is the difference between address autocomplete and forward geocoding?\n\nAutocomplete is optimized for speed on partial input. [Forward geocoding](\u002Flearn\u002Fgeocoding\u002F) is optimized for accuracy on complete input and can interpolate addresses. Use autocomplete for interactive search-as-you-type; switch to forward geocoding when the user finalizes the query, for example by pressing Enter.\n\n### Which SDKs does Stadia Maps offer for address autocomplete?\n\nStadia Maps offers three first-party SDKs for address autocomplete: the [MapLibre GL JS Search Box plugin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F) for the web, [SwiftUI Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fswiftui-autocomplete-search\u002F) for iOS, and [Jetpack Compose Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjetpack-compose-autocomplete-search\u002F) for Android. Each handles debouncing, caching, and result ordering out of the box. If none fit, the underlying HTTP API is available directly.\n\n### What are the default autocomplete timing and input settings on Stadia Maps?\n\nThe Stadia Maps autocomplete SDKs default to a 100ms minimum wait period between requests (`minWaitPeriodMs`) and a 3-character minimum input length (`minInputLength`). The [MapLibre GL JS Search Box plugin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F) also defaults `maxResults` to 5. These defaults balance server load with responsiveness.\n\n### How is an address autocomplete request billed on Stadia Maps?\n\nAutocomplete requests are billed from the unified [Stadia Maps API](\u002Fpricing\u002F) credit pool, the same pool that covers forward geocoding, reverse geocoding, routing, and tiles. Each autocomplete request is a single billable request.\n\n## Where to Go Next\n\n### From the Blog\n\nMore on geocoding and search from the Stadia Maps blog:\n\n- [The Hidden Cost of Search: Why Your Geocoding Bill Is Higher Than It Should Be](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F)\n- [The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos](\u002Fblog\u002Fopen-data-geocoding-global-search\u002F)\n- [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F)\n- [Autocomplete Search for SwiftUI and Jetpack Compose](\u002Fblog\u002Fautocomplete-search-for-swiftui-and-jetpack-compose\u002F)\n- [Introducing Geocoding & Search v2](\u002Fblog\u002Fintroducing-stadia-maps-geocoding-search-v2\u002F)\n\n### Geocoding & Search\n\n- [What Is Geocoding?](\u002Flearn\u002Fgeocoding\u002F) for the complete forward-direction overview\n- [What Is Reverse Geocoding?](\u002Flearn\u002Freverse-geocoding\u002F) for the opposite direction\n- [Autocomplete Search API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F) for the full parameter set\n- [MapLibre GL JS Search Box plugin](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F) for the web\n- [SwiftUI Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fswiftui-autocomplete-search\u002F) for iOS\n- [Jetpack Compose Autocomplete Search](https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjetpack-compose-autocomplete-search\u002F) for Android\n- [Layers documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Flayers\u002F) for the full list of returnable place types\n- [Sources documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsources\u002F): the five open data providers behind the API\n- [Autocomplete Search product page](\u002Fproducts\u002Fgeocoding-search\u002Fautocomplete-search\u002F) and pricing tiers\n",{"title":315,"description":401,"path":402,"published":403,"category":301,"rawbody":404},"Geocoding converts addresses to coordinates and back. Learn how our global geocoding API works, its accuracy levels, and best practices.","\u002Flearn\u002Fgeocoding","2026-07-14","---\ntitle: What Is Geocoding?\ndescription: Geocoding converts addresses to coordinates and back. Learn how our global geocoding API works, its accuracy levels, and best practices.\nauthor: Stadia Maps Team\ncategory: Geocoding & Search\nhead:\n  script: []\nimage: \u002Fimages\u002Fog\u002Fwhat-is-geocoding.png\nimageAlt: What Is Geocoding? — Stadia Maps\npublished: 2026-07-14\nmodified: 2026-08-26\nterm: Geocoding\ntermDescription: The process of converting an address, place name, or point of interest into geographic coordinates.\n---\n\n# What Is Geocoding?\n\n[Geocoding](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FAddress_geocoding) is the process of converting an address, place name, or point of interest into geographic coordinates (latitude and longitude). Also called address geocoding, address lookup, or place search, geocoding is the foundation of any product that needs to bridge human-readable places and machine-readable coordinates. Reverse geocoding does the opposite: it takes a coordinate pair and returns the nearest place. The [Stadia Maps Geocoding API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) handles both directions, along with structured, bulk, and autocomplete variants, and draws on a documented set of open data sources so the provenance of every result is inspectable.\n\n## Key Takeaways\n\n- Geocoding converts a human-readable address or place name into geographic coordinates (latitude and longitude). Reverse geocoding does the opposite.\n- Geocoding quality depends on the underlying data. The Stadia Maps Geocoding API documents its five sources: OpenStreetMap, OpenAddresses, Who's On First, GeoNames, and Foursquare Open Source Places.\n- One credit pool covers forward, reverse, structured, bulk, and autocomplete variants. Pick the endpoint that matches the input shape.\n- Accuracy varies by country. Build a confidence check into any product that geocodes internationally.\n- Stadia Maps permits permanent storage of geocoded results on Standard, Professional, and Enterprise plans without a per-request surcharge.\n\n## Forward vs. Reverse Geocoding\n\nGeocoding has a direction. Every product decision that involves it starts with picking the right one.\n\n- **Forward geocoding** takes a string like `Pärnu mnt 388b` and returns coordinates like `59.381096, 24.661382`. Used for search bars, address forms, and any workflow where a user or dataset knows the place name and needs the location.\n- **Reverse geocoding** takes coordinates like `59.381096, 24.661382` and returns the nearest known place. Used when the input is a GPS fix, a map click, or an IoT device pinging its location.\n\nSome products need both. A ride-share driver's phone reverses their coordinates to display an address; the passenger's app forward-geocodes a destination string to route to it. The [Stadia Maps Geocoding API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) exposes separate endpoints for each direction, plus specialized ones for autocomplete, structured input, and bulk processing.\n\nFor a deeper look at the coordinates-to-place direction, see [What Is Reverse Geocoding?](\u002Flearn\u002Freverse-geocoding\u002F)\n\n## How Geocoding Actually Works\n\nUnder the hood, a geocoder is a chain of parsing, matching, scoring, and ranking decisions. The steps look roughly like this:\n\n1. **Parse the input.** Break the query into components (house number, street, city, postal code, country, place type).\n2. **Search candidate records.** Query the underlying database for matches across the relevant data sources and layers.\n3. **Score candidates.** Rank by string similarity, geographic focus, layer priority, and boundary constraints.\n4. **Interpolate when necessary.** For addresses that do not exist verbatim in the database, the geocoder can estimate the location by interpolating along the street segment. Not every geocoder does this. The Stadia Maps [Forward Geocoding endpoint](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F) does.\n5. **Return the best matches** with a confidence score and full attribution so the caller can decide what to trust.\n\nThe details of each step vary by provider, which is why two geocoders can return different results for the same query. Understanding this pipeline is the difference between debugging a geocoding bug in an hour and shipping a workaround that quietly returns the wrong city for 3% of your users.\n\n## What Data Sources Does a Geocoder Use?\n\nEvery geocoder is only as good as the data it searches. The Stadia Maps Geocoding API is transparent about what it queries; the [full source list](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsources\u002F) is documented and each result carries attribution back to its origin.\n\n- [**OpenStreetMap**](https:\u002F\u002Fwww.openstreetmap.org\u002F) provides the primary global coverage for roads, addresses, and points of interest. Community-maintained and open.\n- [**OpenAddresses**](https:\u002F\u002Fopenaddresses.io\u002F) aggregates authoritative address data from government and public sources worldwide. Stadia Maps is a [corporate sponsor](\u002Fattribution\u002F) of the project.\n- [**Who's On First**](https:\u002F\u002Fwhosonfirst.org\u002F) provides a global gazetteer of administrative places (countries, regions, counties, localities, neighborhoods). Used for hierarchy and reverse geocoding at the boundary level.\n- [**GeoNames**](https:\u002F\u002Fwww.geonames.org\u002F) adds populated places, natural features, and administrative fill-in for parts of the world where OSM coverage is thinner.\n- [**Foursquare Open Source Places**](https:\u002F\u002Fdocs.foursquare.com\u002Fdata-products\u002Fdocs\u002Ffsq-places-open-source) contributes point-of-interest data for businesses and venues.\n\nFiltering the `sources` parameter lets you constrain results to a subset when you want to control what backs your search. That is a real feature; most competitor APIs treat their data provenance as a trade secret.\n\n## Key Geocoding API Parameters\n\nThe forward geocoding endpoint takes one required parameter (`text`) and several optional ones that dramatically change what you get back. Full details in the [Forward Geocoding docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F).\n\n- **`text`**: The place name or address. Required.\n- **`focus.point.lat` \u002F `focus.point.lon`**: Bias results toward a focus point. Use the user's map center or their known location to prefer nearby matches.\n- **`boundary.rect.*`, `boundary.circle.*`, `boundary.country`, `boundary.gid`**: Hard limits on where results can appear. Use these when your product only operates in specific regions.\n- **`layers`**: Restrict to specific data layers (`address`, `venue`, `postalcode`, `country`, and more). Fewer layers means faster, more relevant results.\n- **`sources`**: Restrict to specific data sources (`openstreetmap`, `openaddresses`, `whosonfirst`, `geonames`, `foursquare`). Useful when you want, for example, only address-authoritative sources for a shipping form.\n- **`size`**: Maximum number of results to return. Default is 10.\n- **`lang`**: A BCP47 language tag for localized results.\n\nThe single most common mistake is over-constraining. If your first query returns nothing, drop a boundary or a layer filter before assuming the geocoder is broken.\n\n## Why Geocoding Accuracy Varies by Country\n\nGeocoding quality is not uniform globally. Address density, government data availability, and OSM coverage all vary by country. This is a factual limitation that competitor \"what is geocoding\" pages tend to skip.\n\nSome patterns worth knowing:\n\n- **North America and Western Europe** have deep coverage across OSM, OpenAddresses, and Who's On First. Interpolation fills in most missing house numbers along known streets.\n- **Japan and parts of East Asia** use non-linear addressing systems that do not map cleanly to street-and-number geocoders. Structured input helps a lot here; see the [Structured Geocoding endpoint](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F).\n- **Rapidly growing cities** in South Asia, Southeast Asia, and Africa may have addresses that exist physically but are not yet in any data source. Fuzzy matching and community-driven OSM contributions close the gap over time; expect variance.\n- **Rural and remote areas** everywhere degrade gracefully to the nearest named place rather than an exact street number.\n\nIf your product operates internationally, build in a confidence check (see the [Determining Result Quality docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fdetermining-result-quality\u002F)) and design a fallback UX for low-confidence matches. Do not assume the same accuracy in every market.\n\n## How Do You Geocode an Address?\n\nHere is what a forward geocoding request to the Stadia Maps Geocoding API looks like. This example geocodes an address in Tallinn, Estonia.\n\n```http\nGET https:\u002F\u002Fapi.stadiamaps.com\u002Fgeocoding\u002Fv1\u002Fsearch?text=P%C3%B5hja+pst+27\n```\n\nThe response is a GeoJSON `FeatureCollection`. Each feature carries the coordinates, the parsed address components, a confidence score, and source attribution. Full response format details are in the [Common Response Format docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fapi-response-format\u002F).\n\nFor runnable code in TypeScript, Python, Kotlin, Swift, PHP, or cURL, see the [Stadia Maps Forward Geocoding API docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F).\n\n## Structured vs. Bulk vs. Autocomplete Geocoding\n\nForward geocoding is not always the right endpoint. The [Geocoding & Search overview](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) breaks down when to use each variant.\n\n- **Building an interactive search-as-you-type experience?** Use the [Autocomplete endpoint](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F). It is optimized for partial input and faster response times. See [What Is Address Autocomplete?](\u002Flearn\u002Faddress-autocomplete\u002F)\n- **Working with pre-parsed address components** (`house_number`, `street`, `city`, `region`, `postalcode`, `country`)? Use [Structured Geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F). It takes the guesswork out of string parsing and improves accuracy for postal addresses, especially internationally.\n- **Processing thousands of addresses at once?** Use [Bulk Geocoding](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F). Up to 5,000 queries per request.\n- **Reversing coordinates back to a place?** Use the [Reverse Geocoding endpoint](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F).\n\nComparing providers rather than endpoints? See [What Is the Best Geocoding API?](\u002Flearn\u002Fbest-geocoding-api\u002F) for the evaluation criteria that matter after launch.\n\n## Where Geocoding Falls Short\n\nGeocoding has real limits. A page that pretends otherwise is not being honest with the reader.\n\n- **A geocoder is not an address validator.** It returns the best match it can find. If your user typed a nonexistent address, the geocoder will often return a nearest-street-segment interpolation rather than an error. Check the confidence score and layer type on every result before treating it as authoritative.\n- **Autocomplete and forward geocoding are not interchangeable.** Autocomplete is optimized for speed on partial input; forward geocoding is optimized for accuracy on complete input. Using one where the other belongs produces bad UX or bad results.\n- **Interpolated addresses are estimates, not guarantees.** The result may be tens of meters off the actual building, or on the wrong side of the street. For delivery-critical use cases, verify with a follow-up reverse geocode or with authoritative sources.\n- **Two providers rarely agree exactly.** Different providers use different data sources, different scoring, and different parsers. Pick one and standardize within your own product to avoid inconsistencies.\n- **You may or may not be allowed to store results.** Most vendors charge extra to persist geocoding results in your own database. Stadia Maps allows permanent storage on the Standard, Professional, and Enterprise plans without a surcharge; see the [terms of service](\u002Fterms-of-service\u002F) for details.\n\n## Common Geocoding Use Cases\n\nGeocoding shows up anywhere a product needs to move between human-readable places and machine-readable coordinates. A partial list:\n\n- **Address forms and checkout flows.** Convert a user-entered shipping address to coordinates for downstream routing, delivery-zone checks, or tax calculation.\n- **Store locator and site finder.** Take a user's zip code or city and center the map on the corresponding coordinates.\n- **Lead enrichment and CRM cleanup.** Bulk-geocode a customer list to enable geographic segmentation, territory analysis, or field-sales routing.\n- **Logistics and last-mile delivery.** Convert delivery addresses to coordinates for isochrone-based service-area decisions or routing.\n- **Real estate search.** Geocode a listing's address to place it on a map and enable spatial queries.\n- **Location-aware AI and agents.** Give an LLM or agent the ability to translate free-text user requests (\"a coffee shop near Union Square\") into structured coordinates for a follow-up API call.\n\n::faq-section\n---\nfaqs:\n  - question: What is address geocoding?\n    answer: Address geocoding is the process of converting a street address or place\n      name into geographic coordinates (latitude and longitude). It is the\n      primary way products bridge between human-readable location input and\n      machine-readable spatial data. The Stadia Maps Geocoding API handles\n      address geocoding through its forward geocoding, structured geocoding, and\n      autocomplete endpoints.\n  - question: What is the difference between geocoding and reverse geocoding?\n    answer: \"Geocoding (forward geocoding) converts an address or place name into\n      coordinates. Reverse geocoding does the opposite: it converts coordinates\n      into an address or place. Products that combine both directions are\n      common. For example, a user types a destination (forward geocoded) and a\n      driver's phone shows the address of their current GPS position (reverse\n      geocoded).\"\n  - question: What data sources does the Stadia Maps Geocoding API use?\n    answer: \"The Stadia Maps Geocoding API queries five documented open sources:\n      OpenStreetMap for global roads and points of interest, OpenAddresses for\n      authoritative government address data, Who's On First for administrative\n      places, GeoNames for populated places and natural features, and Foursquare\n      Open Source Places for business and venue data. Every result carries\n      attribution back to its source, and Stadia Maps is a corporate sponsor of\n      the OpenAddresses project.\"\n  - question: Can I store geocoded addresses permanently on Stadia Maps?\n    answer: Yes. With an active Standard, Professional, or Enterprise subscription,\n      geocoded results can be stored permanently in your own database, with no\n      per-request surcharge and no per-user re-validation. Temporary storage in\n      the normal course of your work is allowed on all plans, including Free.\n      Per Stadia Maps' published analysis, Mapbox, AWS, and ESRI often charge\n      between 6x and 8x the cost of a regular query to store results, and Google\n      generally forbids caching outside a specific end-user session.\n  - question: How much does a geocoding request cost on Stadia Maps?\n    answer: Geocoding requests draw from a unified credit pool that also covers\n      routing, tiles, and other endpoints. Forward, structured, and reverse\n      geocoding each cost 20 credits per request. Autocomplete v2 costs 1 credit\n      per request. Bulk geocoding is billed per query inside the batch at the\n      same rate as an individual request, so there are no extra fees for using\n      batch mode.\n  - question: How accurate is geocoding?\n    answer: Accuracy varies by country and by data source. North America and Western\n      Europe have deep coverage across OpenStreetMap, OpenAddresses, and Who's\n      On First. Regions with non-linear addressing systems or newer construction\n      see more variance. Every Stadia Maps result returns a confidence score and\n      a layer type, which is how you detect a weak match in production rather\n      than shipping it to a user.\n---\n::\n\n## Where to Go Next\n\n### From the Blog\n\nMore on geocoding from the Stadia Maps blog:\n\n- [The Open Data Superpower: Why Global Search is Moving Beyond Proprietary Silos](\u002Fblog\u002Fopen-data-geocoding-global-search\u002F)\n- [The Hidden Cost of Search: Why Your Geocoding Bill Is Higher Than It Should Be](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F)\n- [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F)\n- [75 Million More Addresses: Expanding Geocoding Precision](\u002Fblog\u002F75-million-more-addresses-geocoding-precision\u002F)\n- [Introducing Stadia Maps Geocoding & Search v2: Supercharge Your Search](\u002Fblog\u002Fintroducing-stadia-maps-geocoding-search-v2\u002F)\n\n### Geocoding & Search\n\n- [What Is Reverse Geocoding?](\u002Flearn\u002Freverse-geocoding\u002F) for the coordinates-to-place direction\n- [What Is Address Autocomplete?](\u002Flearn\u002Faddress-autocomplete\u002F) for search-as-you-type\n- [What Is the Best Geocoding API?](\u002Flearn\u002Fbest-geocoding-api\u002F) for how to evaluate providers\n- [Geocoding & Search overview docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) for best practices and endpoint selection\n- [Forward Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F)\n- [Reverse Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F)\n- [Structured Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fstructured-search\u002F)\n- [Bulk Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fbulk-geocoding-search\u002F)\n- [Autocomplete Search API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F)\n- [Sources documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsources\u002F): full list of data providers behind the API\n- [Determining Result Quality](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fdetermining-result-quality\u002F): how to read confidence and layer signals\n- [Geocoding product page](\u002Fproducts\u002Fgeocoding-search\u002Fgeocoding\u002F) and [pricing tiers](\u002Fpricing\u002F)\n",{"title":322,"description":406,"path":407,"published":408,"category":301,"rawbody":409},"Reverse geocoding converts coordinates into an address or nearby place. Learn how it handles administrative layers and how to build one with Stadia Maps.","\u002Flearn\u002Freverse-geocoding","2026-07-16","---\ntitle: What Is Reverse Geocoding?\ndescription: Reverse geocoding converts coordinates into an address or nearby place. Learn how it handles administrative layers and how to build one with Stadia Maps.\ncategory: Geocoding & Search\nhead:\n  script: []\nimage: \u002Fimages\u002Fog\u002Fwhat-is-reverse-geocoding.png\npublished: 2026-07-16\nschemaOrg:\n  - \"@type\": SoftwareApplication\n    name: Stadia Maps Reverse Geocoding API\n    description: Convert latitude\u002Flongitude coordinates to street addresses\n    url: https:\u002F\u002Fstadiamaps.com\u002Flearn\u002Freverse-geocoding\u002F\n    applicationCategory: Utility\n    operatingSystem: Web\n    offers:\n      \"@type\": Offer\n      price: \"0\"\n      priceCurrency: USD\n      url: https:\u002F\u002Fstadiamaps.com\u002Fpricing\u002F\n  - \"@type\": FAQPage\n    mainEntity:\n      - \"@type\": Question\n        name: What is reverse geocoding used for?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Reverse geocoding is used to convert a coordinate pair into a human-readable address, place name, or administrative boundary. Common uses include showing a rider's pickup address from GPS coordinates, powering nearby-place suggestions in delivery apps, tagging photos with a location, and identifying which city, county, or country a point falls within.\n      - \"@type\": Question\n        name: What is the difference between reverse geocoding and forward geocoding?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: \"Forward geocoding converts an address or place name into coordinates. Reverse geocoding does the opposite: it converts coordinates into an address or nearby place. Products that combine both directions are common.\"\n      - \"@type\": Question\n        name: What layers can reverse geocoding return on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: The Stadia Maps reverse geocoding endpoint can return fine-grained layers (address, poi, street) or coarse administrative layers (neighbourhood, locality, county, region, country). Use the layers parameter to restrict results. Coarse layers return features that contain the point; fine layers return the nearest features by distance.\n      - \"@type\": Question\n        name: Can I reverse geocode to a postal code?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Not directly. Postal codes are not used as a reverse geocoding layer on the Stadia Maps API. If you need a postal code for a coordinate, use reverse geocoding to retrieve the address and read the postal code from that result.\n      - \"@type\": Question\n        name: How much does a reverse geocoding request cost on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Reverse geocoding requests are billed from the unified Stadia Maps API credit pool, the same pool that covers forward geocoding, routing, and tiles. Each reverse geocoding request is a single billable request.\nterm: Reverse Geocoding\ntermDescription: The process of converting a coordinate pair into a human-readable address or place.\nseo:\n  title: \"Reverse Geocoding API: Convert Coordinates to Addresses\"\n  ogDescription: Learn how to convert latitude\u002Flongitude coordinates to street addresses with Stadia Maps' reverse geocoding API. Fast, accurate, privacy-first.\n  description: Reverse geocoding converts coordinates into an address or nearby place. Learn how it handles administrative layers and how to build one with Stadia Maps.\n---\n\n# What Is Reverse Geocoding?\n\n[Reverse geocoding](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FReverse_geocoding) is the process of converting a coordinate pair (latitude and longitude) into a human-readable address, place name, or administrative boundary. Also called coordinate lookup or address lookup from coordinates, reverse geocoding is what turns a GPS fix, a map click, or an IoT device ping into something a person can read. It is the counterpart to [forward geocoding](\u002Flearn\u002Fgeocoding\u002F), which goes the other direction (address to coordinates). The [Stadia Maps Reverse Geocoding API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) can return the nearest address, the nearest point of interest, or the administrative context (`neighbourhood`, `locality`, `county`, `region`, `country`) for any point on Earth.\n\n## Key Takeaways\n\n- Reverse geocoding converts coordinates into an address, place name, or administrative boundary.\n- The Stadia Maps Reverse Geocoding API supports fine-grained layers (`address`, `poi`, `street`) and coarse administrative layers (`neighbourhood`, `locality`, `county`, `region`, `country`).\n- Coarse-layer requests return features that contain the point. Fine-layer requests return the nearest features by distance.\n- Postal codes are not a reverse-geocoding layer on the Stadia Maps API. Read them from the returned address instead.\n- Reverse geocoding is available on every Stadia Maps plan, and results can be stored permanently on Standard, Professional, and Enterprise plans.\n\n## How Reverse Geocoding Works\n\nUnder the hood, reverse geocoding is a spatial search problem with two distinct modes.\n\n1. **Nearest-neighbor mode** (for fine-grained layers like `address`, `poi`, and `street`). The geocoder searches for the closest features to the coordinate and returns them sorted by distance.\n2. **Point-in-polygon mode** (for coarse administrative layers like `country`, `region`, `county`, `locality`, and `neighbourhood`). The geocoder returns the features whose boundaries contain the point.\n\nThe [Stadia Maps Reverse Geocoding API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) runs both modes from the same endpoint. Which behavior you get depends on the `layers` parameter you pass. Combined queries return a mixed result set.\n\nEach result carries source attribution and a confidence score. See [Determining Result Quality](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fdetermining-result-quality\u002F) for how to read those signals.\n\n## What Are Layers in Reverse Geocoding?\n\nEvery place in the Stadia Maps geocoder is tagged with a [layer](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Flayers\u002F) that describes what kind of thing it is. Reverse geocoding uses layers in two ways: to filter what comes back, and to determine how the search is executed (nearest versus containing).\n\nThe layers most useful for reverse geocoding:\n\n- `address`: A specific street address.\n- `poi` (or `venue` in v1): A business, building, or point of interest.\n- `street`: A road or street segment.\n- `neighbourhood`: A social or administrative neighbourhood (note the British spelling).\n- `locality`: A town, hamlet, or city.\n- `county`, `region`, `country`: Progressively larger administrative units.\n- `coarse`: An alias that queries all administrative layers at once. Fast, useful when you only need context.\n\nPostal codes are not used as a reverse-geocoding layer on the Stadia Maps API. If you need a postal code for a point, reverse geocode to the address layer and read the postal code from the result.\n\n## Reverse Geocoding Parameters That Matter\n\nThe [Reverse Geocoding endpoint](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) takes two required parameters and several optional ones that change the result set.\n\n- `point.lat` and `point.lon`: The coordinate to reverse geocode. Both required.\n- `layers`: Restrict the search to specific layers. Defaults to fine-grained layers when omitted.\n- `sources`: Restrict to specific data sources (`openstreetmap`, `openaddresses`, `whosonfirst`, `geonames`, `foursquare`).\n- `boundary.country`: Limit results to specific countries (ISO 2 or 3 character codes).\n- `boundary.circle.radius`: For fine-grained queries, limit the search to a circle around the point. Defaults to 1km.\n- `size`: Maximum number of results to return. Defaults to 10.\n\nThe most common tuning move is switching to `layers=coarse` for fast administrative-context lookups. That query type does not need to sort by distance and typically returns quickly.\n\n## How Do You Reverse Geocode a Coordinate?\n\nHere is what a reverse geocoding request to the Stadia Maps API looks like. This example reverses a point in Tallinn, Estonia.\n\n```http\nGET https:\u002F\u002Fapi.stadiamaps.com\u002Fgeocoding\u002Fv2\u002Freverse?point.lat=59.444351&point.lon=24.750645\n```\n\nThe response is a GeoJSON `FeatureCollection`. Each feature includes the coordinates, parsed address components, layer, confidence score, and source attribution. Full response format details are in the [Common Response Format docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fapi-response-format\u002F).\n\nFor runnable code in TypeScript, Python, Kotlin, Swift, PHP, or cURL, see the [Stadia Maps Reverse Geocoding API docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F).\n\n## Where Reverse Geocoding Falls Short\n\nReverse geocoding has real limits worth knowing before you build.\n\n- **Coordinates in ambiguous places produce ambiguous results.** A point inside a parking lot, an office park, or a large building can return the parent property, a neighboring address, or nothing useful. Always check the layer and confidence of the top result.\n- **Coordinates over water or wilderness are best effort.** Reverse geocoding returns the nearest feature; if that feature is 20km away, the result is a geographic fact, not an address.\n- **Coarse and fine results answer different questions.** \"What city is this in?\" (coarse, point-in-polygon) and \"What is the nearest street address?\" (fine, nearest-neighbor) look similar but return different shapes of answer. Pick the layer that matches the question.\n- **Postal codes are not a reverse-geocoding layer.** As noted above, read them from the returned address rather than querying them directly.\n- **Two providers rarely agree exactly.** Different providers use different data, different scoring, and different tie-breaking logic. Standardize on one provider to keep your product consistent.\n\n## Common Reverse Geocoding Use Cases\n\nReverse geocoding appears wherever a product has coordinates but needs to display something a human can read.\n\n- **Delivery and ride-share pickup.** A driver's phone reports GPS coordinates. The app reverses those coordinates to display the pickup address to the passenger.\n- **Emergency response.** A 911 call carries GPS coordinates. Reverse geocoding turns those into a street address for the dispatcher.\n- **Photo and content tagging.** Add city, region, and country tags to photos or posts based on where they were captured.\n- **IoT and connected devices.** A sensor pings its location periodically; reverse geocoding turns that into a place the operator recognizes.\n- **Location-aware AI and agents.** Give an agent the ability to answer \"Where am I?\" or \"What neighborhood is this?\" from raw coordinates.\n- **Analytics and segmentation.** Roll up event coordinates to city, region, or country for cohort analysis without asking the user for input.\n\n## Frequently Asked Questions\n\n### What is reverse geocoding used for?\n\nReverse geocoding is used to convert a coordinate pair into a human-readable address, place name, or administrative boundary. Common uses include showing a rider's pickup address from GPS coordinates, powering nearby-place suggestions in delivery apps, tagging photos with a location, and identifying which city, county, or country a point falls within.\n\n### What is the difference between reverse geocoding and forward geocoding?\n\nForward geocoding converts an address or place name into coordinates. Reverse geocoding does the opposite: it converts coordinates into an address or nearby place. See [What Is Geocoding?](\u002Flearn\u002Fgeocoding\u002F) for a full explanation of the forward direction; products that combine both are common.\n\n### What layers can reverse geocoding return on Stadia Maps?\n\nThe Stadia Maps reverse geocoding endpoint can return fine-grained layers (`address`, `poi`, `street`) or coarse administrative layers (`neighbourhood`, `locality`, `county`, `region`, `country`). Use the `layers` parameter to restrict results. Coarse layers return features that contain the point; fine layers return the nearest features by distance. Full list in the [Layers documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Flayers\u002F).\n\n### Can I reverse geocode to a postal code?\n\nNot directly. Postal codes are not used as a reverse geocoding layer on the Stadia Maps API. If you need a postal code for a coordinate, use reverse geocoding to retrieve the address and read the postal code from that result.\n\n### How much does a reverse geocoding request cost on Stadia Maps?\n\nReverse geocoding requests are billed from the unified [Stadia Maps API](\u002Fpricing\u002F) credit pool, the same pool that covers forward geocoding, routing, and tiles. Each reverse geocoding request is a single billable request.\n\n## Where to Go Next\n\n### From the Blog\n\nMore on geocoding and search from the Stadia Maps blog:\n\n- [The Hidden Cost of Search: Why Your Geocoding Bill Is Higher Than It Should Be](\u002Fblog\u002Fwhy-is-your-geocoding-bill-higher-than-it-should-be\u002F)\n- [The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos](\u002Fblog\u002Fopen-data-geocoding-global-search\u002F)\n- [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F)\n- [75 Million More Addresses: Expanding Geocoding Precision](\u002Fblog\u002F75-million-more-addresses-geocoding-precision\u002F)\n- [Introducing Geocoding & Search v2](\u002Fblog\u002Fintroducing-stadia-maps-geocoding-search-v2\u002F)\n\n### Geocoding & Search\n\n- [What Is Geocoding?](\u002Flearn\u002Fgeocoding\u002F) for the forward direction and a full geocoding overview\n- [Reverse Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Freverse-search\u002F) for the full parameter set\n- [Layers documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Flayers\u002F) for the full list of returnable place types\n- [Sources documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsources\u002F): the five open data providers behind the API\n- [Determining Result Quality](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fdetermining-result-quality\u002F): how to read confidence and layer signals\n- [Forward Geocoding API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsearch\u002F)\n- [Autocomplete Search API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F)\n- [Geocoding product page](\u002Fproducts\u002Fgeocoding-search\u002Fgeocoding\u002F) and pricing tiers\n",{"id":411,"bio":384,"extension":18,"jobTitle":384,"meta":412,"name":413,"sameAs":414,"slug":417,"stem":418,"twitterCreator":384,"type":419,"url":420,"__hash__":421},"authors\u002Fauthors\u002Fstadia-maps.yml",{},"Stadia Maps",[415,416],"https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fstadia-maps\u002F","https:\u002F\u002Fgithub.com\u002Fstadiamaps","stadia-maps","authors\u002Fstadia-maps","Organization","https:\u002F\u002Fstadiamaps.com\u002F","jRSutfRcYEknA-OSdkWoPHgm7Iep6BJfLBIsMtzQONk",1789563641318]