[Open-transport] Coverage of GTFS-RT feeds in the world

Pieter Colpaert pieter.colpaert at okfn.org
Fri Oct 14 13:44:08 UTC 2016

Hi Christophe,

Thank you for that clarification! I am going to study SIRI more carefully!

Kind regards,


On 14-10-16 15:14, Christophe Duquesne-Aurige wrote:
> Bonjour à tous Just a few complement about the European Commission's 
> DG Move making the use of Netex and Siri mandatory
> One of the reasons is that they want to rely on CEN standards but also, as you said, because of the wider scope of Siri and NeTEx.
> But your statement is not perfectly right: SIRI is not only connected to SOAP: France made that choice for back-office communication only (not for communication with end users), and this is not the case of all other countries.
> Furthermore there is a REST based (usually using JSON) transport layer in SIRI: you can try this for examplehttp://appli.chouette.mobi/siri_lite/siri/2.0.0/stop-monitoring?RequestorRef=NINOXE:default&MonitoringRef=NINOXE:StopPoint:SP:18:LOC&MaximumStopVisits=3   and check some open source tool and info herehttps://github.com/afimb/siri_lite  and herehttp://www.chouette.mobi/irys/utiliser-irys/siri-lite/
> Another point is that GTFS-RT is a line-centric service, very efficiently designed and optimized for global back-office exchange, but it doesn't provide a stop-centric REST API for end users as SIRI does with, for example, Stop Monitoring (where you can request something like the next 3 passing times for each line at a stop).
> I don't think we should see any competition between GTFS, GTFS-RT, SIRI and NeTEx: they are all good, and all have their pros and cons. What we just need is that people use one of them to provide their data, just choosing the one they prefer or the one which best suits their needs (and using several of them is an option ;-) ).
> Kind regards,
> Christophe

+32 486 74 71 22

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-transport/attachments/20161014/4d9f0c75/attachment-0002.html>

More information about the open-transport mailing list