Autocomplete suggestions added across compatible hosts
Address autocomplete requests are now supported across the compatibility hosts that offer it, matching each provider's own autocomplete request shape.
Notes on geocoding, IP data, and building on the My Geocode API.
Address autocomplete requests are now supported across the compatibility hosts that offer it, matching each provider's own autocomplete request shape.
A usage dashboard that only updates once a day is not really a real time picture at all. It is just yesterday's number wearing today's date on it.
Let a visitor enter their address and see exactly how far your nearest location is, using one geocoding request and a distance formula in your own code.
A server-side geocoding migration can often be invisible to the client applications that depend on it. Here is how to design it that way.
Rooftop geocoding places a point at the actual building. Street-level geocoding interpolates a position along the road. The two look similar on a map and are not the same thing.
A home appliance repair company was assigning jobs to whichever technician happened to be free next, regardless of how far that technician actually had to drive to reach the customer.
The elevation endpoint now handles long routes made up of many coordinates more efficiently, aimed at routing and hiking applications that request elevation profiles.
Licensed data comes with a contract that can change under you. Open data comes with a community that has no reason to renegotiate your access later.
Batch requests on My Geocode are sized to match what large providers already support, so an existing batch integration should not need resizing.
Geocoding calls from a mobile app carry constraints a server-side migration does not have to think about. Here is what to plan for specifically.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom