Source code

Entur believes in open source development and we strive to create re-usable components which can be shared and co-developed internationally. We also make use of some already well established open source projects, such as OpenTripPlanner, where we have become active contributors.

National stop registry (NSR)

Category: National journey planning. License: EUPL-1.2

The stop place registry product consists of two main components, the backend Java application Tiamat, and the front end JavaScript/React application Abzu. Stops are edited by registered users in Abzu's web interface, and the edits are saved and versioned in the Tiamat database. In addition to the main components, we have a few assistant applications, such as asag, which converts Tiamat exports to map data, and Ninkasi which handles the user accounts.

Timetables

Category: National journey planning. License: EUPL-1.2

To store departures, arrivals, trips and journey patterns, we use the application Chouette, developed in France, and selected specifically for its native integration towards the NeTEx format. Chouette is also responsible for the data import process and has extensive data validation functionality.

We use our own branch of Chouette, both for front- and backend.

Journey Planner

Category: National journey planning. License: EUPL-1.2

Entur uses- and has dedicated substantial time and resources to the continued development of OpenTripPlanner (OTP), and we will continue to do so for a foreseeable future. Our interests lie in implementing NeTEx integration for OTP, and the improvement of search response times, and journey suggestion quality. We are contributing to the OTP 2.0 project while using a fork in our own products.

SDK

Category: National journey planning. Lisence: EUPL-1.2

Get a quick start using Entur's API with some of these SDKs.

Tavla

Category: National journey planning. Lisence: EUPL-1.2

Our homebrewed product "Tavla" ("the board!") is a web service which allows users to create their own personalised departure boards. It is designed to be used on large screens in public areas, for example, the lobby of an office building. The user selects the physical location of the board using the geocoder, then defines the search radius of the board, and the transport modes to be displayed. The application looks up stops within the radius and displays them on "the board!". The user can further personalise the departure board by filtering out certain routes or directions of routes. Each personalised board has a unique URL and can be shared freely.