Comparing Transport & Mobility Mode Definitions

As part of the Open Transport Initiative’s work to create our centralised Operator-Info API specification, we also had to create a definition of transport and mobility modes. Yes, there are other definitions for some modes of transport in different mobility specifications. However none of them covered all the modes of transport a modern mobility ecosystem …

Example Use Cases for a Centralised Operator API

We have been asked to provide some example scenarios in which an API designed to our Centralised Operator API Open Standard specification could be used. Here are a couple: Example Use Case 1A transport authority or agency creates an innovation programme and need to provide a definitive list and URLs of all data sources that …

Plans for our Central Operator-Info API

Back at the beginning of 2020, The Open Transport Initiative launched two different API designs as Open Standards. The first was our Customer-account API: A standard way to facilitate peer-to-peer transport data. This gained a lot of attention and is currently the focus of our drive towards transport data sharing and account interoperability. The second …

Beyond Open Transport

Open Transport is our pioneering initiative to change the transport and mobility landscape for the benefit of its customers. Using integrated and shared data via open Application Programming Interfaces (APIs) we want to create better transport services and improve innovation and competition. We see the widespread adoption of an Open Standard for customer account interoperability …

The Open Transport Initiative – Gaining Recognition

Covid-19 has changed the working environment for many people and has definitely changed their approach to spending. Often this is reflected in the corporate world, with a more cautious approach to investment and innovation, as organisations play safe during uncertainty. This topic is something we have been discussing at the Open Transport Initiative. We have …

Open Transport enables a comprehensive and open MaaS ecosystem

Mobility-as-a-Service (MaaS) needs data for it to work. More specifically it needs data about the transportation purchases and usage of its customers. Therefore having access to a broader and more comprehensive set of mobility data over a decent period of time (and over all modes of transportation) provides a better understanding of the different transportation …

Open Transport enables a better approach to MaaS

One (and perhaps the foremost) aim of Mobility-as-a-Service (MaaS) is to put the travelling customer at the core of the service and offer them tailor-made mobility solutions based on their specific needs. 2 very different approaches:To do this effectively MaaS requires one of two approaches to customer data: An aggregated approach:The customer needs to have …

Update of “operator-info” API specification to v1.1

Today we are announcing a update of our “operator-info” API specification to version 1.1.0 This important update to our original Open Standard published in January now incorporates three specific change requests CR001The addition of another “mode”, that of “016 – suspended cable car”. Also now reflected in our Mode API reference implementation at https://open-transport.azure-api.net/mode CR002Change …

Open Transport at Open Banking World Congress

This week, two of our board members (Marcus and Hayden) presented to the Open Banking World Congress on the context, history and future of Open Transport. In a 40 minutes session called “Advancing Towards Open Transport” they explained the use cases and benefits of an Open Standards for mobility account interoperability. Although the Open Banking …