CASE STUDY:

National Transport Body - Open Data Platform

Methods, tech and tools
Serverless cloud services; AWS - Lambda, DynamoDB, Aurora, S3, SQS, ECS Fargate; Typescript; Terraform. CI/CD

THE CHALLENGE

The General Transit Feed Specification (GTFS) is an open-standards system used to share public transport information to riders. Transit providers share data that is then used by software applications (for example bus stop displays and Google Maps).

The Transport Body was looking to move from the current black-box system into an open-source solution while maintaining feature parity. Specific requirements included:

  • Building a system to gather data (via API or download) from c.400 different sources
  • Store and convert consistently formatted data into GTFS
  • Target: 70% of vehicle location data to be matched to timetables.

In February 2024, Doza was selected by the Transport Body's appointed supplier to support the project and existing development team – a decision based on our successful track record working together.

Approach

The solution was developed to replicate data from key sources into a central database platform:

  • Automatic vehicle location (AVL) data, provided by bus operators and ticketing providers, tracks a public transport vehicle’s location
  • The Open Data Platform provides timetables, fares and disruptions data.

A challenge included engaging with the data producers, mainly due to a lack of visibility on how data was being used. To get them onboard, we explained the benefits of the open-source model and how this would support better two-way feedback going forward.

As a black box system, while we knew the inputs and outputs, the internal workings were unknown and required us to reverse engineer the solution. A proof of concept was developed to demonstrate viability.

We built a cloud native solution using GDS practices:

  • Modern, serverless cloud services were selected for security, performance and cost efficiency benefits, as well as supporting the existing skill sets and tools in place
  • The tech stack supports scalability and future demand, allows new features to be added effectively, and supports quicker development and fixing of issues
  • AWS was selected for data screening and to allow data to be ingested with minimal lag.

Implementation of best practice included setting up monitoring and alerting dashboards, and breaking tickets into smaller pieces of work to maintain momentum during sprints. Adding automated ways of working and CI/CD pipelines drove efficiencies in the development process.

ReSULTS

Outcomes

While development is still underway, the solution has already delivered improvements:

  • 72% of vehicle location data mapped to timetables, exceeding 70% target
  • Better API response times, reduction from ten seconds to three seconds.

LATEST CASE STUDIES

Ready to shake things up in your digital world?

Let's chat

Thank you! Your submission has been received - we will be in touch shortly.
Unfortunately, your message has not sent. Please re-try or email hello@doza.consulting.