--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.
Hi Seb,
Afraid we don't use the RDM variant so can't say if we saw that issue or not.
Thanks for that - I can't remember where but I'd read that it's possible to use the CIF timetable as a base.
You might expect this to be the case! But Darwin unfortunately messes with the base timetable from the CIF in ways that can cause problems here.
The one that comes to my mind first is when a TOC cancels a service in Darwin using its extended horizon feature (so before it is published in the Darwin timetable), Darwin will simply omit the service when it does come to publish the timetable for that day instead of correctly publishing a cancelled schedule. Anyone using the CIF as a base would [arguably correctly] show there was a service running as planned, and would just never receive any realtime updates for it. I'm sure there are plenty of other examples of similar behaviour that would cause you issues.
Plenty of us working with both Darwin data and services beyond its horizon already do this and have no choice but to put up with these issues - broadly it does work. But there are definitely gotchas and drawbacks you need to be aware of.
Kind regards,
Oscar
To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/3cc0c25e-c2bd-4c9e-8faf-6f47e868440b%40app.fastmail.com.
To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/70b9b8d8-4cf2-413b-adfa-173a02d6ac26%40oscar-h.com.Attachments:
- OpenPGP_0xAA289EB63EA8D499.asc
- OpenPGP_signature.asc