Open zerebubuth opened 7 years ago
Related: I sometimes see inbound and outbound route shapes in the transit
layer. That's a similar problem, but if we want to tackle that should be done in a separate ticket.
if we want to tackle [de-duplicating inbound and outbound route shapes] should be done in a separate ticket.
Yup, definitely! De-duping shapes is way harder than just de-duping the network name and shield text. We'd be looking at something like skeletron for the shape stuff.
Skeletron, ftw :)
On Wed, Apr 12, 2017 at 10:21 AM, Matt Amos notifications@github.com wrote:
if we want to tackle [de-duplicating inbound and outbound route shapes] should be done in a separate ticket.
Yup, definitely! De-duping shapes is way harder than just de-duping the network name and shield text. We'd be looking at something like skeletron for the shape stuff.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tilezen/vector-datasource/issues/1204#issuecomment-293648878, or mute the thread https://github.com/notifications/unsubscribe-auth/AA0EOw9dlINwWyXySCDwy8x7GtJ7KwZ-ks5rvQg2gaJpZM4M7Hg0 .
A road is quite often part of two bus routes, one for "inbound" and the other "outbound" in reverse. For the purposes of cartography, these are not really two separate routes.
Where the road is part of both inbound and outbound routes, they should be collapsed to a single entry in the
all_*_networks
andall_*_shield_texts
lists.@nvkelso, do we want to distinguish the de-duplicated value from the originals in some way? So that it's possible to tell the difference between a road that the bus goes along in both directions from a road that only has busses going one way or the other.
E.g: Jackson St. SF, part of trolley-bus route 3 (inbound, outbound).