WEBVTT

00:00.000 --> 00:18.560
All right, so hi there, I'm Adam and I've been using public transport since I started

00:18.560 --> 00:25.000
going to school and up till high school it was really easy and it any bus to the station

00:25.000 --> 00:32.760
and then it ran to school and back the same way and you knew it was something quite different

00:32.760 --> 00:39.560
and I couldn't find anything and I've enjoyed but I knew some Python and the time table was

00:39.560 --> 00:47.400
online so why not scrape it so this is what I did and in fact I never got banned for this

00:47.400 --> 00:59.400
I got banned for subscribing to their RSS feed but fortunately in 2018 Post-Nan have come to their

00:59.400 --> 01:09.640
senses and started releasing DFS files and later they created their own JSON API for real-time data

01:09.640 --> 01:23.320
with real-time data on stops and alerts and in 2019 they started publishing DFS RT with delays

01:23.320 --> 01:31.240
and vehicle positions but with no alerts and try to remember this for like three minutes yes

01:31.400 --> 01:38.040
in 2004 Post-Nan have to send them email that you won't schedule data as they comply

01:38.040 --> 01:44.920
okay I didn't notice and in 2004 I was like 8-9

01:47.080 --> 01:58.040
I was making post-Nan data for each of us or normalised okay all right

01:58.040 --> 02:06.520
now since I used the standard files so maybe I could just add another files and other places

02:06.520 --> 02:18.680
whenever I go for holiday yes in theory in 2024 someone knocked on my master on account

02:19.880 --> 02:25.480
asking if I know about transition I didn't know anything about transition so I looked it up

02:25.960 --> 02:37.720
I had other plans but in October I had pretty much basic support implemented which gave me

02:37.720 --> 02:50.920
not only post-Nan but pretty much global coverage and yes so it's not only about writing code

02:50.920 --> 03:00.040
it's also about meeting people this is photo from last year first open transport

03:00.040 --> 03:07.640
on conference I attended to and I met some great people and the idea came up there

03:08.280 --> 03:19.880
to maybe use that API just on the API I talked about and query it and create DFS RT from this and

03:19.960 --> 03:25.960
put alerts in transition and yes so it was my little contribution to transition

03:31.320 --> 03:35.960
transition is not only gave me global coverage but also

03:36.120 --> 03:51.400
root planning this was always missing I never could have done it myself but root planning is one

03:51.400 --> 03:59.800
thing and I thought about taking passenger by the hand and guiding him or guiding them

04:00.520 --> 04:12.520
all the way and I think this is great place to crowdsource data which segue is really nice

04:12.520 --> 04:23.160
into the next talk I hope and for the future I hope to go full on transition and leaving my legacy

04:24.040 --> 04:34.040
back end behind this will make really very very much a lot of things easier

04:35.240 --> 04:45.080
and I hope that one day there will be an up for root planning for buying tickets for

04:45.080 --> 05:05.240
going on a trip and that even my grand night would be able to deal with that up so yay thank you