-
Notifications
You must be signed in to change notification settings - Fork 821
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
make tracks more prominent on z13 and z14 #1591
Comments
This would mean more or less reverting #747 w.r.t. tracks - which i am not too sure is a good idea. Showing all tracks at z=13 is questionable in many areas though - especially of course at low latitudes. At least differentiating grades is fairly pointless. http://www.openstreetmap.org/#map=13/48.0813/7.6565 I would not put too much emphasis of improving readability in forest since forest color is likely to change - see #1242. |
I'd propose to put this on hold because of @matkoniecz's google summer of code project, which is expected to cause major road rendering changes overall. |
some tracks are paved roads (tracktype=grade1) which I think is good to have also on z13. hard to tell the upper tracktype grade... |
I am considering rendering paved tracktype=grade1 tracks like service roads. Function of these roads for pedestrian and cyclists is exactly the same. It is also very similar in case of drivers - both may be used for shortcuts and as first/last part of route but it is not typical, frequently use is restricted. In all cases paved grade1 track is closer to highway=service than to other tracks, though it is the strongest for cyclists (and I am aware about my bias here). The negative side is increased complexity (wait, I though that I mapped highway=track - and I see service road). The positive would be reduced mapping for renderer - I am frequently fixing paved tracks mapped as highway=service. |
@matkoniecz, I mostly agree. tracktype=grade1 and highway=service imply paved and often narrow (single lane) road. There may be still some differences - in some countries it is illegal to drive a motor vehicle on highway=track. |
2015-07-03 18:24 GMT+02:00 Martin Ždila notifications@github.com:
service does not imply a paved road. tracks might be single laned or more
My suggestion would be to add (explicit) access tags accordingly, or you |
The idea of common rendering tracktype=grade1 and highway=service sounds interesting. |
As far as I'm concerned, this is no (longer) an issue - other opinions? |
All the paths, including the tracks, at http://a.tile.openstreetmap.org/14/8135/5332.png are still virtually invisible, although, of course, the decision to remove that information from the map was a conscious one taken for genuine reasons in #747 . I can't see how if that change stays in the issues here can have been resolved? Are there some as-yet-uncommitted changes that would revert some of the changes in 747? |
That is a major improvement, but it will require people accepting that it is probably unrealistic to render tracktype at Z13/14... lets see... |
I would rather accept not distinguishing tracktype at certain zooms than unifiying tracktype=grade1 with service. The latter are different classes of road (agricultural/forest use vs. general access) while the first is (only) about surface. |
Interesting analysis by @imagico about track rendering: |
@imagico, do you think any of the suggestions on your site about this would be implementable? |
The road rendering changes of the ac-style depend on not having purple boundaries and are kind of incompatible with #3467 (well - not strictly technically but design wise they go in a very different direction). |
That's what I was thinking. |
Please make tracks more prominent on zoom 14 and 13 by adding the glow effect as it is on zoom 15+.
On zoom 14 the tracks are very hard to see eg. in forests mostly because of the pattern used (#965).
Zoom 15+ is OK:
Zoom 14 is the least readable:
Zoom 13 is better than 14 because of the missing forest texture, but still should be improved by adding the glow effect as it is on the zoom 15+:
The text was updated successfully, but these errors were encountered: