Commit: r2485: Add simple housenumber handling for OSM data

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.

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@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

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@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Brilliant work ! As Felix said it works! I have my osm address numbers showing as labels on my Mapsource map and notice some interesting results. If a street number doesn't exist it will calculate its probable position, which in itself can be quite useful, as often only a few address numbers are available. It always defaults to the max or min number if the number is outside the scale given, ie if a street has numbers 10 to 30 , 120 will point 30 and 1 to 10. There is an issue if the houses are not regularly spaced or (as happens near me) the last house is not at the end of the road . In which case the pointing is fairly inaccurate, to say the least. However, what a superb tool you & Steve have created! Thanks -- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2485-Add-simple-housenumber-handling-... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Steve and Wanmil, great job! I have done a small test and the only errors were a few numbers with "?" (better skip them): java.lang.IllegalArgumentException: No housenumber: ? I also changed the LocatorConfig.xml,please add <country name="Nederland" abr="NLD" streetBeforeHousenumber="true" postalcodeBeforeCity="true"> <country name="België - Belgique" abr="BEL" streetBeforeHousenumber="true" postalcodeBeforeCity="true">


Steve and Wanmil, great job! I have done a small test and the only errors were a few numbers with "?" (better skip them): java.lang.IllegalArgumentException: No housenumber: ?
Housenumbers for OSM data are still under development so there may be some unwanted log messages. Of course I will remove them later on :-)
I also changed the LocatorConfig.xml,please add <country name="Nederland" abr="NLD" streetBeforeHousenumber="true" postalcodeBeforeCity="true"> <country name="België - Belgique" abr="BEL" streetBeforeHousenumber="true" postalcodeBeforeCity="true">
Thanks for the hint. Can you workout the LocatorConfig.xml and assign the correct format for the rest of countries? WanMil

Hi Wanmil,
Thanks for the hint. Can you workout the LocatorConfig.xml and assign the correct format for the rest of countries?
Not all the countries but I added some that were mentioned in the wiki. Don't know what is meant with regionOffset?

New housenumber preprocessor it a good way to detect bad addr:housenumber tag usage: http://paste.opensuse.org/view/raw/79865771 But output not have id and type of objects. Need more info in SERVE output, like a " node 12345667: No housenumber:" or way/relation.

Hi Maks, I've added the URL of the wrong element. Hope that helps. WanMil
New housenumber preprocessor it a good way to detect bad addr:housenumber tag usage:
http://paste.opensuse.org/view/raw/79865771
But output not have id and type of objects. Need more info in SERVE output, like a " node 12345667: No housenumber:" or way/relation.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Thanks, it looks good. But with the - add-pois-to-areas all errors duplicated real way and generated node: SEVERE (HousenumberGenerator): custom/63240045.osm.pbf: java.lang.IllegalArgumentException: No housenumber ( http://www.openstreetmap.org/browse/node/4611686018429891871): Pargi SEVERE (HousenumberGenerator): custom/63240045.osm.pbf: java.lang.IllegalArgumentException: No housenumber ( http://www.openstreetmap.org/browse/way/116529512): Pargi SEVERE (HousenumberGenerator): custom/63240046.osm.pbf: java.lang.IllegalArgumentException: No housenumber ( http://www.openstreetmap.org/browse/node/4611686018429938775): undefined SEVERE (HousenumberGenerator): custom/63240046.osm.pbf: java.lang.IllegalArgumentException: No housenumber ( http://www.openstreetmap.org/browse/way/145609370): undefined 2013/2/20 WanMil <wmgcnfg@web.de>
Hi Maks,
I've added the URL of the wrong element. Hope that helps.
WanMil

Thanks Minko! The regionOffset gives the n-th element of is_in tag that defines the region. But the is_in tag is used very inconsistently so it's only a hint and has only an effect if the location-autofill=is_in is used. WanMil
Hi Wanmil,
Thanks for the hint. Can you workout the LocatorConfig.xml and assign the correct format for the rest of countries?
Not all the countries but I added some that were mentioned in the wiki. Don't know what is meant with regionOffset?
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Brilliant work ! As Felix said it works!
Thanks!
I have my osm address numbers showing as labels on my Mapsource map and notice some interesting results. If a street number doesn't exist it will calculate its probable position, which in itself can be quite useful, as often only a few address numbers are available. It always defaults to the max or min number if the number is outside the scale given, ie if a street has numbers 10 to 30 , 120 will point 30 and 1 to 10.
There is an issue if the houses are not regularly spaced or (as happens near me) the last house is not at the end of the road . In which case the pointing is fairly inaccurate, to say the least. However, what a superb tool you & Steve have created! Thanks
In the Garmin map format not each number is referenced but a routable segement of a street is assigned with min/max values for each side of the street (left/right) and the information if the numbers are even/odd/both. I think that explains most of your remarks? Have fun! WanMil
participants (6)
-
Felix Hartmann
-
Maks Vasilev
-
Minko
-
n Willink
-
svn commit
-
WanMil