Opened 10 years ago

Closed 10 years ago

#2586 closed defect (fixed)

Nominatim requires UK postcode queries to have a 'space' in-between both parts of postcode.

Reported by: chris_debian Owned by: twain
Priority: major Milestone:
Component: nominatim Version:
Keywords: Postcode lookup Cc:


Hi, all.

OpenSatNav? (.org) has started to use Nominatim as an optional 'search engine'. We (OSN) are finding that it works really well.

With UK postcodes, we find that look-ups require a 'space' to be used between the first and second part of the postcode. Potentially, this could make the user think that postcode searches are failing, when in-fact they are just not been queried properly.

Can you confirm whether it is possible to permit searches without a 'space', or whether we need to try to find a work-around on the front-end?


a) User searches for postcode DL7 0SN

Result: Address identified.

b) User searches for postcode DL70SN

Result: Address not recognised.

OSN it tracking this bug, here:

Many thanks,



Change History (2)

comment:1 Changed 10 years ago by twain

Owner: changed from openstreetmap@… to twain
Status: newassigned

Sort of fixed.

I was able to get the fallback code (that calculated an approximate location for a postcode not present in the data) to accept a postcode without a space. But this means it is using the fallback code even when it has an exact match. The result is hopefully usable - let me know if this is fixed 'enough'?

comment:2 Changed 10 years ago by chris_debian

Resolution: fixed
Status: assignedclosed

Thanks, for the rapid fix, Brian. This works well with OpenSatNav?.

Happy to close.


Note: See TracTickets for help on using tickets.