Skip to content
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

Merge #tracks-notunnel-nobridge into #roads-fill #174

Merged
merged 5 commits into from
Sep 21, 2013

Conversation

matthijsmelissen
Copy link
Collaborator

The layer #tracks-notunnel-nobridge has been merged into #roads-fill.

This unifies the various track-definitions.

Rendering changes:
The rendering order of tracks versus other roads is now determined by z_order.
Therefore, tracks are now rendered at the same level as service roads, footways, cycleways, and paths, instead of below them.
The rendering of the tracks themselves has not been altered.

The layer order used to be as follows.

(bridges)                           B
direction-pre-bridges.directions    R
access-pre-bridges.access           R
waterway-bridges                    R/B
roads-low-zoom                      R/B
aerialways                          R/B
ferry-routes                        T/R
turning-circle-fill                 R
roads-fill                          R
tracks-notunnel-nobridge            R
buildings                           ???
buildings-lz                        ???
highway-area-fill                   R
roads-casing                        R
highway-area-casing                 R
area-barriers.barriers              T/R
cliffs                              T/R
line-barriers.barriers              T/R
tracks-tunnels                      T
footbikecycle-tunnels               T
turning-circle-casing               R
landuse-overlay                     T/R
castlewalls-poly.castlewalls        T/R
castlewalls.castlewalls             T/R
citywalls                           T/R
tunnels                             T

I classified all layers between and including the bridge-layers and the tunnels-layer with one of the following classifications:

B    Bridge level.
R/B  Above roads but below bridges.
R    Road level.
T/R  Above tunnels but below roads.
T    Tunnel level.

I grouped all of the layers within one class together, without changing the order within the classes. For now, I ignored the buildings-layers, due to the difficulties with ordering buildings, highways and highway-areas described in gravitystorm#172.

This change causes a couple of changes in the rendering, which mainly occur in rare cases.
- Casings of turning circles are now drawn above foot/bike/track tunnels (they were already drawn above other tunnels), and above cliffs and barriers (just like other roads are drawn above cliffs and barriers).
- Landuse-overlays (i.e., military and national park), castlewalls, and citywalls are now drawn above foot/bike/track tunnels (they were already drawn above other tunnels).
- Ferry-routes are now drawn below roads (highways, tracks, turning-circles, and highway-areas).
- Railways on level 12 (due to the #roads-low-zoom layer), aerialways, and waterway-bridges are now drawn above access and directions markers of roads (they were already drawn above the roads themselves).
The layer #tracks-notunnel-nobridge has been merged into #roads-fill.

This unifies the various track-definitions.

Rendering changes:
The rendering order of tracks versus other roads is now determined by z_order.
Therefore, tracks are now leveled at the same level as service roads, footways, cycleways, and paths, instead of below them.
The rendering of the tracks themselves has not been altered.
@matthijsmelissen
Copy link
Collaborator Author

This is step 3 of #162.

Oops, roads should only render from level 13 on.
Make sure that tracks without tracktype render as before merging #tracks-notunnel-nobridge into #roads-fill, by providing defaults.
@gravitystorm gravitystorm merged commit 6bdf373 into gravitystorm:master Sep 21, 2013
@matthijsmelissen matthijsmelissen deleted the roadsv3.0 branch December 2, 2013 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants