#21069 closed enhancement (fixed)
[Patch] "Role 'section' is not among expected values 'device/from/to/force'" while creating average_speed enforcement
Reported by: | Talkless | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 21.06 |
Component: | Internal preset | Version: | tested |
Keywords: | validator enforcement relation member role | Cc: | Talkless |
Description
I get complain about "section" field for these relations using JOSM 17919 on Debian Sid:
https://www.openstreetmap.org/relation/12921878
https://www.openstreetmap.org/relation/12921877
There's "section" key for "average_speed" enforcement:
JOSM 17919 on Debian Sid.
https://wiki.openstreetmap.org/wiki/Relation:enforcement#Members
Attachments (2)
Change History (22)
comment:1 by , 3 years ago
Component: | Core validator → Internal preset |
---|---|
Keywords: | validator enforment relation member role added |
Version: | → tested |
comment:2 by , 3 years ago
Keywords: | enforcement added; enforment removed |
---|
comment:3 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 3 years ago
Milestone: | → 21.06 |
---|---|
Type: | defect → enhancement |
by , 3 years ago
Attachment: | josm_21069_v2.patch added |
---|
patch version 2 with correct order of values and additional keys
comment:8 by , 3 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Summary: | "Role 'section' is not among expected values 'device/from/to/force'" while creating average_speed enforcement → [Patch] "Role 'section' is not among expected values 'device/from/to/force'" while creating average_speed enforcement |
comment:10 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:12 by , 3 years ago
Looking at the examples, member_expression
might be useful:
… <roles> <role key="device" text="location of enforcement device" requisite="required" type="node,way,closedway" member_expression="highway=speed_camera" /> <role key="from" text="node on way where enforcement starts" requisite="required" type="node" /> <role key="to" text="where enforcement ends" requisite="optional" type="node" /> <role key="section" text="ways forming the section of messurement" requisite="required" type="way" member_expression="highway" /> </roles>
follow-up: 14 comment:13 by , 3 years ago
highway=speed_camera is a different tagging method and not needed for the enforcement relation. But we can add the member expression for the section role.
follow-up: 16 comment:14 by , 3 years ago
Replying to Klumbumbus:
highway=speed_camera is a different tagging method and not needed for the enforcement relation. But we can add the member expression for the section role.
Just wonder how the "device" should be tagged then, but well, I am fine with only the expression for "section".
comment:16 by , 3 years ago
follow-up: 19 comment:17 by , 3 years ago
Maybe, it is worth thinking about splitting all enforcement relations into own presets for each enforcement=*
by creating one more level (subgroup) in the menu. Common parts, like roles, could still use chunks. New ticket?
follow-up: 20 comment:19 by , 3 years ago
comment:20 by , 3 years ago
Replying to Don-vip:
In 17958/josm:
Thank you.
Replying to Don-vip:
Replying to skyper:
New ticket?
Yes please. Working on the 21.06 release right now.
Good to know that there will be release this week. Thanks for your work.
See #21081 for the new ticket.
In 17948/josm: