[{"data":1,"prerenderedAt":553},["ShallowReactive",2],{"footer-learn-links":3,"site-prefooter-cta":16,"learn-\u002Flearn\u002Fgdpr-compliant-mapping-api\u002F":24,"related-learn-\u002Flearn\u002Fgdpr-compliant-mapping-api\u002F":524,"learn-org-author":541},[4,7,10,13],{"title":5,"path":6},"What Is a GDPR-Compliant Mapping API?","\u002Flearn\u002Fgdpr-compliant-mapping-api",{"title":8,"path":9},"What Is Satellite Imagery Resolution?","\u002Flearn\u002Fsatellite-imagery-resolution",{"title":11,"path":12},"What Is Address Autocomplete?","\u002Flearn\u002Faddress-autocomplete",{"title":14,"path":15},"Vector vs. Raster Map Tiles","\u002Flearn\u002Fvector-versus-raster-map-tiles",{"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,"body":26,"category":507,"description":508,"extension":509,"head":510,"image":512,"imageAlt":513,"keywords":513,"meta":514,"modified":513,"navigation":516,"path":6,"published":517,"rawbody":518,"schemaOrg":513,"seo":519,"stem":520,"term":521,"termDescription":522,"__hash__":523},"learn\u002Flearn\u002Fgdpr-compliant-mapping-api.md",{"type":27,"value":28,"toc":490},"minimark",[29,33,46,49,54,82,86,89,98,142,159,163,166,174,192,195,199,202,212,227,235,244,250,254,263,266,270,273,305,314,318,321,347,350,354,357,395,399,403,408,411,431,435,486],[30,31,5],"h1",{"id":32},"what-is-a-gdpr-compliant-mapping-api",[34,35,36,37,45],"p",{},"When teams evaluate a mapping API for GDPR, they are usually asking three concrete questions: does the provider track my end users, what does it log, and where are requests processed. Stadia Maps documents its answers to all three. Per the ",[38,39,44],"a",{"href":40,"rel":41,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Feu-gdpr-endpoints\u002F",[42],"external","_blank","EU endpoints documentation",", Stadia Maps is \"confident that our privacy practices and procedures satisfy GDPR requirements by default,\" and offers EU-only endpoints for teams that need a guarantee that requests never leave the European Union.",[34,47,48],{},"This page covers what Stadia Maps does. It is not legal advice, and it does not assess whether any particular application is compliant.",[50,51,53],"h2",{"id":52},"key-takeaways","Key Takeaways",[55,56,57,61,64,67,79],"ul",{},[58,59,60],"li",{},"Stadia Maps does not track end users, build behavioral profiles, resell data, or use data for ad targeting.",[58,62,63],{},"Map tiles and API calls are cookie-less, stateless, and anonymous by default. There are no third-party cookies or tracking pixels on any service.",[58,65,66],{},"EU-only endpoints route all requests to servers in Frankfurt and Paris, and PII is scrubbed at the network edge.",[58,68,69,70,74,75,78],{},"Switching to EU endpoints is a hostname change: ",[71,72,73],"code",{},"tiles-eu.stadiamaps.com"," and ",[71,76,77],{},"api-eu.stadiamaps.com",".",[58,80,81],{},"Stadia Maps publishes a Data Processing Addendum and a Privacy Policy covering what is collected and why.",[50,83,85],{"id":84},"what-does-a-mapping-api-actually-collect","What Does a Mapping API Actually Collect?",[34,87,88],{},"The privacy question that matters for most teams is not what the provider promises, but what the integration technically does. Some location SDKs generate telemetry from user actions regardless of what your own application logs.",[34,90,91,92,97],{},"Per the ",[38,93,96],{"href":94,"rel":95,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Fprivacy\u002Fprivacy-commitment\u002F",[42],"Stadia Maps privacy commitment",", the platform is built so that:",[55,99,100,107,113,118,124,130,136],{},[58,101,102,103],{},"There are ",[104,105,106],"strong",{},"no client-side scripts that phone home",[58,108,102,109,112],{},[104,110,111],{},"no third-party cookies or tracking pixels"," on any service",[58,114,102,115],{},[104,116,117],{},"no user-identifying headers or geolocation sniffing",[58,119,120,121],{},"Map tiles and API calls are ",[104,122,123],{},"cookie-less, stateless, and anonymous by default",[58,125,126,127],{},"Geocoding and search are ",[104,128,129],{},"query-based, not session-based",[58,131,132,133],{},"Routing and navigation ",[104,134,135],{},"does not store location history",[58,137,138,139],{},"Maps ",[104,140,141],{},"do not log identifying info",[34,143,144,145,149,150,152,153,158],{},"What Stadia Maps does collect is limited to operating and securing the infrastructure, preventing abuse and fraud, and debugging service issues. Per the privacy commitment page, Stadia Maps \"never collect ",[146,147,148],"span",{},"s"," or store ",[146,151,148],{}," location data tied to individual users.\" The ",[38,154,157],{"href":155,"rel":156,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Fprivacy\u002Fprivacy-policy\u002F",[42],"Privacy Policy"," covers the specifics.",[50,160,162],{"id":161},"what-are-eu-only-endpoints","What Are EU-Only Endpoints?",[34,164,165],{},"Some teams need more than a policy commitment. They need a guarantee that network requests are handled inside a specific jurisdiction, either because of internal policy, a customer contract, or a regulator.",[34,167,168,169,173],{},"Stadia Maps offers ",[38,170,172],{"href":40,"rel":171,"target":43},[42],"EU-only endpoints"," for exactly that case. Per the documentation:",[55,175,176,185],{},[58,177,178,179,74,182,78],{},"Requests connect exclusively to two servers positioned in the European Union: ",[104,180,181],{},"Frankfurt, Germany",[104,183,184],{},"Paris, France",[58,186,187,188,191],{},"Stadia Maps systems ",[104,189,190],{},"scrub PII at the network's edge",", so any request that must ultimately be handled by internal services in other regions is managed privately.",[34,193,194],{},"This is offered as an option rather than a default, because the standard endpoints already operate under the same privacy practices. EU endpoints exist for teams that need the jurisdictional guarantee on top.",[50,196,198],{"id":197},"how-do-you-use-the-eu-endpoints","How Do You Use the EU Endpoints?",[34,200,201],{},"Switching is a hostname change. No code restructuring, no separate account.",[34,203,204,205,208,209,211],{},"For map tiles and styles, replace ",[71,206,207],{},"tiles.stadiamaps.com"," with ",[71,210,73],{},":",[213,214,219],"pre",{"className":215,"code":216,"language":217,"meta":218,"style":218},"language-http shiki shiki-themes github-light","https:\u002F\u002Ftiles-eu.stadiamaps.com\u002Fstyles\u002Falidade_smooth.json\n","http","",[71,220,221],{"__ignoreMap":218},[146,222,225],{"class":223,"line":224},"line",1,[146,226,216],{},[34,228,229,230,208,233,211],{},"For routing, geocoding, time zone, and other API services, replace ",[71,231,232],{},"api.stadiamaps.com",[71,234,77],{},[213,236,238],{"className":215,"code":237,"language":217,"meta":218,"style":218},"https:\u002F\u002Fapi-eu.stadiamaps.com\u002Fgeocoding\u002Fv2\u002Fsearch?text=Union+Square\n",[71,239,240],{"__ignoreMap":218},[146,241,242],{"class":223,"line":224},[146,243,237],{},[34,245,246,247,78],{},"Every official Stadia Maps SDK accepts a base path or host override, so the change is typically one line. Full examples for TypeScript, Python, Kotlin, Swift, PHP, and cURL are in the ",[38,248,44],{"href":40,"rel":249,"target":43},[42],[50,251,253],{"id":252},"what-about-self-hosting","What About Self-Hosting?",[34,255,256,257,262],{},"For teams whose requirements go beyond endpoint jurisdiction, Stadia Maps offers ",[38,258,261],{"href":259,"rel":260,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002Fon-prem-embedded\u002F",[42],"On-Prem and Embedded Solutions",". Running tiles and APIs inside your own infrastructure means location requests never reach a third party at all.",[34,264,265],{},"That is a heavier lift than switching a hostname, but it is the option that exists when a compliance requirement cannot be satisfied by a vendor commitment.",[50,267,269],{"id":268},"what-documentation-is-available-for-compliance-review","What Documentation Is Available for Compliance Review?",[34,271,272],{},"Procurement and legal teams generally ask for artifacts rather than marketing claims. Stadia Maps publishes:",[55,274,275,282,289,296],{},[58,276,277,278,281],{},"A ",[38,279,157],{"href":155,"rel":280,"target":43},[42]," covering what is collected and why",[58,283,277,284],{},[38,285,288],{"href":286,"rel":287,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Flegal\u002Fdata-processing-addendum\u002F",[42],"Data Processing Addendum",[58,290,291],{},[38,292,295],{"href":293,"rel":294,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Fterms-of-service\u002F",[42],"Terms of Service",[58,297,298,299,304],{},"An ",[38,300,303],{"href":301,"rel":302,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Finfrastructure\u002F",[42],"infrastructure overview"," describing how the platform is built",[34,306,307,308,313],{},"For requirements not covered by the standard documents, Stadia Maps works directly with teams on tailored arrangements. The ",[38,309,312],{"href":310,"rel":311,"target":43},"https:\u002F\u002Fstadiamaps.com\u002Fsupport\u002F",[42],"support page"," has contact options.",[50,315,317],{"id":316},"where-this-page-stops","Where This Page Stops",[34,319,320],{},"Worth being direct about the limits of what a vendor page can tell you.",[55,322,323,329,335,341],{},[58,324,325,328],{},[104,326,327],{},"This is not legal advice."," Whether your application is GDPR-compliant depends on what data you collect, your lawful basis, your own retention practices, and factors that have nothing to do with your mapping provider.",[58,330,331,334],{},[104,332,333],{},"A compliant provider does not make your application compliant."," The mapping API is one processor in your stack. Your own data handling is the larger question.",[58,336,337,340],{},[104,338,339],{},"Requirements vary by use case and jurisdiction."," A consumer app, a healthcare platform, and a government contractor face different obligations from the same regulation.",[58,342,343,346],{},[104,344,345],{},"Verify rather than take a vendor's word."," Read the DPA and the Privacy Policy. If a specific control matters to you, ask about it directly before you build.",[34,348,349],{},"For anything beyond what is documented, talk to counsel who knows your use case.",[50,351,353],{"id":352},"common-compliance-driven-use-cases","Common Compliance-Driven Use Cases",[34,355,356],{},"Teams that end up on EU endpoints or self-hosted deployments usually have a specific driver.",[55,358,359,365,371,377,383,389],{},[58,360,361,364],{},[104,362,363],{},"EU-based products"," with internal policy or customer contracts requiring data residency.",[58,366,367,370],{},[104,368,369],{},"Healthcare and health-adjacent apps"," where location can be combined with other fields to become sensitive.",[58,372,373,376],{},[104,374,375],{},"Financial services"," operating under sector rules on top of general privacy regulation.",[58,378,379,382],{},[104,380,381],{},"Government and public sector"," with procurement requirements around data handling and jurisdiction.",[58,384,385,388],{},[104,386,387],{},"Enterprise B2B software"," where the customer's own compliance review extends to subprocessors.",[58,390,391,394],{},[104,392,393],{},"Consumer apps positioning on privacy"," where tracking by a vendor would undercut the product's own promise.",[396,397],"faq-section",{":faqs":398},"[{\"question\":\"Does Stadia Maps track end users?\",\"answer\":\"No. Per the Stadia Maps privacy commitment, there is no user tracking, no behavioral profiling, and no data reselling or ad targeting. Map tiles and API calls are cookie-less, stateless, and anonymous by default, with no client-side scripts that phone home and no third-party cookies or tracking pixels on any service.\"},{\"question\":\"What are Stadia Maps EU endpoints?\",\"answer\":\"EU endpoints are alternate hostnames that route all requests to servers located in the European Union, specifically Frankfurt, Germany and Paris, France. Stadia Maps systems scrub PII at the network edge, so any request ultimately handled by internal services in other regions is managed privately. Use tiles-eu.stadiamaps.com for map tiles and api-eu.stadiamaps.com for API services.\"},{\"question\":\"How do I switch to Stadia Maps EU endpoints?\",\"answer\":\"Replace tiles.stadiamaps.com with tiles-eu.stadiamaps.com for map tiles and styles, and api.stadiamaps.com with api-eu.stadiamaps.com for routing, geocoding, time zone, and other API services. Every official Stadia Maps SDK accepts a base path or host override, so the change is typically one line of configuration.\"},{\"question\":\"What data does Stadia Maps collect?\",\"answer\":\"Stadia Maps collects only the minimal data necessary to operate and secure its infrastructure, prevent abuse and fraud, and debug service issues. Per the privacy commitment page, Stadia Maps never collects or stores location data tied to individual users. Full details are in the Privacy Policy.\"},{\"question\":\"Does Stadia Maps offer a Data Processing Addendum?\",\"answer\":\"Yes. Stadia Maps publishes a Data Processing Addendum alongside its Privacy Policy and Terms of Service. For requirements not covered by the standard documents, Stadia Maps works directly with teams on tailored arrangements.\"},{\"question\":\"Can I self-host Stadia Maps for compliance reasons?\",\"answer\":\"Yes. Stadia Maps offers On-Prem and Embedded Solutions for teams whose requirements go beyond endpoint jurisdiction. Running tiles and APIs inside your own infrastructure means location requests never reach a third party.\"}]",[50,400,402],{"id":401},"where-to-go-next","Where to Go Next",[404,405,407],"h3",{"id":406},"from-the-blog","From the Blog",[34,409,410],{},"More on privacy and location data from the Stadia Maps blog:",[55,412,413,419,425],{},[58,414,415],{},[38,416,418],{"href":417},"\u002Fblog\u002Finvisible-costs-of-routing-privacy-pricing-mau-trap\u002F","The Invisible Costs of Routing: Privacy, Pricing & the MAU Trap",[58,420,421],{},[38,422,424],{"href":423},"\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F","Precision Meets Privacy: Elevating the Consumer Search Experience",[58,426,427],{},[38,428,430],{"href":429},"\u002Fblog\u002Fopen-data-geocoding-global-search\u002F","The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos",[404,432,434],{"id":433},"privacy-and-compliance","Privacy and Compliance",[55,436,437,444,451,456,461,466,473,480],{},[58,438,439,443],{},[38,440,442],{"href":441},"\u002Fprivacy\u002Fprivacy-commitment\u002F","Privacy Commitment"," for what Stadia Maps does and does not collect",[58,445,446,450],{},[38,447,449],{"href":448},"\u002Fprivacy\u002Fprivate-location-apis-maps\u002F","Private Location APIs and Maps"," for the GDPR and CCPA overview",[58,452,453],{},[38,454,157],{"href":455},"\u002Fprivacy\u002Fprivacy-policy\u002F",[58,457,458],{},[38,459,288],{"href":460},"\u002Flegal\u002Fdata-processing-addendum\u002F",[58,462,463],{},[38,464,295],{"href":465},"\u002Fterms-of-service\u002F",[58,467,468,472],{},[38,469,471],{"href":40,"rel":470,"target":43},[42],"EU Endpoints documentation"," for setup instructions and code examples",[58,474,475,479],{},[38,476,478],{"href":477},"\u002Finfrastructure\u002F","Infrastructure overview"," for how the platform is built",[58,481,482,485],{},[38,483,261],{"href":484},"\u002Fproducts\u002Fon-prem-embedded\u002F"," for self-hosted deployments",[487,488,489],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":218,"searchDepth":491,"depth":491,"links":492},4,[493,495,496,497,498,499,500,501,502],{"id":52,"depth":494,"text":53},2,{"id":84,"depth":494,"text":85},{"id":161,"depth":494,"text":162},{"id":197,"depth":494,"text":198},{"id":252,"depth":494,"text":253},{"id":268,"depth":494,"text":269},{"id":316,"depth":494,"text":317},{"id":352,"depth":494,"text":353},{"id":401,"depth":494,"text":402,"children":503},[504,506],{"id":406,"depth":505,"text":407},3,{"id":433,"depth":505,"text":434},"Location Platform","A GDPR-compliant mapping API avoids tracking end users and can keep requests in the EU. Learn what Stadia Maps collects, and how EU-only endpoints work.","md",{"script":511},[],"\u002Fimages\u002Fog\u002Fwhat-is-a-gdpr-compliant-mapping-api.png",null,{"author":515},"Stadia Maps Team",true,"2026-08-05","---\ntitle: What Is a GDPR-Compliant Mapping API?\ndescription: A GDPR-compliant mapping API avoids tracking end users and can keep requests in the EU. Learn what Stadia Maps collects, and how EU-only endpoints work.\nauthor: Stadia Maps Team\ncategory: Location Platform\nimage: \u002Fimages\u002Fog\u002Fwhat-is-a-gdpr-compliant-mapping-api.png\nhead:\n  script: []\npublished: 2026-08-05\nterm: GDPR-Compliant Mapping API\ntermDescription: A mapping or location API that does not track end users, collects only operational data, and can route requests to servers in a specific jurisdiction.\n---\n\n# What Is a GDPR-Compliant Mapping API?\n\nWhen teams evaluate a mapping API for GDPR, they are usually asking three concrete questions: does the provider track my end users, what does it log, and where are requests processed. Stadia Maps documents its answers to all three. Per the [EU endpoints documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Feu-gdpr-endpoints\u002F), Stadia Maps is \"confident that our privacy practices and procedures satisfy GDPR requirements by default,\" and offers EU-only endpoints for teams that need a guarantee that requests never leave the European Union.\n\nThis page covers what Stadia Maps does. It is not legal advice, and it does not assess whether any particular application is compliant.\n\n## Key Takeaways\n\n- Stadia Maps does not track end users, build behavioral profiles, resell data, or use data for ad targeting.\n- Map tiles and API calls are cookie-less, stateless, and anonymous by default. There are no third-party cookies or tracking pixels on any service.\n- EU-only endpoints route all requests to servers in Frankfurt and Paris, and PII is scrubbed at the network edge.\n- Switching to EU endpoints is a hostname change: `tiles-eu.stadiamaps.com` and `api-eu.stadiamaps.com`.\n- Stadia Maps publishes a Data Processing Addendum and a Privacy Policy covering what is collected and why.\n\n## What Does a Mapping API Actually Collect?\n\nThe privacy question that matters for most teams is not what the provider promises, but what the integration technically does. Some location SDKs generate telemetry from user actions regardless of what your own application logs.\n\nPer the [Stadia Maps privacy commitment](https:\u002F\u002Fstadiamaps.com\u002Fprivacy\u002Fprivacy-commitment\u002F), the platform is built so that:\n\n- There are **no client-side scripts that phone home**\n- There are **no third-party cookies or tracking pixels** on any service\n- There are **no user-identifying headers or geolocation sniffing**\n- Map tiles and API calls are **cookie-less, stateless, and anonymous by default**\n- Geocoding and search are **query-based, not session-based**\n- Routing and navigation **does not store location history**\n- Maps **do not log identifying info**\n\nWhat Stadia Maps does collect is limited to operating and securing the infrastructure, preventing abuse and fraud, and debugging service issues. Per the privacy commitment page, Stadia Maps \"never collect [s] or store [s] location data tied to individual users.\" The [Privacy Policy](https:\u002F\u002Fstadiamaps.com\u002Fprivacy\u002Fprivacy-policy\u002F) covers the specifics.\n\n## What Are EU-Only Endpoints?\n\nSome teams need more than a policy commitment. They need a guarantee that network requests are handled inside a specific jurisdiction, either because of internal policy, a customer contract, or a regulator.\n\nStadia Maps offers [EU-only endpoints](https:\u002F\u002Fdocs.stadiamaps.com\u002Feu-gdpr-endpoints\u002F) for exactly that case. Per the documentation:\n\n- Requests connect exclusively to two servers positioned in the European Union: **Frankfurt, Germany** and **Paris, France**.\n- Stadia Maps systems **scrub PII at the network's edge**, so any request that must ultimately be handled by internal services in other regions is managed privately.\n\nThis is offered as an option rather than a default, because the standard endpoints already operate under the same privacy practices. EU endpoints exist for teams that need the jurisdictional guarantee on top.\n\n## How Do You Use the EU Endpoints?\n\nSwitching is a hostname change. No code restructuring, no separate account.\n\nFor map tiles and styles, replace `tiles.stadiamaps.com` with `tiles-eu.stadiamaps.com`:\n\n```http\nhttps:\u002F\u002Ftiles-eu.stadiamaps.com\u002Fstyles\u002Falidade_smooth.json\n```\n\nFor routing, geocoding, time zone, and other API services, replace `api.stadiamaps.com` with `api-eu.stadiamaps.com`:\n\n```http\nhttps:\u002F\u002Fapi-eu.stadiamaps.com\u002Fgeocoding\u002Fv2\u002Fsearch?text=Union+Square\n```\n\nEvery official Stadia Maps SDK accepts a base path or host override, so the change is typically one line. Full examples for TypeScript, Python, Kotlin, Swift, PHP, and cURL are in the [EU endpoints documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Feu-gdpr-endpoints\u002F).\n\n## What About Self-Hosting?\n\nFor teams whose requirements go beyond endpoint jurisdiction, Stadia Maps offers [On-Prem and Embedded Solutions](https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002Fon-prem-embedded\u002F). Running tiles and APIs inside your own infrastructure means location requests never reach a third party at all.\n\nThat is a heavier lift than switching a hostname, but it is the option that exists when a compliance requirement cannot be satisfied by a vendor commitment.\n\n## What Documentation Is Available for Compliance Review?\n\nProcurement and legal teams generally ask for artifacts rather than marketing claims. Stadia Maps publishes:\n\n- A [Privacy Policy](https:\u002F\u002Fstadiamaps.com\u002Fprivacy\u002Fprivacy-policy\u002F) covering what is collected and why\n- A [Data Processing Addendum](https:\u002F\u002Fstadiamaps.com\u002Flegal\u002Fdata-processing-addendum\u002F)\n- [Terms of Service](https:\u002F\u002Fstadiamaps.com\u002Fterms-of-service\u002F)\n- An [infrastructure overview](https:\u002F\u002Fstadiamaps.com\u002Finfrastructure\u002F) describing how the platform is built\n\nFor requirements not covered by the standard documents, Stadia Maps works directly with teams on tailored arrangements. The [support page](https:\u002F\u002Fstadiamaps.com\u002Fsupport\u002F) has contact options.\n\n## Where This Page Stops\n\nWorth being direct about the limits of what a vendor page can tell you.\n\n- **This is not legal advice.** Whether your application is GDPR-compliant depends on what data you collect, your lawful basis, your own retention practices, and factors that have nothing to do with your mapping provider.\n- **A compliant provider does not make your application compliant.** The mapping API is one processor in your stack. Your own data handling is the larger question.\n- **Requirements vary by use case and jurisdiction.** A consumer app, a healthcare platform, and a government contractor face different obligations from the same regulation.\n- **Verify rather than take a vendor's word.** Read the DPA and the Privacy Policy. If a specific control matters to you, ask about it directly before you build.\n\nFor anything beyond what is documented, talk to counsel who knows your use case.\n\n## Common Compliance-Driven Use Cases\n\nTeams that end up on EU endpoints or self-hosted deployments usually have a specific driver.\n\n- **EU-based products** with internal policy or customer contracts requiring data residency.\n- **Healthcare and health-adjacent apps** where location can be combined with other fields to become sensitive.\n- **Financial services** operating under sector rules on top of general privacy regulation.\n- **Government and public sector** with procurement requirements around data handling and jurisdiction.\n- **Enterprise B2B software** where the customer's own compliance review extends to subprocessors.\n- **Consumer apps positioning on privacy** where tracking by a vendor would undercut the product's own promise.\n\n::faq-section\n---\nfaqs:\n  - question: Does Stadia Maps track end users?\n    answer: No. Per the Stadia Maps privacy commitment, there is no user tracking,\n      no behavioral profiling, and no data reselling or ad targeting. Map tiles\n      and API calls are cookie-less, stateless, and anonymous by default, with\n      no client-side scripts that phone home and no third-party cookies or\n      tracking pixels on any service.\n  - question: What are Stadia Maps EU endpoints?\n    answer: EU endpoints are alternate hostnames that route all requests to servers\n      located in the European Union, specifically Frankfurt, Germany and Paris,\n      France. Stadia Maps systems scrub PII at the network edge, so any request\n      ultimately handled by internal services in other regions is managed\n      privately. Use tiles-eu.stadiamaps.com for map tiles and\n      api-eu.stadiamaps.com for API services.\n  - question: How do I switch to Stadia Maps EU endpoints?\n    answer: Replace tiles.stadiamaps.com with tiles-eu.stadiamaps.com for map tiles\n      and styles, and api.stadiamaps.com with api-eu.stadiamaps.com for routing,\n      geocoding, time zone, and other API services. Every official Stadia Maps\n      SDK accepts a base path or host override, so the change is typically one\n      line of configuration.\n  - question: What data does Stadia Maps collect?\n    answer: Stadia Maps collects only the minimal data necessary to operate and\n      secure its infrastructure, prevent abuse and fraud, and debug service\n      issues. Per the privacy commitment page, Stadia Maps never collects or\n      stores location data tied to individual users. Full details are in the\n      Privacy Policy.\n  - question: Does Stadia Maps offer a Data Processing Addendum?\n    answer: Yes. Stadia Maps publishes a Data Processing Addendum alongside its\n      Privacy Policy and Terms of Service. For requirements not covered by the\n      standard documents, Stadia Maps works directly with teams on tailored\n      arrangements.\n  - question: Can I self-host Stadia Maps for compliance reasons?\n    answer: Yes. Stadia Maps offers On-Prem and Embedded Solutions for teams whose\n      requirements go beyond endpoint jurisdiction. Running tiles and APIs\n      inside your own infrastructure means location requests never reach a third\n      party.\n---\n::\n\n## Where to Go Next\n\n### From the Blog\n\nMore on privacy and location data from the Stadia Maps blog:\n\n- [The Invisible Costs of Routing: Privacy, Pricing & the MAU Trap](\u002Fblog\u002Finvisible-costs-of-routing-privacy-pricing-mau-trap\u002F)\n- [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002Fprecision-meets-privacy-consumer-search-experience\u002F)\n- [The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos](\u002Fblog\u002Fopen-data-geocoding-global-search\u002F)\n\n### Privacy and Compliance\n\n- [Privacy Commitment](\u002Fprivacy\u002Fprivacy-commitment\u002F) for what Stadia Maps does and does not collect\n- [Private Location APIs and Maps](\u002Fprivacy\u002Fprivate-location-apis-maps\u002F) for the GDPR and CCPA overview\n- [Privacy Policy](\u002Fprivacy\u002Fprivacy-policy\u002F)\n- [Data Processing Addendum](\u002Flegal\u002Fdata-processing-addendum\u002F)\n- [Terms of Service](\u002Fterms-of-service\u002F)\n- [EU Endpoints documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Feu-gdpr-endpoints\u002F) for setup instructions and code examples\n- [Infrastructure overview](\u002Finfrastructure\u002F) for how the platform is built\n- [On-Prem and Embedded Solutions](\u002Fproducts\u002Fon-prem-embedded\u002F) for self-hosted deployments\n",{"title":5,"description":508},"learn\u002Fgdpr-compliant-mapping-api","GDPR-Compliant Mapping API","A mapping or location API that does not track end users, collects only operational data, and can route requests to servers in a specific jurisdiction.","Rgx3azocaDgJ36Ru8qaqKEBvhUn4LmP0T7t3k8Nx4Ww",[525,530,535],{"title":14,"description":526,"path":15,"published":527,"category":528,"rawbody":529},"Vector and raster are the two main map tile formats. Learn how they differ, when to use each, and how Stadia Maps serves both with MapLibre and OpenLayers.","2026-07-27","Maps","---\ntitle: Vector vs. Raster Map Tiles\ndescription: Vector and raster are the two main map tile formats. Learn how they differ, when to use each, and how Stadia Maps serves both with MapLibre and OpenLayers.\nauthor: Stadia Maps Team\ncategory: Maps\nimage: \u002Fimages\u002Fog\u002Fwhat-is-vector-vs-raster-map-tiles.png\nhead:\n  script: []\npublished: 2026-07-27\nschemaOrg:\n  - \"@type\": FAQPage\n    mainEntity:\n      - \"@type\": Question\n        name: What is the difference between vector and raster map tiles?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Raster map tiles are PNG or JPG images that get stitched together in a grid. Vector map tiles contain a mathematical description of the geometry plus structured data about each feature on the map, and get rendered client-side. Vector tiles allow dynamic styling, look sharp at any resolution, and typically reduce tile requests by around 60%. Raster tiles are simpler to render and battle-tested across older devices and rendering libraries.\n      - \"@type\": Question\n        name: Which is better, vector or raster map tiles?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: According to the Stadia Maps Switching to Vector Tiles guide, vector tiles offer greater flexibility, look great on any screen, and typically reduce costs by around 60%. However, if your application is targeting older devices or does not need a high level of detail, raster tiles are not necessarily a bad option.\n      - \"@type\": Question\n        name: Do vector map tiles cost less than raster map tiles?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: On the Stadia Maps API, both vector and raster tile requests are billed the same way, but vector tiles typically require fewer total requests to render a comparable map. The Switching to Vector Tiles guide reports users switching to vector make approximately 60% fewer tile requests on average.\n      - \"@type\": Question\n        name: What format are Stadia Maps vector tiles served in?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Stadia Maps vector tiles are distributed in the widely-adopted Mapbox Vector Tile (MVT) format, with a schema compatible with OpenMapTiles. They render in MapLibre GL JS, MapLibre Native, Leaflet (via maplibre-gl-leaflet), OpenLayers (via ol-mapbox-style), and other MVT-compatible renderers.\n      - \"@type\": Question\n        name: Can I use vector tiles with Leaflet?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Yes. Leaflet can render Stadia Maps vector tiles via the maplibre-gl-leaflet plugin. You swap L.tileLayer for L.maplibreGL and point at a Stadia Maps vector style URL. This is the quickest migration path from raster Leaflet to vector without switching frameworks.\nterm: Map Tile\ntermDescription: A single image or data file, one of many that get stitched together to form a complete interactive map. Comes in two main formats, raster and vector.\n---\n\n# Vector vs. Raster Map Tiles\n\nVector and raster are the two main formats used to serve interactive map tiles. Raster tiles are PNG or JPG images stitched into a grid. Vector tiles contain a mathematical description of geometry plus structured data about each feature, rendered on the client. The [Stadia Maps Map Tiles API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fvector\u002F) serves both formats, so this comparison is not a pitch for one over the other. It's an honest walkthrough of the trade-offs.\n\n## Key Takeaways\n\n- Raster tiles are PNG or JPG images. Vector tiles are structured data, rendered client-side.\n- Vector tiles allow dynamic styling (colors, language, layer visibility, 3D perspective). Raster tiles do not.\n- According to Stadia Maps' [Switching to Vector Tiles guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fguides\u002Fswitching-your-maps-from-raster-to-vector-tiles\u002F), users switching to vector make approximately 60% fewer tile requests on average.\n- Raster tiles are battle-tested and easy to render on older devices and simpler libraries.\n- Stadia Maps serves both formats and contributes to MapLibre. Co-founder Luke Seelenbinder serves on MapLibre's governing board.\n\n## What Are Raster Map Tiles?\n\nRaster map tiles are PNG or JPG images that get stitched together in a grid to form a complete interactive map. When you zoom in and out of a map and see little blank squares filling in like a mosaic, those are tiles.\n\nThe [Stadia Maps Raster Map Tiles API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fraster\u002F) serves all of Stadia's house styles as PNG raster tiles at 256×256 and 512×512 pixel sizes. Raster tiles are supported up to zoom 20 for most styles (Stamen Watercolor is the exception at zoom 16).\n\n**Raster advantages (from the Stadia Maps guide):**\n\n- **Simplicity.** Just about every device can render a PNG or JPG image, and it is easy to build a performant renderer around them. Raster tiles do not require any other resources (fonts, icons) or special client-side logic.\n- **Specificity.** For minimalist styles, raster tiles can be more bandwidth-efficient because they only contain the raw visible pixels.\n\n**Raster limitations (from the Stadia Maps guide):**\n\n- **Inflexibility.** You cannot change much about raster tiles. Hiding a layer, changing the language of labels, or altering the appearance of the tiles is not possible client-side.\n- **Scalability.** Raster map tiles cannot be scaled up and down. High-DPI displays need 4× the pixels, and zooming produces temporary blur until the new tiles load.\n\n## What Are Vector Map Tiles?\n\nVector map tiles contain a mathematical description of geometry and structured data about each feature on the map. Rather than pre-rendered pixels, the tile carries the raw data and the client renders it in real time.\n\nThe [Stadia Maps Vector Map Tiles API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fvector\u002F) serves tiles in the widely-adopted Mapbox Vector Tile (MVT) format, with a schema compatible with OpenMapTiles. Stadia Maps supports zoom levels 0 through 14 for vector tiles, with over-zooming from the z14 tile beyond that. Stadia Maps recommends the [MapLibre GL JS](https:\u002F\u002Fmaplibre.org\u002F) and MapLibre Native renderers, but the tiles work in any MVT-compatible renderer.\n\n**Vector advantages (from the Stadia Maps guide):**\n\n- **Flexibility.** The actual data is preserved in the tile. You can [change the language](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fchanging-the-map-label-language\u002F) of text labels, change color scheme dynamically, switch styles based on time of day, or [add 3D perspective](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fadding-3d-buildings-to-your-maps-with-maplibre\u002F).\n- **Scalability.** Vector shapes scale up and down smoothly. Zooming feels continuous rather than stepped, and high-DPI displays get sharp output without extra bandwidth.\n- **Cost.** Vector tiles cover a larger area per tile. Stadia's guide reports users switching to vector make approximately 60% fewer tile requests on average.\n\n**Vector limitations (from the Stadia Maps guide):**\n\n- **Complexity.** Tiles render client-side, which may create performance concerns for older or embedded applications. Initial map load involves more network requests for fonts, icons, and style resources.\n- **Size.** For applications that only need a low level of detail and don't use 3D features, vector tiles can weigh slightly more. This is offset because zooming past level 14 uses the information already in the z14 tile.\n\n## Vector vs. Raster: Which Should You Use?\n\nThe [Stadia Maps Switching to Vector Tiles guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fguides\u002Fswitching-your-maps-from-raster-to-vector-tiles\u002F) summarizes the choice directly: \"Vector tiles offer greater flexibility, look great on any screen, and typically reduce costs by around 60%. However, if your application is targeting older devices or doesn't need a high level of detail (for example, our Alidade Smooth and Alidade Smooth Dark styles), raster tiles are not necessarily a bad option.\"\n\nChoose **vector** when you need:\n\n- Client-side style customization or language switching\n- 3D perspective, custom camera angles, or dynamic theming\n- Lower total tile requests at scale\n- Sharp rendering on high-DPI displays without paying 4× bandwidth\n\nChoose **raster** when you need:\n\n- Support for older devices or renderers that don't understand MVT\n- A minimalist style where bandwidth per tile is very small\n- The absolute simplest integration path in Leaflet, WordPress, or a static site\n- Static images (for those, the [Stadia Maps Static Maps API](https:\u002F\u002Fstadiamaps.com\u002Fproducts\u002Fmaps\u002Fstatic-maps\u002F) is a different product, tailored for embedding images in emails or apps without a JS runtime)\n\n## How Do You Serve Vector and Raster Tiles with Stadia Maps?\n\nBoth formats use straightforward URL patterns. Replace `\u003Cstyle>` with any of the [Stadia Maps map styles](https:\u002F\u002Fdocs.stadiamaps.com\u002Fthemes\u002F).\n\n**Vector tile URL formats:**\n\n```text\nhttps:\u002F\u002Ftiles.stadiamaps.com\u002Fdata\u002Fopenmaptiles.json\nhttps:\u002F\u002Ftiles.stadiamaps.com\u002Fdata\u002Fopenmaptiles\u002F{z}\u002F{x}\u002F{y}.pbf\n```\n\n**Raster tile URL format:**\n\n```text\nhttps:\u002F\u002Ftiles.stadiamaps.com\u002Ftiles\u002F\u003Cstyle>\u002F{z}\u002F{x}\u002F{y}{r}.png\n```\n\nThe `{r}` placeholder handles HiDPI (\"retina\") display support. Replace it with `@2x` for 2× scaled images, or drop it for 256×256 output.\n\nEU-only endpoints are available for both formats at `tiles-eu.stadiamaps.com`. See the [EU Endpoints docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Feu-gdpr-endpoints\u002F) for details.\n\nAuthentication uses domain-based auth for browser applications or an API key for backend and mobile applications. Full details in the [Authentication guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fauthentication\u002F).\n\n## How to Switch from Raster to Vector Tiles\n\nThe [Switching to Vector Tiles guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fguides\u002Fswitching-your-maps-from-raster-to-vector-tiles\u002F) walks through the common migration paths.\n\n- **Switching to MapLibre GL JS (web).** The most feature-rich option. See the [MapLibre GL JS quickstart](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fvector-maps-with-maplibre-gl-js\u002F).\n- **Keeping Leaflet.** Add vector rendering support via the `maplibre-gl-leaflet` plugin. Swap `L.tileLayer` for `L.maplibreGL` and point at a Stadia Maps vector style URL. See the [Vector Tiles with Leaflet tutorial](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fvector-tiles-with-leaflet\u002F).\n- **React Leaflet.** Add a small component. See the [Vector Tiles with React Leaflet tutorial](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fvector-tiles-with-react-leaflet\u002F).\n- **OpenLayers.** Load the `ol-mapbox-style` plugin and call `olms.apply` with a Stadia Maps vector style URL.\n- **Mobile (iOS, Android, Flutter, React Native).** See the [Native and Multi-platform maps overview](https:\u002F\u002Fdocs.stadiamaps.com\u002Fnative-multiplatform\u002Foverview\u002F).\n\n## Where Vector vs. Raster Tile Comparisons Fall Short\n\nA few things worth knowing before you take any comparison table (this one included) as absolute.\n\n- **\"60% fewer tile requests\" is an average, not a guarantee.** The actual reduction depends on the level of detail, the size of the viewport, and how much users pan and zoom. The Stadia Maps guide reports it as an average across users who switched.\n- **Vector isn't universally faster.** Initial map load can involve more network requests for fonts, icons, and style resources. First-paint may feel slower even when total data is lower.\n- **Not every renderer handles MVT with the same fidelity.** The Stadia Vector docs explicitly note that OpenLayers rendering \"isn't quite as powerful as MapLibre GL JS, but it's the quickest migration path to most of the benefits.\" Same idea for the Leaflet plugin.\n- **Older devices matter.** If a meaningful part of your user base runs older embedded browsers or low-power devices, raster is often the safer default. The Stadia guide calls this out explicitly.\n- **Style customization has its own learning curve.** The flexibility of vector tiles only pays off if you actually build styles. If you never customize, the raster experience of Stadia's house styles is just as good visually.\n\n## Common Use Cases for Vector and Raster Map Tiles\n\nWhere each format shines, drawn from the Stadia Maps docs and product page.\n\n**Vector tile use cases:**\n\n- Interactive web and mobile apps that need custom styling, language switching, or 3D perspective\n- Marker clustering, polyline overlays, and polygon overlays in [MapLibre GL JS](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fclustering-styling-points-with-maplibre\u002F)\n- Data visualization on top of a customizable basemap\n- Applications where reducing total tile requests matters at scale\n\n**Raster tile use cases:**\n\n- WordPress sites and CMS integrations via the [Leaflet](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fwordpress-with-leaflet\u002F) or [Mapster](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fwordpress-with-mapster\u002F) plugins\n- Older devices or environments that cannot run a WebGL-based renderer\n- QGIS and other GIS tools that consume raster XYZ tile services\n- Minimalist styles like [Alidade Smooth](https:\u002F\u002Fdocs.stadiamaps.com\u002Fmap-styles\u002Falidade-smooth\u002F) where bandwidth per tile is already very small\n\n## Frequently Asked Questions\n\n### What is the difference between vector and raster map tiles?\n\nRaster map tiles are PNG or JPG images that get stitched together in a grid. Vector map tiles contain a mathematical description of the geometry plus structured data about each feature on the map, and get rendered client-side. Vector tiles allow dynamic styling, look sharp at any resolution, and typically reduce tile requests by around 60%. Raster tiles are simpler to render and battle-tested across older devices and rendering libraries.\n\n### Which is better, vector or raster map tiles?\n\nAccording to the [Stadia Maps Switching to Vector Tiles guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fguides\u002Fswitching-your-maps-from-raster-to-vector-tiles\u002F): \"Vector tiles offer greater flexibility, look great on any screen, and typically reduce costs by around 60%. However, if your application is targeting older devices or doesn't need a high level of detail, raster tiles are not necessarily a bad option.\"\n\n### Do vector map tiles cost less than raster map tiles?\n\nOn the [Stadia Maps API](\u002Fpricing\u002F), both vector and raster tile requests are billed the same way. Vector typically requires fewer total requests to render a comparable map. The Switching to Vector Tiles guide reports users switching to vector make approximately 60% fewer tile requests on average.\n\n### What format are Stadia Maps vector tiles served in?\n\nStadia Maps vector tiles are distributed in the widely-adopted Mapbox Vector Tile (MVT) format, with a schema compatible with [OpenMapTiles](https:\u002F\u002Fopenmaptiles.org\u002F). They render in MapLibre GL JS, MapLibre Native, Leaflet (via `maplibre-gl-leaflet`), OpenLayers (via `ol-mapbox-style`), and other MVT-compatible renderers.\n\n### Can I use vector tiles with Leaflet?\n\nYes. Leaflet can render Stadia Maps vector tiles via the [`maplibre-gl-leaflet`](https:\u002F\u002Fgithub.com\u002Fmaplibre\u002Fmaplibre-gl-leaflet) plugin. You swap `L.tileLayer` for `L.maplibreGL` and point at a Stadia Maps vector style URL. This is the quickest migration path from raster Leaflet to vector without switching frameworks. Full walkthrough in the [Vector Tiles with Leaflet tutorial](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fvector-tiles-with-leaflet\u002F).\n\n## Where to Go Next\n\n### From the Blog\n\nMore on maps and rendering from the Stadia Maps blog:\n\n- [How We Fixed Water Feature Rendering Across All Zoom Levels](\u002Fblog\u002Ffixing-missing-water-interactive-basemaps\u002F)\n- [2026 Satellite Imagery Update: 37M km² at 30cm Resolution](\u002Fblog\u002F2026-satellite-imagery-update\u002F)\n- [Custom Markers and POST Support for Static Maps](\u002Fblog\u002Fcustom-markers-in-static-map-images\u002F)\n- [Announcing Cacheable Static Maps](\u002Fblog\u002Fannouncing-cacheable-static-map-images\u002F)\n- [Our SwiftUI DSL Is Joining the MapLibre Family](\u002Fblog\u002Fmaplibre-swiftui-dsl\u002F)\n\n### Maps\n\n- [Vector Map Tiles docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fvector\u002F) for tile URLs, authentication, and renderer support\n- [Raster Map Tiles docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Fraster\u002F) for PNG tile URL formats and retina support\n- [Switching to Vector Tiles guide](https:\u002F\u002Fdocs.stadiamaps.com\u002Fguides\u002Fswitching-your-maps-from-raster-to-vector-tiles\u002F) for a full migration walkthrough\n- [Map Styles library](https:\u002F\u002Fdocs.stadiamaps.com\u002Fthemes\u002F) for the complete gallery of Stadia house styles\n- [Interactive Web Maps overview](https:\u002F\u002Fdocs.stadiamaps.com\u002Fmaps-for-web\u002F) for renderer selection and framework choices\n- [Custom Map Styling](https:\u002F\u002Fdocs.stadiamaps.com\u002Fcustom-styles\u002F) for building your own styles on top of the OpenMapTiles schema\n- [Maps product page](\u002Fproducts\u002Fmaps\u002F) and pricing tiers\n- [Static Maps product page](\u002Fproducts\u002Fmaps\u002Fstatic-maps\u002F) if you need pre-rendered map images instead\n",{"title":11,"description":531,"path":12,"published":532,"category":533,"rawbody":534},"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.","2026-07-28","Geocoding & Search","---\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":536,"description":537,"path":538,"published":539,"category":533,"rawbody":540},"What Is Geocoding?","Master geocoding fundamentals: Convert addresses to coordinates and vice versa. Learn how our global geocoding API works, data accuracy levels, and best practices.","\u002Flearn\u002Fgeocoding","2026-07-14","---\ntitle: What Is Geocoding?\ndescription: \"Master geocoding fundamentals: Convert addresses to coordinates and vice versa. Learn how our global geocoding API works, data accuracy levels, and best practices.\"\ncategory: Geocoding & Search\nhead:\n  script: []\nimage: \u002Fimages\u002Fog\u002Fwhat-is-geocoding.png\npublished: 2026-07-14\nschemaOrg:\n  - \"@type\": FAQPage\n    mainEntity:\n      - \"@type\": Question\n        name: What is address geocoding?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Address geocoding is the process of converting a street address or place name into geographic coordinates (latitude and longitude). It is the primary way products bridge between human-readable location input and machine-readable spatial data. The Stadia Maps Geocoding API handles address geocoding through its forward geocoding, structured geocoding, and autocomplete endpoints.\n      - \"@type\": Question\n        name: What is the difference between geocoding and reverse geocoding?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: \"Geocoding (forward geocoding) converts an address or place name into coordinates. Reverse geocoding does the opposite: it converts coordinates into an address or place. Products that combine both directions are common.\"\n      - \"@type\": Question\n        name: What data sources does the Stadia Maps Geocoding API use?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: \"The Stadia Maps Geocoding API queries five documented open sources: OpenStreetMap for global roads and points of interest, OpenAddresses for authoritative government address data, Who's On First for administrative places, GeoNames for populated places and natural features, and Foursquare Open Source Places for business and venue data.\"\n      - \"@type\": Question\n        name: Can I store geocoded addresses permanently on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Yes. With a Standard, Professional, or Enterprise subscription, geocoded results can be stored permanently in your own database. Most competitor APIs charge a premium to allow storage.\n      - \"@type\": Question\n        name: How much does a geocoding request cost on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Geocoding requests are billed from a unified credit pool on the Stadia Maps API, the same pool that covers routing, tiles, and other endpoints. Forward, reverse, structured, and autocomplete requests are each single billable requests. Bulk geocoding is billed per address in the batch.\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\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 sponsors OpenAddresses.\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.\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\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](https:\u002F\u002Fstadiamaps.com\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## Frequently Asked Questions\n\n### What is address geocoding?\n\nAddress geocoding is the process of converting a street address or place name into geographic coordinates (latitude and longitude). It is the primary way products bridge between human-readable location input and machine-readable spatial data. The [Stadia Maps Geocoding API](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Foverview\u002F) handles address geocoding through its forward geocoding, structured geocoding, and autocomplete endpoints.\n\n### What is the difference between geocoding and reverse geocoding?\n\nGeocoding (forward geocoding) converts an address or place name into coordinates. Reverse geocoding does the opposite: it converts coordinates into an address or place. Products that combine both directions are common. For example, a user types a destination (forward geocoded) and a driver's phone shows the address of their current GPS position (reverse geocoded).\n\n### What data sources does the Stadia Maps Geocoding API use?\n\nThe Stadia Maps Geocoding API queries five documented open sources: [OpenStreetMap](https:\u002F\u002Fwww.openstreetmap.org\u002F) for global roads and points of interest, [OpenAddresses](https:\u002F\u002Fopenaddresses.io\u002F) for authoritative government address data, [Who's On First](https:\u002F\u002Fwhosonfirst.org\u002F) for administrative places, [GeoNames](https:\u002F\u002Fwww.geonames.org\u002F) for populated places and natural features, and [Foursquare Open Source Places](https:\u002F\u002Fdocs.foursquare.com\u002Fdata-products\u002Fdocs\u002Ffsq-places-open-source) for business and venue data. Every result carries attribution back to its source; see the [Sources documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsources\u002F) for the full list.\n\n### Can I store geocoded addresses permanently on Stadia Maps?\n\nYes, with a Standard, Professional, or Enterprise subscription, geocoded results can be stored permanently in your own database. Most competitor APIs charge a premium (often 10x the standard request price) to allow storage. See the [Stadia Maps terms of service](https:\u002F\u002Fstadiamaps.com\u002Fterms-of-service\u002F) for the full policy.\n\n### How much does a geocoding request cost on Stadia Maps?\n\nGeocoding requests are billed from a unified credit pool on the [Stadia Maps API](\u002Fpricing\u002F), the same pool that covers routing, tiles, and other endpoints. Forward, reverse, structured, and autocomplete requests are each single billable requests. Bulk geocoding is billed per address in the batch. See the pricing page for plan tiers and credit allocations.\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- [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- [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\n",{"id":542,"bio":513,"extension":18,"jobTitle":513,"meta":543,"name":544,"sameAs":545,"slug":548,"stem":549,"twitterCreator":513,"type":550,"url":551,"__hash__":552},"authors\u002Fauthors\u002Fstadia-maps.yml",{},"Stadia Maps",[546,547],"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",1786420640016]