CLIMATHON 2019 No data no hackathon - Berlin, 25th of October 2019 Alexander Pilz - VBB
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
CLIMATHON 2019 No data no hackathon Berlin, 25th of October 2019 Alexander Pilz
VBB – main facts
Berlin:
• Surface: 892 km²
• 3.375 Mio. Inhabitants
• 12 Administrative districts
Brandenburg:
• Surface: 29 484 km²
• 2.449 Mio. Inhabitants
• 14 Counties, 4 County-level cities
• 419 Cities and communities
VBB:
• Surface: 30 376 km²
• 5.824 Mio. Inhabitants
Zahlen Stand 30.06.2018
Seite 2
significant disparities
Highly populated metropolis
Berlin
Inhabitants: 3.375 million
Population density:
3 785 inhabitants/km2
Thinly populated area
county Prignitz
Inhabitants: 78 799
Population density:
37 inhabitants/km2
Seite 3
digitalized user
• living processes more digitalized
• experienced in social media
• increasing expectations of information
and level of service
• convenience beats data privacy
Quelle: ww.twitter.com
Seite 4
Fahrpla Pers. VMEE ViP
Abfahrt
nbuch Fahrpla
s- plan
online n VGB VBBr
VTF NEB
HAFAS MIL CV
Print2 A10
SVF
Center
Web
rbbtext UVG
VBB-
VGP
VBB Abfahrts-
tafeln
Anreise-
Widget
ca. 325 Webseiten
DB-
RIS Internet
HTML- Tarif-
Virtueller
Auskunft VBB.de
Server
NAS berater
Spree-Neiße-Bus BAHN.de S-Bahn
DB Navigator A
HAFAS
Apps iPhone Handy-
Android Handy- Windows Phone
VBB
HAFAS-
Ticketing Ticketing
Routing normal
Daten- Export
„Plan-
pool Routing barrierefrei
daten“
(soll) Push
Notification Aktiver/passiver Server
Server DELFI
Aktiver/passiver Server
HAFA EU-Spirit Dritte via VBB-API
An-
S- GTFS- schluss- HIM Karte mit Realgraph und
Dynamische
Abfahrtstafeln
Print Daten Tool Live-Fahrplan - TXL, SXF
EU-Spirit XML
- Hennigsdorf
DELFI XML - Falkensee
- Fürstenwalde
- Strausberg
VBB- - u. weitere
Tarif- OSM
Karten-
DELF
Alle übrigen VBB- Daten-
Stand:
Jan 2016 VU
dienst I
bank
…simplified
smart data (disturbances) data infrastructure
realtime data scheduled
timetable migration timtable
data data
receiving
systems
Seite 6
scheduled timetable data - harmonization needed 60 persons at 33 agencies (local public transport operators) 6 different system interfaces 850 data set imports p.a. Harmonizing of: • ID (local, regional and national) • coordinates • attributes • line numbers • stop names • stop ownership • matching fare attributes • interchanging times and distances
two data models I
13.000 stop areas
"Berlin-W annsee"
(DB AG)
H
H
H
H
S W annsee Platform A
(BVG-Bus)
Platform B
H
"W annsee"
(S-Bahn)
"W annsee, S-Bhf.”
(HVG-Bus)
two data models II 50.000 stop poles
simple stations…
Source: www.pinterest.com… are easy to integrate
S Bahn +1 DB
Bus &
MetroTram
Sammel-Hst. MetroTram N5 N8 148
0 Bus & Tram
Zwischengeschoss
Str.
-1 Ausgang + U5 Ausgang + U8
Zwischengeschoss
-2
Zwischengeschoss
-3 Ausgang + U8
U2 U2
Zwischengeschoss
-4 U8 U8
Ausgang + U2
Zwischengeschoss
-5 Ausgang + U8 Ausgang + U2
U5
U5 (Hönow)
-6
U5 (Endbahnhof)integrated traffic control systems (ITCS)
Uckermark
Prignitz
• 42 transport operators Ostprignitz-
Ruppin
Ober-
havel
Barnim
• 27 with ITCS
• 15 (smaller) transport operators Havelland Märkisch-
Oderland
without ITCS Berlin
1 2
3
• more cooperation's between Potsdam-
Mittelmark Teltow-
Oder-Spree
the larger and the smaller ones Fläming Dahme-
Spreewald Spree-
needed to fill the gap Neiße
Ober- 4
• tendering processes demands 1 = Brandenburg an der Havel
Elbe-
Elster
spree-
wald-
2 = Potsdam
Lausitz
now always ITCS
Spree-Neiße-Bus
3 = Frankfurt (Oder)
4 = Cottbusreal time statistics
Every trip of a vehicle gains every 330 sec a data message.
VBB system receives every second app. 8 messages
app. 480 messages per minute
nearly 29.000 messages per hour
more than 340.000 messages from 6 a.m. to 6 p.m.smart data needed for… • communication of disruption (e.g. longer emergency call, blocked route, broken water-pipeline – alternative routes necessary) • explanations of real time data (e.g. „Canceled“-Information for an stop, e.g. because of an bomb-disposal) • correction of data (e.g. replacement service because of spontanous construction work or lack of vehicles • explanations of deviant timetables and line routes (e.g. deviant timetable as usal because of construction work, also as prior notice) • explanations of disorders without timetable changes (e.g. bus stop were put in another street)
data for moving infrastructure
open data VBB
API static data broken lifts
• realtime data • GTFS • RSS-Feed for lift
• access with unique id • infrastructure disturbances
and base-url • line colors vbb.de/aufzug
• documentation vbb.de/datensaetze
vbb.de/climathon
Seite 16what shouldn't be focused today?
• multimodal open source router number 42 with outstanding UI/UX
• breakthrough unique routing core for all modes of worldwide transport
• next attempt to solve global indoor navigation
• …
Seite 17ideas? mobility emission tracker • walking vs. micro mobility? • go to chinese shop vs. delivery service? • bike to central station? • virtual incentives? • gamification? Seite 18
ideas? new mobile barriers • route checker for prm? • notification tool to mobility provider? • feedback to public authority? • prediction for availability? Seite 19
HAVE FUN
You can also read
