-
Notifications
You must be signed in to change notification settings - Fork 9
render separate cycleways differently than walkways #94
Comments
Can show a screenshot of a quest where it creates confusion? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hmm, so you are confused by the question whether there is an island on the "crossing" of a footway and a cycleway? Yeah, I would be too. It looks like a bug to be honest - I can't think of a good reason why this should be asked at all. Can you tell me the location at which this can be observed? |
This one is here: |
I have no problem with assigning crossing quests to this type of crossing. It would be just much easier to solve them if cycleway and walkway would be rendered slightly differently. |
Hm well, I'd like to avoid putting too much information in the background map and using too many distinctive colors on that map: It should stay unobstrusive. Also, if those two are rendered differently, it would require to distinguish not only between those two, but distinguish between footway, cycleway and foot- and cycleways (i.e. one way used for both footway and cycleway even if they are segregated). So, probably set another color(?) In any case, I just looked up in which layer these would be in the jawg.io tiles: |
I came to raise an issue about the same thing having been similarly confused/challenged, and I see one already exists. I'm often finding cycleways are mapped but pavements/sidewalks aren't, so when you're asked a question (particularly the crossing ones), it make it harder to orientate if you're on the way it's asking about or not (i.e. is it asking about the cycleway or the footpath).
If you used blue and pink to match the existing scheming, then couldn't you do alternate dashed or something (if that's possible) for the shared one, so you'd only need two more colours. See also this related issue in the main repo: |
Although, from UX/accessibility perspective, things should not differ only in color (think different types of color blindness etc.) |
Use case
In SC cycleways are rendered exactly the same as walkways which may create confusion which element I am filling info in. In most desperate cases I had to open separate app to see which crossing is in question.
Proposed Solution
Just use different colour to render them. Default OSM style uses blue dashes so some blue tint would be the best.
The text was updated successfully, but these errors were encountered: