Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#13953 closed defect (fixed)

lockable=no instead of lock=no

Reported by: geozeisig Owned by: team
Priority: normal Milestone: 16.12
Component: Internal preset Version:
Keywords: template_report Cc:


What steps will reproduce the problem?

Kartiert man einen Jagdanstand amenity=hunting_stand wird ein Formular geöffnet in unter anderem Schloss ausgewählt werden kann.

What is the expected result?

Durch Auswahl von Schloss sollte lockable=yes oder lockable=no getaggt werden.

What happens instead?

Es wird aber lock=yes bzw lock=no erzeugt. Mit lock=yes wird aber schon eine Schleuse lock=yes getaggt. Siehe auch Wiki hunting_stand

Please provide any additional information below. Attach a screenshot if possible.

Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-06-21 01:29:31 +0200 (Tue, 21 Jun 2016)
Build-Date:2016-06-21 01:33:29
Relative:URL: ^/trunk

Identification: JOSM/1.5 (10448 de) Windows 7 32-Bit
Memory Usage: 148 MB / 494 MB (21 MB allocated, but free)
Java version: 1.8.0_111-b14, Oracle Corporation, Java HotSpot(TM) Client VM
Dataset consistency test: No problems found

- OpeningHoursEditor (32583)
- PicLayer (32495)
- buildings_tools (32639)
- reltoolbox (32639)
- undelete (32584)
- utilsplugin2 (32584)

Tagging presets:

Map paint styles:

Last errors/warnings:
- W: Datei <josm.cache>\tiles\ kann nicht gelöscht werden
- W: Datei <josm.cache>\tiles\TMS_INDEX_v2.key kann nicht gelöscht werden
- W: Datei <josm.cache>\tiles\ kann nicht gelöscht werden
- W: Old style SideButton usage for action$UploadAction@10f9df7
- W: Old style SideButton usage for action$CancelAction@18a3d13

Attachments (0)

Change History (7)

comment:1 Changed 7 years ago by Klumbumbus

Component: CoreInternal preset
Milestone: 16.11

It was obviously based on osm wiki which proposed lock=yes until march 2015

comment:2 Changed 7 years ago by skyper

A validator rule with autofix would be useful to change this once lockable is accepted as there are more than 5000 combinations of amenity=hunting_stand and lock=yes according to taginfo.

comment:3 Changed 7 years ago by Klumbumbus

In 11263/josm:

see #13953 - deprecate lock in favor of lockable for amenity=hunting_stand

comment:4 Changed 7 years ago by Klumbumbus

I will add a lock=yes checkbox to teh river and canal presets, but I wait to trigger a retranslation.

comment:5 Changed 7 years ago by Klumbumbus

In 11280/josm:

see #13953 - add lock checkbox to canal and river preset, move name out of optional part of canal, river and stream presets, remove undocumented height values for hunting_stands

comment:6 Changed 7 years ago by Klumbumbus

Resolution: fixed
Status: newclosed

comment:7 Changed 7 years ago by Don-vip

Milestone: 16.1116.12

Milestone renamed

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.