Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ramp=separate should not be rendered on steps #545

Closed
Ltrlg opened this issue Mar 30, 2021 · 2 comments · Fixed by #569
Closed

ramp=separate should not be rendered on steps #545

Ltrlg opened this issue Mar 30, 2021 · 2 comments · Fixed by #569

Comments

@Ltrlg
Copy link

Ltrlg commented Mar 30, 2021 •
edited
Loading

Because by definition it is already rendered.

For example at 47.46562/-0.51004: currently way/671118656 has a blue line, but the actual ramp, way/671118654, is already visible, hence the information is displayed twice.
@Florimondable
Copy link
Member

I guess sometimes the separated ramp is not mapped.

@Ltrlg
Copy link
Author

Ltrlg commented Mar 31, 2021

That would be in contradiction with the definition: “There is a ramp, but it is mapped as a separate way in OpenStreetMap.”

There are probably errors in the database, but I don’t think double rendering in correctly tagged areas is better than not rendering in incorrectly tagged areas.

Florimondable added a commit to Florimondable/cyclosm-cartocss-style that referenced this issue May 14, 2021
@Florimondable
Remove rendering of ramp:xxx=separate. Fix cyclosm#545
d07b391
@Florimondable Florimondable mentioned this issue May 14, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove rendering of ramp separate Florimondable/cyclosm-cartocss-style
2 participants
@Ltrlg @Florimondable