Menu

What "accurate" means for a geocoder, and how I decide a change is safe
📰

What "accurate" means for a geocoder, and how I decide a change is safe

DEV Community: rust·Théo Mathieu·1 day ago
#WcfrXBha
#devtorust#devto#dev#country#case
Reading 0:00
15s threshold

I run OpenGeocoding. Originally published on the OpenGeocoding blog . Cross-post formatting was prepared with AI assistance.

“How accurate is it?” sounds like one question, but a geocoder answers several at once. Did it find anything? Is the answer in the right country? Is the point close enough to be useful? Is it as precise as the address you sent, a house for a house and a town for a town? And when it returns a house number or a postcode, does that agree with yours?

This post explains how I score those questions for OpenGeocoding, how close I count as close enough, which losses I accept when I change the engine, and how I keep the test set from grading the index on its own data. The first post has the pass rates; this one is about what stands behind them.

A pass has several conditions

The scorer looks only at the first result. A best-of-several answer would flatter every service, and an application usually takes the first one.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.