If you’re looking at a CIF-format timetable, these are the “associations”. Here’s the relevant line:
AANY39274C904792212122305191111100NPSHDRSFLD TO P
Breaking this down:
AAN: new association
Y39274: UID of the first train (2B60, the 1535 from Sheffield)
C90479: UID of the second train (2B25, the 1712 from Huddersfield)
221212: start date (Dec 12, 2022)
230519: end date (May 19, 2023)
1111100: weekdays this association is valid on (M-F, not weekends)
NP: type of association - NP presumably stands for “next/previous", there’s also JJ and VV for trains joining/dividing
S: date indicator (used to handle the edge case of associations with over-midnight services)
HDRSFLD: the place where the association happens (here, Huddersfield)
two spaces: not entirely sure what these are for, the docs call them “location suffixes” but I don’t think I’ve ever seen them used
T: “diagram type”, apparently always T
O: operating use only (can also be “P” for associations that are documented for passenger use - I believe these are always of type JJ or VV)
many spaces: reserved for future expansion
P: STP indicator, as with standard CIF entries
If you’re looking at the JSON timetable provided by Network Rail, there should be something similar, albeit in a pre-parsed format. Not sure if there’s any way to get association data from Darwin and the like.
Best wishes,
Gaelan
> --
> You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
openraildata-t...@googlegroups.com.
> To view this discussion on the web, visit
https://groups.google.com/d/msgid/openraildata-talk/dee85641-0377-4478-9898-aa5adb87b7c1n%40googlegroups.com.