This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

Major incorrect postcode returned on reversegeocode

0

Hi! I have reverse searched a GPS co-ordinate: -27.37324,153.047182 and it returns: St Kevin's Primary School, Deborah Street, North Chermside, Geebung, Brisbane, Queensland, 5055, Australia

All information is correct with one exception. The postcode 5055 is wrong. In fact it is not even close. That postcode comes from a totally different state in Australia at the other end of the country (specifically South Australia).

If I do a regular search for: St Kevin's Primary School, North Chermside it once again returns the correct information except for the wrong postcode: St Kevin's Primary School, Deborah Street, North Chermside, Geebung, Brisbane, Queensland, 5055, Australia

If I do a regular search for: North Chermside It returns the correct postcode for that suburb: North Chermside, Chermside, Brisbane, Queensland, 4032, Australia

A quick search indicates this incorrect 5055 postcode is returned for a handful of suburbs in the same physical vicinity (although these suburbs may have a slightly different postcode of their own).

It appears to be that geofencing for those suburbs is where the issue arises.

How does one go about reporting/repairing this information? Appreciate and feedback.

Cheers Todd

asked 04 Mar '19, 05:03

todddixon's gravatar image

todddixon
11113
accept rate: 0%

edited 04 Mar '19, 11:21

scai's gravatar image

scai ♦
33.3k21309459


2 Answers:

2

According to this: https://nominatim.openstreetmap.org/details.php?place_id=80662662, the postcode is not in the OSM database, but is imported by Nominatim. There is no link next to a node or relation in OSM, which is typical for information that is not found in OSM.

I guess that you could report that on the Nominatim Github repository.

answered 04 Mar '19, 11:11

escada's gravatar image

escada
19.0k16166302
accept rate: 21%

1

Nightly Nominatim looks at postcodes and calculates a center point for each. The /details page can't link to a single OSM object here.

(04 Mar '19, 11:36) mtmail

2

This place https://www.openstreetmap.org/node/2207501595 is mapped with postcode 5055. All others addresses in the neighborhood seem to be 4034. Once changed Nominatim will recalculate the 5055 position (once per night). Deleted the place now https://www.openstreetmap.org/changeset/67763854

answered 04 Mar '19, 11:40

mtmail's gravatar image

mtmail
4.8k1574
accept rate: 27%

edited 04 Mar '19, 11:44

Thank you for your quick response. I notice that it picked up the 5055 from part of the phone number on that site. I don’t understand fully understand how Openstreetmap and Nominatim work under the bonnet but your explanation is at least a little insight in to it’s inner workings! I appreciate your help.

Cheers 😊

(04 Mar '19, 12:22) todddixon

The nightly postcode recalculation worked on my worldwide setup, but I still see the issue on https://nominatim.osm.org/reverse.php?lat=-27.37324&lon=153.047182 You might have to open an issue on https://github.com/openstreetmap/Nominatim/issues to have the administrators review that. I open reply to open issues there but don't have access to the Openstreetmap foundation servers.

(05 Mar '19, 21:42) mtmail

Source code available on GitHub .