Presentation on Esri European User Conference 2011 by David Lellouche from RATP.

1. HOW TO INCLUDE GIS THREE DIMENSIONNAL TECHNOLOGY
IN TRANSPORT NETWORK REPRESENTATION.
Include 3D in the passenger information standard
David Lellouche. RATP. Engineering department ING. Innovative customers technologies and mobility

2. Summary
• 1) Transport and passenger information CEN standards
• 2) 3D representation of historized or scheduled topology of
line versions. Managing the future?
• 3) Modelling a 3D station for services.
• 4) conclusions

3. CEN Standards and technical specifications for
modelling and exchange transport data
Concepts and model for database
TRANSMODEL 5.1 IFOPT
Multimodal operations
Schedules & vehicle dentification of fixed
schedules objects in TP
Tactical planning
Network description Stop Place
Fare collection
Accessibility
Rostering
Operation monitoring Path link
Personnel disposition.
Equipments
Passenger information
All fonctionnals domains Topography
XML messages and services
SIRI Next European
Real time data Standard NETEX
exchange Scheduled data exchange
based on national standards
Stop monitoring (trident, transexchange, vdv,
General message
Facility monitoring noptis, tap/tsi …)
Disruption messages Network description part 1
….. Tactical planning part 2
Fare collection part 3
Include IFOPT concepts.

4. Link with GIS
• GIS shape or projection of transport network topology. Stop point, line, route, path
link and stop place or station in database.
• Interoperability of ESRI Product with oracle, WMS, WFS.
• Integrate GML (Geographic MarkUp Langage with 3D or Z) in transport object
exchange standard.
• Exchange transport layer with the INSPIRE European Directive and interoperable
format. (ISO Geographic Data File, GDF which include a transport layer)
• Link between infrastructure and transport superset objects.

5. Summary
• 1) Transport and passenger information Standards
• 2) 3D representation of historicized or scheduled topology
of line versions. Managing the futur?
• 3) Modelling a 3D station for services
• 4) conclusions

6. RATP NETWORK
Metro / subway RER suburban
- 14 lines. 1 automated
- 1 400 millions trips/year
railway lines
- 212 km of tracks - 447 millions de trips/years
- 298 stations -115 km of tracks
- 3 000 drivers - 67 stations
- 835 drivers
Tramway :
Bus
Accessibility on all the bus Network
3 lines
Real time information at each stop point and 4 in project
- 3 lines (T1, T2, T3)
Bus network Mobilien - 80 millions trips /years
Night network Noctilien - 82 trains
- 351 lines
- 952 millions de trips/an
- 12 000 drivers
- 4 200 bus
- 16 000 stop points
- 21 bus garage center

7. GIS ESRI Tools to draw the Bus lines
Oracle spatial
With SDE and
ARCGIS 9.2
Arc engine
Desktop
Administration
Arcmap
ArcCatalog
Prototype
3D
with arcscene

8. Show and draw the anticipated network.
Choose a date in the future.
Line
Draw the line by selecting Other layers
->routes
Road infrastructure on POI
->transport link
Urban reference database address
->infrastructure link
Stop points

9. 2D representation of futur network in progress
• How to resolve the concurrence between differents software sessions
• Define a plan or a date if each object have a separate version life
• Define the future is always false. How to have multiple competitives versions
with fusion mechanism or one reference version after an other.
• How to modify an anticipated version and propagate the modifications on
times axe.
• Show the time and the interaction between object using 3D tools modeling

10. 3D view of times and line version with arcscene
use Z as time. A line shape and a beginning and ending date from today
The attributs of line selected
In the 3D view
Under zero: Historized
upper zero: futur

11. Reference or historicized Network in 3D

12. Interact with object. Sculpt the time by modifying the 3D shape ?
Use or create specific mud tools
show the scale, show the link between common objects

13. Summary
• 1) Transport and passenger information Standards
• 2) 3D representation of historized or scheduled topology of
line versions. Managing the futur?
• 3) Modelling a 3D station for services.
• 4) conclusions

14. « Gare de lyon station » 3D prototype
Main goals and services
• RATP
Modelling stations (560 stations = 384 metro stations + 67 rail stations + 112 tramway stations )
Showing the station, entrances and exits for safety and security plan and on site space learning
Path link for indoor route computer or passenger guidance in station (7800 corridors + 6500 spaces, hall,
concourses)
Accessibility for passengers information map in site
Managing and monitoring equipments like passenger information display for real time information
Compatibility between 2 D infrastructure and bus topology reference database with 3D station.
°
Virtual reality and 360° photo and video to visualise the deasable persons navigation path and the
equipment.
• LOCAL TRANSPORT AUTORITY
Build an IFOPT stop place reference database to identify the common multi operator stop. Enhance
intermodality in Ile de France for real time data exchange.

15. Minimal set of information of IFOPT concept.
Easy to anderstood with 3D
Level, path link, statique assignement between logical network (line, route, scheduled stop point)
and the physical network of a station (quay, stop place entrance, space, quay).
Stop place gare de lyon
Stop place entrance With label and identifier
QUAY
Stop point assignement
Line Scheduled stop point
Path link

16. 2D, 3D coherence of differents geographics sources on
gare de lyon station
External and enterprise reference data. Link between transport, road and urban data
3D Building from Bus lines
National geographic institut.
RER line
Path link and level
Of underground
station

17. IFOPT fonctionnal domains.
3D proptotype, a core description of station
IFOPT Admin-Mdl::DataManagedObject
TM-Mdl::Place
PlaceId[0..1] : PlaceId
PointProjection[0..1] : PointProjection Topog-Mdl::Country
CreationDateTime[1] : dateTime LinkProjection[0..1] : LinkProjection
Identification of fixed object in ModificationDateTime[0..1] : dateTime
VersionFrame[0..1] : string
AdministrativeAreaRef[0..1] : AdminAreaCode
ZoneProjection[0..1] : ZoneProjection
CountryCode[1] : CountryIanaEnum
CountryName[0..1] : nlString
ShortName[0..1] : nlString
public transport. AlternativeCommonName
AccessiblePlace
1
is in
ElementId[1] : string
NameTypeRef[0..1] : nmtoken
1 address
Language[0..1] : lang 0..* allias
Name[1] : nlString
ShortName[0..1] : nlString 0..* 0..*
Abbreviation[0..1] : nlString
1
Address-Mdl::Address
«enumeration» transport for AbstractStopPlaceElement
VehicleModesEnum CountryRef[0..1] : CountryIanaEnum
PrimaryTransportMode[0..1] : ModeCode AddressId[0..1] : AddressId
air
Topo rail
suburbanRail
0..*
1
0..*
access by
1
Point urbanRail StopPlaceComponent
metro
graphiy Stops tram
bus
TM-Mdl::TransportMode
StopPlaceElementRef[0..1] : StopPlaceId
StopPlaceComponentId[1] : ComponentId
LevelRef[0..1] : LevelCode
Of trolleyBus
coach
ferry
TransportModeType[1] : ModeCode
isIndoors[0..1] : boolean
0..*
water «enumeration»
interest telecabin
funicular
taxi
AccessModesEnum
foot
bicycle
subplace of
1 1
is part of
0..*
Access- selfDrive
unknown
car
taxi
StopPlace
Stop all
other
shuttle
1
StopPlaceId[ ]
StopPlaceId[1] : StopPlaceId
PublicCode[0..1] : StopPlaceCode
ibility 0..*
1
StopPlaceName[0..1] : nlString
ShortName[0..1] : nlString *
1 entrances
place path links
StopPlaceType[0..1] : StopPlaceTypeEnum
ParentPlaceRef[0..1] : StopPlaceId
Weighting[1] : InterchangeWeightingEnum
1
AbstractPathLink neigbour of
has levels is on
FromPlaceRef[1] : PlaceId 1 * has
ToPlaceRef[1] : PlaceId 0..* from level
FromLevelRef[0..1] : LevelCode
0..1
ToLevelRef[0..1] : LevelCode 0..*
FromEntranceRef[0..1] : ComponentId
0..1 0..*
ToEntranceRef[0..1] : ComponentId 0..* to level
Description[0..1] : nlString Level
0..1
STOP PLACE: Distance[0..1] : distance
Steps[0..1] : integer
FromToDirectionOfUse[0..1] : DirectionOfUseEnum
LevelCode[1] : LevelCode
LevelName[0..1] : nlString
StopPlaceEntrance
EntranceName[0..1] : nlString
Direction[0..1] : PathDirectionEnum from IsExternal[0..1] : boolean
MaximumFlowPerMinute[0..1] : integer IsEntry[0..1] : boolean
to
DefaultDuration[0..1] : duration 0..1 IsExit[0..1] : boolean
0..*
LEVEL: FrequentTravellerDuration[0..1] : duration
OccasionalTravellerDuration[0..1] : duration
MobilityRestrictedTravellerDuration[0..1] : duration
0..1
Width[0..1] : metres
Height[0..1] : metres
STOP PATH LINK: 0..*
to
AbstractStopPlaceSpace
from
QUAY: 0..*
StopPathLink
PathName[0..1] : nlString 0..*
1
1
BoardingUse[0..1] : boolean
AlightingUse[0..1] : boolean
0..*
0..*
BOARDING POSITION: 1 Quay
has
AccessSpace 0..* PublicCode[0..1] : PublicCode
AccessSpaceName[0..1] : nlString QuayName[0..1] : nlString
AccessSpaceType[0..*] : AccessSpaceEnum Label[0..1] : nlString
ACCESS SPACE: 0..* PassageType[0..1] : PassageEnum
subzone of
0..*
DestinationDisplay[0..1] : nlString
QuayType[0..1] : QuayTypeEnum
CompassBearing[0..1] : compassBearing
1
STOP PLACE ENTRANCE: IFOPT / TS278 SG6 BoardingPosition
0..*
CompassOctant[0..1] : CompassOctantEnum
ParentQuayRef[0..1] : ComponentId
subzone of
Stop Place PublicCode[0..1] : PublicCode 1
BoardingPositionName[0..1] : nlString
Basic Path Model Label[0..1] : nlString
BoardingPositionType[0..1] : BoardingPositionTypeEnum

18. Différents methods to aggregate thestop point of multiple operators
Hub and spokes

19. 2D stop place polygone.
A shape to identify all the operators composants inside.

20. Gare de lyon 3D prototype
Services
• 3D view
• 2D passenger information map
• Indoor route computer
• Virtual reality , visualisation of equipment
• Plan a trip for restricted mobility persons

21. 3D map with IFOPT base with ARCSCENE

22. Semi Automatic generation of 2D passenger information map.
GIS IFOPT database and on site sign information

23. Three indoor routes with differents level of accessibility.

24. Web application:
a level station discovery with ESRI flex application

25. Web: address to address route computer with video
°
360° navigation path throught connection and transit

26. Questions ?
To be or not
to be in 3D ?