The JSON feed is a nearly 1-1 direct translation of the Network Rail CIF feed – v29 remains the latest version of that document. RSPS5046 refers to the RSP version of the CIF and should also be best read in context of the NR CIF document, it mentions that it’s derived from it at the start. I would suggest the same for the JSON feed, as those codes are directly lifted from the CIF.
Use the Network Rail CIF appendices to get a list of valid activity codes (or perhaps BPLAN? Someone can correct me here).
A pick up only station would be ‘U ’ rather than just U from memory. An open call is ‘T ’. You will never have a train in the GBTT timed at 0000.
You should use activity codes to get the correct usage of GBTT arr/dep. There are some cases (particularly around the Caledonian Sleeper) where the GBTT times are populated but should not be advertised to the public.
Tom
--
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, visit
https://groups.google.com/d/msgid/openraildata-talk/10f6bb18-cb19-4236-b223-071c51495f70n%40googlegroups.com.
On 25 Feb 2025, at 10:57, Michael Flynn <mi...@a1publishing.com> wrote:On the OpenRailData wiki the link for the spec (https://wiki.openraildata.com/images/2/27/CIF_End_User_Spec_v29.pdf) is to one dated 2015. I have found a more up to date CIF spec (https://www.rspaccreditation.org/downloadPublic.php?DOCUMENT=RSPS5046+P-04-01+Timetable+Information+Data+Feed+Interface+Specification.pdf&ID=1427) dated 2024 from this page on the net, https://www.rspaccreditation.org/publicDocumentation.php#RSPS5xxx.
--
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, visit https://groups.google.com/d/msgid/openraildata-talk/89E2B227-F7F8-4E6C-99AD-1D23DB04CD4F%40poggs.co.uk.
On 25 Feb 2025, at 11:17, Michael Flynn <mi...@a1publishing.com> wrote:>> You will never have a train in the GBTT timed at 0000Is this definitive?
>> A pick up only station would be ‘U ’ rather than just U from memory. An open call is ‘T ’.Yes, I see that, a U and or a T, etc.. My original code will do that (hopefully, I assume:).>> You will never have a train in the GBTT timed at 0000Is this definitive?>> using passing times as an indicator that a service doesn’t stop which is fine for meIt will be good enough for me too, combined with the 0000 dep/arr time, except....where's the activity codes on the JSON feeds? This would be best for me, I wouldn't need to change my logic. I don't see them anywhere though.
On 25 Feb 2025, at 13:35, Michael Flynn <mi...@a1publishing.com> wrote:The original subject seems to have been lost. Are the activity codes left out of the JSON feeds?