GBFS is governed by MobilityData, and MDS is managed by the Open Mobility Foundation. While the specifications serve different purposes, they – like our organizations – work closely together.
Join us for a trip down memory lane as we celebrate the contributions, collaboration, and collective great work happening across the OMF community.
After two years of pioneering work, here is what we have to share.
Take the survey to help us prioritize the development of features, allocate resources, and better understand how we can support adoption of new versions of MDS.
In dismissing a recent complaint with prejudice, the court made clear that there is no legal basis to challenge the use of MDS on privacy grounds. Learn more about this legal development, and the Open Mobility Foundation’s work to support and enhance privacy best practices.
One way that cities can take advantage of the flexibility MDS offers is through the MDS Vehicles endpoint, which lets cities know the current status of shared use vehicles in the public right of way.
No matter how cities use MDS, there are concrete steps they can take to ensure that citizen privacy and data security are protected.
Building on the best practices and policies of cities using MDS, the Privacy Guide for Cities offers a starting point to develop appropriate standards, make policy decisions, and implement new mobility programs with data privacy and security well-protected.
This is the first in a three-part series about the architectural landscape where we will explore the vision for MDS.
Whether they’re handling an emergency or just a planned road closure, cities are using the Mobility Data Specification (MDS) to make real-time changes and measure compliance in a constantly evolving environment.