Opened 8 years ago

Closed 4 years ago

#516 closed defect/bug (fixed)

Searching streets

Reported by: gnixdorf Owned by: KaZeR
Priority: major Milestone: version 0.2.1
Component: core Version: git master
Severity: Keywords:


  • using svn Version 08.12.2009 with linux
  • found Berlin in City search dialog
  • NO streets available in Street search dialog

What is wrong?

Same story on smartphone with newest wince build.

Change History (7)

comment:1 Changed 8 years ago by

This is the known "is_in" problem with OpenStreetMaps?. If you take the osm file, open it in an editor and look for a street you are searching, you'll notice there is no '<tag k="is_in..." />' what makes it difficult to determine to which town a street belongs. This is described here.

comment:2 Changed 8 years ago by

Sorry, I provided a wrong link, here is the right one Search for my town works, but I can't find my street

comment:3 Changed 8 years ago by gnixdorf

Please have a look at the extract from the osm file. Biesdorf-Nord is a part of Berlin, the "is_in" tag is set. The Street Maisweg will be found, Weizenweg not. Both haven't the "is_in" tag.

By the way, in the navit version from 08.11.2009 both streets where found.

<node id="29885013" version="10" timestamp="2009-10-13T07:55:02Z" uid="115651" user="Konrad Aust" changeset="2832945" lat="52.5197998" lon="13.5601933">

<tag k="is_in" v="Berlin,Bundesrepublik Deutschland,Europe"/> <tag k="name" v="Biesdorf-Nord"/> <tag k="place" v="hamlet"/> <tag k="postal_code" v="12683"/>


<way id="8778859" version="6" timestamp="2009-08-09T11:18:09Z" uid="6669" user="Elwood" changeset="2083677">

<nd ref="68094660"/> <nd ref="68094736"/> <nd ref="115539737"/> <nd ref="68094702"/> <nd ref="68094768"/> <nd ref="63158515"/> <nd ref="63158628"/> <nd ref="63158524"/> <nd ref="63158502"/> <nd ref="61700607"/> <tag k="highway" v="residential"/> <tag k="maxspeed" v="30"/> <tag k="name" v="Maisweg"/> <tag k="postal_code" v="12683"/>


<way id="8778855" version="5" timestamp="2009-08-09T11:18:02Z" uid="6669" user="Elwood" changeset="2083677">

<nd ref="68094727"/> <nd ref="68094690"/> <nd ref="63158495"/> <nd ref="63158625"/> <nd ref="63158502"/> <nd ref="61724971"/> <tag k="highway" v="residential"/> <tag k="maxspeed" v="30"/> <tag k="name" v="Weizenweg"/> <tag k="postal_code" v="12683"/>


comment:4 Changed 8 years ago by

Mhm ok I think I misunderstood the way Navit is using to search for the streets in a town. On the Wiki page it is stated "the shape of the town is guessed". I haven't found the code doing this yet (I'm just a user myself ;) ).

Question at the developers: As you see in the excerpt of Biesdorf the "postal_code" tag is availlable. I took a look at the Berlin OSM map and it seems this tag is used quite often (at least here in Germany). I also took a look at other countries and must admit they are not using this tag often enough. Perhaps multiple ways of street finding could be implemented depending on the information availlable?

comment:5 Changed 8 years ago by

Does Navit use boundary (multi)polygons from OSM to determine the city a street belongs to yet? Admin-level=6 relations should be the most accurate way of determining the town/city any street belongs to where the data exists. Unfortunately supporting that is a bit of a beast as far as I can tell, so I guess not many Software support that yet. So far I have only really come across Nominatim ( ) that supports it, but it does work quite well there.

It would be useful if there were a pre-processor that could be used across all the different OSM projects that automatically tagged all streets with the is_in tag based on the various different methods of determining this data.

comment:6 Changed 7 years ago by kazer

  • Milestone set to version 0.2.1

comment:7 Changed 4 years ago by usul

  • Resolution set to fixed
  • Status changed from new to closed

Thanks due to heavy development within Navit (and on OSM of course, too). This naming hierachy issues had been fixed very well. I tested Berlin and worked fine to list all the streets as soon as you enter first chars.

I close the ticket

Note: See TracTickets for help on using tickets.