Opened 5 years ago
Closed 5 years ago
#18183 closed enhancement (fixed)
foot=use_sidepath on a cycleway, validation problem, segregated
Reported by: | Allroads | Owned by: | Klumbumbus |
---|---|---|---|
Priority: | normal | Milestone: | 19.10 |
Component: | Core validator | Version: | tested |
Keywords: | use_sidepath foot cycleway | Cc: |
Description
When there is a foot=use_sidepath on a cycleway, there is this warning: Missing tag - Combined foot- and cycleway without segregated.
When use_sidepath is used on a cycleway, there is a separated footway drawn in next to the cycleway, even there could be a little verge between them, when the footway is connected well, the use_sidepath is set on the cycleway, this is important for correct foot routing.
A tag segregated is not needed.
Josm should not instruct us to put a tag. Segregated= When used use_sidepath
Segregated is unnecessary.
When used use_sidepath there is always a way drawn in next to the way with the use_sidepath tag.
It is annoying to get all these warnings.
This tag use_sidepath is developed in the Netherlands for bicycle and is usefull for mofa, moped and foot.
In such situation it is not allowed to use the cycleway by foot, it is a good way to direct the foot routing over the drawn in footway.
Law tells us,
In certain circumstances it is permitted to use the cycle path as a pedestrian, but for most common use it is prohibited and therefore the pedestrian should not be routed over the pedestrian path.
It is not a hard foot=no,therefore use use_sidepath.
Attachments (1)
Change History (9)
comment:1 by , 5 years ago
Keywords: | cycleway added |
---|
comment:2 by , 5 years ago
I fully understand your point.
A few, who makes JOSM and so many use it. Respect for all your commitment.
Time is always an issue.
The problem for most of us, the knowledge to help you all.
My role for now is, only to make a ticket to express the problem.
From this side to make JOSM better.
Yep, I watched the live vid from you, nice to see/hear some background information about your contribution. Well done.
So, don't be irritated about my "annoying" expression.
I believe you are not, you just took it as point to make your point.
comment:3 by , 5 years ago
I'm fine, don't worry :) my comment is a call for help: I need someone willing to do the dirty work of updating our bicycle stuff on a long period (every time we change/update something for a country, it breaks something else in another one, so it will take some time to converge to something suitable for everyone). Probably a lot of discussion on @tagging and/or wiki will be required.
comment:4 by , 5 years ago
Another thing: it's a lot easier for people willing to fix issues when they contain the following information:
- first three blocks of JOSM status report
- a small sample data set showing the problem
- links to the wiki for the related tags
by , 5 years ago
Attachment: | use_sidepath.JPG added |
---|
comment:5 by , 5 years ago
comment:6 by , 5 years ago
Hi, I think Allroads is right, there should be no warning.
use_sidepath just mean there is a mandatory road for you next to the current way.
So if set, there is no pedestrian on the cycleway hence no segregated tag is needed.
foot=use_sidepath is not documented though, only bicycle=use_sidepath exists in the wiki, this is a shame that the wiki do not define use_sidepath by itself.
comment:7 by , 5 years ago
Milestone: | → 19.10 |
---|---|
Owner: | changed from | to
Replying to Allroads:
At SOTM 2019 I expressed my frustration about cycleway/bicycle tagging. It's insanely complex to handle all the possibilities and I haven't time to check every possible combinations of cycleway-related tags in the world, so I gave up looking at those tickets.
Someone needs to step up to focus on this subject and provide validator/presets/rendering patches that address all issues.