This is what I've been going off of for routes with a loop at the end (KC Streetcar, Denver L Line):
- If a service runs in a loop at one end and hits multiple stations along the way, the entire loop should be mapped and the endpoint of the line should be the point where the loop closes and two-
Not necessarily saying I have a preference here one way or another but the above is I think why those lines are the way they are.
Yeah, the line ending at a junction point ("Loop") is in line with the draft manual. You'll see this in Chicago too for all the L lines that terminate at the, um, loop.
That said, if someone started a trip on the outbound side of the loop and didn't take a return ride in the opposite direction, they won't be able to map their travels properly without using a DIV point. This could be an argument in favor of running the line concurrent with itself to the first bidirectional station, but... it isn't actually feasible to avoid all cases where someone might need to put a DIV point in their rlist file, so we need a way of enabling that to the non-power user regardless.
Will fix up the other issues, thanks for the review.
