[mkgmap-dev] housenumbers and addr:interpolationFrom GerdP gpetermann_muenchen at hotmail.com on Mon Dec 1 21:43:15 GMT 2014
Hi WanMil, I agree that we should not support undocumented tagging. The question for me is whether the combination of type=associatedStreet and members with role=house whch have the addr:interpolation=* tag is documented. I fear the wiki is not clear about this. Regarding the normal use of addr:interpolation: I'll add some code to check if the evaluation is useful. I think it will improve results when the nodes of the way have no addr:street tag. The tag value in the addr:interpolation would also be interesting when it is a number, e.g. a value 3 in combination with housenumbers 2 and 20 mean 2,5,8,11,14,17,20, while a value 2 means even. I have no idea why someone would use that with numbers like 18, so maybe all the data using numbers is wrong. Gerd WanMil wrote > Hi Gerd, hi Andrzej, > > yes, up to now mkgmap collects all elements (pois and polygons) tagged > with addr:housenumber and mkgmap:street (which need to be set by the > style). The elements are afterwards assigned to the nearby street with > the same name. Elements more far away than 500m (?) are discarded. > The street is then divided into segments and mkgmap tries to find the > housenumbers at both ends and both sides of the segments. Additionally > it checks if all housenumbers on one side of the segment are > even/odd/both. > > Relations like associatedStreet and addr:interpolation were not > implemented by me because the quality was very very bad on the time of > my implementation. Most useful addr:interpolation lines did have a > start/stop point with adequate tagging (addr:housenumber and > addr:street) so there wouldn't have been any quality gain by supporting > it. > > Now there might have been changes in the tagging quality. Although I > would recommend to check that first. I strongly recommend to only > support taggings how they are documented in the wiki. Otherwise mkgmap > would support bad tagging which I think is not helpful at all. > > WanMil > >> Hi Gerd, >> >> isn't it a direct fit for Garmin format? >> >> I don't know details, but I assume that cgpsmapper format is very >> straight description of internal structure of img. My understanding is >> that if you assign house numbers to two consecutive junctions, then GPS >> will interpolate addresses between these junctions. Cgpsmapper offer >> possibility to define different numbers for both sides of the road and >> settings like even/odd/both, which describe how interpolation should be >> computed. I guess mkgamp already has similar settings hidden somewhere >> in algorithms. >> > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at .org > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- View this message in context: http://gis.19327.n5.nabble.com/housenumbers-and-addr-interpolation-tp5825987p5826020.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
- Previous message: [mkgmap-dev] housenumbers and addr:interpolation
- Next message: [mkgmap-dev] [Patch v2] evaluate type=associatedStreet
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list