-
Notifications
You must be signed in to change notification settings - Fork 822
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
Unpaved no access #4137
Unpaved no access #4137
Conversation
Are there any opinions about this code? If I understand it right, it removes the only thing that has been disputed lately, so I guess it could be merged soon. |
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.
I do not find residential, tertiary or primary easily distinguishable, and find secondary marginal.
I also don't feel that this cartography fits with the rest of the style.
I haven't done a line-by-line review of the MSS but am concerned about adding this much code and complexity to a difficult part of the codebase.
I also have the hard time seeing the difference, but fixing this problem would be quite simple.
I'm surprised to hear that. In my opinion pattern rendering on areas is well-established and consistent with the whole style.
That is a valid concern. On the other hand there is high demand for this feedback, which could help mitigate roads mistagging - see #110 (comment). |
eed7f92
to
2b18036
Compare
Rebased to current master. |
896022c
to
52ee66e
Compare
I would really like to move that forward. Regarding the MSS file: Of course, this PR adds code, but the code is not complex. Remember that Mapnik has kindly implemented pattern renderings on line strings because of our request, so that now we have straightforward code. Regarding the pattern being distinguishable, I could provide a version with more contrast, if desired. Should I do so? |
I very much support that, either this or #3399.
I think this as now is a good balance between clear readability and not being too bold to illustrate a secondary distinction and not messing too much with the overall balance of the map. |
52ee66e
to
acb71d9
Compare
Closing this in favour of #3399, to centralize discussion and not have too many open PR: |
Fixes #110
Closes #3399 (alternative version)
Changes proposed in this pull request:
This PR is an alternative version of #3399 that does not render access on roads any more, to simplify the overall rendering of roads. (It does not change, however, the access rendering for tracks, footways and so on, which follows a completely different approach than access rendering on roads.)