Author: twain
[Added to the original trac issue at 6.08pm, Saturday, 5th December 2009]

Ways with identical addresses are merged, otherwise they are both shown.

I think an extra option to control the amount of merging may be needed.

Author: MichalP
[Added to the original trac issue at 9.39pm, Thursday, 15th April 2010]

another example http://nominatim.openstreetmap.org/search?q=sancova+bratislava

to make it harder:

• opposite lanes are not connected (they are connected by different roads) (but they are close to each other, like couple of meters)

• each lane is in a different district and has different postcode (middle of the road is the administrative border)

• some of the ways may have unfilled other names (like local_name), either on purpose or unintentionally

is it possible to merge results if they are closer than say 10 meters ?

maybe group by ST_Distance (if it worked...)

where would you suggest to start hacking ?

Author: MichalP
[Added to the original trac issue at 12.37pm, Friday, 21st May 2010]

there is proposal for relation collected ways
http://wiki.openstreetmap.org/wiki/Relations/Proposed/Collected_Ways

this one could be used to determine one street.

Author: datendelphin
[Added to the original trac issue at 8.42pm, Tuesday, 10th July 2012]

seems to be fixed in the mean time

Author: jbohmdk
[Added to the original trac issue at 1.41am, Friday, 9th August 2013]

Problem is still there, two examples that I recently looked at in detail:

Harlsevej (unique in the current planet data)

Tulstrup Have, Hillerd

("" is a national letter, just copy/paste it).

These two roads are typical examples of the reasons a road is split in the osm data. Harlsevej is a long tertiary road, which is split whenever things like speed limits or sidewalk presence changes. Both roads also feature side branches sharing the name (they are effectively shared driveways, some with, some without, public right of way). One end of Harlsevej also features a split into right and left lanes near a roundabout. Neither has (nor should have) any special route relation, all have direct connections between their parts (shared nodes, no need for fuzzy distance checks).

However Nominatum currently (2013-08-09 01:20 UTC) returns both roads as a large number of hits, in seemingly random order.

The rule should be simple: If two roads with the same name, share a node and share (derived) is_in relations and other Nominatim relevant data, they should become one in the Nominatim database. If they share the same name and share a node, but differ in properties that Nominatim needs for other operations, they should be internally linked, so a search returns just a single merged object consisting of the segments that match the search criteria (for instance, if the search is limited to the part of Harlsevej that has an implicit or explicit is_in Tjreby, then those parts should be returned as one stretch of road which is less than the full road, but still the merge of many segments).

Author: lonvia
[Added to the original trac issue at 8.09am, Sunday, 9th February 2014]

The duplicates of Harlsevej are related to an update bug where the wrong default admin_level was assigned. That has been fixed in the meantime and should take effect the next time the OSM is changed.

For merging streets see ticket #4952.