So, to have enough time for our last routing specialist now from Finland, we would start
on time.
Yes?
Please, no, it's not working because it's for the camera.
I'm screaming because we don't have an audience here.
Yeah, it's not a microphone.
Yeah, but yeah, let's welcome our last, more like the speaker from Finland.
It's Joel Lappallian.
I hope I speak your name well.
And yeah, we are really glad to have you with us.
Introducing Diki Transits to us, like from Finland we expect a lot because you are already
known for great mobility solutions.
And yeah, let's give him the chance to explain Diki Transits to us and highlight the really
interesting components.
Hello, hopefully you can hear me well.
My name is Joel Lappallianen.
I'm from Finland, a set, and I work as a developer on the OpenTrip planner and the Diki
Transits projects.
And today I'm here to talk about the Diki Transits project.
So what is Diki Transits?
It's an open source project that does multimodal public transportation, journey planning.
It was founded in Finland around 2014 or 15.
I have personally been working on the project since 2017.
The goal of the project was to replace existing legacy property, journey planners, and the
project is funded by three transportation authorities or sort of authorities in Finland.
The project has, or the components of the projects have since been used elsewhere, for
example in Germany.
The project consists of user interfaces, which I'm going to talk more about in this presentation,
and backend services and open APIs.
So first a bit about the backend services.
So for routing and much more, we are using OpenTrip planner.
Hannes will have a presentation next about OpenTrip planner, so I'm not going to go too
much into it now.
For geocoding, we are using Pellias that we have further improved, so it deals with
GTFS data and so on.
And for maps, we are using this project called HSL Map Server, which uses Thileive GL and
OpenStreetMap.
And we also use OpenStreetMap for the geocoding as well.
So now for the user interfaces.
So first, this is the digit transit user interface.
It's written in JavaScript and uses React.
It's responsive, most of our users are on mobile devices.
It's browser-based, and it's also meant to be, so you can use it with screen readers
and so on.
It's configurable, you can have different themes.
My screenshots will be from different sites, so they will have different configurations
and themes.
So this is the front page on desktop.
Here you can start the itinerary search.
You can enter origin and destination, which can be like addresses or stops or whatever.
And you can add some favorites or use favorites for locations.
And then you can enter these stops near you pages.
I will display later on what this means.
And then you have this search box for stops and routes and bike rental station and bike
and car parks and so on.
I won't show those views now because the time is a bit limited.
And on the map, if I would have tuned in a bit more, there would have been more shown.
Now it's just showing some stations.
Okay, so these are the itinerary views on mobile.
The view on the left, it's showing the summary of the found results.
It's showing multiple itineraries in this view and just like a summary of those.
The length of the legs is based on the duration of the leg.
And we support real-time data, so the screen numbers are real-time estimates.
And this is multimodal, so in this suggestions there's buses, trains, metros, walking, there
could be bike rental.
And then we have this multimodal also split into separate suggestions on the top.
There's cycling, there could be just walking, combining cycling with public transportation
or combining cars with public transportation.
And on the right, the view is shown when you click open some suggestions.
It shows more details about the suggestions and it shows the map.
If the trip was happening right now, we could display the relevant vehicle on map for the
suggestions and yeah, there's more details here.
This view is the stops near you page that I mentioned earlier.
So we did some design and discuss with real users and they found this view to be useful.
So we have split this into like different modes.
It shows the next departures for buses in this view, but there's another view that shows
for example trains or metro or whatever is available in the city.
And there's also one view that shows the departures for your fare stops.
And these stops are the stops that are near you or a selected location.
And on the map it will show the vehicles that travel through the stops and also the bus
lines.
So here's an example how this digital unit UI can be integrated into different websites.
This is the front page for the Helsinki Regional Transportation Authority.
On the left side, we have the same components we had in the front page from the digital
unit UI.
This is drawn to shared components.
So this only acts like an entry point.
So once user does select locations here, he or she will be redirected into the digitized
user interface.
And here's another example how digitized UI can be integrated.
This is done through an iframe widget.
There's a view which can be used to generate this iframe snippets.
And this is for general routing, but it's also possible to have only this for walking
or cycling.
So the user will be redirected to the correct view.
This is another project, another user interface.
Previously we called it virtual monitor, but now there's more called stop monitor, which
kind of describes it better.
So this stop monitor is meant for like businesses or private persons or public transportation
authorities.
So they can have this screen somewhere which displays the departures for the stops near
that location.
So this view is for, I should also mention that this is written with TypeScript and also
used React.
This view is for generating this view, the stop monitor view.
In this you can have multiple stops on the same view and you can have multiple views
that can rotate based on some time frame.
So for every five seconds it will change which view is shown.
And there's many options for layouts here.
Here is just an example end result.
You can have like this speed view where there's departures on the left and on the right this
is for airport and on the bottom there's relevant alerts for that stop.
And this stop can be modified later on, so once you have created this it's not really
final, you can still do modifications.
So what's next in the digitized project?
We started the project so early on that Open Tree Planner only had version one out.
So we are currently working on improving the support for using Open Tree Planner version
two.
It's already working but there's some optimizations that can be done.
So the digitized UI that I showed it's like version two and we have version three that
is better optimized for using Open Tree Planner two.
And then we will have a possibility to have a map view on the stop monitor so you can
have displayed the vehicles that are going to the stop so the user can see okay this
vehicle is going here maybe I should start going to the stop.
And then we will improve the support for first and last month services.
So we have already been supporting like bike rental stations and in Germany they have added
support for like scooter rentals, like floating vehicles and we will also focus more on like
flexible public transportation so there's many types of services like that and this
can include like taxis or stuff like that.
So for more information you can visit d-transit.fi which contains some documentation relevant
to the project and the repositories are hosted under this HSL development community GitHub
account there's many projects there some are not digitized projects but if you search
for digitized projects you will find the relevant ones.
And we have this email address digitized at HSL.fi which if you send message there it
will I will get the message.
So thank you that was the presentation now there's time for questions if you have any.
Yes for me it's interesting from your country that I would like to have this kind of information
for Europe.
Yeah.
In community first and it would be interesting to have the best range to reach a place everywhere
in Europe and it's not easy for the moment you have only national lines and so I remember
it was 20 years ago when it was CEPRO with regional trains in Germany but they were slow
and had problems with that also I know I know also to go from Brussels to Firebook in Brysgau
in Germany it was CEPRO by the train in Germany and so on so all this kind of information
and you plan to have to extend your project to the European level.
So we might expand it to include Estonia for this finished project but there's still some
issues with scaling this because if we are using multi-criteria search it doesn't scale
to this continental scale yet on the machines we are running on.
So there's some optimizations needed to get it work.
This might be included in the first and last mile services I'm not quite sure on the details
yet we are still on the like design phase on what we will support but that is an idea
that we have discussed previously.