Carsharing is a unique mobility option that provides the flexibility of a car without needing to actually own one. Individuals using carshare are able to save money on maintenance, gas, and insurance, and worry less about parking. For cities, the benefits of carshare are even greater. Every carshare vehicle takes 13 personally owned cars off the road and encourages more people to use alternative modes of transportation. This in turn helps combat climate change, puts less stress on a city’s roads, and complements the local transportation systems.
Photo by Mika Baumeister on Unsplash
What is Mobility Data Specification (MDS)?
MDS is a framework for standardizing and sharing mobility data that agencies and operators can use. It helps operators and cities exchange information in a standard format so they can ingest data and build systems to understand program success. MDS has three sub-specifications: Provider, Agency and Policy.
In our previous post about MDS feed health and interpretation challenges, we discussed MDS feed health and challenges to interpreting your feed. Now we will take a look at when the data itself is problematic, and some things to consider when troubleshooting.
In the first blog post in this series, Introduction to Mobility Data Specification (MDS), we discussed what MDS is and broke down the specification.
For micromobility programs that are getting set up with MDS or looking to ensure their data aligns with the spec, there are a lot of ways it can diverge; some are more critical than others. They all start with the question: how do you know if your data adheres to MDS?
One of the most important aspects of launching and sustaining a successful micromobility program is being able to make data-informed decisions to achieve a program’s objectives. To create a foundation of trust and to build a common methodology for understanding and utilizing data, cities and operators need a data sharing standard — that’s where MDS comes in.