Modify ↓
#9287 closed enhancement (wontfix)
render surface=grass like landuse=grass
| Reported by: | mkoniecz | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Internal mappaint style | Version: | |
| Keywords: | Cc: |
Description
landuse=grass is frequently misused for tagging surfaces that are grass but belong to other landuses (residential, railway, highway etc).
Areas with surface=grass makes far more sense in situation like this.
Attachments (0)
Change History (4)
comment:1 by , 12 years ago
| Component: | Core imagery → Internal mappaint style |
|---|
comment:4 by , 12 years ago
surface=grass might be ok but you missed landcover=grass.
We could think about supporting landcover (Taginfo).
Note:
See TracTickets
for help on using tickets.



First of all, rendering has nothing to do with JOSM (except the internal rendering style). So this task should be addressed to the rendering styles of the map(s) instead. Be careful not mapping for the renderer.
But never the less, does it make sense to render the surface? On a map I want normally to see the function of an area and not something which looks similar to an aerial image.
Is it useful, when I have a leisure=pitch & sport=soccer rendered in different styles depending of the surface (sand, grass, tartan, ...)?
Is it useful to have different areas rendered the same way depending on surface? Assume different areas with leisure=pitch, amenity=parking or landuse=residential and all these areas are looking the same, because they all have surface=grass!