-
Notifications
You must be signed in to change notification settings - Fork 825
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
Reviewing roads_info #5032
Comments
I would not want to mix in the discussion on actually rendering
Fixing #3581 will require integrating
The number of layers is not an issue per se. Separate layers are useful for modularization when
We should not just combine unrelated things into one layer just to keep the layer count low. There is very little benefit in that and making changes becomes more difficult. |
Thanks for clarifying the issues. I was wondering whether |
This would seem a useful step forward. If nothing else it would reduce the effort involving in addressing #4226 (which would really need a new, coherent render for It would be somewhat tedious to add tunnel and bridge rendering for guideways for the tiny number of real-life examples, but I can't see any major obstacles? |
Picking up on one of the many topics raised in #5027 :
Adding a suitable slot for
highway=busway
would make sense, in (slightly) reducing the barrier to development. There was a promising start in #4226, and one point of apparent consensus was that rendering forhighway=busway
ought to be combined / visually coherent withhighway=bus_guideway
. I suspect it is a historical anachronism for guided busways to have their own layer (guideways
). So would we want to create a slot for both and dump the separate guideways layer?This connects to a more general question (triggered by #5021) of whether we have too many layers?
The text was updated successfully, but these errors were encountered: