Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

render separate cycleways differently than walkways #94

Open
vvizzo opened this issue Apr 6, 2021 · 13 comments
Open

render separate cycleways differently than walkways #94

vvizzo opened this issue Apr 6, 2021 · 13 comments

Comments

@vvizzo
Copy link

vvizzo commented Apr 6, 2021

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.

@vvizzo vvizzo changed the title render separate cycleways differently that walkways render separate cycleways differently than walkways Apr 6, 2021
@westnordost
Copy link
Member

Can show a screenshot of a quest where it creates confusion?

@vvizzo

This comment has been minimized.

@westnordost

This comment has been minimized.

@vvizzo

This comment has been minimized.

@westnordost

This comment has been minimized.

@vvizzo
Copy link
Author

vvizzo commented Apr 6, 2021

Screenshot_20210406-152923

@westnordost
Copy link
Member

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?

@vvizzo
Copy link
Author

vvizzo commented Apr 6, 2021

@westnordost
Copy link
Member

westnordost commented Apr 6, 2021

Hmm indeed, there is actually a crossing here. A zebra:

image

@vvizzo
Copy link
Author

vvizzo commented Apr 7, 2021

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.

@westnordost
Copy link
Member

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:
In layer road:
class: path
type: cycleway or type: footway or type: path

@westnordost westnordost transferred this issue from streetcomplete/StreetComplete Apr 10, 2021
@peternewman
Copy link
Contributor

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).

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(?)

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:
streetcomplete/StreetComplete#3594

@mnalis
Copy link
Member

mnalis commented Dec 23, 2021

Although, from UX/accessibility perspective, things should not differ only in color (think different types of color blindness etc.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants