When a postcode search is performed in OSM (via the website), Nominatim seems to return the postcode centroid rather than using any existing tags, such as addr:postcode or postal_code. If that is the case, then no amount of correctly tagging objects with a given postcode would alter where that pin is displayed and, therefore, I don’t think there’s anything that can be done to address the complaint on note #3681409. I’m sure we must have been here before but could others who are fond of address data please weigh in? HP23 4QZ is the point in question. Thanks.
Nominatim uses CodePoint Open to augment the list of postcode centroids in the UK where they are missing in OSM. That’s where the data comes from and where the complaints probably should go to.
That said, data from OSM itself has always precedence for Nominatim. If you add the addresses for the houses that have the postcode and add addr:postcode, the result centroid should move accordingly. However, it will always be at the centre of the addresses given and not necessarily on top of station road. (Although you could just add addr:postcode to the Station road way, which currently would effectively put the postcode where they want it. It might get you into trouble with other mappers though.)
I follow your logic but personally I wouldn’t tag the road itself with addr:postcode (as it’s not an address) but with postal_code. Would this work?
Yes, that will be picked up as well.
Thanks. Have tagged as such on changeset #163746445.
It might be worth adding a note tag to that segment of Station Road to explain why it’s a full postcode, otherwise someone might truncate the postal_code tag to just the HP23 district.
Thanks. Now added.
You can be more specific in how you search with Nominatim (if the postcode is on each object). E.g.
- The Post Office, HP23 4QS
- 44 Station Road, HP23 4QS
- 44, HP23 4QS doesn’t work as desired
And for debugging, you’ll get more information by using this User Interface of Nominatim. Nominatim Demo
1 Like