#10689 closed enhancement (invalid)
Veraltete protected Vorlage in josm?
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description (last modified by )
Bin gerade über ein Naturschutzgebiet bei uns in der Gegend gestolpert.
Das wiki sagt, protect_id ist deprecated
Key:protect_id
Stattdessen gibt es den neuen key protect_class
Key:protect_class
Vielleicht bitte einmal in josm die vorgeschlagenen keys überprüfen und eventuell anpassen.
Danke und viele Grüße
Olli
Attachments (0)
Change History (7)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Description: | modified (diff) |
---|
comment:3 by , 10 years ago
Maybe it is no preset, just let me show you, what i did.
I added a node / an area and then wanted to add "protected.." to this area.
When pressing the first two letters "pr..", josm suggests me protect_class then.
Here is a screenshot at dropbox
https://www.dropbox.com/s/177gk8uixt3gw69/josm_pr.png?dl=0
Olli
follow-up: 7 comment:4 by , 10 years ago
The autocompletion uses not only the tags defined in presets but also all the tags used in the downloaded data. So in your case there was probably an object which was tagged with protectet_class=*
in the osm data you downloaded.
comment:6 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:7 by , 10 years ago
Replying to Klumbumbus:
The autocompletion uses not only the tags defined in presets but also all the tags used in the downloaded data. So in your case there was probably an object which was tagged with
protectet_class=*
in the osm data you downloaded.
Another reason could be an external preset which includes the tag.
Do not know where you got the information from but there is no
protect*=*
key at all in the defaultpresets.protect_id=*
(auto fix) ?boundary=protected_area
(wiki) seem to be in use but we do not have a preset.