Warning signs you are locked into a proprietary format
Vendor lock-in around a geocoding response format creeps in gradually. Here are the specific warning signs worth watching for.
Notes on geocoding, IP data, and building on the My Geocode API.
Vendor lock-in around a geocoding response format creeps in gradually. Here are the specific warning signs worth watching for.
Storing or computing coordinates using the wrong numeric type can introduce rounding errors on the order of meters, entirely separate from any error in the original geocoding.
Geocode a visitor's address once and compare it against a short fixed list of office coordinates in your own code to find the closest match.
Postal code coverage has improved specifically in rural and low-density areas, where postal boundaries tend to be harder to map accurately.
An internet provider's sales team needed an instant answer for a specific service address, not just a general sense of which postal codes were served.
If switching a location API takes a quarter, the previous integration was designed to make leaving expensive, whether or not that was the stated intention.
Elevation figures are checked against fixed, independently surveyed benchmark points with known heights, and consistency across nearby samples is a further useful sanity check.
Unit and apartment numbers do not need to be stripped out before geocoding an address, and doing so can lose useful information for no benefit.
Comparing geocoding vendors on price alone misses real costs elsewhere. Here is a simple model that accounts for more than the per-request rate.
A vacation rental platform kept discovering listings with addresses that were slightly, sometimes deliberately, wrong, after a guest had already shown up and found nothing at the pin.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom