l

Brendan O’Brien Head of Technical Services Dublin City Council

Real Time Passenger Information

Real Time Passenger Information

RTPI an essential element of any modern Transport system

Takes the guesswork out of when your bus will arrive.

Makes it possible to plan and reduces waiting on street.

Provides a public face on how a service operates.

DCC since 1994 had wanted to introduce RTPI but technically not

possible until fleet equipped.

When in 2009 RTPI was finally approved –

Dublin City Council Traffic Department undertook the task of

delivering it initially in Dublin and then throughout the country.

Real Time Passenger Information

Integrated Transport Products

Integrated Public Products Integrated Real Time Integrated Ticketing Integrated Journey

Planner

Virtuous Circle

The data behind these products assists regulatory control to improve services and produce better information for to the public

INFORMATIONReal Time

Journey PlannerLeap Card

More Information for Service analysis

Monitoring and Improving Public

Transport Contracts

Real Time Information

3 Main Elements to the National Real Time Information Programme

1. Working with Public Transport Operators to ensure accurate predictions

2. Delivering integrated real time information to on street displays in Greater Dublin Area, Cork, Galway, Limerick and Waterford

3. Delivering integrated real time information for Bus, Luas and Irish Rail via www.TransportforIreland.ie, smartphone apps and sms services.

The Real Time System

CENTRAL RTPI

SERVER

SignsSMS service

Website and Apps

Other Operators

No Server & Time estimation system

AVL = Automatic Vehicle Location

Luas Dublin Bus Bus Éireann Irish Rail

Information Cycle

Service control

On Vehicle/• Prediction

s• Ticketing• On Bus

info

Bus Statistics

Route Planning

Schedules

NTA/Operator

Punctuality, Reliability, % operated, where delays occur

Data Cycle for RTPI

Service control

Vehicle• Predictions

• Ticketing• On Bus info

Bus Statistic

s

Route Plannin

g

Schedules

Operator Data

system

Control CentreCurtailments cancellations

AdditionsCrisis

Management Agreed schedule

Real timeSigns, Web,

etc..

RTPI central system

On Vehicle System

AVLC RTPI Data

PublishedLineName>123</PublishedLineName>   <OperatorRef>bac</OperatorRef>   <DestinationRef>MARINO</DestinationRef>   <DestinationName>Marino via O'Connell Street</DestinationName>   <Monitored>true</Monitored>   <InCongestion>false</InCongestion>   <BlockRef>123006:31</BlockRef>   <VehicleRef>28023</VehicleRef> - <MonitoredCall>  <VisitNumber>28</VisitNumber>   <VehicleAtStop>false</VehicleAtStop>

 

  <AimedDepartureTime> 2010-03-08 T13:21:22 <

  <ExpectedDepartureTime> 2010-03-08 T13:22:42 <

Web Site and Web Uses SIRI ET ( Estimated Timetable ) Dublin Bus

Journey Centric with ref to Timetable contained in VDV 452 Not suitable for use in Displays on Street as no Clear Down. Same updates as with SM but much less data Transfer as it

tracks a journey and visits to each stop.

Uses VDV 454 ( Estimated Time Table ) Bus Eireann Not suitable for use in Displays on Street as no Clear Down. Same updates as with SM but much less data Transfer as it

tracks a journey and visits to each stop.

Multi Operator Bi-Lingual Website

Interchange Display

• For Train/Bus Station • Airport

• Hospital

•Multiple Stops

•Multiple Operators

SMS service

Website

Server & time estimation system

AVL-equipped fleet Trapeze

Server & time estimation system

GPRS comms

Radio comms

Other Bus operators

AVL-equipped fleet Init

Not AVL-equipped

No Server & Time estimation system

DCC CENTRAL RTPI

SERVER

APP

Luas Irish Rail Track based estimation

SM feed

VDV 453 SM feed

SM feed to both website and signs

SM feed

ET feed

VDV 454

Direct feed from API to App only

ET feed to National Journey Planner

ET feed

Api database open sky – will facilitate public API also

Access to Data ( Open Data Sharing )

• Provide Open data access for third Party Developers.

• Published Web Services Interface.

• Allows access to all RTPI data in the System.

• Queries can be made on Bus Stops.

• Currently being tested for DCC developed APP .

• Service hosted in the “Cloud “

• In Line with DUBLINKED initiative.

RTPI System

Web Services

SIRI SM Open Data Platform

Bus Stops and Services File Path:  

Operator Code bac

ServiceID 8208

ServiceRef 00016005

Valid Days Sa

Direction Inbound

PublicServiceCode 16

 

JourneyRef 11263 11274 11291 11297 11313 11326 11261

JourneyStartTime 06:30 06:45 07:00 07:15 07:30 07:45 08:00

Runningboard 16002 16003 16005 16007 16009 16011 16001

Default headway (hh:mm)

 

Stop Ref Stop Name

05171 Brehon Field Rd 06:30 06:45 07:00 07:15 07:30 07:45 08:00

02976 Brehon Field Rd 06:31 06:46 07:01 07:16 07:31 07:46 08:01

02977 Brehon Field Rd 06:32 06:47 07:02 07:17 07:32 07:47 08:02

02978 Grange Road 06:33 06:48 07:03 07:18 07:33 07:48 08:03

02979 Grange Road 06:33 06:48 07:03 07:18 07:33 07:48 08:03

02980 Grange Road 06:34 06:49 07:04 07:19 07:34 07:49 08:04

02981 Grange Road 06:35 06:50 07:05 07:20 07:35 07:50 08:05

02991 Grange Road 06:36 06:51 07:06 07:21 07:36 07:51 08:06

02992 Grange Road 06:36 06:51 07:06 07:21 07:36 07:51 08:06

01325 Grange Road 06:36 06:51 07:06 07:21 07:36 07:51 08:06

01326 Grange Road 06:37 06:52 07:07 07:22 07:37 07:52 08:07

01327 Grange Road 06:37 06:52 07:07 07:22 07:37 07:52 08:07

01328 Grange Road 06:37 06:52 07:07 07:22 07:37 07:52 08:07

01329 Grange Road 06:39 06:54 07:09 07:24 07:38 07:53 08:08

01330 Grange Road 06:39 06:54 07:09 07:24 07:38 07:53 08:08

01331 Rathfarnham Rd 06:40 06:55 07:10 07:25 07:39 07:54 08:09

01332 Rathfarnham Rd 06:41 06:56 07:11 07:26 07:40 07:55 08:10

01333 Rathfarnham Rd 06:42 06:57 07:12 07:27 07:41 07:56 08:11

01334 Rathfarnham Rd 06:42 06:57 07:12 07:27 07:41 07:56 08:11

07293 Rathfarnham Rd 06:42 06:57 07:12 07:27 07:41 07:56 08:11

01335 Rathfarnham Rd 06:43 06:58 07:13 07:28 07:42 07:57 08:12

Type of Information available Retrieve real time bus information for

given stop number. Filtered by route and Operator

Retrieve Timetable Bus Information by Date Filtered by Operator, route, Date and Stop ID

Retrieve Full Timetable Bus Information Retrieve Bus Stop Information Retrieve Route Information Retrieve Real Time Route ( Bus position )

Information ( later release)

Method to retrieve real time bus information for given stop number and

route

stopid - required, existing bus stop id routeid – optional, route identifier maxresults – optional, maximum number of results, if not

provided system will limit number of results depending on server configuration

operator – optional, bus service operator (e.g. DublinBus), if not provided information for all providers is returned

format – optional, valid values: xml, json; if not provided JSON format is used by default

Stop Information- <busstopinformation  <errorcode>0</errorcode>   <errormessage />   <numberofresults>1</numberofresults>   <timestamp>05/12/2012 16:21:22</timestamp> -  <stopid>184</stopid>   <displaystopid>184</displaystopid>   <shortname>Botanic Rd</shortname>   <shortnamelocalized>Botanic Rd</shortnamelocalized>   <fullname>Cliftonville Road</fullname>   <fullnamelocalized>Cliftonville Road</fullnamelocalized>   <latitude>53.369695</latitude>   <longitude>-6.2689711111</longitude>   <lastupdated>31/10/2012 15:17:34</lastupdated> - <operators>- <operator>  <name>bac</name> - <routes>  <route>4</route>   <route>83</route>   <route>9</route>  

Time Table Info <numberofresults>45</numberofresults>   <stopid>184</stopid>   <timestamp>05/12/2012 16:27:31</timestamp> - <results>- <result>  <arrivaldatetime>05/12/2012 16:33:00</arrivaldatetime>   <destination>Monkstown Ave</destination>   <destinationlocalized>Monkstown Ave</destinationlocalized>   <operator>Dublin Bus</operator>   <lowfloorstatus>no</lowfloorstatus>   <route>4</route>   </result>- <result>  <arrivaldatetime>05/12/2012 16:48:00</arrivaldatetime>   <destination>Monkstown Ave</destination>   <destinationlocalized>Monkstown Ave</destinationlocalized>   <operator>Dublin Bus</operator>   <lowfloorstatus>no</lowfloorstatus>   <route>4</route>   </result>- <result>  <arrivaldatetime>05/12/2012 16:48:00</arrivaldatetime>   <destination>Monkstown Ave</destination>   <destinationlocalized>Monkstown Ave</destinationlocalized>   <operator>Dublin Bus</operator>   <lowfloorstatus>no</lowfloorstatus>   <route>4</route>   </result>

Real Time Information <numberofresults>5</numberofresults>   <stopid>184</stopid>   <timestamp>05/12/2012 16:25:05</timestamp> - <results>- <result>  <arrivaldatetime>05/12/2012 16:27:37</arrivaldatetime>   <duetime>2</duetime>   <departuredatetime>05/12/2012 16:27:37</departuredatetime>   <departureduetime>2</departureduetime>   <scheduledarrivaldatetime>05/12/2012 16:21:00</scheduledarrivaldatetime>   <scheduleddeparturedatetime>05/12/2012 16:21:00</scheduleddeparturedatetime>   <destination>Limekiln Avenue</destination>   <destinationlocalized>Ascl. na Tiníleach</destinationlocalized>   <origin>Charlestown Rd</origin>   <originlocalized>Charlestown Rd</originlocalized>   <direction />   <operator>bac</operator>   <additionalinformation />   <lowfloorstatus>no</lowfloorstatus>   <route>9</route>  

Method to retrieve real time bus information for given stop number and route

XML:

<realtimeinformation> <errorcode>[Error code]</errorcode> <errormessage>[Additional error details]</errormessage> <numberofresults>[Number of results]</numberofresults> <stopid>[Stop Id]</stopid> <timestamp>[Date/time information returned]</timestamp> <results> <result> <arrivaldatetime>[Arrival time in dd/MM/yyyy HH:mm:ss

format]</arrivaldatetime> <destination>[Service destination name]</destination> <destinationlocalized>[Translated service destination

name]</destinationlocalized> <operator>[Bus service operator name]</operator> <lowfloorstatus>[Bus low floor status (yes or no)]</lowfloorstatus> <route>[Route]</route> </result> </results> </realtimeinformation>

When Will API be available

First use is for the new App APP will be released shortly

Some time to assess operation and determine with Dublinked how it will be made available.

Release to Third part developers late Q1/Q2 2013

Suggestions for what to do with the data.????