Photo by Alicia Paydli on Unsplash
Today, Ride Report, in collaboration with Lime and Bird Canada, released our exciting report showing high e-scooter usage in Edmonton, including frequent travel to downtown and business improvement districts and replacement of car travel.
From June 1, 2020 to October 31, 2020, more than 600,000 trips were taken on shared e-scooters.
Photo by Mika Baumeister on Unsplash
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.
Photo by Let's Kick on Unsplash
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.