Quote from: voldapet on March 23, 2023, 12:05:27@karlchick
Point 8
Do you want to render a surface type in the map? Or you want to use a surface as fallback if tracktype isn't defined? What surface type you'd required? https://wiki.openstreetmap.org/wiki/Key:surface
Point 9
I'm sorry, but are you really sure that the contours in <Z12 have any practical benefit for hikers/bikers?
Point 12
The `lm_landuse` item should contain a combination of the original `landuse=residential` and the custom areas generated from the building location. IIRC, there is a logic where small areas are removed from the dataset. Frankly, I would prefer to avoid adding `landuse=residential` because of duplication of data. I'll check (later) the simplification factor and also the filtration of small areas...
Point 8
If you want to align with OAM surfaces, that would make our lives as theme creators alot simpler, here are the OAM tag mapping settings:
<osm-tag key='surface' value='paved' equivalent-values='hard' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='asphalt' equivalent-values='concrete,cement,metal_grid,brick,chipseal,interlock,plastic,granite' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='compacted' equivalent-values='fine_gravel' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='smooth_paved' equivalent-values='concrete:plates,concrete:lanes,paving_stones,paving_stones:30,paving_stones:20,bricks,cement,metal,wood' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='rough_paved' equivalent-values='unhewn_cobblestone,cobblestone,stone,grass_paver,cobblestone:flattened,sett' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='gravel' equivalent-values='pebblestone,woodchips' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='raw' equivalent-values='ground,dirt,grass,sand,earth,mud,clay,saltrock,stone,dirt/sand,soil,trail' renderable='false' zoom-appear='8' />
<osm-tag key='surface' value='winter' equivalent-values='ice,snow' renderable='false' />
<osm-tag key='surface' value='unpaved' equivalent-values='unpaved_minor' renderable='false' zoom-appear='8' />
Point 9
I think having the major and then major and medium gradually introduced earlier provides the following benefits:
1. You can visualise the landscape over a wider area, see how hills/mountains lie with respect to other landscape features like lakes and roads etc.
2. The map doesn't suddenly become very blank.
I can understand how this might have been desirable with older phones with limited resources, but most modern phones now easily cope with this in OAM maps.
Point 12
I dispute that landuse=residential is duplication, the lm_landuse tag is not the same ways/shapes. I really would prefer to use landuse=residential instead of lm_landuse since it matches OSM and also matches the other corresponding OSm tagged ways, e.g. schools, grass, parking etc. I find that lm_landuse=residential often cuts across a lot of other ways, or is completely missing for large parts of villages, or includes areas that are not residential. E.g. see attached which compares LoMap and OAM residential areas (beige areas).