-
Notifications
You must be signed in to change notification settings - Fork 826
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.
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
Additional access marking #5049
Additional access marking #5049
Conversation
highway=pedestrian should support restricted access
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good - except for the color of the dashing for pedestrian roads IMO - using white here breaks with the overall principle of using gray colors for the access dashing on roads. It also can lead to confusion with the construction dashing, which uses white color as well. Furthermore it is much higher contrast than the other roads relative to the fairly dark pedestrian fill color.
I would probably try the light gray used for highway=road
access dashing - the gray fill color of highway=road
has similar contrast to that relative to highway=pedestrian
- and that would more or less also match the contrast of the dashing on other road types.
As far as the increase in XML code volume is concerned - that is to be expected. This is an unfortunate side effect of how our road rendering is designed. It is important to keep an eye on this - but i am very much against constraining our design decisions because of such effects. Ways exist to counteract this code volume increase (by moving some of the styling logic outside of CartoCSS/XML - like we did for example with the path to footway/cycleway/bridleway re-classification). But we need to carefully weigh the pros and cons here (code volume, rendering efficiency and code accessibility and maintainability).
Change pedestrian access marking colour to common light shade of grey. Also consolidate names.
Changed as suggested. I've also consolidated the variable names for ease of maintenance - the access marking on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixes #5024
Fixes #4998
Changes proposed in this pull request:
access=destination
) onhighway=motorway/trunk/primary
(currently onlyaccess=no
shown)highway=pedestrian
using white as contrasting colour.Note that a tweak to
functions.sql
is needed to allowhighway=pedestrian
to support "restricted" access marking.Test rendering:
"restricted" access on major highways is not expected to be valid tagging. The purpose of the PR is to highlight potentially incorrect tagging.
Illustrations are taken from a hacked legend rendering, with
access=destination
on all highways.Note that the increased "coverage" of access tags needs to be weighed against a 7% increase in lines of XML. This is a result of all the added combinations of road types / 3 SQL queries / 3 access types.