Tracks too dominant on z13 #620
Comments
|
Yeah I agree could we drop them for that zoom level or make them thinner. I forget do we have easy access to a length of a way a way_length (not sure if way_area works the for that or just closed ways) as an idea (not thought about it too greatly...maybe problems with it) can be really long ones we can render them on that zoom level. |
What about really long tracks that are represented by many small ways? |
|
Tracks are odd. At the high end, they're like roads, at the low end they're like paths. I think track grade is the way to go here, if we're making distinctions. I'd be happy to see them appearing like something between an unclassified road and a service road for the better built grades, but not for less imposing forms (If the road you want to map is an official road in a region, or the only thing linking towns and villages or other centres of population, it should be tagged as highway=unclassified or greater instead even if it's unsurfaced. That hierarchy already covers "importance for the general map user".) Maybe the more roadlike forms (grade1, maybe grade 2) could have a more roadlike rendering? Only using brownscale rather than greyscale. The more pathlike forms perhaps keeping something akin to the current rendering, but less intense. Same browns for all types, for consistency? |
|
2014-06-13 13:21 GMT+02:00 Andrew Chadwick [email protected]:
yes, wouldn't use more than one type of brown, (for simplicity, |
|
I find the Morse Code dashes the style currently uses a little hard to follow in crowded plantation-y woodland too: http://www.openstreetmap.org/?mlat=51.7932&mlon=-1.0957#map=13/51.7932/-1.0957 I gather they're for distinguishing track grades and surfaces, and fair enough. Even so, if dashes are still going to be used for some tracks, could the dashes be made regular? |
- Make paths and tracks less visible on z13/z14, by making them narrower and remove the casing at these zoomlevels. This declutters in high-density environments, while at the same keeping the paths and tracks visible in low-density environments. - Hide private paths and tracks on z13/z14. - Define path/track widths with variables. - Make widths of path/track bridges and tunnels more consistent. - Add rendering for steps in tunnels. - Add background (glow) to steps, just like footways. This solves the following issues: * gravitystorm#211 (Poor result of rendering areas with many footways in zoom level 13) * gravitystorm#620 (Tracks too dominant on z13) * Trac 1508: don't render tracks of high tracktype at low zoom (-> wontfix) * Trac 3788: Don't render highway=track, access=private at z13&14 * Trac 4015: Rendering of highway=path with access=no is inconsistent * gravitystorm#634: private footways should not be rendered up to z13
- Make paths and tracks less visible on z13/z14, by making them narrower and remove the casing at these zoomlevels. This declutters in high-density environments, while at the same keeping the paths and tracks visible in low-density environments. - Hide private paths and tracks on z13/z14. - Define path/track widths with variables. - Make widths of path/track bridges and tunnels more consistent. - Add rendering for steps in tunnels. - Add background (glow) to steps, just like footways. This solves the following issues: * gravitystorm#211 (Poor result of rendering areas with many footways in zoom level 13) * gravitystorm#620 (Tracks too dominant on z13) * Trac 1508: don't render tracks of high tracktype at low zoom (-> wontfix) * Trac 3788: Don't render highway=track, access=private at z13&14 * Trac 4015: Rendering of highway=path with access=no is inconsistent * gravitystorm#634: private footways should not be rendered up to z13
|
Closed by #747. |
On z13, tracks are currently too dominant, especially with tracktype=grade1. They are more dominant than highway=unclassified, which should be the other way around.
Example.
The text was updated successfully, but these errors were encountered: