Re: [talk-au] Fwd: OSM Search results return strange stuff for Victoria.
On Wed, 20 Jan 2021 at 10:19, cleary wrote: > I was told that the correct tag for places such as towns or suburbs is > postal_code=* whereas the addr:postcode tag is for individual locations. > > However, even with that tag on the suburb boundary, Nominatim is getting > it wrong, particularly for streets close to suburb boundaries. I found > multiple examples in Sydney suburbs without much effort. In each case the > suburb boundary included the correct postal_code=* tag. In one instance > the postcode shown by Nominatim is the special postcode for PO Boxes in an > adjacent suburb, not even the usual postcode for street addresses. I can > only presume a business in the area is tagged in OSM with its postal > address, a PO Box in the adjacent suburb, and that has been taken by > Nominatim as the postcode for this area. > > Perhaps we need to tag individual streets with postcodes, especially > streets near suburb boundaries. > > One final thought ... perhaps Nominatim reads only addr:postcode=* tags > and does not understand postal_code=* If so, that might explain the > anomalies. > There are references to postal_code=* in the Nominatim code base, I'd suggest reporting those examples you found to the Nominatim issue tracker. I'm not sure if you have addresses on opposite sides of a street with different postcodes or not, so my preference is to map the actual address objects rather than adding a postcode to the road. ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] Fwd: OSM Search results return strange stuff for Victoria.
I was told that the correct tag for places such as towns or suburbs is postal_code=* whereas the addr:postcode tag is for individual locations. However, even with that tag on the suburb boundary, Nominatim is getting it wrong, particularly for streets close to suburb boundaries. I found multiple examples in Sydney suburbs without much effort. In each case the suburb boundary included the correct postal_code=* tag. In one instance the postcode shown by Nominatim is the special postcode for PO Boxes in an adjacent suburb, not even the usual postcode for street addresses. I can only presume a business in the area is tagged in OSM with its postal address, a PO Box in the adjacent suburb, and that has been taken by Nominatim as the postcode for this area. Perhaps we need to tag individual streets with postcodes, especially streets near suburb boundaries. One final thought ... perhaps Nominatim reads only addr:postcode=* tags and does not understand postal_code=* If so, that might explain the anomalies. On Wed, 20 Jan 2021, at 9:15 AM, Graeme Fitzpatrick wrote: > Re-sent to list as well! > > Thanks > > Graeme > > > -- Forwarded message - > From: *Graeme Fitzpatrick* > Date: Wed, 20 Jan 2021 at 08:14 > Subject: Re: [talk-au] OSM Search results return strange stuff for Victoria. > To: Jonathon Rossi > > > > > > On Tue, 19 Jan 2021 at 21:41, Jonathon Rossi wrote: > > I've not mapped them before but curious now why we don't seem to have > > imported addr:postcode tags for suburbs, Nominatim uses them before > > centroids. > > > > Surely addr:postcode doesn't have to be unique because it sounds like some > > countries have postcodes based on postal routes or other less > > administrative boundaries. > > From recent posts re addresses on the tagging list, the UK even has > unique postcodes for individual buildings, & even for different > businesses / organisations inside the one building! > > Thanks > > Graeme > > ___ > Talk-au mailing list > Talk-au@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-au > ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
Re: [talk-au] OSM Search results return strange stuff for Victoria.
Search is powered by Nominatim: https://nominatim.openstreetmap.org/ui/details.html?osmtype=W=625658428=highway It returns: Computed Postcode 3192 This page describes the process for computed postcodes, basically the center point of all elements with a postcode. There is an Overpass query here you can run to see those elements: https://github.com/mtmail/Nominatim/blob/master/docs/develop/Postcodes.md All the elements with a postcode of 3190 are grouped tightly together, so 3192 is closer. On Tue, Jan 19, 2021 at 8:54 PM Ewen Hill wrote: > This is a weird one... > Do a search for 3 Remington Drive, Highett e.g... > > > https://www.openstreetmap.org/search?query=3%20Remington%20Drive%2C%20Highett#map=19/-37.95363/145.04802=N > > It returns the correct street but the incorrect postcode.of 3192 .. > > Does anyone know how 3192 is injected into the returned address please? > > Ewen > > ___ > Talk-au mailing list > Talk-au@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-au > -- Jono ___ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
