Add matching status to geocode output

[mikepease]

As I've been evaluating the correctness of the geocoder, I've wrapped the geocoder function inside a query that tells me which components of the input address matched.

I compare the components of the output of normalize_address() to the components of the geocode.addy geocoded address.

When all the components match, I'm pretty sure it's a good geocode. When most of the components match, I can get a pretty good idea of how accurate the geocode is.

Maybe you'd like to add these "match" attributes to the output of geocode() to augment the rating column. house number matched?
street name matched?
street direction matched?
city matched?
state matched?
zip matched?

[robe]

That's a good idea. Was also thinking about having some configurable rating object you can pass in to denote the weights you want to use for each. Though it would make things a bit verbose. Possibly a lookup table of rating options and you just pass in a code to denote which you want to use.

[mikepease]

The lookup table sounds like a fine idea.

So, what would be returned if you weight city & zip highest but no matching street could be found? Could you return a centroid of the intersection of the city and zip? What else might be a suitable output?

[robe]

Milestone renamed