You could be right, but I think it's a little beside the point.
The challenge illustrated in the blog post is that it's practically impossible to build a really accurate address dataset since the real world is messy for the reasons you listed. Just like falsehoods programmers believe about names [1], you shouldn't put much faith in anything that claims to normalize addresses either.
As other commenters have said in the replies, my situation is not uncommon in Europe.
As long as it shows that your address corresponds to that plot of land it's still a perfectly accurate address dataset. Your address just kind of sucks. That doesn't make the dataset less accurate, just less useful.
Still a lot better than some other parts of the world though. In Asia you sometimes have addresses that boil down to the nearest landmark and a phone number for the mailman to call
> it's practically impossible to build a really accurate address dataset since the real world is messy for the reasons you listed
Different entities will have orthogonal needs when it comes to your address. First responders want a door, the post office wants a mailbox, assessors want a plot number, etc.
The challenge illustrated in the blog post is that it's practically impossible to build a really accurate address dataset since the real world is messy for the reasons you listed. Just like falsehoods programmers believe about names [1], you shouldn't put much faith in anything that claims to normalize addresses either.
As other commenters have said in the replies, my situation is not uncommon in Europe.
As they say, 'the map is not the territory.'
[1]: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...