Schedule in JSON format and CR records.

[Paolo Ferracin]

Hello!

I migrated the schedule importer in my software from CIF format to JSON format, but there is something that doesn't add up to me.

In the JSON format I can't find any element resembling the CR (Changes end Route) record of the CIF; the information of the BS and CR record appears to be contained in the schedule_segment object, but there is only one segment for each schedule. Where are the changes recorded?

I would be interested in speed changes in particular (Speed field of BS and CR records).

For example, this schedule has a speed change from 110 to 100 mph in the CIF file:

BSNP719702305212312030000001 POO2Y582094112259320 EMU506 110      S S          P

BX         LMY

LOBHAMNWS 2210 22104A WL     TB

...

LIBLTCHLY 2347 2348H     234723484  SL SL T

CRLTNBZRD OO2Y582116122209000 EMU350 100      S S

LILTNBZRD 2354H2355H     23552355         T           4

...

but in the JSON it's all 110 mph. There is only one speed for the whole schedule:

 "CIF_speed": "110"

The VSTP suffers from the same problem: syntactically there may be more than one schedule_segment (it's an array), but from a quick analysis there is always only one element in the array, even where I would expect a Change en Route.

Any advice would be appreciated.

Thanks

Paolo

[Peter Hicks (Poggs)]

Hi Pablo

> On 21 Aug 2023, at 13:56, Paolo Ferracin <paolo.f...@gmail.com> wrote:
>
> In the JSON format I can't find any element resembling the CR (Changes end Route) record of the CIF; the information of the BS and CR record appears to be contained in the schedule_segment object, but there is only one segment for each schedule. Where are the changes recorded?

Change-en-Route records aren’t supported in the JSON-format schedule data, so you won’t see them.

> The VSTP suffers from the same problem: syntactically there may be more than one schedule_segment (it's an array), but from a quick analysis there is always only one element in the array, even where I would expect a Change en Route.

Although the functionality exists to have more than one schedule_segment in a VSTP message, in practice the source systems (primarily TRUST/TSI) don’t support change-en-route functionality in VSTP messages. In fact, you can put in any kind of point-to-point timing in to TRUST for a VSTP and it’ll be accepted, subject to a small number of rules.


Peter

[Paolo Ferracin]

Hi Peter,

Thanks, that's not the answer I was hoping for, but at least now I can stop searching for an information that doesn't exist :)