2. Management of public transport
network geodata
• geodata aren´t administered by a single authority
• there are even no mandatory regulations
• accuracy or up-to-dateness of these geodata aren´t
subject to any standardization
• public transport network data are managed by
− Integrated Transport Systems organizers
(coordinators) in particular regions
− directly by public transport operators
www.geoinformatics.upol.cz
3. Existing geodata of public transport
• incomplete data warehouses
• incorrectly located objects
• layers without the system of coordinates
• errors like undershoots, overshoots
• missing attributes
• inappropriate logical structure and method of data
management
• incompatible data for exchange between data
warehouses
www.geoinformatics.upol.cz
4. Support for solution
• existing world standards for the exchange of public
transport data
− GTFS (General Transit Feed Specification)
− IFOPT (Identification of Fixed Objects in Public Transport)
− SIRI (Service interface for real-time information)
− NeTEx (Network Exchange)
• accepted czech format – Uniform Data Format (JDF)
• new standard for public transport data in the Czech
Republic - Uniform Data System for Public Transport
(JSDV)
www.geoinformatics.upol.cz
5. Data model for public transport
network management
• for the Olomouc Region managed by authority
Coordinator of Integrated Public Transport System
(KIDSOK)
• developed by KIDSOK, company ASSECO Central
Europe and Department of Geoinformatics UP
• data model based on the world-wide recognized
standards for public transport data exchange and
rules for their management
• cooperation has several other downstream targets
www.geoinformatics.upol.cz
6. Data model for public transport
network management
• built on standard NeTEx – adapted for conditions
applicable in the Czech Republic
• compatible with JDF
• accounted the requirements of KIDSOK
www.geoinformatics.upol.cz
7. Entities in the data model
– Stop
• basic element - a stop as a point feature
• position of the stop is calculated as a centroid of all
signposts
• each stop must be identified by a unique multi-digit
number from nationwide schedule information
system (CIS ID) - e.g. No 24768 for Olomouc, tržnice
• each bus stop has CIS multi-digit number, position
(using X and Y coordinates), name (consisting of the
names of a city, city part and locality)
www.geoinformatics.upol.cz
8. Entities in the data model
– Boarding Edge
• linked to bus stop by CIS ID
• is a border part of the platform, defined as a paved
area allowing safe movement of passengers when
boarding or leaving a vehicle
• length is routinely the same as the length of a
platform, or at least the length of the longest vehicle
• each stop has at least two boarding edges (one for
each direction)
• attributes – height, length, type, wheelchair
accessibility, …
www.geoinformatics.upol.cz
9. Entities in the data model
– Stop Lane
• linked to the boarding edge and stop by ID
• marked by two points (front and end positions)
• length is routinely the same as the length of a
boarding edge
• each boarding egde has at least one stop lane
• attributes – information about existing of a bay or
turning lane, length and depth of a bay, …
www.geoinformatics.upol.cz
10. Entities in the data model
– Signpost
• linked to the boarding edge and stop by ID
• defined as a distinct upright marker designating
bus, tram, trolleybus or other stop
• represented by a point (X, Y coordinates)
• usually placed at the front part of a boarding edge
• each boarding edge has at least one signpost
• attributes – type of transport, design
(post, console, frame), placement (solitary, sheltermounted, wall-mounted etc.) and about its owner or
administrator, …
www.geoinformatics.upol.cz
11. Entities in the data model
– other entities
• equipment of bus stop/boarding edge
− shelters, concourses, waiting areas, benches, ticket machines etc.
• access space
− underpass, overpass, space of stop , hall, etc.
• tariff zone
• parking
www.geoinformatics.upol.cz
12. Data collection and updating
• new mobile application for field data collection on the
tablets with OS Android
• mobile application allows collection of data about
stops, boarding edges, signposts, stop lanes and all
spaces and objects related to boarding edge or stop
• application works offline, all data must be uploaded prior to
the field mapping, and downloaded to a central data
warehouse after completion of every mapping
• functions for recording positions of spatial elements, make
photographic documentation, descriptive attributes
• data mostly entered through code lists (more than 25)
www.geoinformatics.upol.cz
13. Future work
• now mobile application currently installed on five
tablets and final testing has been already conducted
• pilot field testing revealed that a time frame necessary
to edit one stop - 15 minutes
• within IDS in Olomouc Region - more than 2500
unique stop names
• in the field data collection is involved department of
Geoinformatics, in data collection or updating
participate also other subjects
www.geoinformatics.upol.cz
14. THE DATA MODEL FOR DATA MANAGEMENT
OF PUBLIC TRANSPORT
Thank you for your attention
Lenka ZAJÍČKOVÁ
