Thanks for the info and other suggestions guys. Nice to know I can rely on the version number for cleared incidents. I guess I'll just have to suck it up for public transport messages and find a workaround.
Mike ________________________________ From: Brian Butterworth <[email protected]> To: [email protected] Sent: Tuesday, 6 January, 2009 11:34:18 Subject: Re: [backstage] Travel feed data.... I don't know if this is any help... http://www.dft.gov.uk/transportdirect/tools/intelligentlinks 2009/1/6 Peter Schofield <[email protected]> Hi Mike, You are correct in deducing that road traffic messages are cleared when their version number is set to 255. It does always work. We have had issues in the past were incident version numbers incremented above 255 (particularly after an incident was cleared, then updated to become active again), but this has now been fixed. Cleared messages are now always set to 255. As regards the point about public transport nodes always being set as 'railway service', this is due to a limitation in our service provider's description of incidents. Hope this helps. Best regards, Peter. -- Peter Schofield, Travel Content Producer, BBC English Regions (New Media) Area F1, Level 10, BBC Birmingham, The Mailbox, BIRMINGHAM B1 1RF. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Mike Moody Sent: 05 January 2009 16:48 To: [email protected] Subject: [backstage] Travel feed data.... I'm wondering if one of you good fellows can help me....? I am in the process of writing a vista gadget (similar to the ones produced by the daily snooze) that consumes the BBC travel feeds. The idea is to provide a gadget that can display the latest travel information for a specified area. The development is done (for the most part) but I'm having some specific problems with the data within the XML feeds: For Road traffic messages... The only way I can see to tell if a road incident has been cleared is if the version_number attribute on the road_traffic_message node is set to 255. This seems very arbitrary and I'm not sure if it always works... For other (public transport) messages... Each item has a transport_mode node (with an attribute of the same name) on the root public_transport_information node. I assumed that this transport_mode sub-node described the type of transport mode for the item.... however it is always "railway service" (entity reference: pti1_1) regardless of whether the node describes air, ferry or railway information. Any help / clarification on these would be most helpful. Mike -- Brian Butterworth follow me on twitter: http://twitter.com/briantist web: http://www.ukfree.tv - independent digital television and switchover advice, since 2002
