Closed nvkelso closed 8 years ago
Perhaps these should end up in the transit layer, rather than the roads layer? They'd end up with kind=ferry
by default, it looks like.
We pack railway
in the roads layer now and a good number of ferries are more part of the road network than the public transit network, so we already have the "not road things drawing sometimes as roads" in a default styling problem. I'd rather keep the transit
layer for things that are specifically public transit.
Reading up on the wiki, it looks like ferry=*
should be included (at least for a minimum set of popular values, like we currently do for roads), and with the high-road logic extended to set kind=ferry
.
Default OSM styling shows these coming in very early (8 or 9 I remember)? Should we do that or throttle it based on the ferry=* value (like we do for roads)?
After mapzen/TileStache#64 and #281, it looks like this:
@nvkelso could you review, please?
I dig it :)
Considerations:
On Thu, Oct 1, 2015 at 2:54 PM, Matt Amos notifications@github.com wrote:
@nvkelso https://github.com/nvkelso could you review, please?
— Reply to this email directly or view it on GitHub https://github.com/mapzen/vector-datasource/issues/187#issuecomment-144860804 .
@rmarianski Was this taken to dev
? I'm not seeing ferry lines in SF or NYC tiles, for instance NYC:
I took master, but it looks like this pr hasn't been merged yet: https://github.com/mapzen/vector-datasource/pull/281
I've merged this one now (the TileStache change was already merged).
I see these in NYC and SF now, thanks!
Routes that go from land to water to land again show gaps in the map today for the ferry part, let's fill those in.
Read up: https://wiki.openstreetmap.org/wiki/Tag:route%3Dferry
Sounds like it has the same general structure as roads with the highway tag but are route=ferry for the primary distinction.
Let's brainstorm how we want these kinds to end up in tiles (we don't want them to default render as roads).