Moving off a Google Places autocomplete integration
Autocomplete is one of the trickier pieces to migrate because its request pattern and session behavior differ across providers. Here is what to plan for.
Notes on geocoding, IP data, and building on the My Geocode API.
Autocomplete is one of the trickier pieces to migrate because its request pattern and session behavior differ across providers. Here is what to plan for.
A browser SDK for a server-side lookup mostly just moves your API key somewhere a visitor's browser can see it. That is not a convenience worth having.
Carrier-grade NAT pools large numbers of mobile subscribers behind a small number of public IP addresses, which puts a hard ceiling on how precise mobile IP geolocation can be.
A local business directory kept publishing listings at addresses that turned out to be empty lots, until it started checking each submission before publishing it.
Sum the upward changes between consecutive points along a route to get one elevation gain figure straight from raw latitude and longitude data.
Geocode.Farm requests now work against our host unchanged, matching its parameters and response fields with only a host name and key to update.
A per-key limit alone assumes one key means one user. Rate limiting by network closes the loophole where that assumption quietly breaks down.
Elevation lookups are usually a small dependency inside a bigger Google Maps account. Here is how to move that specific piece cleanly.
The same street name can be written correctly in several different scripts and spellings. Matching addresses across these variants is a genuine data quality challenge.
Show each customer's local time right next to their support ticket, so an agent knows whether it is a reasonable hour to pick up the phone.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom