Opened 10 years ago

Last modified 4 years ago

#1134 new defect/bug

If multiple streets have the same name, only one is found

Reported by: sleske Owned by: KaZeR
Priority: minor Milestone: version 0.6.0
Component: core Version: git master
Severity: Keywords:


At present, when searching for a street within a city using the standard search dialog, Navit will only show one result per street name.

However, some cities have multiple streets with the same name (usually in different parts of the city). In these cases, only one of the streets can be found with Navit, the rest is "invisible" to the search.

Examples (in Germany):

Gartenstraße, Berlin Berliner Straße, Köln

In each case, if I search for the street, I get one hit, even though there are multiple streets with the name.

Navit should somehow show all the streets. Ideally with some indication to tell them apart, such as their suburb, or their distance from the city center...

Change History (5)

comment:1 Changed 10 years ago by sleske

This problem, and possible solutions, is discussed in #794. The basic problem is that a single street usually consists of more than one segment in the OSM data, and thus in the binfile. Navit combines these segments into one by name. This is usually correct, but not if the segments actually belong to two different streets with the same name...

comment:2 Changed 10 years ago by usul

  • Milestone set to version 0.5.1

I know this problem, in our city we have 2-3 streetnames that are in use for different streets. One example is the Schulstraße, that is present in 3 districts.

I see different approaches to solve this issue: *distinguish streets by postal_code *distinguish streets by distance

It's not that easy, because as you said already, a single road can be spitted into several segments, that can be interrupted by segments which don't have the name=* tag.(for example to stop cars as here at the Friedhofsweg). The postal_code isn't everywhere present and might cause wrong assignments if no code available. The distance might be a better choice to cluster all way segments together?

comment:3 Changed 10 years ago by sleske

Good point about a single street still being interrupted. However, I believe for now we could live with occasionally splitting a street incorrectly, so I'd start with just considering sets of connected ways with the same name as "one street". Also factoring in distance would be even better, but also more complex.

The postcode is a good idea too, but coverage in OSM is probably not sufficient right now (plus, there are countries without postcodes).

comment:4 Changed 5 years ago by

  • Milestone changed from version 0.5.1 to version 0.5.2

This ticket was pushed back in order to bring 0.5.1 out soon.

comment:5 Changed 4 years ago by

  • Milestone changed from version 0.5.2 to version 0.6.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.