Given how many of those are typos I'm not sure how much advantage there is in replacing them with compressed incomprehensible strings. Typo one of these map codes and you'll end up in a different zip code and at first glance nothing will look wrong because they are designed for machines, not people.
Re:Should Mapcodes Replace GPS?
by thisisdave on Monday May 09, 2016 @01:52AM
(#11657845)
To some extent, this could be addressed with standard error detection/correction techniques (e.g. error-correcting codes). But that would make the strings longer and often wouldn't help until they made it to a computer anyway.
The units have GPS in them. The number of possible streets near them is pretty small, so an autocomplete or similar might work really well.
Or just a dropdown.
Address data is so incredibly difficult to work with and it's pretty clear that it's difficult for everyone involved. Census data is incorrect, OSM is often incorrect, other free sources are filled with typos, post office is consistently bad (No, my last name is not Nicholson...), shapefiles are often haphazardly done. It's so difficult to work with. That said, the amount of quality work to even get it to this point is amazing. Serious kudos to everyone who helps out here.
I've spent an asinine amount of time recently trying to get Chicago's parking ticket data cleaned up. Lake Shore drive is probably the #1 culprit:
Unique lake shore drive instances:
128Example of the awfulness: