Difference between revisions of "Darwin:Push Port"
PeterHicks (talk | contribs) m (Remove superfluous colon in link) |
PeterHicks (talk | contribs) m (→Data: Include gzip compression) |
||
| Line 15: | Line 15: | ||
A Stomp client is required to connect to the service, and an XML parser is required to make use of the data. [[Darwin:Push_Port_XML_Schemas|XSDs]] for the interface are available. | A Stomp client is required to connect to the service, and an XML parser is required to make use of the data. [[Darwin:Push_Port_XML_Schemas|XSDs]] for the interface are available. | ||
| − | + | Messages are sent individually, not batched, with the message body compressed using gzip. | |
| + | |||
| + | A number of elements are sent inside a [[Darwin:uR_Element|update response]] element, which is in turn nested inside a 'Pport' element: | ||
* [[Darwin:Schedule_Element|Schedule data]] | * [[Darwin:Schedule_Element|Schedule data]] | ||
Revision as of 15:05, 28 January 2015
About
The Darwin Push Port is an XML push feed that continuously streams information about the creation of, and changes to, train schedule records, together with train running predictions made by Darwin.
The Push Port can be filtered to a specific area of interest by TIPLOC, or to provide information for the entire country. Either way, the information delivered is complex and must be properly interpreted before presentation to end users.
The Push Port requires the user to build a database capable of capturing extremely high volumes of information, as well as a query engine to draw the information from your database. There is a large amount of interpretation work involved in this; however this allows substantial flexibility to apply the information to any product within the limitations of your own infrastructure.
Availability
The Darwin Push Port feed is expected to be available by 31st March 2015.
Data
A Stomp client is required to connect to the service, and an XML parser is required to make use of the data. XSDs for the interface are available.
Messages are sent individually, not batched, with the message body compressed using gzip.
A number of elements are sent inside a update response element, which is in turn nested inside a 'Pport' element:
- Schedule data
- Association data
- Actual and Forecast data
- Train Order data
- Status of 'Train Table Suppression' and Station Messages
- Train Alert data
- Tracking ID corrections
- Alarm information
