NYC area notes (mostly broken concurrencies)

[si404]

LIRR:

• MonBra has point +DIV_BP that HemBra, OysBayBra, PortJefBra, RonBraGCT and RonBra don't

NYCS:

• A and AOzo have shaping points mid-section BroJct <-> +SKIP_LibAve and +SKIP_LibAve <-> +SKIP_VanSicAve that C does not
• R/S Times Square is not the same as 123/7/NQW Times Square, breaking the yellow trunk concurrency
• F '+DIV_Q_E' isn't in the same place as Q '+DIV_F_N'
• 2 - needs a +DIV_5 label between BroPkE and E180St

MetroNorth:

• NJ PorJerLn missing points that concurrent lines have: *OldBerCouLn_S between +DIV_New and SecJct and shaping point between Rut and +SKIP_Wes

AirTrain:

• Howard Beach and Jamaica routes end at a junction, rather than a station - very different to how every other route we do here operates

[the_spui_ninja]

AirTrain:

• Howard Beach and Jamaica routes end at a junction, rather than a station - very different to how every other route we do here operates

Are you referring to the "Loop" point? Should both continue around the loop again to end at Terminal 1?

[si404]

AirTrain:

• Howard Beach and Jamaica routes end at a junction, rather than a station - very different to how every other route we do here operates

Are you referring to the "Loop" point?

yes

Should both continue around the loop again to end at Terminal 1?

The trains don't, so no - it's Federal Circle they need to go to.

Though, at the moment, service is bi-directional between Howard Beach/Jamaica and Terminal 4 (with no terminal loop), as Terminal 1 station (and the track past it) is closed.

[the_spui_ninja]

Should both continue around the loop again to end at Terminal 1?

The trains don't, so no - it's Federal Circle they need to go to.

Though, at the moment, service is bi-directional between Howard Beach/Jamaica and Terminal 4 (with no terminal loop), as Terminal 1 station (and the track past it) is closed.

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.

[Duke87]

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.