-
Notifications
You must be signed in to change notification settings - Fork 823
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
Don't render track roads at z13 or z14 #4440
Comments
Related to #3798 and #765, clashes with #1591. Keep in mind that in terms of road rendering systematics removing highway=track from z13/14 would require removing cycleway/footway as well - which in turn would render the map even more useless for non-motorized navigation in non-urban contexts than it is right now (after in particular #747 and #3467) - see also #3808 (comment). A workable way of rendering tracks and paths at z13/14 has been shown in http://blog.imagico.de/drawing-the-lines/. |
And please always provide links to your sample locations. |
|
That might not be a bad thing at z13. Paths and service roads aren't rendered at that level either. Footways aren't any more important then service roads. Also, I think it's a bad premise to call not rendering them at z13 useless. It's not like people can't just zoom in one more level to see footways if they need to. No one is checking out the details of footway at that level anyway.
I had thought of that, but it's pretty unlikely anyone is going to write the code for it or deal with the other stuff that they would have to for it to merged. Whereas, there's a good chance someone will just change a zoom level. Which takes almost nothing to implement. Not to mention there's been a lot of talk about simplifying rendering anyway. Maybe this would be a good opportunity. |
I would be for removing footways at Z14 and Z13. They look pretty weird and are not necessary as they are in Chicago here: https://www.openstreetmap.org/#map=14/41.8737/-87.6136 |
Re: "a lot of them are either private or not generally drivable” The definition of highway=track does not include that access is private, or that they are not accessible to ordinary passenger vehicles. These are roads mainly used for forestry, agriculture, ranching, or sometimes recreation. Rural areas have track roads stretching for many kilometers. If they are not shown on z13 and z14 it will not be possible to see the road network in those places. |
Sure, it's not in the definition, but that's just the nature of the roads. A good portion of "forestry, agriculture, ranching" roads are private whatever OSMs definition of a track road is. Recreation roads not so much, but it would still be worth making an exception in render ones that are not so boldly (if at all).
In a good portion of the cases they are blocked at their entrances by barriers though and can't (or shouldn't be) driven down by 99% of the people who are viewing the style. In no way are such roads part of the road network either. Nor does that change just because of how far the track road goes for. |
Another example of where the rendering is bad at z13. It really shouldn't look like there's large gabs in the track roads when they don't exist in real life. |
Their rendering tends to get kind of wacky at those zoom levels. Especially when there are multiple track roads mapped in the same area or if they are curved. I don't think they need to be rendered at z13 or z14 anyway. Since a lot of them are either private or not generally drivable (I'd be interested to know how many are tagged with surface=asphalt or similar. Whatever the number, they aren't major roads).
Z13
Z14
The text was updated successfully, but these errors were encountered: