That a building|property will have only one address.
Sometimes (eg: rural Australia) property addresses are updated from an older numbered lot based system (that goes astray when properties are subdivided and infill houses appear) to a system that numbers houses by driveway distance from last major intersection.
For five or ten years a house can be recieving mail or be on the records with both the old and the new address.
So as an example, if you use the UPSP Cities by ZIP Code to research 77005 and you would see that they recommend using the city name of “Houston” for mail, but they would also recognize “West University Place”. There’s also a city called “Southside Place” which should be avoided when it comes to sending mail. But then that kind of makes me think that if a house is within the limits of one or these small cities, then it could in theory have the same street name but have two different city values in different databases.
Then on the other hand there’s a somewhat related problem where a small town or village (e.g. Somers, WI and Scotland, CT) can have multiple ZIP codes and that ends up causing a lot of headaches for the residents of the town since they all might live nearby but then each section of the town might end up associated with some other larger city it’s closest to.
[1]: https://tools.usps.com/zip-code-lookup.htm?citybyzipcode
Not that there's a mailbox on the mailing address street. (There's only a small side profile of a house/yard on the mailing address street side). There doesn't seem to be a good reason for the mailing address.
This one affects me personally and it bugs me programmers think that they know better than I do about my address when I try and enter the city name and zip code, then they "correct" the city name based on the zip code and make it read only.
a) what was the point of me entering the city if you were going to fill it in anyway ?
b) this has happened in the last two cities I've lived and is dirt common around a major metro area in the United States. Stop autocorrecting user entered data, let them be wrong!
That struck me, although I already knew that a ZIP code could span multiple cities and sometimes even states. I just thought there would be no confusion about which city name to use.
Overall addresses are such a mess, and they are a mess even for governmental agencies like this one.
https://www.ordnancesurvey.co.uk/news/new-national-vernacula...
Had some calls where people would be hurt in a forest on a trail system and it was pretty common for people to not even know the name of the trail they are on nor which street they entered it from. Sometimes the GPS location the phone provided to EMS would help, but it also wasn't always 100% reliable, especially if they were in a forest. So being able to have them look at a map on their phone, pin where they are, and give a what3word location would have been immensely helpful.
The kind of system you linked to would also have been quite helpful for the other problems I mentioned.
When merging records the old address, no longer valid with the local land management agency, still appears on old notices and on current state and or federal records (as land naming agencies are layered in some locales with changes taking time to perculate).
The old address is "the correct address" in the context of birth records, old newspaper articles, last years tax records, etc.
You're technically pedantically correct .. but in a manner that's moot when faced with the realities of day to day day reconciliation of meaning of text on an envelope or document.
