So, welcome to this talk about OTP.
You had a bit about open trip planer before, but I hope to give you some more information
about how you can use open trip planer and what I have been using open trip planer for
the past few years.
So, my name is Jonas Linson, I'm a software developer living in Sweden in Gothenburg, South
Potter of Sweden, or South Western Potter of Sweden.
I have been working with public transportation solutions for 25 years and with open trip
planer for the past 6 years setting up and configuring the open trip planer solution
for the southern part of Sweden.
So open trip planer is a multimodal search engine, it's a Java application that has been
in development since 2009.
We have cleared a hair for that has been involved for, I don't know, if that is from
the start and some of the e-dwell preserves as well.
It is a active community, but we are also actively sitting for more competent developers
to be able to extend all the capabilities of this platform.
We have, as we can see here, a range 100 commits per week.
So, is that a lot or is that very little?
It depends on the product that you are working on, some of you might find that lot or
some of you might have more than 100 commits per day, I don't know.
The developers are actively sitting and developing together since starting of this year
and they have an active form for discussing all the matters for that all the difference
in the different people are experiencing and we are using it for that as well.
Many of the talks they have been considering data and data is the core of being able to
do development as you are only hearing from the previous talk as well.
And open free planner handles time-tube data on both analytics and GTFS formats and also
real-time information, which is very important in both the series as we have some
targets before and GTFS RTS, and to be able to transfer between different stops, you
also need to route on the street network and there we consume the information from open
street map.
So that is a really important part of being able to do and transfer its calculations.
Here are some of the numbers that we are handling.
We have 8.000 stops, so almost as many as people here in Phastam today were
this weekend.
We manage more than a million addresses to be able to decide from your home address to
a specific stop or vice versa.
If you sitting at work, you want to go home.
You can either use a search for the address or if you know the longitude and let's
you, some of you might do that, you can do that as well.
We handle real-time data, so we have 300 real-time updates per second, which we consume
to be able to provide a travel message that is current for you.
So that is 300 queries per second, roughly 1 million queries per day.
And at the core of being able to provide search results, we have time table data, which
most of you might see in this decision and be translating that into just CSE files, might
be one solution, but I would like, or I mean, it's much prefer to have months of something
more structured like a GTFS or Netflix data.
And using that information, routing as the core of OTP functionality.
So in this room, we are, I think, the definition room or the specification of this room
was 80 people, so 100 of the total people here at Boston this weekend, roughly, so the
total amount in here at the conference is 8000, which are the amount of stops that we
handle in front of, or it's off the screen.
And when a person wants to travel, he needs to decide, or the engine needs to do the calculation
on how to provide a good transit's alternative between all of the people at Boston.
Or only in this room, you can have many different alternatives, how to get from the here
to the end of the room.
So that is the core of the functionality.
And we also have the problems with the real-time updates.
So in some cases, it's just that you just barely make it to the train, or bus, on in
some cases, you just barely miss it, but it is very important when you do your searches
that you get the information or the suggestions that are still possible to take.
And sometimes you can just run and then you make the transfer.
And sometimes I think that many of you going here experience some of the problems that
occurred this weekend, that there are lots of delays and lots of cancellations and in case
of cancellations, you can't go at all.
In some cases, delays or this situation, we have had 20 below, and the during the Christmas
weekend and such.
And if you get stranded on a stop with snow, 20 below, then you really, really need
a real-time based travel solution that can get you where you're going.
Now you need to get real-time data that is accurate.
Some people have more troubles for needs to have actual processing information on how
to get from one place another.
Open Trip Planner does have a solution or panel wheel share searches.
And what is a wheel share accessible, accessible search, it depends.
As many things you have talked about before here, data quality is very key to making it
possible to provide a valuable search results.
In some cases, it would be very nice to have a flux capacitor in your transfer.
There are me also looking at data.
There are definitely time-traumal nutrients in Sweden.
I don't know if you ever know that.
So if a traffic operator knows of a delay at a stop, and they do a manual update on
the next stop and saying, we know that the train will be 20 minutes late.
If they don't then update the stop after that, you can go from one stop to the next
in-minestimments.
So this of course is a problem.
And we do manipulate the information to, as this is nothing case, we don't have
and try to own the trains in Sweden.
Maybe in future, I don't know, or maybe in the past.
So another information or consistency problem that we have with Rio de la
Beta is what if we don't have any real-dometat?
If we have only the time-table information available, then the user that watches the
map and their mobile app, they see that there might be a bus on this way.
I think that you won't have experience this, right?
So, and in the application for Scona, the position for those buses are transparent,
so does the goes buses?
Will there be a bus?
Will there not be a bus?
That is the message, right?
So to manipulate the real-dometat, to be able to trust it, that is very important.
And we have had some of the talks here also focusing on the key aspect of having real
real, really accurate data.
And being unable to understand what that data means, it's also important.
When I first looked at some issues that we have, I thought this happened.
The train that seems just platform.
It arrived out in one platform, and it left on another platform.
So I thought that this was the case.
It wasn't a big surprise.
No, no, 111 trains in Sweden either.
Bombers, right?
But after train arrives at platform 1, and it is disconnected so that the only different
part of the train continues, it leaves on platform 1, 8.
Two different platforms.
So it is not a levitating train, also for the future in Sweden.
So maybe next year, right?
And to be able to travel, don't only go by train.
You use your feet, right?
To get to the final destination, or some of you might feel the train station as the final destination.
I think train stations are very nice in bus stations as well, but I don't live there.
So I go by, I continue from the bus stop and train stop by foot.
So it is very important to also use the OpenSuite map data to be able to chance get to the end
point, or where I'm actually going.
If the street map data isn't connected to the public transport data, then it's not possible to do
the transit on a specific stop.
Because I can't exit the bus, because there is no street available actually in the data.
So it is as if the street doesn't exist at all.
So then the routing engine, having no possibility to suggest a transfer at a stop,
unless you go to the next stop, or the stop on that, and get off, transfer, and go back.
And the people using the app are very confused.
So aren't the public authority, and transfer to authority?
No, what they're due.
And the answer is, yeah, there might be some truth to that as well.
But it is the quality of data, and the all the hard work that the people update in the
upper street map information is due.
But up near the information is not always enough as well.
We have to decide on what different things matter, or the, I was a bit distracted.
There are one map, and one stair at the button left.
And there is one larger stair in the middle of the image.
Are those one, two, or three stairs?
Right?
When you have a flat platform, as you have many longer stairs,
does that still make it one stair, or is it a team?
And this depends, or this makes a difference, because when you have a longer stair,
then the routing engine has to consider the transfer time, which is times 1.5.
Or, yeah, how you can feel it.
So the people that have set up the transfer times between the train and the bus,
if they think that that's two stairs,
then they have decided, OK, this is the travel time,
and that we can have this suggestion.
And if open street map data is not accurate,
then we won't have that as a valid transfer point.
So we won't have that option in the results.
But it would be always fun as a way.
It might not always be the way that you want it to.
But it is the way that the data allows it to do.
And I hope to have maybe one more developer, or two,
to make it more and better, solution to get
public transportation for all of you.
So does it?