Hi Gerd,

i try this and i think, that looks good (only a quick check). It shows the name of the suburb and/or town with "," seperated if both is set.

landuse=residential & name!=* & mkgmap:admin_level10=* {set Ortsteil='${mkgmap:admin_level10}'}
landuse=residential & name!=* & mkgmap:admin_level9=*  {set Ortsteil='${mkgmap:admin_level9}'}

landuse=residential & name!=* & mkgmap:admin_level8=*  {set Kreis='${Kreis} ${mkgmap:admin_level8}' | '${mkgmap:admin_level8}'}
landuse=residential & name!=* & mkgmap:admin_level7=*  {set Kreis='${Kreis} ${mkgmap:admin_level7}' | '${mkgmap:admin_level7}'}
landuse=residential & name!=* & mkgmap:admin_level6=*  {set Kreis='${Kreis} ${mkgmap:admin_level6}' | '${mkgmap:admin_level6}'}

landuse=residential & name!=* & Ortsteil=*    {set PolyName='${Ortsteil}'}
landuse=residential & name!=* & Kreis=*        {set PolyName='${Kreis}'}
landuse=residential & name!=* & Ortsteil=*    & Kreis=*        {set PolyName='${Ortsteil},${Kreis}'}

PolyName=* { name '${PolyName}' }

I´m not sure, if a logic is furthermore nessecary.

Thank you for this good idea!

Arndt

Gerd Petermann <GPetermann_muenchen@hotmail.com> hat am 19. Oktober 2017 um 06:46 geschrieben:

Hi Arndt,

one simple solution to set a name would be to use something like
landuse=residential & name!=* & mkgmap:admin_level10=* { name '${mkgmap:admin_level10=*}'}
landuse=residential & name!=* & mkgmap:admin_level9=* { name '${mkgmap:admin_level9=*}'}
landuse=residential & name!=* & mkgmap:admin_level8=* { name '${mkgmap:admin_level8=*}'}
...

If we add logic to check if a place node can be found within a residential area I see some problems:
1) A quick search showed that most residential areas don't contain any place nodes
2) Many place nodes are not inside of any landuse area, e.g. https://www.openstreetmap.org/node/340983656 or
https://www.openstreetmap.org/node/3609029156

So I think we would need a different logic, e.g. mkgmap could set a tag with the name of the closest place node.
We already have a similar logic for the handling of the --location-autofill=nearest option, but that is now only used for points,
not for polygons. The option also has some difficulties:
nearest The city/hamlet points that are closest to the element are used
to assign the missing address fields. Beware that cities located
in the same tile are used only. So the results close to a tile
border have less quality.

For the beginning, I'd say that closest would mean "smallest distance to the point that is calculated as the average of
all nodes of the polygon", like the --add-pois-to-areas option does when no special node is found that sets the position.
So, maybe a new option --location-auto-name-area could trigger this.

Comments?

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Arndt Röhrig <arndt@speichenkarte.de>
Gesendet: Mittwoch, 18. Oktober 2017 16:48:52
An: Development list for mkgmap
Betreff: [mkgmap-dev] name for residential

Hi @all,

today i´ve learnd, that name-tags at residential-lines not so good.

https://forum.openstreetmap.org/viewtopic.php?id=56873&p=27 #655 - #668

In BaseCamp ist it usefull, to klick on a residential and see the name of the town. (as in Garmin-Maps)

Is it possible, that mkgmap gives the residentiel a name (if none is there). Perhaps from a place-POI that is in the residential?

Hope you understand my strange englisch :)

Arndt

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev