Open Feeds - Schedule Format Document

Mae'r cais hwn wedi cael ei dynnu'n ôl gan y sawl a'i wnaeth. Efallai y bydd esboniad yn yr ohebiaeth isod.

Dear Network Rail Limited,

I've become stuck making use of the JSON formatted schedule feed, specifically I can't find information about the keys used for a TIPLOC update row and one hasn't appeared recently enough for me to look at (and work out for myself).
So I would like a copy of the document specifying the format of the JSON appearing in the schedule feed, whilst I'm asking please can I have the same for the CIF version of the feed too.
If for some reason that is unavailable then please provide an example of a line which would appear in the JSON file to communicate that a TIPLOC has been updated.

Yours faithfully,

Robert Gauld

Gadawodd Peter Hicks anodiad ()

See https://wiki.openraildata.com/index.php/... for details of the JSON schedule file record format

Gadawodd Robert Gauld anodiad ()

Thank Peter I'd already found that, indeed I've been using that site a lot recently. Unfortunately in the case of an updated TIPLOC the fields listed on that page don't allow for inclusion of the new_tiploc and old_tiploc like the CIF format does. Wanting to know what those fields are called I thought I'd try to get the document they were likely to quote from so that I had it handy for any future questions I have.

Gadawodd Peter Hicks anodiad ()

The JSON format data has no concept of an 'update' record - these records are replaced with a 'delete' and then a 'create' immediately after. So if TIPLOC 'ABCDE' for a location was replaced with 'ABCDEZ', you'd receive a delete record, and then a create record.

Gadawodd Robert Gauld anodiad ()

Thank you Peter, it would appear to be an error on the wiki page we both looked at then, which states "create, update or delete" for the transaction_type field.

Dear Network Rail Limited,

Another user of whatdotheyknow.com has informed me that the JSON format of the schedule format has no concept of an update, dealing with these as a delete followed by a create. Since this holds with what the open rail data wiki states about the other types of record within the JSON format and I see no reason why TIPLOCs would be treated differently I'd like to withdraw my request.

Yours faithfully,

Robert Gauld

Gadawodd Peter Hicks anodiad ()

I wrote the wiki, let me get it fixed for you!