Template talk:Generic:Map Features:barrier
barrier=step and barrier=haha are too rare to add to this page
This page is supposed to be an overview of commonly used barrier values.
barrier=haha
has only been used 15 times, and could be mapped asbarrier=retaining_wall
instead.barrier=step
has only been used 171 times, and many uses should bebarrier=kerb
instead.
I do not think these tags should be listed here. --Jeisenbe (talk) 05:56, 15 October 2020 (UTC)
barrier=bollard now listed twice
@MalgiK: your recent edit has duplicated barrier=bollard
- now it is listed twice, at the beginning of "linear barriers" and also at the beginning of "access control on highways". I believe it should only be listed once. --Jeisenbe (talk) 04:28, 9 November 2020 (UTC)
- @Jeisenbe: Actually it was a bit on purpose, especially i did a search for a different photo to better illustrate the row version. I think it's not wrong, just a bit redundant, (which is not the first redundancy within osm, just think about separate addr:*-nodes and same duplicate address information on POIs.) ;-) Also this counts for
barrier=cable_barrier
, i did add earlier days, so it is there in both table divisions. Forbarrier=kerb
i wouldn't do it, because the tagging seems in general a bit different. --MalgiK (talk) 04:41, 9 November 2020 (UTC)- This is a list of features which is meant to be an introduction for new mappers, so it's rather confusing to list the same thing twice (also, the description is currently incorrect, since it was copied from the next entry). I would suggest removing the duplicate entries for bollard and cable_barrier. --Jeisenbe (talk) 05:27, 9 November 2020 (UTC)
- Justed checked, it seems
barrier=rope
is the 3rd candidate who would also qualify for both Access_control_on_highways & Linear_barriers) categories. I agree it could appear confusing. What about of a compromise using a third category on bottom, where we list the possible duplicate items? --MalgiK (talk) 06:08, 9 November 2020 (UTC) - @Jeisenbe: Thanks, desc' fixed. --MalgiK (talk) 06:14, 9 November 2020 (UTC)
- Justed checked, it seems
- This is a list of features which is meant to be an introduction for new mappers, so it's rather confusing to list the same thing twice (also, the description is currently incorrect, since it was copied from the next entry). I would suggest removing the duplicate entries for bollard and cable_barrier. --Jeisenbe (talk) 05:27, 9 November 2020 (UTC)
Adding a 3rd table title (category)
@Jeisenbe: Continuing from talk above, i missed to tell i did earlier today also add barrier=jersey_barrier
. So the full list of items for this potentiel 3rd category would be:
barrier=bollard
barrier=chain
barrier=cable_barrier
barrier=gate
barrier=jersey_barrier
barrier=kerb
barrier=rope
barrier=tank_trap
and e.g. barrier=wicket_gate
(has low amount)
Do you want do this? --MalgiK (talk) 06:27, 9 November 2020 (UTC)
- Most of those are usually not linear barriers that function like a fence or wall, but simply access controls on highways which are sometimes mapped as a short way with 2 or 3 nodes. The true exceptions are
barrier=bollard
which is commonly a single node but can also be a long line of bollards e.g. between a road and a sidewalk, andbarrier=cable_barrier
which is often parallel to a road. I guess there is some usage ofbarrier=chain
andbarrier=rope
as linear barriers as well.barrier=tank_trap
,barrier=gate
are just to block highways so shouldn't be included. --Jeisenbe (talk) 07:56, 9 November 2020 (UTC)
- Yes, i agree that some punctiform objects for road access control will sometimes mapped as line objects when mappers deeply zoom into the map and doing detail mapping because these features blocks the streets no only by a center point in the middle of a street like mostly a single bollard is donig this. I think good examples are known for drawn lines cross the street for
gates
,lift_gates
or asliding_gates
. But when i go again through the list above i would expect for such a group of road blockers only:gate
&wicket_gate
. The others (bollard
,chain
,cable
,jersey
,kerb
,rope
andtank_trap
) are also exist along a street or as linear objects somewhere else. Thechain
andrope
i think are good for the group along a street, e.g. see an example for achain
https://www.openstreetmap.org/way/339874145 as a valid linear object. And when i look through https://overpass-turbo.eu/s/ZSK (query for wayrope
) a substantial rate represents not road blockers. So i would create a 3rd group ofbollard
,chain
,cable
,jersey
,kerb
,rope
andtank_trap
for mixed usage of road blocker and non road blockers (linear objects). --MalgiK (talk) 09:21, 9 November 2020 (UTC)
- Yes, i agree that some punctiform objects for road access control will sometimes mapped as line objects when mappers deeply zoom into the map and doing detail mapping because these features blocks the streets no only by a center point in the middle of a street like mostly a single bollard is donig this. I think good examples are known for drawn lines cross the street for