Examine individual changes

Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to navigation Jump to search

This page allows you to examine the variables generated by the Abuse Filter for an individual change.

Variables generated for this change

VariableValue
Edit count of the user (user_editcount)
654
Name of the user account (user_name)
'Wielandb'
Whether or not a user is editing through the mobile interface (user_mobile)
false
Page ID (page_id)
313381
Page namespace (page_namespace)
3000
Page title (without namespace) (page_title)
'Key:opened='
Full page title (page_prefixedtitle)
'Proposal:Key:opened='
Action (action)
'edit'
Edit summary/reason (summary)
'End Voting'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Proposal page | name = Key:open | user = | key = open | value = | type = {{IconNode}} | definition = Whether a feature is normally open | appearance = none | status = Voting | draftStartDate = 2024-01-23 | rfcStartDate = 2024-03-19 | voteStartDate = 2024-04-22 | voteEndDate = 2024-05-07 | tagging = {{Tag|open|*}}, {{Tag|opening|*}} | users = {{u|Wielandb}} on behalf of {{u|OPENER}} }} {{Ambox|type=caution|text=The proposal initially started with the key {{Tag|opened}} to follow the existing {{Tag|locked}} tag. However we realized that "opened" is only used as a verb or when something has recently been opened and therefore changed it to {{Tag|open}}. See: * https://wiki.openstreetmap.org/wiki/Proposal_talk:Key:opened%3D#'opened'_is_the_wrong_word * https://dictionary.cambridge.org/grammar/british-grammar/open-or-opened * https://english.stackexchange.com/questions/141547/opened-vs-open}} ==Proposal== <!-- A short statement of what you propose, including a list of what tag(s) are being proposed to be added, changed, or deprecated --> This proposal wants to establish the key {{Tag|open}}. Similar to the key {{Tag|locked}}, {{Tag|open}} describes whether an object that can be opened or closed is usually open. This applies to objects such as gates (e.g. {{Key|barrier|gate}}) and especially doors ({{Key|door}}). Additionally, we propose to reuse {{Key|opening}} to determine the clearance width of an object tagged with {{Tag|open|partial}}. <!-- Which Database Elements (nodes, ways, areas, relations) each of the tags can be used on could be included here or under the Tagging heading, or both. --> ==Rationale== <!-- Explanation of why the proposal is needed, and why you chose the specific key and value of the tag. Compare with similar tags or previous proposals, if relevant. Consider significance and potential uses of the data.--> OSM currently only states the existence of doors, but not if they are open or closed. There is no doubt that most doors in reality can be opened or closed at any time. So their opening state is mostly temporary and should not be mapped in OSM. However there are doors or gates at public places (e.g. shopping centres, train stations, libraries, parks, universities etc.) that are technically doors or gates but often not perceived as such because they are constantly open. Currently this cannot be represented sufficiently in OSM. Either the doors are not mapped which is wrong (because OSM maps physically present features) or the doors are mapped but then it is not clear that they do not form a barrier. To give an example: Interior doors at train stations and airports are in control of the the operators and constantly open so passengers can easily pass through. They are usually fixated with a door holder or door stay to prevent them from accidentally snap shutting or being closed by unauthorized people. The doors are only closed in exceptional scenarios like when a fire is broken out or on construction work. The same logic applies to barriers like arm barriers ({{Tag|barrier|lift_gate}}) on streets and other features that can be opened / closed. The information whether something is open by default helps to know if e.g. a door is easily passable. This is especially important for people with strollers, wheelchair users and cyclists. The information can also be used by routing engines to find more suitable / accessible routes. <!-- Keep the tag short while still being logical and descriptive enough to need little explanation. Avoid tag names which might cause confusion with a different tag. British English terms are preferred, when possible --> ==Tagging== <!-- A table, list, or set of subheadings explaining each tag: * Definition of the meaning of the tag and how it should be used * Elements tagged: nodes, ways, areas or relations? [if a feature is smaller than 5m by 5m it would usually be mapped only as a node] * Comparison with current tagging schemes (if applicable) * Additional tags used in combination (including existing tags) * When other tags should be used instead. -->{{Tag|open}} describes the "default state" of a feature that can be opened / closed either by hand or a mechanism. Default means the idle or passive state of the feature without / prior to any user interaction. Four values are proposed for the key {{Tag|open}}: * {{Tag|open|yes}} - Somehow open. Generic value, use a more specific value if possible. ** {{Tag|open|full}} - Completely open. For doors with multiple wings, all wings have to be fully open. ** {{Tag|open|partial}} - Only partially open. E.g. just one of several wings is open or one wing is just open to some extent. * {{Tag|open|no}} - Closed ('''default value'''). Needs to be opened by hand or a mechanism to pass through. This tag as well as its default value only applies to elements, which can be opened and closed. So for example it '''does not''' apply to elements tagged with: * {{Tag|door|no}} or {{Tag|door|revolving}} * barriers like {{Tag|barrier|entrance}}, {{Tag|barrier|turnstile}}, {{Tag|barrier|cycle_barrier}} etc. * {{Tag|automatic_door|continuous}} === Automatic doors === Tagging {{Tag|open}} on automatic doors ({{Tag|automatic_door}}) is of limited use, but still possible. It is mostly useful if the doors are out of order / deactivated. If tagged on operational automatic doors the default state is the state prior to any button press or motion sensor detection. === Clearance width of an open door === * For {{Tag|open|full}}, the key {{Tag|opening|:=}} can be omitted as it is already covered by {{Tag|maxwidth:physical}} (or sometimes other dimensional keys like {{Tag|door:width}} / {{Tag|width}} that describe the distance between the doorposts). * For {{Tag|open|partial}}, the key {{Tag|opening|:=}} is used to record the clearance width of the opening. === Why reusing the "opening" key? === [[File:Prtially open door dimensions.svg|thumb|Visualises the measurements of a permanently half-open double door]] * "opening" implicitly describes what should be measured in contrast to "width" or "maxwidth". * The term "opening" is linguistically connected to "open". * {{Tag|maxwidth:physical}} already describes the fully open clearance width of gates and doors, so it cannot be used. * {{Tag|opening|:=}} is already used to tag measurements of {{Tag|barrier|cycle_barrier}} clearance, which is similar to what is required here. The similarity becomes especially apparent for partially open sliding gates. === Conditional opening === If it is known that a feature is open at specific times or if it follows some other recurring pattern, use the {{Tag|*:conditional|}} suffix. For example: * If doors are open, but closed during winter, it can be recorded with {{Tag|open|yes}}; {{Tag|open|3=no @ (winter)|:=conditional}}. * If doors are only open during busy hours on Monday to Friday from 7am till 9am, it can be recorded with ({{Tag|open|no}}); {{Tag|open|3=yes @ (Mo-Fr 07:00-09:00)|:=conditional}}. === Relation between <code>open</code> and <code>locked</code> === * {{Tag|open|no}} just describes an object (e.g. door) that is normally closed, '''but not''' that it is impossible to open or disallowed to pass. * {{Tag|locked|yes}} implies {{Tag|open|no}}, while {{Tag|open|no}} '''does not''' imply {{Tag|locked|yes}} or {{Tag|access}}. === Local knowledge === We want to specify that the key {{Tag|open}} should only be used if you have sufficient local knowledge about the place so that you can make a reasonable judgement regarding the value. Do not just tag a value if you visited the place once. This is similar to keys like {{Tag|locked}} and {{Tag|seasonal}}. ==Examples== <!-- Examples of what elements should be tagged: real-world images, openstreetmap.org screenshots, links to OpenStreetMap elements that use the proposed tagging. -->{| class="wikitable" |+ !Image !Tagging !Description |- |[[File:Set of opened double doors inside Chemnitz Main Station.jpg|100x100px]] |{{Tag|indoor|door}} {{Tag|door|hinged}} {{Tag|open|full}} {{Tag|maxwidth:physical|2}} |Open door at a train station connecting the entrance hall to the platforms. The door is always fully open, so {{Tag|maxwidth:physical}} is sufficient. |- |[[File:Closed set of double doors at Chemnitz Main Station.jpg|110x110px]] |{{Tag|entrance|yes}} {{Tag|open|no}} {{Tag|maxwidth:physical||1.2}} |Closed door leading to the entrance hall of a train station. This may provide a challenge for wheelchair users. {{Tag|open|no}} is assumed if not explicitly tagged oherwise. |- |[[File:Set of double doors with one door open at Chemnitz Main Station.jpg|102x102px]] |{{Tag|entrance|yes}} {{Tag|open|partial}} ⁣{{Tag|opening|0.6|:=}} {{Tag|maxwidth:physical||1.2}} |Partially open door at a train station. While wheelchair users do not have to open the door, their wheelchair may not fit through. |- |[[File:Half-open sliding garage door.jpg|100x100px]] |{{Tag|barrier|gate}} {{Tag|open|partial}} {{Tag|opening||1.5}} {{Tag|maxwidth:physical||4}} |A sliding gate of a garage that is partially open. (Note that the image shows a private garage which in reality is probably not regularly open nor legally accessible) |- |[[File:Gate Apples Rosemoor.jpg|100x100px]] |{{Tag|barrier|gate}} {{Tag|open|full}} {{Tag|maxwidth:physical||2.2}} |Open gate at an orchard. The gate is always fully open, so {{Tag|maxwidth:physical}} is sufficient. |} ==Rendering== <!-- Optional rendering suggestion, if relevant -->No special rendering is suggested for general-purpose map styles such as carto. However, indoor map styles are encouraged to adopt specific icons for the different cases. ==Features/Pages affected== <!-- List of wiki pages that would be edited if the proposal is approved --> * {{Tag|open}} * {{Tag|opening}} * {{Tag|maxwidth:physical}} * {{Tag|indoor|door}} * {{Tag|door}} * {{Tag|entrance|yes}} * {{Tag|barrier}} ==External discussions== <!-- Links to mailing lists, other forums where this proposal has been discussed... --> * [https://lists.openstreetmap.org/pipermail/tagging/2024-March/067781.html Tagging mailing list] * [https://community.openstreetmap.org/t/rfc-feature-proposal-key-opened/110685 Forum announcement] ==Comments== <!-- There must be at least 2 weeks set aside for comment on the proposal. Do not go to a vote without addressing the comments and fixing any problems with the proposal. The wiki talk page is used for comments, it is linked from the proposal page for those unfamiliar with wikis. --> Please comment on the [[{{TALKPAGENAME}}|discussion page]]. == Voting == {{Proposed feature voting}} <!-- Cheat sheet: {{vote|yes}} OPTIONAL MESSAGE HERE --~~~~ {{vote|no}} YOUR REASONS HERE --~~~~ {{vote|abstain}} YOUR COMMENTS HERE --~~~~ Place your vote below, at the end of the list. --> {{vote|yes}} --[[User:Pelderson|Peter Elderson]] ([[User talk:Pelderson|talk]]) 13:31, 22 April 2024 (UTC) {{vote|yes}} —[[User:Dieterdreist|Dieterdreist]] ([[User talk:Dieterdreist|talk]]) 13:51, 22 April 2024 (UTC) {{vote|yes}} This gives a definition for an ATYL I was going to use anyway.--[[User:Sbre|Sbre]] ([[User talk:Sbre|talk]]) 13:56, 22 April 2024 (UTC) {{vote|no}} The door state {{tag|open|partial}} is also open. {{tag|opening}} is already there as {{tag|maxwidth:physical}}. See [https://wiki.openstreetmap.org/wiki/Proposal_talk:Key:opened%3D#Adding_opening_hours=*_to_the_door_may_be_more_specific_/_key_mixes_opened/closed-state_with_door_width this discussion]. Examples in the proposal use {{tag|maxwidth:physical}} for the {{tag|width}} of the door, but {{tag|maxwidth:physical}} applies here, as this proposal assumes the common door state is permanent enough to be mapped. --[[User:Fabi2|Fabi2]] ([[User talk:Fabi2|talk]]) 14:19, 22 April 2024 (UTC) {{vote|yes}} --[[User:Nielkrokodil|Nielkrokodil]] ([[User talk:Nielkrokodil|talk]]) 16:22, 22 April 2024 (UTC) {{vote|yes}} I think this is an essential information for wheelchair users. —[[User:Gymate|Gymate]] ([[User talk:Gymate|talk]]) 17:21, 22 April 2024 (UTC) {{vote|yes}} --[[User:Hypo808|Hypo808]] ([[User talk:Hypo808|talk]]) 13:16, 24 April 2024 (UTC) {{vote|yes}} This will be very useful for the default handling of barrier accessibility in routing engines. {{Tag|open|yes}} is more specific than {{Tag|access|yes}} here. This also allows more detailed travel time estimations at accessible barriers, i.e. whether you have to wait for the barrier to open or whether it is already open. --[[User:JeroenvanderGun|JeroenvanderGun]] ([[User talk:JeroenvanderGun|talk]]) 17:39, 24 April 2024 (UTC) {{vote|yes}} --[[User:Adiatmad|Adiatmad]] ([[User talk:Adiatmad|talk]]) 04:23, 25 April 2024 (UTC) {{vote|yes}} Having mapped lots of gates that are actually permanently open, this would be a very useful tag for routing and rendering. [[User:HellMap|HellMap]] ([[User talk:HellMap|talk]]) 11:00, 26 April 2024 (UTC) {{vote|no}} The subject of the proposal is important, but the proposal is not yet ready for voting. At least, two things should be added: (a) relation of the "open" tag to the "locked" tab ("locked" is missing in the examples) (b) tagging of closed doors that can be opened by pushing a button or by light barrier --[[User:Voschix|voschix]] ([[User talk:Voschix|talk]]) 17:06, 27 April 2024 (UTC) {{vote|yes}} --[[User:Tokada|Tokada]] ([[User talk:Tokada|talk]]) 12:22, 28 April 2024 (UTC) {{vote|yes}} --[[User:Michi2|Michi]] ([[User talk:Michi2|talk]]) 19:12, 28 April 2024 (UTC) {{vote|yes}} I think that, as of currently, the users that voted no aren't correct for the following reasons: (1) open=partial is meant to apply, as I understood it, to doors that can be partially opened to a fixed position and (2) I don't think that the open=* tag is meant to describe the way in which you open the doors themselves and I'm not convinced it should be that way. What makes me a little bit hesitant to vote yes is that it doesn't explicitly state the relation of this tag to the opening hours of the map feature on which the doors are. But I think this is more of a nitpick and can be assumed that open=yes, means that during the opening hours. --[[User:Comfyquiettree|comfyquiettree]] ([[User talk:Comfyquiettree|talk]]) 18:13, 5 May 2024 (UTC) {{vote|no}} I see no need for this feature --[[User:Chris66|chris66]] ([[User talk:Chris66|talk]]) 19:04, 5 May 2024 (UTC) {{vote|yes}} This feature will let me plan hiking routes based on the number of gates I need to wrangle. --[[User:Carnildo|Carnildo]] ([[User talk:Carnildo|talk]]) 19:29, 5 May 2024 (UTC) {{vote|yes}} --[[User:Nacktiv|Nacktiv]] ([[User talk:Nacktiv|talk]]) 22:08, 5 May 2024 (UTC) {{vote|yes}} --[[User:Uboot|Uboot]] ([[User talk:Uboot|talk]]) 07:16, 6 May 2024 (UTC) {{vote|yes}} --[[User:GanderPL|GanderPL]] ([[User talk:GanderPL|talk]]) 08:40, 6 May 2024 (UTC) {{vote|no}} Wherever a feature is closed or opened is in my opinion too temporary to be mapped in OSM, beyond this, is seems a tag too redundant to locked=* --[[User:Szydzio|Szydzio]] ([[User talk:Szydzio|talk]]) 11:59, 6 May 2024 (UTC) {{vote|no}} I don't see the point of this tag - whether a gate or door is open is temporary. They are open during the day and closed at night. It is not a permanent feature. After all, we don't know if the door is closed permanently or only at a given moment. [[User:Maro21|maro21]] 21:35, 6 May 2024 (UTC)'
New page wikitext, after the edit (new_wikitext)
'{{Proposal page | name = Key:open | user = | key = open | value = | type = {{IconNode}} | definition = Whether a feature is normally open | appearance = none | status = Post-Vote | draftStartDate = 2024-01-23 | rfcStartDate = 2024-03-19 | voteStartDate = 2024-04-22 | voteEndDate = 2024-05-07 | tagging = {{Tag|open|*}}, {{Tag|opening|*}} | users = {{u|Wielandb}} on behalf of {{u|OPENER}} }} {{Ambox|type=caution|text=The proposal initially started with the key {{Tag|opened}} to follow the existing {{Tag|locked}} tag. However we realized that "opened" is only used as a verb or when something has recently been opened and therefore changed it to {{Tag|open}}. See: * https://wiki.openstreetmap.org/wiki/Proposal_talk:Key:opened%3D#'opened'_is_the_wrong_word * https://dictionary.cambridge.org/grammar/british-grammar/open-or-opened * https://english.stackexchange.com/questions/141547/opened-vs-open}} ==Proposal== <!-- A short statement of what you propose, including a list of what tag(s) are being proposed to be added, changed, or deprecated --> This proposal wants to establish the key {{Tag|open}}. Similar to the key {{Tag|locked}}, {{Tag|open}} describes whether an object that can be opened or closed is usually open. This applies to objects such as gates (e.g. {{Key|barrier|gate}}) and especially doors ({{Key|door}}). Additionally, we propose to reuse {{Key|opening}} to determine the clearance width of an object tagged with {{Tag|open|partial}}. <!-- Which Database Elements (nodes, ways, areas, relations) each of the tags can be used on could be included here or under the Tagging heading, or both. --> ==Rationale== <!-- Explanation of why the proposal is needed, and why you chose the specific key and value of the tag. Compare with similar tags or previous proposals, if relevant. Consider significance and potential uses of the data.--> OSM currently only states the existence of doors, but not if they are open or closed. There is no doubt that most doors in reality can be opened or closed at any time. So their opening state is mostly temporary and should not be mapped in OSM. However there are doors or gates at public places (e.g. shopping centres, train stations, libraries, parks, universities etc.) that are technically doors or gates but often not perceived as such because they are constantly open. Currently this cannot be represented sufficiently in OSM. Either the doors are not mapped which is wrong (because OSM maps physically present features) or the doors are mapped but then it is not clear that they do not form a barrier. To give an example: Interior doors at train stations and airports are in control of the the operators and constantly open so passengers can easily pass through. They are usually fixated with a door holder or door stay to prevent them from accidentally snap shutting or being closed by unauthorized people. The doors are only closed in exceptional scenarios like when a fire is broken out or on construction work. The same logic applies to barriers like arm barriers ({{Tag|barrier|lift_gate}}) on streets and other features that can be opened / closed. The information whether something is open by default helps to know if e.g. a door is easily passable. This is especially important for people with strollers, wheelchair users and cyclists. The information can also be used by routing engines to find more suitable / accessible routes. <!-- Keep the tag short while still being logical and descriptive enough to need little explanation. Avoid tag names which might cause confusion with a different tag. British English terms are preferred, when possible --> ==Tagging== <!-- A table, list, or set of subheadings explaining each tag: * Definition of the meaning of the tag and how it should be used * Elements tagged: nodes, ways, areas or relations? [if a feature is smaller than 5m by 5m it would usually be mapped only as a node] * Comparison with current tagging schemes (if applicable) * Additional tags used in combination (including existing tags) * When other tags should be used instead. -->{{Tag|open}} describes the "default state" of a feature that can be opened / closed either by hand or a mechanism. Default means the idle or passive state of the feature without / prior to any user interaction. Four values are proposed for the key {{Tag|open}}: * {{Tag|open|yes}} - Somehow open. Generic value, use a more specific value if possible. ** {{Tag|open|full}} - Completely open. For doors with multiple wings, all wings have to be fully open. ** {{Tag|open|partial}} - Only partially open. E.g. just one of several wings is open or one wing is just open to some extent. * {{Tag|open|no}} - Closed ('''default value'''). Needs to be opened by hand or a mechanism to pass through. This tag as well as its default value only applies to elements, which can be opened and closed. So for example it '''does not''' apply to elements tagged with: * {{Tag|door|no}} or {{Tag|door|revolving}} * barriers like {{Tag|barrier|entrance}}, {{Tag|barrier|turnstile}}, {{Tag|barrier|cycle_barrier}} etc. * {{Tag|automatic_door|continuous}} === Automatic doors === Tagging {{Tag|open}} on automatic doors ({{Tag|automatic_door}}) is of limited use, but still possible. It is mostly useful if the doors are out of order / deactivated. If tagged on operational automatic doors the default state is the state prior to any button press or motion sensor detection. === Clearance width of an open door === * For {{Tag|open|full}}, the key {{Tag|opening|:=}} can be omitted as it is already covered by {{Tag|maxwidth:physical}} (or sometimes other dimensional keys like {{Tag|door:width}} / {{Tag|width}} that describe the distance between the doorposts). * For {{Tag|open|partial}}, the key {{Tag|opening|:=}} is used to record the clearance width of the opening. === Why reusing the "opening" key? === [[File:Prtially open door dimensions.svg|thumb|Visualises the measurements of a permanently half-open double door]] * "opening" implicitly describes what should be measured in contrast to "width" or "maxwidth". * The term "opening" is linguistically connected to "open". * {{Tag|maxwidth:physical}} already describes the fully open clearance width of gates and doors, so it cannot be used. * {{Tag|opening|:=}} is already used to tag measurements of {{Tag|barrier|cycle_barrier}} clearance, which is similar to what is required here. The similarity becomes especially apparent for partially open sliding gates. === Conditional opening === If it is known that a feature is open at specific times or if it follows some other recurring pattern, use the {{Tag|*:conditional|}} suffix. For example: * If doors are open, but closed during winter, it can be recorded with {{Tag|open|yes}}; {{Tag|open|3=no @ (winter)|:=conditional}}. * If doors are only open during busy hours on Monday to Friday from 7am till 9am, it can be recorded with ({{Tag|open|no}}); {{Tag|open|3=yes @ (Mo-Fr 07:00-09:00)|:=conditional}}. === Relation between <code>open</code> and <code>locked</code> === * {{Tag|open|no}} just describes an object (e.g. door) that is normally closed, '''but not''' that it is impossible to open or disallowed to pass. * {{Tag|locked|yes}} implies {{Tag|open|no}}, while {{Tag|open|no}} '''does not''' imply {{Tag|locked|yes}} or {{Tag|access}}. === Local knowledge === We want to specify that the key {{Tag|open}} should only be used if you have sufficient local knowledge about the place so that you can make a reasonable judgement regarding the value. Do not just tag a value if you visited the place once. This is similar to keys like {{Tag|locked}} and {{Tag|seasonal}}. ==Examples== <!-- Examples of what elements should be tagged: real-world images, openstreetmap.org screenshots, links to OpenStreetMap elements that use the proposed tagging. -->{| class="wikitable" |+ !Image !Tagging !Description |- |[[File:Set of opened double doors inside Chemnitz Main Station.jpg|100x100px]] |{{Tag|indoor|door}} {{Tag|door|hinged}} {{Tag|open|full}} {{Tag|maxwidth:physical|2}} |Open door at a train station connecting the entrance hall to the platforms. The door is always fully open, so {{Tag|maxwidth:physical}} is sufficient. |- |[[File:Closed set of double doors at Chemnitz Main Station.jpg|110x110px]] |{{Tag|entrance|yes}} {{Tag|open|no}} {{Tag|maxwidth:physical||1.2}} |Closed door leading to the entrance hall of a train station. This may provide a challenge for wheelchair users. {{Tag|open|no}} is assumed if not explicitly tagged oherwise. |- |[[File:Set of double doors with one door open at Chemnitz Main Station.jpg|102x102px]] |{{Tag|entrance|yes}} {{Tag|open|partial}} ⁣{{Tag|opening|0.6|:=}} {{Tag|maxwidth:physical||1.2}} |Partially open door at a train station. While wheelchair users do not have to open the door, their wheelchair may not fit through. |- |[[File:Half-open sliding garage door.jpg|100x100px]] |{{Tag|barrier|gate}} {{Tag|open|partial}} {{Tag|opening||1.5}} {{Tag|maxwidth:physical||4}} |A sliding gate of a garage that is partially open. (Note that the image shows a private garage which in reality is probably not regularly open nor legally accessible) |- |[[File:Gate Apples Rosemoor.jpg|100x100px]] |{{Tag|barrier|gate}} {{Tag|open|full}} {{Tag|maxwidth:physical||2.2}} |Open gate at an orchard. The gate is always fully open, so {{Tag|maxwidth:physical}} is sufficient. |} ==Rendering== <!-- Optional rendering suggestion, if relevant -->No special rendering is suggested for general-purpose map styles such as carto. However, indoor map styles are encouraged to adopt specific icons for the different cases. ==Features/Pages affected== <!-- List of wiki pages that would be edited if the proposal is approved --> * {{Tag|open}} * {{Tag|opening}} * {{Tag|maxwidth:physical}} * {{Tag|indoor|door}} * {{Tag|door}} * {{Tag|entrance|yes}} * {{Tag|barrier}} ==External discussions== <!-- Links to mailing lists, other forums where this proposal has been discussed... --> * [https://lists.openstreetmap.org/pipermail/tagging/2024-March/067781.html Tagging mailing list] * [https://community.openstreetmap.org/t/rfc-feature-proposal-key-opened/110685 Forum announcement] ==Comments== <!-- There must be at least 2 weeks set aside for comment on the proposal. Do not go to a vote without addressing the comments and fixing any problems with the proposal. The wiki talk page is used for comments, it is linked from the proposal page for those unfamiliar with wikis. --> Please comment on the [[{{TALKPAGENAME}}|discussion page]]. == Voting == {{Proposed feature voting}} <!-- Cheat sheet: {{vote|yes}} OPTIONAL MESSAGE HERE --~~~~ {{vote|no}} YOUR REASONS HERE --~~~~ {{vote|abstain}} YOUR COMMENTS HERE --~~~~ Place your vote below, at the end of the list. --> {{vote|yes}} --[[User:Pelderson|Peter Elderson]] ([[User talk:Pelderson|talk]]) 13:31, 22 April 2024 (UTC) {{vote|yes}} —[[User:Dieterdreist|Dieterdreist]] ([[User talk:Dieterdreist|talk]]) 13:51, 22 April 2024 (UTC) {{vote|yes}} This gives a definition for an ATYL I was going to use anyway.--[[User:Sbre|Sbre]] ([[User talk:Sbre|talk]]) 13:56, 22 April 2024 (UTC) {{vote|no}} The door state {{tag|open|partial}} is also open. {{tag|opening}} is already there as {{tag|maxwidth:physical}}. See [https://wiki.openstreetmap.org/wiki/Proposal_talk:Key:opened%3D#Adding_opening_hours=*_to_the_door_may_be_more_specific_/_key_mixes_opened/closed-state_with_door_width this discussion]. Examples in the proposal use {{tag|maxwidth:physical}} for the {{tag|width}} of the door, but {{tag|maxwidth:physical}} applies here, as this proposal assumes the common door state is permanent enough to be mapped. --[[User:Fabi2|Fabi2]] ([[User talk:Fabi2|talk]]) 14:19, 22 April 2024 (UTC) {{vote|yes}} --[[User:Nielkrokodil|Nielkrokodil]] ([[User talk:Nielkrokodil|talk]]) 16:22, 22 April 2024 (UTC) {{vote|yes}} I think this is an essential information for wheelchair users. —[[User:Gymate|Gymate]] ([[User talk:Gymate|talk]]) 17:21, 22 April 2024 (UTC) {{vote|yes}} --[[User:Hypo808|Hypo808]] ([[User talk:Hypo808|talk]]) 13:16, 24 April 2024 (UTC) {{vote|yes}} This will be very useful for the default handling of barrier accessibility in routing engines. {{Tag|open|yes}} is more specific than {{Tag|access|yes}} here. This also allows more detailed travel time estimations at accessible barriers, i.e. whether you have to wait for the barrier to open or whether it is already open. --[[User:JeroenvanderGun|JeroenvanderGun]] ([[User talk:JeroenvanderGun|talk]]) 17:39, 24 April 2024 (UTC) {{vote|yes}} --[[User:Adiatmad|Adiatmad]] ([[User talk:Adiatmad|talk]]) 04:23, 25 April 2024 (UTC) {{vote|yes}} Having mapped lots of gates that are actually permanently open, this would be a very useful tag for routing and rendering. [[User:HellMap|HellMap]] ([[User talk:HellMap|talk]]) 11:00, 26 April 2024 (UTC) {{vote|no}} The subject of the proposal is important, but the proposal is not yet ready for voting. At least, two things should be added: (a) relation of the "open" tag to the "locked" tab ("locked" is missing in the examples) (b) tagging of closed doors that can be opened by pushing a button or by light barrier --[[User:Voschix|voschix]] ([[User talk:Voschix|talk]]) 17:06, 27 April 2024 (UTC) {{vote|yes}} --[[User:Tokada|Tokada]] ([[User talk:Tokada|talk]]) 12:22, 28 April 2024 (UTC) {{vote|yes}} --[[User:Michi2|Michi]] ([[User talk:Michi2|talk]]) 19:12, 28 April 2024 (UTC) {{vote|yes}} I think that, as of currently, the users that voted no aren't correct for the following reasons: (1) open=partial is meant to apply, as I understood it, to doors that can be partially opened to a fixed position and (2) I don't think that the open=* tag is meant to describe the way in which you open the doors themselves and I'm not convinced it should be that way. What makes me a little bit hesitant to vote yes is that it doesn't explicitly state the relation of this tag to the opening hours of the map feature on which the doors are. But I think this is more of a nitpick and can be assumed that open=yes, means that during the opening hours. --[[User:Comfyquiettree|comfyquiettree]] ([[User talk:Comfyquiettree|talk]]) 18:13, 5 May 2024 (UTC) {{vote|no}} I see no need for this feature --[[User:Chris66|chris66]] ([[User talk:Chris66|talk]]) 19:04, 5 May 2024 (UTC) {{vote|yes}} This feature will let me plan hiking routes based on the number of gates I need to wrangle. --[[User:Carnildo|Carnildo]] ([[User talk:Carnildo|talk]]) 19:29, 5 May 2024 (UTC) {{vote|yes}} --[[User:Nacktiv|Nacktiv]] ([[User talk:Nacktiv|talk]]) 22:08, 5 May 2024 (UTC) {{vote|yes}} --[[User:Uboot|Uboot]] ([[User talk:Uboot|talk]]) 07:16, 6 May 2024 (UTC) {{vote|yes}} --[[User:GanderPL|GanderPL]] ([[User talk:GanderPL|talk]]) 08:40, 6 May 2024 (UTC) {{vote|no}} Wherever a feature is closed or opened is in my opinion too temporary to be mapped in OSM, beyond this, is seems a tag too redundant to locked=* --[[User:Szydzio|Szydzio]] ([[User talk:Szydzio|talk]]) 11:59, 6 May 2024 (UTC) {{vote|no}} I don't see the point of this tag - whether a gate or door is open is temporary. They are open during the day and closed at night. It is not a permanent feature. After all, we don't know if the door is closed permanently or only at a given moment. [[User:Maro21|maro21]] 21:35, 6 May 2024 (UTC)'
Unified diff of changes made by edit (edit_diff)
'@@ -7,5 +7,5 @@ | definition = Whether a feature is normally open | appearance = none -| status = Voting +| status = Post-Vote | draftStartDate = 2024-01-23 | rfcStartDate = 2024-03-19 '
Unified diff of changes made by edit, pre-save transformed (edit_diff_pst)
'@@ -7,5 +7,5 @@ | definition = Whether a feature is normally open | appearance = none -| status = Voting +| status = Post-Vote | draftStartDate = 2024-01-23 | rfcStartDate = 2024-03-19 '
Lines added in edit (added_lines)
[ 0 => '| status = Post-Vote' ]
Lines removed in edit (removed_lines)
[ 0 => '| status = Voting' ]
Lines added in edit, pre-save transformed (added_lines_pst)
[ 0 => '| status = Post-Vote' ]
New page wikitext, pre-save transformed (new_pst)
'{{Proposal page | name = Key:open | user = | key = open | value = | type = {{IconNode}} | definition = Whether a feature is normally open | appearance = none | status = Post-Vote | draftStartDate = 2024-01-23 | rfcStartDate = 2024-03-19 | voteStartDate = 2024-04-22 | voteEndDate = 2024-05-07 | tagging = {{Tag|open|*}}, {{Tag|opening|*}} | users = {{u|Wielandb}} on behalf of {{u|OPENER}} }} {{Ambox|type=caution|text=The proposal initially started with the key {{Tag|opened}} to follow the existing {{Tag|locked}} tag. However we realized that "opened" is only used as a verb or when something has recently been opened and therefore changed it to {{Tag|open}}. See: * https://wiki.openstreetmap.org/wiki/Proposal_talk:Key:opened%3D#'opened'_is_the_wrong_word * https://dictionary.cambridge.org/grammar/british-grammar/open-or-opened * https://english.stackexchange.com/questions/141547/opened-vs-open}} ==Proposal== <!-- A short statement of what you propose, including a list of what tag(s) are being proposed to be added, changed, or deprecated --> This proposal wants to establish the key {{Tag|open}}. Similar to the key {{Tag|locked}}, {{Tag|open}} describes whether an object that can be opened or closed is usually open. This applies to objects such as gates (e.g. {{Key|barrier|gate}}) and especially doors ({{Key|door}}). Additionally, we propose to reuse {{Key|opening}} to determine the clearance width of an object tagged with {{Tag|open|partial}}. <!-- Which Database Elements (nodes, ways, areas, relations) each of the tags can be used on could be included here or under the Tagging heading, or both. --> ==Rationale== <!-- Explanation of why the proposal is needed, and why you chose the specific key and value of the tag. Compare with similar tags or previous proposals, if relevant. Consider significance and potential uses of the data.--> OSM currently only states the existence of doors, but not if they are open or closed. There is no doubt that most doors in reality can be opened or closed at any time. So their opening state is mostly temporary and should not be mapped in OSM. However there are doors or gates at public places (e.g. shopping centres, train stations, libraries, parks, universities etc.) that are technically doors or gates but often not perceived as such because they are constantly open. Currently this cannot be represented sufficiently in OSM. Either the doors are not mapped which is wrong (because OSM maps physically present features) or the doors are mapped but then it is not clear that they do not form a barrier. To give an example: Interior doors at train stations and airports are in control of the the operators and constantly open so passengers can easily pass through. They are usually fixated with a door holder or door stay to prevent them from accidentally snap shutting or being closed by unauthorized people. The doors are only closed in exceptional scenarios like when a fire is broken out or on construction work. The same logic applies to barriers like arm barriers ({{Tag|barrier|lift_gate}}) on streets and other features that can be opened / closed. The information whether something is open by default helps to know if e.g. a door is easily passable. This is especially important for people with strollers, wheelchair users and cyclists. The information can also be used by routing engines to find more suitable / accessible routes. <!-- Keep the tag short while still being logical and descriptive enough to need little explanation. Avoid tag names which might cause confusion with a different tag. British English terms are preferred, when possible --> ==Tagging== <!-- A table, list, or set of subheadings explaining each tag: * Definition of the meaning of the tag and how it should be used * Elements tagged: nodes, ways, areas or relations? [if a feature is smaller than 5m by 5m it would usually be mapped only as a node] * Comparison with current tagging schemes (if applicable) * Additional tags used in combination (including existing tags) * When other tags should be used instead. -->{{Tag|open}} describes the "default state" of a feature that can be opened / closed either by hand or a mechanism. Default means the idle or passive state of the feature without / prior to any user interaction. Four values are proposed for the key {{Tag|open}}: * {{Tag|open|yes}} - Somehow open. Generic value, use a more specific value if possible. ** {{Tag|open|full}} - Completely open. For doors with multiple wings, all wings have to be fully open. ** {{Tag|open|partial}} - Only partially open. E.g. just one of several wings is open or one wing is just open to some extent. * {{Tag|open|no}} - Closed ('''default value'''). Needs to be opened by hand or a mechanism to pass through. This tag as well as its default value only applies to elements, which can be opened and closed. So for example it '''does not''' apply to elements tagged with: * {{Tag|door|no}} or {{Tag|door|revolving}} * barriers like {{Tag|barrier|entrance}}, {{Tag|barrier|turnstile}}, {{Tag|barrier|cycle_barrier}} etc. * {{Tag|automatic_door|continuous}} === Automatic doors === Tagging {{Tag|open}} on automatic doors ({{Tag|automatic_door}}) is of limited use, but still possible. It is mostly useful if the doors are out of order / deactivated. If tagged on operational automatic doors the default state is the state prior to any button press or motion sensor detection. === Clearance width of an open door === * For {{Tag|open|full}}, the key {{Tag|opening|:=}} can be omitted as it is already covered by {{Tag|maxwidth:physical}} (or sometimes other dimensional keys like {{Tag|door:width}} / {{Tag|width}} that describe the distance between the doorposts). * For {{Tag|open|partial}}, the key {{Tag|opening|:=}} is used to record the clearance width of the opening. === Why reusing the "opening" key? === [[File:Prtially open door dimensions.svg|thumb|Visualises the measurements of a permanently half-open double door]] * "opening" implicitly describes what should be measured in contrast to "width" or "maxwidth". * The term "opening" is linguistically connected to "open". * {{Tag|maxwidth:physical}} already describes the fully open clearance width of gates and doors, so it cannot be used. * {{Tag|opening|:=}} is already used to tag measurements of {{Tag|barrier|cycle_barrier}} clearance, which is similar to what is required here. The similarity becomes especially apparent for partially open sliding gates. === Conditional opening === If it is known that a feature is open at specific times or if it follows some other recurring pattern, use the {{Tag|*:conditional|}} suffix. For example: * If doors are open, but closed during winter, it can be recorded with {{Tag|open|yes}}; {{Tag|open|3=no @ (winter)|:=conditional}}. * If doors are only open during busy hours on Monday to Friday from 7am till 9am, it can be recorded with ({{Tag|open|no}}); {{Tag|open|3=yes @ (Mo-Fr 07:00-09:00)|:=conditional}}. === Relation between <code>open</code> and <code>locked</code> === * {{Tag|open|no}} just describes an object (e.g. door) that is normally closed, '''but not''' that it is impossible to open or disallowed to pass. * {{Tag|locked|yes}} implies {{Tag|open|no}}, while {{Tag|open|no}} '''does not''' imply {{Tag|locked|yes}} or {{Tag|access}}. === Local knowledge === We want to specify that the key {{Tag|open}} should only be used if you have sufficient local knowledge about the place so that you can make a reasonable judgement regarding the value. Do not just tag a value if you visited the place once. This is similar to keys like {{Tag|locked}} and {{Tag|seasonal}}. ==Examples== <!-- Examples of what elements should be tagged: real-world images, openstreetmap.org screenshots, links to OpenStreetMap elements that use the proposed tagging. -->{| class="wikitable" |+ !Image !Tagging !Description |- |[[File:Set of opened double doors inside Chemnitz Main Station.jpg|100x100px]] |{{Tag|indoor|door}} {{Tag|door|hinged}} {{Tag|open|full}} {{Tag|maxwidth:physical|2}} |Open door at a train station connecting the entrance hall to the platforms. The door is always fully open, so {{Tag|maxwidth:physical}} is sufficient. |- |[[File:Closed set of double doors at Chemnitz Main Station.jpg|110x110px]] |{{Tag|entrance|yes}} {{Tag|open|no}} {{Tag|maxwidth:physical||1.2}} |Closed door leading to the entrance hall of a train station. This may provide a challenge for wheelchair users. {{Tag|open|no}} is assumed if not explicitly tagged oherwise. |- |[[File:Set of double doors with one door open at Chemnitz Main Station.jpg|102x102px]] |{{Tag|entrance|yes}} {{Tag|open|partial}} ⁣{{Tag|opening|0.6|:=}} {{Tag|maxwidth:physical||1.2}} |Partially open door at a train station. While wheelchair users do not have to open the door, their wheelchair may not fit through. |- |[[File:Half-open sliding garage door.jpg|100x100px]] |{{Tag|barrier|gate}} {{Tag|open|partial}} {{Tag|opening||1.5}} {{Tag|maxwidth:physical||4}} |A sliding gate of a garage that is partially open. (Note that the image shows a private garage which in reality is probably not regularly open nor legally accessible) |- |[[File:Gate Apples Rosemoor.jpg|100x100px]] |{{Tag|barrier|gate}} {{Tag|open|full}} {{Tag|maxwidth:physical||2.2}} |Open gate at an orchard. The gate is always fully open, so {{Tag|maxwidth:physical}} is sufficient. |} ==Rendering== <!-- Optional rendering suggestion, if relevant -->No special rendering is suggested for general-purpose map styles such as carto. However, indoor map styles are encouraged to adopt specific icons for the different cases. ==Features/Pages affected== <!-- List of wiki pages that would be edited if the proposal is approved --> * {{Tag|open}} * {{Tag|opening}} * {{Tag|maxwidth:physical}} * {{Tag|indoor|door}} * {{Tag|door}} * {{Tag|entrance|yes}} * {{Tag|barrier}} ==External discussions== <!-- Links to mailing lists, other forums where this proposal has been discussed... --> * [https://lists.openstreetmap.org/pipermail/tagging/2024-March/067781.html Tagging mailing list] * [https://community.openstreetmap.org/t/rfc-feature-proposal-key-opened/110685 Forum announcement] ==Comments== <!-- There must be at least 2 weeks set aside for comment on the proposal. Do not go to a vote without addressing the comments and fixing any problems with the proposal. The wiki talk page is used for comments, it is linked from the proposal page for those unfamiliar with wikis. --> Please comment on the [[{{TALKPAGENAME}}|discussion page]]. == Voting == {{Proposed feature voting}} <!-- Cheat sheet: {{vote|yes}} OPTIONAL MESSAGE HERE --~~~~ {{vote|no}} YOUR REASONS HERE --~~~~ {{vote|abstain}} YOUR COMMENTS HERE --~~~~ Place your vote below, at the end of the list. --> {{vote|yes}} --[[User:Pelderson|Peter Elderson]] ([[User talk:Pelderson|talk]]) 13:31, 22 April 2024 (UTC) {{vote|yes}} —[[User:Dieterdreist|Dieterdreist]] ([[User talk:Dieterdreist|talk]]) 13:51, 22 April 2024 (UTC) {{vote|yes}} This gives a definition for an ATYL I was going to use anyway.--[[User:Sbre|Sbre]] ([[User talk:Sbre|talk]]) 13:56, 22 April 2024 (UTC) {{vote|no}} The door state {{tag|open|partial}} is also open. {{tag|opening}} is already there as {{tag|maxwidth:physical}}. See [https://wiki.openstreetmap.org/wiki/Proposal_talk:Key:opened%3D#Adding_opening_hours=*_to_the_door_may_be_more_specific_/_key_mixes_opened/closed-state_with_door_width this discussion]. Examples in the proposal use {{tag|maxwidth:physical}} for the {{tag|width}} of the door, but {{tag|maxwidth:physical}} applies here, as this proposal assumes the common door state is permanent enough to be mapped. --[[User:Fabi2|Fabi2]] ([[User talk:Fabi2|talk]]) 14:19, 22 April 2024 (UTC) {{vote|yes}} --[[User:Nielkrokodil|Nielkrokodil]] ([[User talk:Nielkrokodil|talk]]) 16:22, 22 April 2024 (UTC) {{vote|yes}} I think this is an essential information for wheelchair users. —[[User:Gymate|Gymate]] ([[User talk:Gymate|talk]]) 17:21, 22 April 2024 (UTC) {{vote|yes}} --[[User:Hypo808|Hypo808]] ([[User talk:Hypo808|talk]]) 13:16, 24 April 2024 (UTC) {{vote|yes}} This will be very useful for the default handling of barrier accessibility in routing engines. {{Tag|open|yes}} is more specific than {{Tag|access|yes}} here. This also allows more detailed travel time estimations at accessible barriers, i.e. whether you have to wait for the barrier to open or whether it is already open. --[[User:JeroenvanderGun|JeroenvanderGun]] ([[User talk:JeroenvanderGun|talk]]) 17:39, 24 April 2024 (UTC) {{vote|yes}} --[[User:Adiatmad|Adiatmad]] ([[User talk:Adiatmad|talk]]) 04:23, 25 April 2024 (UTC) {{vote|yes}} Having mapped lots of gates that are actually permanently open, this would be a very useful tag for routing and rendering. [[User:HellMap|HellMap]] ([[User talk:HellMap|talk]]) 11:00, 26 April 2024 (UTC) {{vote|no}} The subject of the proposal is important, but the proposal is not yet ready for voting. At least, two things should be added: (a) relation of the "open" tag to the "locked" tab ("locked" is missing in the examples) (b) tagging of closed doors that can be opened by pushing a button or by light barrier --[[User:Voschix|voschix]] ([[User talk:Voschix|talk]]) 17:06, 27 April 2024 (UTC) {{vote|yes}} --[[User:Tokada|Tokada]] ([[User talk:Tokada|talk]]) 12:22, 28 April 2024 (UTC) {{vote|yes}} --[[User:Michi2|Michi]] ([[User talk:Michi2|talk]]) 19:12, 28 April 2024 (UTC) {{vote|yes}} I think that, as of currently, the users that voted no aren't correct for the following reasons: (1) open=partial is meant to apply, as I understood it, to doors that can be partially opened to a fixed position and (2) I don't think that the open=* tag is meant to describe the way in which you open the doors themselves and I'm not convinced it should be that way. What makes me a little bit hesitant to vote yes is that it doesn't explicitly state the relation of this tag to the opening hours of the map feature on which the doors are. But I think this is more of a nitpick and can be assumed that open=yes, means that during the opening hours. --[[User:Comfyquiettree|comfyquiettree]] ([[User talk:Comfyquiettree|talk]]) 18:13, 5 May 2024 (UTC) {{vote|no}} I see no need for this feature --[[User:Chris66|chris66]] ([[User talk:Chris66|talk]]) 19:04, 5 May 2024 (UTC) {{vote|yes}} This feature will let me plan hiking routes based on the number of gates I need to wrangle. --[[User:Carnildo|Carnildo]] ([[User talk:Carnildo|talk]]) 19:29, 5 May 2024 (UTC) {{vote|yes}} --[[User:Nacktiv|Nacktiv]] ([[User talk:Nacktiv|talk]]) 22:08, 5 May 2024 (UTC) {{vote|yes}} --[[User:Uboot|Uboot]] ([[User talk:Uboot|talk]]) 07:16, 6 May 2024 (UTC) {{vote|yes}} --[[User:GanderPL|GanderPL]] ([[User talk:GanderPL|talk]]) 08:40, 6 May 2024 (UTC) {{vote|no}} Wherever a feature is closed or opened is in my opinion too temporary to be mapped in OSM, beyond this, is seems a tag too redundant to locked=* --[[User:Szydzio|Szydzio]] ([[User talk:Szydzio|talk]]) 11:59, 6 May 2024 (UTC) {{vote|no}} I don't see the point of this tag - whether a gate or door is open is temporary. They are open during the day and closed at night. It is not a permanent feature. After all, we don't know if the door is closed permanently or only at a given moment. [[User:Maro21|maro21]] 21:35, 6 May 2024 (UTC)'
Unix timestamp of change (timestamp)
'1715149367'