Latest revision as of 13:20, 2 July 2024

The Rail Data Marketplace is a rail data platform operated by the Rail Delivery Group. Some existing open feeds are also offered through the marketplace, some new feeds are only offered through the marketplace.

Background

The RDG states that the Rail Data Marketplace originates in the Joint Rail Data Action Plan, and Williams-Shapps Plan for Rail.^[1]

The Joint Rail Data Action Plan is a policy paper published in 2018, which sought to increase rail data sharing across the industry, and which criticised the "perceived closed nature of the railway industry";^[2] The Rail Delivery Group committed in the joint action plan to publishing the CTI and CIGP feeds through the NRDP, but failed to do so. The Williams-Shapps Plan for Rail outlined the strategy and objectives of an "open by default" Rail Data Service under the proposed Great British Railways.^[3]

In 2021, the Department for Transport announced £5 million in government funding for a new Rail Data Marketplace,^[4] with the Rail Delivery Group selecting Tata Consultancy Services to develop the platform.^[5]

Feeds

A summary of some feeds is available here. Every feed requires a separate subscription, and agreement by the user to a separate licence agreement. There are three types of feed - files, streaming, and APIs. Streaming feeds are offered via Apache Kafka (STOMP and OpenWire are unavailable). There's no officially documented or supported mechanism for retrieving files from the Rail Data Marketplace in software.

Substitutions

Some fares, timetable, and routeing file feeds can be replaced with DTD files, which can be retrieved automatically from the NRDP.
KB feeds are APIs – not files – on the RDM, but it may still be more convenient to access these through the NRDP instead of the RDM, as you'll only need to enable one subscription, with one set of secrets.
Similarly, it may be more convenient to use the LDB SOAP service instead of the RDM offering, which is split across multiple endpoints, with separate secrets.
The "Staff Version" web service on the RDM doesn't currently work, the LDBSVWS SOAP service is the only alternative (see here for special registration information about LDBSVWS).

Criticism

The Rail Data Marketplace is controversial among feeds users. ^[6]^[7]^[8]

References

[1] ttps://raildata.org.uk/dashboard/helpAndInformation/aboutRDM

[2] ttps://www.gov.uk/government/publications/joint-rail-data-action-plan/joint-rail-data-action-plan-addressing-barriers-to-make-better-use-of-rail-data

[3] ttps://assets.publishing.service.gov.uk/media/60cb29dde90e0743ae8c29c1/gbr-williams-shapps-plan-for-rail.pdf (56)

[4] ttps://www.gov.uk/government/news/data-revolution-set-to-improve-rail-travel-for-passengers

[5] ttps://www.tcs.com/who-we-are/newsroom/press-release/rail-delivery-group-selects-tcs-to-help-create-uk-government-rail-data-marketplace

[6] ttps://groups.google.com/g/openraildata-talk/c/T1ejY551ZUw/m/Hjpd4YdFBgAJ

[7] ttps://groups.google.com/g/openraildata-talk/c/xbqi6dOP4XU/m/Tcw3M_PTBAAJ

[8] ttps://groups.google.com/g/openraildata-talk/c/qAErlL2oRxc/m/TgiMq9QaAwAJ

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

@@ Line 16: / Line 16: @@
 * Similarly, it may be more convenient to use the LDB [[NRE_Darwin_Web_Service_(Public)|SOAP service]] instead of the RDM offering, which is split across multiple endpoints, with separate secrets.
 * The "Staff Version" web service on the RDM doesn't currently work, the LDBSVWS [[NRE_Darwin_Web_Service_(Staff)|SOAP service]] is the only alternative (see [[About_the_National_Rail_Feeds#Registering_for_OpenLDBSV.2FDarwin_Staff_Webservice|here]] for special registration information about LDBSVWS).
-* The "Darwin Real Time Train Information" feed on the RDM is the only pub/sub feed, but doesn't work. That aside, it's only offered in an alternative schema-less JSON format, and via Apache Kafka, instead of the more conventional OpenWire or STOMP. The only alternative is the NRDP's [[Darwin:Push Port|push port]].
 = Criticism =