I made this project entirely in my free time. At first my goal was to have routes for when I am bicycling. I used a user location-based approach for this. It was set up in a way that I could also add routes for my buses/trains, etc. But there was one big flaw: your location is not very accurate in the train, especially in the NS Intercity train.

The setup of the entire project was very solid and it is very easy to add or remove states or screens, so I searched for a solution and came across the NS API. After I implemented the API, I also searched for an API for everything other than the train (buses, trams, etc.)

So I came across another API, OvLive. In combination with the Vertrektijd API I use it to get the information from the rest of the public transport of the Netherlands.

What challenges did I face?

One challenge was how to set up the entire project. First I thought of ways to do it, so I did some research. Unity Mapbox? Google Maps API? NS API? But those API's don't have routes for bicycles. So the only option left for me was location-based and that is exactly what I did. I calculate everything based on the current location.

Another challenge was knowing how API's work, how to get data from them, etc. But with some research online, I was able to figure everything out.

What did I learn?

I learned how to manage the Unity GPS system and how to code more SOLID and clearer. On a more specific note, I also learned how to calculate delays if you have the current point and the distance between 2 points.

Later on in the project I also learned how API's work, how to call them and how to get the data in a clean, structured way.

Code & mechanics

Go back

Home page