The problem with a dis-aggregated transportation network and why one MaaS Platform is not the answer

Residents and visitors of cities, regions and even countries often face a dis-aggregated public transportation network (what we have alternatively called a fragmented transport landscape). Making it more difficult for them to move around without resorting to private transport modes that are typically higher carbon producing than their mass transit competitors. So the idea of […]

The first API Directory for Transport?

Devising a centralised transport operator look-up service has been an interesting output for the Open Transport initiative (as well as creating the actual customer account integration API). But it wasn’t something that we originally anticipated that we would need to do. It was just something that we identified along-the-way as being necessary for true interoperability […]

API Specification v0.9.1

Today there’s two updates to the Open Transport API: The creation of a new centralised operator look-up API (following our recent decision to create an API that will act as a directory of each registered mobility operator). This has been given the name “operator-info” and the specification set at version 0.9.1 An update to the […]

Centralised transport look-up API

In previous posts we have mentioned the need for a centralised look-up service for all transport / mobility providers. This is needed (especially in the early stages of the Open Transport standard) to enforce data consistency between those who have adopted it. To achieve this, the Open Transport team have agreed that we need to […]