[{"data":1,"prerenderedAt":843},["ShallowReactive",2],{"footer-learn-links":3,"site-prefooter-cta":16,"learn-\u002Flearn\u002Faddress-autocomplete\u002F":24,"related-learn-\u002Flearn\u002Faddress-autocomplete\u002F":818,"learn-org-author":831},[4,7,10,13],{"title":5,"path":6},"What Is Address Autocomplete?","\u002Flearn\u002Faddress-autocomplete",{"title":8,"path":9},"What Is Reverse Geocoding?","\u002Flearn\u002Freverse-geocoding",{"title":11,"path":12},"What Is Geocoding?","\u002Flearn\u002Fgeocoding",{"title":14,"path":15},"What Is an Isochrone?","\u002Flearn\u002Fisochrones",{"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":692,"description":782,"extension":783,"head":784,"image":786,"imageAlt":787,"keywords":787,"meta":788,"modified":787,"navigation":790,"path":6,"published":791,"rawbody":792,"schemaOrg":793,"seo":813,"stem":814,"term":815,"termDescription":816,"__hash__":817},"learn\u002Flearn\u002Faddress-autocomplete.md",{"type":27,"value":28,"toc":757},"minimark",[29,33,46,51,70,74,77,115,118,132,136,139,187,196,200,208,315,319,327,389,393,396,412,425,443,447,450,494,498,501,520,532,536,539,577,581,586,589,593,600,604,619,623,639,643,650,654,658,661,689,693,753],[30,31,5],"h1",{"id":32},"what-is-address-autocomplete",[34,35,36,37,45],"p",{},"Address 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 ",[38,39,44],"a",{"href":40,"rel":41,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F",[42],"external","_blank","Stadia Maps Autocomplete Search API"," powers this experience through a fast, partial-input endpoint plus first-party SDKs for the web, iOS, and Android.",[47,48,50],"h2",{"id":49},"key-takeaways","Key Takeaways",[52,53,54,58,61,64,67],"ul",{},[55,56,57],"li",{},"Address autocomplete suggests places as a user types, based on partial input and typically ranked by proximity or a focus point.",[55,59,60],{},"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.",[55,62,63],{},"Stadia Maps ships three first-party SDKs (MapLibre GL JS, SwiftUI, Jetpack Compose) that handle debouncing, caching, and result ordering out of the box.",[55,65,66],{},"The Stadia Maps SDKs default to a 100ms minimum wait period between requests and a 3-character minimum input length.",[55,68,69],{},"Each autocomplete request is billed as a single request from the unified Stadia Maps API credit pool.",[47,71,73],{"id":72},"how-address-autocomplete-works","How Address Autocomplete Works",[34,75,76],{},"Autocomplete is a variant of forward geocoding tuned for speed on incomplete input. It follows this rough flow:",[78,79,80,87,93,103,109],"ol",{},[55,81,82,86],{},[83,84,85],"strong",{},"User types."," The client waits for a minimum number of characters (typically two or three) before firing the first request.",[55,88,89,92],{},[83,90,91],{},"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.",[55,94,95,98,99,102],{},[83,96,97],{},"Server searches."," The ",[38,100,44],{"href":40,"rel":101,"target":43},[42]," matches the partial input against the geocoding database and returns ranked candidates.",[55,104,105,108],{},[83,106,107],{},"Client renders results."," Suggestions appear under the search field, typically 3 to 5 at a time.",[55,110,111,114],{},[83,112,113],{},"User selects one."," The application takes the selected feature (with its full coordinates, address components, and layer) and moves on to the next step.",[34,116,117],{},"Two implementation details that matter in production:",[52,119,120,126],{},[55,121,122,125],{},[83,123,124],{},"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.",[55,127,128,131],{},[83,129,130],{},"Result caching."," Recent queries can be served from the local cache, which cuts perceived latency and reduces API calls.",[47,133,135],{"id":134},"which-autocomplete-sdk-should-you-use","Which Autocomplete SDK Should You Use?",[34,137,138],{},"Stadia 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.",[52,140,141,167,177],{},[55,142,143,150,151,155,156,155,159,162,163,166],{},[83,144,145],{},[38,146,149],{"href":147,"rel":148,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fmaplibre-gl-js-autocomplete-search-plugin\u002F",[42],"MapLibre GL JS Search Box plugin"," for the web. Adds a search control to a MapLibre GL JS map. Configurable via options like ",[152,153,154],"code",{},"useMapFocusPoint",", ",[152,157,158],{},"mapFocusPointMinZoom",[152,160,161],{},"minInputLength",", and ",[152,164,165],{},"minWaitPeriodMs",". Available as an npm package or a CDN script tag.",[55,168,169,176],{},[83,170,171],{},[38,172,175],{"href":173,"rel":174,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fswiftui-autocomplete-search\u002F",[42],"SwiftUI Autocomplete Search"," for iOS. A drop-in SwiftUI view for native iOS apps.",[55,178,179,186],{},[83,180,181],{},[38,182,185],{"href":183,"rel":184,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Fjetpack-compose-autocomplete-search\u002F",[42],"Jetpack Compose Autocomplete Search"," for Android. A composable for native Android apps built with Jetpack Compose.",[34,188,189,190,195],{},"If 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 ",[38,191,194],{"href":192,"rel":193,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fsdks\u002Foverview\u002F",[42],"official SDKs"," also expose the endpoint from TypeScript, Python, Kotlin, Swift, and PHP.",[47,197,199],{"id":198},"address-autocomplete-parameters-that-matter","Address Autocomplete Parameters That Matter",[34,201,202,203,207],{},"The ",[38,204,206],{"href":40,"rel":205,"target":43},[42],"Autocomplete Search endpoint"," takes one required parameter and several optional ones that tune the result set.",[52,209,210,218,230,247,275,299,307],{},[55,211,212,217],{},[83,213,214],{},[152,215,216],{},"text",": The partial user input. Required.",[55,219,220,229],{},[83,221,222,225,226],{},[152,223,224],{},"focus.point.lat"," \u002F ",[152,227,228],{},"focus.point.lon",": Bias results toward a focus point. Typically the map center or the user's known location.",[55,231,232,246],{},[83,233,234,155,237,155,240,155,243],{},[152,235,236],{},"boundary.rect.*",[152,238,239],{},"boundary.circle.*",[152,241,242],{},"boundary.country",[152,244,245],{},"boundary.gid",": Hard limits on where results can appear. Use these when your product only operates in specific regions.",[55,248,249,254,255,155,258,155,261,155,264,155,267,270,271,274],{},[83,250,251],{},[152,252,253],{},"layers",": Restrict to specific layers (",[152,256,257],{},"address",[152,259,260],{},"venue",[152,262,263],{},"poi",[152,265,266],{},"street",[152,268,269],{},"locality",", and more). Fewer layers means faster, more relevant results. ",[152,272,273],{},"layers=coarse"," is the fastest option when you do not need addresses or POIs.",[55,276,277,282,283,155,286,155,289,155,292,155,295,298],{},[83,278,279],{},[152,280,281],{},"sources",": Restrict to specific data sources (",[152,284,285],{},"openstreetmap",[152,287,288],{},"openaddresses",[152,290,291],{},"whosonfirst",[152,293,294],{},"geonames",[152,296,297],{},"foursquare",").",[55,300,301,306],{},[83,302,303],{},[152,304,305],{},"size",": Maximum number of results to return. Default is 10; most autocomplete UIs display 3 to 5.",[55,308,309,314],{},[83,310,311],{},[152,312,313],{},"lang",": A BCP47 language tag for localized results.",[47,316,318],{"id":317},"autocomplete-defaults-worth-knowing","Autocomplete Defaults Worth Knowing",[34,320,202,321,326],{},[38,322,325],{"href":323,"rel":324,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fautocomplete\u002F#ready-to-go-integrations",[42],"Stadia Maps SDKs"," enforce a set of defaults documented in the API and SDK references. Each one exists to balance API cost, server load, and interaction responsiveness.",[52,328,329,346,355,360,366,375],{},[55,330,331,98,334,338,339,342,343,345],{},[83,332,333],{},"Minimum input length.",[38,335,337],{"href":40,"rel":336,"target":43},[42],"Autocomplete Search docs"," recommend waiting for two or three characters of user input before sending a query. The ",[38,340,149],{"href":147,"rel":341,"target":43},[42]," defaults ",[152,344,161],{}," to 3.",[55,347,348,351,352,354],{},[83,349,350],{},"Debouncing."," The MapLibre plugin defaults ",[152,353,165],{}," 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.",[55,356,357,359],{},[83,358,130],{}," The MapLibre plugin caches recent results to avoid duplicate calls.",[55,361,362,365],{},[83,363,364],{},"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.",[55,367,368,351,371,374],{},[83,369,370],{},"Maximum results.",[152,372,373],{},"maxResults"," to 5.",[55,376,377,380,381,385,386,388],{},[83,378,379],{},"Layer selection."," Specifying only the ",[38,382,253],{"href":383,"rel":384,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Flayers\u002F",[42]," you need improves relevance and performance. ",[152,387,273],{}," is especially useful when POIs and addresses are not needed.",[47,390,392],{"id":391},"how-do-you-add-address-autocomplete","How Do You Add Address Autocomplete?",[34,394,395],{},"Here is what a direct call to the Stadia Maps Autocomplete Search API looks like. This example searches for a partial query in Tallinn, Estonia.",[397,398,403],"pre",{"className":399,"code":400,"language":401,"meta":402,"style":402},"language-http shiki shiki-themes github-light","GET https:\u002F\u002Fapi.stadiamaps.com\u002Fgeocoding\u002Fv2\u002Fautocomplete?text=Union+Squa&lang=en\n","http","",[152,404,405],{"__ignoreMap":402},[406,407,410],"span",{"class":408,"line":409},"line",1,[406,411,400],{},[34,413,414,415,418,419,424],{},"The response is a GeoJSON ",[152,416,417],{},"FeatureCollection",". Each feature includes coordinates, parsed address components, layer, confidence score, and source attribution. Full response format details are in the ",[38,420,423],{"href":421,"rel":422,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fapi-response-format\u002F",[42],"Common Response Format docs",".",[34,426,427,428,155,431,434,435,438,439,424],{},"For most applications, the ",[38,429,149],{"href":147,"rel":430,"target":43},[42],[38,432,175],{"href":173,"rel":433,"target":43},[42],", or ",[38,436,185],{"href":183,"rel":437,"target":43},[42]," 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 ",[38,440,442],{"href":40,"rel":441,"target":43},[42],"Autocomplete Search API docs",[47,444,446],{"id":445},"where-address-autocomplete-falls-short","Where Address Autocomplete Falls Short",[34,448,449],{},"Autocomplete is not the right tool for every search interaction. Real limits worth knowing:",[52,451,452,463,469,479,488],{},[55,453,454,457,458,462],{},[83,455,456],{},"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 ",[38,459,461],{"href":460},"\u002Flearn\u002Fgeocoding\u002F","forward geocoding"," once the user finalizes their query.",[55,464,465,468],{},[83,466,467],{},"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.",[55,470,471,474,475,478],{},[83,472,473],{},"Ranking is context-dependent."," Without a ",[152,476,477],{},"focus.point"," or a boundary, \"Springfield\" could match any of dozens. Provide a focus point or country hint whenever possible.",[55,480,481,484,485,487],{},[83,482,483],{},"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 ",[152,486,273],{}," for the fastest possible search.",[55,489,490,493],{},[83,491,492],{},"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.",[47,495,497],{"id":496},"address-autocomplete-vs-forward-geocoding-which-do-you-need","Address Autocomplete vs. Forward Geocoding: Which Do You Need?",[34,499,500],{},"Both convert human-readable place input into coordinates. They optimize for different phases of the user interaction.",[52,502,503,513],{},[55,504,505,506,512],{},"Use ",[83,507,508],{},[38,509,511],{"href":40,"rel":510,"target":43},[42],"address autocomplete"," while the user is still typing. Fast responses, partial input, ranked suggestions.",[55,514,505,515,519],{},[83,516,517],{},[38,518,461],{"href":460}," 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.",[34,521,522,523,526,527,531],{},"The MapLibre GL JS Search Box plugin can automatically switch to the forward geocoding endpoint on Enter via the ",[152,524,525],{},"searchOnEnter"," option, if your plan includes the forward geocoding endpoint. See the ",[38,528,530],{"href":529},"\u002Fpricing\u002F","Stadia Maps pricing page"," for plan details.",[47,533,535],{"id":534},"common-address-autocomplete-use-cases","Common Address Autocomplete Use Cases",[34,537,538],{},"Autocomplete appears wherever a product asks a user to enter a real-world place.",[52,540,541,547,553,559,565,571],{},[55,542,543,546],{},[83,544,545],{},"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.",[55,548,549,552],{},[83,550,551],{},"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.",[55,554,555,558],{},[83,556,557],{},"Store locator and site finder."," User types a city or zip code and the map centers on the selected result.",[55,560,561,564],{},[83,562,563],{},"Map-based search interfaces."," Real estate, travel, and outdoor apps let users search for places directly on the map.",[55,566,567,570],{},[83,568,569],{},"Data entry and CRM lookup."," Sales and support tools use autocomplete to attach a canonical place to a record.",[55,572,573,576],{},[83,574,575],{},"Point-of-interest discovery."," Restaurants, hotels, landmarks, and businesses surface as venues the user can select without knowing the full name.",[47,578,580],{"id":579},"frequently-asked-questions","Frequently Asked Questions",[582,583,585],"h3",{"id":584},"what-is-address-autocomplete-used-for","What is address autocomplete used for?",[34,587,588],{},"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.",[582,590,592],{"id":591},"what-is-the-difference-between-address-autocomplete-and-forward-geocoding","What is the difference between address autocomplete and forward geocoding?",[34,594,595,596,599],{},"Autocomplete is optimized for speed on partial input. ",[38,597,598],{"href":460},"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, for example by pressing Enter.",[582,601,603],{"id":602},"which-sdks-does-stadia-maps-offer-for-address-autocomplete","Which SDKs does Stadia Maps offer for address autocomplete?",[34,605,606,607,610,611,614,615,618],{},"Stadia Maps offers three first-party SDKs for address autocomplete: the ",[38,608,149],{"href":147,"rel":609,"target":43},[42]," for the web, ",[38,612,175],{"href":173,"rel":613,"target":43},[42]," for iOS, and ",[38,616,185],{"href":183,"rel":617,"target":43},[42]," for Android. Each handles debouncing, caching, and result ordering out of the box. If none fit, the underlying HTTP API is available directly.",[582,620,622],{"id":621},"what-are-the-default-autocomplete-timing-and-input-settings-on-stadia-maps","What are the default autocomplete timing and input settings on Stadia Maps?",[34,624,625,626,628,629,631,632,635,636,638],{},"The Stadia Maps autocomplete SDKs default to a 100ms minimum wait period between requests (",[152,627,165],{},") and a 3-character minimum input length (",[152,630,161],{},"). The ",[38,633,149],{"href":147,"rel":634,"target":43},[42]," also defaults ",[152,637,373],{}," to 5. These defaults balance server load with responsiveness.",[582,640,642],{"id":641},"how-is-an-address-autocomplete-request-billed-on-stadia-maps","How is an address autocomplete request billed on Stadia Maps?",[34,644,645,646,649],{},"Autocomplete requests are billed from the unified ",[38,647,648],{"href":529},"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.",[47,651,653],{"id":652},"where-to-go-next","Where to Go Next",[582,655,657],{"id":656},"from-the-blog","From the Blog",[34,659,660],{},"More on geocoding and search from the Stadia Maps blog:",[52,662,663,669,674,679,684],{},[55,664,665],{},[38,666,668],{"href":667},"\u002Fblog\u002F","The Hidden Cost of Search: Why Your Geocoding Bill Is Higher Than It Should Be",[55,670,671],{},[38,672,673],{"href":667},"The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos",[55,675,676],{},[38,677,678],{"href":667},"Precision Meets Privacy: Elevating the Consumer Search Experience",[55,680,681],{},[38,682,683],{"href":667},"Autocomplete Search for SwiftUI and Jetpack Compose",[55,685,686],{},[38,687,688],{"href":667},"Introducing Geocoding & Search v2",[582,690,692],{"id":691},"geocoding-search","Geocoding & Search",[52,694,695,700,706,713,719,725,731,738,746],{},[55,696,697,699],{},[38,698,11],{"href":460}," for the complete forward-direction overview",[55,701,702,705],{},[38,703,8],{"href":704},"\u002Flearn\u002Freverse-geocoding\u002F"," for the opposite direction",[55,707,708,712],{},[38,709,711],{"href":40,"rel":710,"target":43},[42],"Autocomplete Search API reference"," for the full parameter set",[55,714,715,718],{},[38,716,149],{"href":147,"rel":717,"target":43},[42]," for the web",[55,720,721,724],{},[38,722,175],{"href":173,"rel":723,"target":43},[42]," for iOS",[55,726,727,730],{},[38,728,185],{"href":183,"rel":729,"target":43},[42]," for Android",[55,732,733,737],{},[38,734,736],{"href":383,"rel":735,"target":43},[42],"Layers documentation"," for the full list of returnable place types",[55,739,740,745],{},[38,741,744],{"href":742,"rel":743,"target":43},"https:\u002F\u002Fdocs.stadiamaps.com\u002Fgeocoding-search-autocomplete\u002Fsources\u002F",[42],"Sources documentation",": the five open data providers behind the API",[55,747,748,752],{},[38,749,751],{"href":750},"\u002Fproducts\u002Fgeocoding-search\u002Fautocomplete-search\u002F","Autocomplete Search product page"," and pricing tiers",[754,755,756],"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":402,"searchDepth":758,"depth":758,"links":759},4,[760,762,763,764,765,766,767,768,769,770,778],{"id":49,"depth":761,"text":50},2,{"id":72,"depth":761,"text":73},{"id":134,"depth":761,"text":135},{"id":198,"depth":761,"text":199},{"id":317,"depth":761,"text":318},{"id":391,"depth":761,"text":392},{"id":445,"depth":761,"text":446},{"id":496,"depth":761,"text":497},{"id":534,"depth":761,"text":535},{"id":579,"depth":761,"text":580,"children":771},[772,774,775,776,777],{"id":584,"depth":773,"text":585},3,{"id":591,"depth":773,"text":592},{"id":602,"depth":773,"text":603},{"id":621,"depth":773,"text":622},{"id":641,"depth":773,"text":642},{"id":652,"depth":761,"text":653,"children":779},[780,781],{"id":656,"depth":773,"text":657},{"id":691,"depth":773,"text":692},"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.","md",{"script":785},[],"\u002Fimages\u002Fog\u002Fwhat-is-address-autocomplete.png",null,{"author":789},"Stadia Maps Team",true,"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\u002F)\n- [The Open Data Superpower: Why Global Search Is Moving Beyond Proprietary Silos](\u002Fblog\u002F)\n- [Precision Meets Privacy: Elevating the Consumer Search Experience](\u002Fblog\u002F)\n- [Autocomplete Search for SwiftUI and Jetpack Compose](\u002Fblog\u002F)\n- [Introducing Geocoding & Search v2](\u002Fblog\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",[794],{"@type":795,"mainEntity":796},"FAQPage",[797,801,804,807,810],{"@type":798,"name":585,"acceptedAnswer":799},"Question",{"@type":800,"text":588},"Answer",{"@type":798,"name":592,"acceptedAnswer":802},{"@type":800,"text":803},"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.",{"@type":798,"name":603,"acceptedAnswer":805},{"@type":800,"text":806},"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.",{"@type":798,"name":622,"acceptedAnswer":808},{"@type":800,"text":809},"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.",{"@type":798,"name":642,"acceptedAnswer":811},{"@type":800,"text":812},"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.",{"title":5,"description":782},"learn\u002Faddress-autocomplete","Address Autocomplete","A search-as-you-type interface that suggests addresses, places, and points of interest as a user types, ranked by relevance and proximity.","EONRynGN6MnZ1efflrxVtx_hlJrFGmNd8klVCYpj-TQ",[819,823,827],{"title":11,"description":820,"path":12,"published":821,"category":692,"rawbody":822},"Learn how geocoding works, where the data comes from, and how to use the Stadia Maps Geocoding API.","2026-07-14","---\ntitle: What Is Geocoding?\ndescription: Learn how geocoding works, where the data comes from, and how to use the Stadia Maps Geocoding API.\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",{"title":8,"description":824,"path":9,"published":825,"category":692,"rawbody":826},"Reverse geocoding converts coordinates into an address or nearby place. Learn how it handles administrative layers and how to build one with Stadia Maps.","2026-07-16","---\ntitle: What Is Reverse Geocoding?\ncategory: Geocoding & Search\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.\nhead:\n  script: []\nimage: \u002Fimages\u002Fog\u002Fwhat-is-reverse-geocoding.png\npublished: 2026-07-16\nschemaOrg:\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.\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",{"title":14,"description":828,"path":15,"published":821,"category":829,"rawbody":830},"Learn how isochrones work, what parameters matter, and how to generate one with the Stadia Maps Isochrone API.","Routing & Navigation","---\ntitle: What Is an Isochrone?\ndescription: Learn how isochrones work, what parameters matter, and how to generate one with the Stadia Maps Isochrone API.\ncategory: Routing & Navigation\nhead:\n  script: []\nimage: \u002Fimages\u002Fog\u002Fwhat-is-an-isochrone.png\npublished: 2026-07-14\nschemaOrg:\n  - \"@type\": FAQPage\n    mainEntity:\n      - \"@type\": Question\n        name: What is an isochrone map?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: An isochrone map displays one or more isochrone shapes, each connecting all points reachable within a set travel time or distance from a common starting point. Isochrone maps are used for site selection, accessibility analysis, service-area planning, and mobility studies.\n      - \"@type\": Question\n        name: What is the difference between an isochrone and an isodistance?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Isochrones measure reachability in units of time; isodistances measure reachability in units of distance. The Stadia Maps Isochrone API can be used to produce either by setting a time or distance value on each contour in the request.\n      - \"@type\": Question\n        name: What travel modes does the Stadia Maps Isochrone API support?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: The Stadia Maps Isochrone API supports nearly a dozen travel modes, including auto, bicycle, pedestrian, bus, taxi, and truck. Traffic-influenced variants exist for auto, bus, taxi, and truck. The full list is in the API reference.\n      - \"@type\": Question\n        name: Do isochrones account for traffic?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: They can. The Stadia Maps Isochrone API offers traffic-influenced profiles via _traffic and _traffic_premium suffixes on supported costing models. A traffic-influenced isochrone with an explicit date_time reflects live conditions and historical patterns; a static isochrone assumes average speeds. Traffic-influenced routing requires a Standard plan or higher.\n      - \"@type\": Question\n        name: How is an isochrone request billed on Stadia Maps?\n        acceptedAnswer:\n          \"@type\": Answer\n          text: Isochrone requests are billed as routing requests on the Stadia Maps API credit system. Contour count does not multiply the cost; a single request with three contours is a single billable request.\nterm: Isochrone\ntermDescription: A shape on a map showing everywhere reachable from a starting point within a set travel time or distance, given a mode of travel.\n---\n\n# What Is an Isochrone?\n\nAn [isochrone](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FIsochrone_map) is a shape on a map that shows everywhere you can reach from a starting point within a set travel time or distance, given a mode of travel. Also called a travel time map, isoline, or reachable range, an isochrone follows the road, path, or transit network, so the shape reflects how people actually move, not just how far a straight line goes. The [Stadia Maps Isochrone API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F) returns them as GeoJSON polygons or linestrings for driving, walking, cycling, and nearly a dozen other travel modes.\n\n## Key Takeaways\n\n- An isochrone shows everywhere reachable from a starting point within a set travel time or distance, based on the real road, path, or transit network.\n- Unlike a fixed-radius buffer, an isochrone accounts for road geometry, one-way streets, mode of travel, and (optionally) real-time traffic.\n- The Stadia Maps Isochrone API supports nearly a dozen travel modes, including driving, walking, cycling, bus, taxi, and truck.\n- Output is a GeoJSON FeatureCollection that renders directly in MapLibre GL JS, Leaflet, or any GeoJSON-aware map library.\n- Isochrones are the right tool for site selection, service-area planning, and accessibility analysis. They are not a substitute for routing (single ETA) or matrix (ranked distances).\n\n## Why Not Just Use a Radius for Isochrones?\n\nA fixed-radius buffer is fast, but for most real questions, it is wrong. A 10-minute drive out of downtown San Francisco covers a different area than a 10-minute drive out of suburban Phoenix. Highways, one-way streets, rivers with no bridges, transit availability, and pedestrian-only zones all bend the shape.\n\nCases where a radius breaks:\n\n- **Rivers and rail corridors.** A bridge or tunnel can be the only crossing for kilometers. A circle ignores that.\n- **One-way networks.** Driving out of a dense center is often slower than driving in. The reachable area is asymmetric.\n- **Mode mismatch.** A 15-minute walking radius reaches almost nothing on a road network built for cars, not people.\n- **Time of day.** A drive-time isochrone at 04:00 is much larger than the same isochrone at 17:30 when accounting for traffic.\n\nIf your product or application is making decisions based on who can reach a point quickly, then a radius is a meaningful penalty for accuracy. That is what the [Stadia Maps Isochrone API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F) is designed to fix.\n\n## How Isochrones Are Calculated\n\nIsochrone engines work in roughly the same way:\n\n1. Take the [road, path, and transit network](https:\u002F\u002Fwiki.openstreetmap.org\u002Fwiki\u002FRouting) as a graph.\n2. Assign a travel cost to every edge based on speed, mode, and any time-of-day model.\n3. Run a search outward from the origin, expanding by accumulated cost rather than distance.\n4. When the search hits each time or distance threshold, capture the reachable subgraph.\n5. Turn that subgraph into a polygon or linestring by buffering reachable edges and dissolving the result.\n\nStadia Maps runs isochrones on [Valhalla](https:\u002F\u002Fgithub.com\u002Fvalhalla\u002Fvalhalla), an open-source routing engine that Stadia Maps contributes to. Valhalla uses a tiled, multimodal graph and supports per-mode costing models, which is why the same endpoint can produce a useful pedestrian, bicycle, or automobile isochrone without swapping engines. For more on how the Stadia Maps routing stack fits together, see the [Routing overview](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F).\n\n## Isochrone Parameters That Matter\n\nThe [Stadia Maps Isochrone API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F) exposes the parameters that actually change the shape.\n\n- **`locations`**: The starting point (latitude and longitude). Required.\n- **`costing`**: The travel mode. Options include `auto`, `bicycle`, `pedestrian`, `bus`, `taxi`, and `truck`, among others. The full list is in the [API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fapi-reference\u002F).\n- **`contours`**: One or more time or distance thresholds. Each contour can carry a `color` that is echoed back in the response for direct rendering.\n- **`polygons`**: Set to `true` for filled polygons or `false` for linestrings. Use linestrings for accessibility plots or overlay layers.\n- **`date_time`**: For traffic-influenced modes, the departure or arrival time. Skipping this defaults to average conditions.\n\nTwo more that are less obvious but matter in production:\n\n- **`denoise`**: Removes small disconnected fragments below a relative size threshold. Lower it if you need to see remote islands of reachability.\n- **`generalize`**: Simplification tolerance in meters. Lower numbers produce more detailed shapes and larger payloads.\n\n## How Traffic Changes an Isochrone\n\nFor automobile, bus, taxi, and truck modes, the Stadia Maps Isochrone API supports [traffic-influenced profiles](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F#traffic-influenced-profiles) via the `_traffic` and `_traffic_premium` suffixes. `auto_traffic` and `truck_traffic_premium` are two examples.\n\nTraffic-influenced isochrones combine live conditions with historical data, so a rush-hour isochrone is typically smaller than the same isochrone at 03:00. If your product uses isochrones for logistics, dispatch, or delivery-zone decisions, a static-speed isochrone will overstate reachability during peak hours.\n\nTraffic-influenced routing requires a Standard plan or higher. See the [pricing page](\u002Fpricing\u002F) for plan details.\n\n## How Do You Generate an Isochrone?\n\nHere is what a request to the Stadia Maps Isochrone API looks like. This example asks for a 5-minute pedestrian isochrone from a point in Tallinn, Estonia.\n\n```http\nPOST https:\u002F\u002Fapi.stadiamaps.com\u002Fisochrone\u002Fv1\nContent-Type: application\u002Fjson\n\n{\n  \"locations\": [{\"lat\": 59.436884, \"lon\": 24.742595}],\n  \"costing\": \"pedestrian\",\n  \"contours\": [{\"time\": 5, \"color\": \"aabbcc\"}],\n  \"polygons\": true\n}\n```\n\nThe response is a [GeoJSON](https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fhtml\u002Frfc7946) `FeatureCollection` with one feature per contour. It renders directly in [MapLibre GL JS](https:\u002F\u002Fmaplibre.org\u002F), Leaflet, or any GeoJSON-aware renderer.\n\nFor runnable code in TypeScript, Python, Kotlin, Swift, PHP, or cURL, see the [Stadia Maps Isochrone API docs](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F). A step-by-step MapLibre GL JS walkthrough is in the [Display Isochrones on a Map tutorial](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fdisplay-isochrones-on-a-map\u002F).\n\n## Where Isochrones Fall Short\n\nIsochrones are not always the right tool. Beyond the parameter details in the [Isochrones documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F), here are the practical patterns worth knowing:\n\n- **Very small time bands are noisy.** A 1-minute isochrone is mostly buffer around the origin. For travel times below a few minutes, results depend heavily on off-road buffering rather than on real network travel, so use very short contours with caution.\n- **Static isochrones do not reflect traffic.** Without a `date_time` parameter, automobile isochrones can dramatically overstate reachability at rush hour or understate it at night.\n- **Cross-provider comparisons rarely agree.** Two providers will produce different polygons for the same origin because they use different graphs, different speed models, and different generalization settings. Standardize on a single provider for consistency across your product.\n- **Isochrones describe geographic reachability, not service areas.** Delivery zones, minimum-order distances, and exclusion rules are business logic that should sit on top of the isochrone, not inside it.\n\n## Isochrone vs. Matrix vs. Routing: Which Do You Need?\n\nThe [Stadia Maps Routing API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002F) family includes several related endpoints. Pick the right one:\n\n- For a single point-to-point travel time or ETA, use [standard routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F). It is cheaper and more precise than an isochrone.\n- For \"which of these N destinations is closest by drive time,\" use the [Time\u002FDistance Matrix API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F). Isochrones describe an area, not a ranking.\n- For service-area billing logic, compute the isochrone once, store the polygon, and query against it. Recomputing on every request wastes API credits.\n\n## Common Isochrone Use Cases\n\nIsochrones answer questions where a \"how far in time\" constraint matters more than a \"how far in miles\" constraint. The [Stadia Maps Isochrones product page](\u002Fproducts\u002Frouting-navigation\u002Fisochrones\u002F) frames it as \"reachable range decision-making\" and lists example questions this API commonly answers:\n\n- **Site selection.** Retail, healthcare, and logistics teams compare reachable population, demographics, or competitor density inside a drive-time band. A 20-minute isochrone is a better proxy for catchment than a 10-mile radius.\n- **Accessibility and mobility analysis.** Walking or transit isochrones show real access to schools, clinics, or grocery stores, not just distance.\n- **EV and fuel planning.** A driving isochrone with a distance constraint answers \"what is reachable in the last 20 miles before I need to charge or refuel?\"\n- **Marketplace coverage.** When a merchant joins a delivery platform, an isochrone defines the visible service area.\n- **Real estate search.** Filtering listings by \"30 minutes from my office by transit\" is an isochrone query against a property index.\n\n## Frequently Asked Questions\n\n### What is an isochrone map?\n\nAn isochrone map displays one or more isochrone shapes, each connecting all points reachable within a set travel time or distance from a common starting point. Isochrone maps are used for site selection, accessibility analysis, service-area planning, and mobility studies.\n\n### What is the difference between an isochrone and an isodistance?\n\nIsochrones measure reachability in units of time; isodistances measure reachability in units of distance. The [Stadia Maps Isochrone API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F) can be used to produce either by setting a `time` or `distance` value on each contour in the request.\n\n### What travel modes does the Stadia Maps Isochrone API support?\n\nThe [Stadia Maps Isochrone API](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F) supports nearly a dozen travel modes, including `auto`, `bicycle`, `pedestrian`, `bus`, `taxi`, and `truck`. Traffic-influenced variants exist for `auto`, `bus`, `taxi`, and `truck`. The full list is in the [API reference](https:\u002F\u002Fdocs.stadiamaps.com\u002Fapi-reference\u002F).\n\n### Do isochrones account for traffic?\n\nThey can. The Stadia Maps Isochrone API offers [traffic-influenced profiles](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F#traffic-influenced-profiles) via `_traffic` and `_traffic_premium` suffixes on supported costing models. A traffic-influenced isochrone with an explicit `date_time` reflects live conditions and historical patterns; a static isochrone assumes average speeds. Traffic-influenced routing requires a Standard plan or higher.\n\n### How is an isochrone request billed on Stadia Maps?\n\nIsochrone requests are billed as routing requests on the [Stadia Maps API](\u002Fpricing\u002F) credit system. Contour count does not multiply the cost; a single request with three contours is a single billable request.\n\n## Where to Go Next\n\n### From the Blog\n\nMore on isochrones and adjacent routing topics:\n\n- [The Invisible Costs of Routing: Privacy, Pricing & the MAU Trap](\u002Fblog\u002Finvisible-costs-of-routing-privacy-pricing-mau-trap\u002F)\n- [Beyond the Car: Routing for the Other 90% of Transport](\u002Fblog\u002Fbeyond-the-car-routing-for-specialized-fleets\u002F)\n- [Why Basic OSM Routing Needs Real-Time Traffic](\u002Fblog\u002Fwhy-osm-routing-needs-real-time-traffic\u002F)\n- [Traffic-Influenced Routing Is Here (Public Preview)](\u002Fblog\u002Ftraffic-influenced-routing-in-public-preview\u002F)\n\n### Routing & Navigation\n\n- [Isochrones API documentation](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fisochrones\u002F) for the full parameter set\n- [Display Isochrones on a Map tutorial](https:\u002F\u002Fdocs.stadiamaps.com\u002Ftutorials\u002Fdisplay-isochrones-on-a-map\u002F) with a working MapLibre GL JS example\n- [Standard Routing](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Fstandard-routing\u002F) for a single point-to-point ETA\n- [Time\u002FDistance Matrix](https:\u002F\u002Fdocs.stadiamaps.com\u002Frouting\u002Ftime-distance-matrix\u002F) for ranked distances to many destinations\n- [Stadia Maps Isochrones product page](\u002Fproducts\u002Frouting-navigation\u002Fisochrones\u002F) and pricing tiers\n- [Matrix Routing product page](\u002Fproducts\u002Frouting-navigation\u002Fmatrix-routing\u002F)\n",{"id":832,"bio":787,"extension":18,"jobTitle":787,"meta":833,"name":834,"sameAs":835,"slug":838,"stem":839,"twitterCreator":787,"type":840,"url":841,"__hash__":842},"authors\u002Fauthors\u002Fstadia-maps.yml",{},"Stadia Maps",[836,837],"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",1784885903802]