Countries that have changed their time zone rules
A country's UTC offset is not permanent. Governments periodically redraw zone boundaries, adjust offsets, or add and drop daylight saving, and software has to keep up.
Coverage by country, accuracy measurements, and how to read the precision and confidence in each answer.
A country's UTC offset is not permanent. Governments periodically redraw zone boundaries, adjust offsets, or add and drop daylight saving, and software has to keep up.
Twice a year, a range of local times either does not exist or exists twice. Software that assumes every clock time is unambiguous will fail exactly then.
Not every time zone sits on a clean hour boundary. Several countries use 30 or 45 minute offsets, and code that assumes whole hours will break on them.
Time zone offsets are not fixed physical facts, they are legal decisions that governments change. Here is how that gets tracked and kept current.
Thousands of phones on the same carrier network can share one public IP address. That single fact explains most of the accuracy limits on mobile geolocation.
A VPN does not hide a user from IP geolocation, it just relocates them to the exit server. Here is what that means for the data you get back.
An IP address identifies a network connection, not a physical address. Understanding that distinction prevents most IP geolocation disappointment.
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.
Accuracy claims mean nothing without a method. Here is how reference addresses with known coordinates are used to check what a geocoder actually returns.
Only Data quality, as it is published.
Subscribe to Data quality