The problem with SLA language nobody can act on
A 99.99 percent uptime promise means nothing if the credit for missing it is a rounding error and the process for claiming it takes longer than the outage did.
Notes on geocoding, IP data, and building on the My Geocode API.
A 99.99 percent uptime promise means nothing if the credit for missing it is a rounding error and the process for claiming it takes longer than the outage did.
ip-api.com's flat JSON response is widely copied elsewhere in the industry. Here is what changes when you migrate that specific integration.
The same key works as a header, a bearer token, basic auth, or a query parameter, so pick whichever mechanism fits the tool making the request.
Some coordinates sit in places where more than one government claims sovereignty. Location data has to describe reality on the ground without taking a political side.
An online store needed a shipping estimate before checkout, working from nothing but the postal code a shopper had typed into a single field.
MapQuest Geocoding requests now work against our host unchanged, matching its parameters and response fields so switching needs only a host and key.
Country codes and subdivision codes look simple until you hit the exceptions. Here is what ISO 3166-1 and 3166-2 actually cover, and where confusion creeps in.
Some location APIs quietly become analytics businesses on the side, selling what they see. We resolve the lookup you asked for and stop there.
Geocode.Farm serves a smaller niche in the geocoding market. Here is what a migration to a compatible drop-in host actually involves.
Caching addresses saves requests, but only if your cache and your quota headers agree on what has actually been looked up.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom