You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: chris_debian [Submitted to the original trac issue database at 10.18pm, Tuesday, 29th December 2009]
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?
Author: twain [Added to the original trac issue at 5.23pm, Monday, 11th January 2010]
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'?
Reporter: chris_debian
[Submitted to the original trac issue database at 10.18pm, Tuesday, 29th December 2009]
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?
Example:
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:
http://www.opensatnav.org/issues/show/81
Many thanks,
Chris
(chris_debian)
The text was updated successfully, but these errors were encountered: