[Geocoding] Error in Address looks like it always converts, "Grand" to "gr"
marc tobias
mtm at opencagedata.com
Thu Mar 7 22:52:50 UTC 2019
Hi Bill,
The normalization mapping of Grand=>gr is also applied when the
search index is created and updated. In other words the database
contains 'gr' and during search time Nominatim searches for 'gr'
(and 'Road' is mapped to 'rd').
In OpenStreetMap data that street has the name 'Grand Oaks Road'
https://www.openstreetmap.org/way/16711544 It might be wrong, I
see other map providers have 'Grand Oak Drive'. If you have local
knowledge you can edit the name of the road in OpenStreetMap.
The house number node (https://www.openstreetmap.org/node/5732245606)
calls the street "Grand Oak Drive".
It is far outside the imported city boundaries of Hillsborough
though https://www.openstreetmap.org/relation/179869 I'd say it's
a case where the official boundaries don't match with what people
living there consider the extend of the city.
marc tobias
> From: Bill <w1rep at yahoo.com>
> Subject: [Geocoding] Error in Address looks like it always converts
> "Grand" to "gr"
> Message-ID: <1471051918.1076002.1551990509812 at mail.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Looks like it changes Grand to gr and doesn't find the address!!!
> Thanks, Bill
>
>
> Debug output for Geocode::lookup
> Geocode: 'Query' => '420 Grand Oak Hillsborough, NC USA'
More information about the Geocoding
mailing list