Reading the confidence and precision fields correctly
Precision tells you what kind of match you got. Confidence tells you how sure the geocoder is. Mixing up the two leads to bad filtering logic.
Notes on geocoding, IP data, and building on the My Geocode API.
Precision tells you what kind of match you got. Confidence tells you how sure the geocoder is. Mixing up the two leads to bad filtering logic.
A regional grocer needed to know exactly which neighborhoods its new warehouse could serve profitably, so it turned every order address into a distance from the loading dock.
A single call with a hundred addresses inside it counts as a hundred requests, not one. Here is why we count bulk calls by item instead of by call.
Send a list of latitude and longitude pairs to the reverse endpoint in one call and get back an address for each one, in order, without extra overhead.
A look at what actually changes when you point a Google Maps Platform integration at My Geocode, and what your existing code gets to keep untouched.
A per-request price matches what an API actually costs to run. Seat pricing measures headcount, not usage, and geocoding traffic rarely follows either.
Accuracy claims mean nothing without a method. Here is how reference addresses with known coordinates are used to check what a geocoder actually returns.
Turn a spreadsheet export into a single POST request and get back one geocoded result per row, without writing a request loop or paying for extra calls.
A lending platform started checking the IP address behind every signup, catching hosting-provider traffic and shared fraud ranges before an application ever reached underwriting.
No account, no card and no key needed to start. Any address gets up to 2,500 free geocoding, IP, timezone and elevation requests a day.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom