Opened 6 years ago
Closed 6 years ago
#15515 closed enhancement (wontfix)
remove natural=fell preset
Reported by: | mkoniecz | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Internal preset | Version: | |
Keywords: | template_report natural fell | Cc: |
Description (last modified by )
What steps will reproduce the problem?
- create area
- select it
- start adding tag with key natural and value fell
What is the expected result?
natural=fell is not autocompleted
What happens instead?
natural=fell is in preset
Please provide any additional information below. Attach a screenshot if possible.
as part of https://github.com/gravitystorm/openstreetmap-carto/issues/545 I checked how natural=fell is used
Actual use of the tag for areas as of October 2017 includes different kinds of treeless areas, in particular areas vegetated primarily by grasses (Poaceae) which are commonly tagged as natural=grassland or landuse=meadow, areas mostly vegetated by dwarf scrubs which are more commonly tagged natural=heath, rain fed peat producing wetlands for which the established tagging is natural=wetland + wetland=bog and areas with very little or no vegetation which in most cases qualify as natural=scree or natural=bare_rock. When mapping preferably choose the tag that best and most precisely describes the specific setting you are looking at. Data users should not expect a particular type of surface or vegetation for areas tagged natural=fell.
from https://wiki.openstreetmap.org/wiki/Tag:natural%3Dfell appears to be a good description of the situation
Therefore I think that natural=fell usage should not be encouraged and I propose to remove it from presets
matching iD report: https://github.com/openstreetmap/iD/issues/4502
matching Vespucci report: https://github.com/simonpoole/beautified-JOSM-preset/issues/41
URL:http://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2017-10-30 23:58:23 +0100 (Mon, 30 Oct 2017) Build-Date:2017-10-31 02:33:18 Revision:13064 Relative:URL: ^/trunk Identification: JOSM/1.5 (13064 en) Linux Ubuntu 16.04.3 LTS Memory Usage: 428 MB / 871 MB (127 MB allocated, but free) Java version: 1.8.0_151-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: :0.0 1920x1080 Maximum Screen Size: 1920x1080 Dataset consistency test: No problems found Plugins: + OpeningHoursEditor (33185) + buildings_tools (33735) + lakewalker (33712) + reverter (33572) + undelete (33480) Map paint styles: - https://josm.openstreetmap.de/josmfile?page=Styles/AdvertisingStyle&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/MaxspeedIcons&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/LessObtrusiveNodes&zip=1 + ${HOME}/Documents/install_moje/josm_style_sidewalks/Styles_Sidewalks-style.mapcss + https://josm.openstreetmap.de/josmfile?page=Styles/NumberedWalkingNodeNetworks&zip=1 + https://josm.openstreetmap.de/josmfile?page=Styles/HU-HighlightHikingTrailSigns&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/Fixme&zip=1 + ${HOME}/Desktop/tmp/josmfile Validator rules: + ${HOME}/Documents/install_moje/josm_validator/josm.validator.mapcss Last errors/warnings: - W: Failed to load Mappaint styles from '${HOME}/Desktop/tmp/josmfile'. Exception was: java.io.FileNotFoundException: ${HOME}/Desktop/tmp/josmfile (No such file or directory) - E: java.io.FileNotFoundException: ${HOME}/Desktop/tmp/josmfile (No such file or directory) - W: Initializing map style ${HOME}/Desktop/tmp/josmfile completed in 2 ms (1 errors, 0 warnings) - W: No configuration settings found. Using hardcoded default values for all pools.
Attachments (0)
Change History (6)
comment:1 by , 6 years ago
Description: | modified (diff) |
---|
comment:2 by , 6 years ago
Description: | modified (diff) |
---|
comment:3 by , 6 years ago
comment:5 by , 6 years ago
Keywords: | natural fell added |
---|
comment:6 by , 6 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
That's not a one-man show. You change the wiki and based on this change ask the editors to remove an established tagging.
Sorry - even it would not be established for many years and use in large amounts this would be the wrong way.
Surprisingly, the tag is used worldwide, we can find it in areas where it probably shouldn't be used (Africa, South America, etc.)