[mkgmap-dev] Commit: r2485: Add simple housenumber handling for OSM data --
From WanMil wmgcnfg at web.de on Mon Feb 18 19:58:40 GMT 2013
Hi Felix, I committed a change that the first number in the housenumber string is accepted. So no special evaluation of "24-28" or "24,28" or "24/28". In all cases the 24 is used. I think that's the best way for now. Maybe some more intelligent solutions can be added later on. WanMil > First of all, great it's working including popups for the housenumber. > However before tackling more means of how addresses could be inside OSM > without addr:housenumber and add:street, it would be great to have the > following nomination errors cleaned up: > > SEVERE (HousenumberGenerator): c:\openmtbmap\maps\63650031.osm.pbf: > java.lang.IllegalArgumentException: No housenumber: 11B/2 > && SEVERE (HousenumberGenerator): c:\openmtbmap\maps\63650031.osm.pbf: > java.lang.IllegalArgumentException: No housenumber: 3-5 > > Could theese be solved? > I got a long list of them.... > > Mostly it's "-" > or "/" > > both is very common in Austria. > > As for / in Austria this can be safely dropped, as it denotes the > number of a floor or a flat. > about - as in 3-5 I'm not sure what is the best way to handle them. I > would say if 3-5 ain't possible, then make both a 3 and a 5 as address. > (not 4, as that will be on the other side of the street). > > > Then there are some of the following: > SEVERE (HousenumberGenerator): c:\openmtbmap\maps\63650031.osm.pbf: > java.lang.IllegalArgumentException: No housenumber: 25 Stiege 3 > > Stiege needs to be treated the same as "/", meaning drop it and only use > the first value. > Yes I know, probably worldwide they are not very common, but in Vienna > we got thousands of numbered flats already. So there is not only the > house address, but also a number for each flat in the house. > Dunno how to tell them apart. > > SEVERE (HousenumberGenerator): c:\openmtbmap\maps\63650031.osm.pbf: > java.lang.IllegalArgumentException: No housenumber: 37,39 > should be treated as searchable for both 37 and 39. Same for 37;39 > > > > Then there are even some crazy ones like: > SEVERE (HousenumberGenerator): c:\openmtbmap\maps\63650031.osm.pbf: > java.lang.IllegalArgumentException: No housenumber: 153-155/1 > or SEVERE (HousenumberGenerator): c:\openmtbmap\maps\63650031.osm.pbf: > java.lang.IllegalArgumentException: No housenumber: 153-155/2 > > In that case the official housenumber would be really 153-155/1, but as > a search result both 153 and 155 needs to be possible. > > On 17.02.2013 14:25, svn commit wrote: >> Version 2485 was committed by wanmil on Sun, 17 Feb 2013 >> >> Add simple housenumber handling for OSM data >> >> Housenumbers that are tagged with addr:housenumber and add:street are now applied. It can be enabled with the undocumented parameter --x-housenumbers. It's not yet an official parameter because it handles only a small subset of housenumbers. >> _______________________________________________ >> mkgmap-dev mailing list >> mkgmap-dev at lists.mkgmap.org.uk >> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >
- Previous message: [mkgmap-dev] Commit: r2485: Add simple housenumber handling for OSM data --
- Next message: [mkgmap-dev] Commit: r2485: Add simple housenumber handling for OSM data
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list