Hi Florian, what would be the solution for this case? Should mkgmap change the name to Bosfeld for the part of "Bosfelder Weg" that runs through Bosfeld ? That would mean something like roate the four labels so that the last is lost and put Bosfeld as first label. I seem to remember similar cases in other hamlets, so maybe we can use this as a general rule? Gerd Florian Lohoff-2 wrote
On Sat, Apr 04, 2015 at 03:03:47PM +0200, Gerd Petermann wrote:
Hi all,
some month ago we discussed the idea to implement addr:place support. It it assumed that an address has addr:housenumber and either addr:place or addr:street. Up to now those with addr:place are ignored. It is also assumed that the addr:place tag is used in hamlets and small villages and that the roads in such a hamlet have no name.
I've coded the following simple approach: For each element (node/way) with addr:housenumber=* and addr:place=* and addr:street!=* search the nearest routable way that has no name (mkgmap:street!=*) If the closest road is within a given range (150m), store the place name as a possible road name. Perform a 2nd search to find also the closest road with a name or ref. If we find exactly one possible name for the road, use it.
As a small example - I have a small Hamlet here called Bosfeld beloning to a town called Rheda-Wiedenbrück with a suburb of Rheda.
The main street through Bosfeld is called "Bosfelder Weg" although all adresses are "Bosfeld 1" through 60 or something.
So mkgmap:street!=* will be wrong in finding the next routable way.
Flo -- Florian Lohoff
f@
We need to self-defense - GnuPG/PGP enable your email today!
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
signature.asc (845 bytes) <http://gis.19327.n5.nabble.com/attachment/5839774/0/signature.asc>;
-- View this message in context: http://gis.19327.n5.nabble.com/addr-place-support-tp5839721p5839777.html Sent from the Mkgmap Development mailing list archive at Nabble.com.