Author Topic: NYC area notes (mostly broken concurrencies)  (Read 4947 times)

0 Members and 1 Guest are viewing this topic.

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2074
  • Last Login:Today at 07:34:29 am
NYC area notes (mostly broken concurrencies)
« on: September 25, 2023, 12:04:47 pm »
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

Offline the_spui_ninja

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 805
  • Last Login:Yesterday at 10:05:50 am
  • THE Western SD Highway Nut
Re: NYC area notes (mostly broken concurrencies)
« Reply #1 on: September 25, 2023, 04:46:49 pm »
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?
An adventure is only an inconvenience rightly considered. An inconvenience is only an adventure wrongly considered. - G.K. Chesterton

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2074
  • Last Login:Today at 07:34:29 am
Re: NYC area notes (mostly broken concurrencies)
« Reply #2 on: September 25, 2023, 04:56:58 pm »
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
Quote
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.

Offline the_spui_ninja

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 805
  • Last Login:Yesterday at 10:05:50 am
  • THE Western SD Highway Nut
Re: NYC area notes (mostly broken concurrencies)
« Reply #3 on: September 25, 2023, 05:18:44 pm »
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.
An adventure is only an inconvenience rightly considered. An inconvenience is only an adventure wrongly considered. - G.K. Chesterton

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1020
  • Last Login:Yesterday at 10:18:20 pm
Re: NYC area notes (mostly broken concurrencies)
« Reply #4 on: September 25, 2023, 07:50:34 pm »
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.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4436
  • Last Login:Yesterday at 10:28:37 pm
  • I like C++
Re: NYC area notes (mostly broken concurrencies)
« Reply #5 on: October 02, 2024, 09:01:38 pm »
kevinmc.log:NY: duplicate label CHAST in ny.j
kevinmc.log- Please report this error in the Travel Mapping forum.
kevinmc.log- Unable to parse line: NY J CanSt ChaSt
--
yakra.log:NY: duplicate label 36ST in ny.r
yakra.log-  Please report this error in the Travel Mapping forum.
yakra.log-  Unable to parse line: NY R 36St UniSt
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1020
  • Last Login:Yesterday at 10:18:20 pm
Re: NYC area notes (mostly broken concurrencies)
« Reply #6 on: October 04, 2024, 05:48:09 pm »
Ah yes, the R train stopping at 2 unrelated stations both named "36 Street". A less-noticed sibling to the B train stopping at 2 unrelated and both fairly prominent stations both named "7 Avenue".

https://github.com/TravelMapping/RailwayData/pull/215

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4436
  • Last Login:Yesterday at 10:28:37 pm
  • I like C++
Re: NYC area notes (mostly broken concurrencies)
« Reply #7 on: October 07, 2024, 05:24:50 pm »
Looks like the _Bro & _Que suffixes got reversed.

Funny thing is, I don't need to fix my .rlist right away; despite the broken line my travels on the R train are accounted for via concurrency augments. :D
« Last Edit: October 07, 2024, 05:29:11 pm by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca