-
Notifications
You must be signed in to change notification settings - Fork 6
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
Processing interrupted connected routes #55
Comments
So are we talking about a whole new set of csv files that indicate when a route that should be treated as a single entity despite existing as multiple disconnected pieces? |
We need a concept first. Maybe we can use _con.csv for it? And yes, the routes should be treated "as one". |
Thinking what the consequences would be to place these entries in the existing _con.csv files. In usai, for example, it might make sense to have the three segments of I-35 (broken up by the I-35E/W splits in Minnesota and Texas) as a single "connected route". Users would then see stats for a single I-35, which would be nice. But what bad things might happen.. hmm.. |
This would be nice for the multiple segments of I-74 (normal & 'Future') in NC. |
Given our current setup, these need to be only with a system. But I'm willing to run an update (maybe onto the test DB) with a few examples (maybe I-35 and the I-74s) to see if there are any unintended consequences. |
True, it always the same system... |
I think the idea in #87 would help here. |
Does it? |
The ideas here seem potentially relevant for the IL 108 ferry split discussion: https://forum.travelmapping.net/index.php?topic=4160 Combining the ideas here with 6-field .list entries could remove one of the reasons people dislike the "split at ferry crossings" rule: it's still a single route so should only count as one route for maps and stats and should require only one .list entry. |
That could be as simple as allowing DISCONNECTED_ROUTE to be marked FP. |
Definitely need a lot more thought and discussion before doing anything like this. |
yep! Still a long way. We need a concept first! |
http://tm.teresco.org/forum/index.php?topic=1888
I guess we need new system csv files or have to extend the _con.csv files.
However, a concept is needed first.
The text was updated successfully, but these errors were encountered: