[Geocoding] holes in the nominatim search results

Allan Visochek avisochek3 at gmail.com
Tue Mar 29 18:23:48 UTC 2016


Hey there,

I'm having trouble making sense of some gaps in the data I am getting from
the nominatim search.

For a project that I am working on, I need to find the length of various
streets. I've set up a program which does the following and works fine:

1. Query the raw osm file for all way elements with a particular name.
2. For each element, iterate over the node reference tags and retrieve the
longitude and latitude coordinates of each node.
3. Add the distances between each pair of consecutive nodes if they are
within the boundaries of a particular city.

Again, this program works fine, I'd be glad to include the code if it would
be helpful, but have left it out for now to keep things concise.

To save time, I have installed nominatim. My current method is to search
for elements using the street name as a query and return the geojson for
that element:

/search?q=Chapel+Street&format=json
I've also tried:
/search?format=json&street=Chapel+Street
and I've tried this with a number of different streets.

The problem here is that a lot of segments of any particular street are
left out. I have checked to verify that my local results are the same as
those

The following is a graph of the coordinates of every element / street
segment returned by nominatim for a particular search query:

[image: Inline image 1]

So each line and color represents a different element and the spaces in
between are not accounted for. For comparison, here's the same graph with
the same street name using my original program.

[image: Inline image 2]

Here's another one:
Nominatim:
[image: Inline image 4]

Raw OSM:
[image: Inline image 5]

Is there anything that I could to get all of the street segments returned
by a nominatim search?

Thanks in advanced, I will greatly appreciate any help you can give me!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20160329/dd27d012/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 37417 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20160329/dd27d012/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 37737 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20160329/dd27d012/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 32686 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20160329/dd27d012/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 35700 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20160329/dd27d012/attachment-0007.png>


More information about the Geocoding mailing list