Regulation .22 Data and Reporting.
Current through 2026-01-20. Source: COBRA Register Volume 04, Issue 02. Published by the Baltimore City Department of Legislative Reference.
Balt., Md., COBRA § 14.02.01.22 (2026)
Regulation .22 Data and Reporting.LinkCopy Citation
A.
GPS.
A permit holder shall ensure each dockless vehicle in their fleet is equipped with on-board GPS technology that does not rely on a user’s mobile device to obtain spatial information.
B.
Publicly Accessible Application Program Interface (API).
(1)
The permit holder shall provide a publicly accessible API.
(2)
The permit holder shall ensure that:
(a)
The public API is in a gbfs.json file format;
(b)
There are no “stations” in the parlance of GBFS, therefore both station_status.json and station_information.json should return an empty list;
(c)
FreE-Bicycle-status.json is required;
(d)
The field “vehicle_type” is added to the public API to describe the vehicle type, which may be:
(i)
“Bicycle”;
(ii)
“E-Bicycle”;
(iii)
“Scooter”; or
(iv)
Another type of specified permitted vehicle;
(e)
The Department is instructed on how to request authentication, if the public API requires authentication;
(f)
The location of the public API is provided to the Department; and
(g)
A smart phone-based application used to rent dockless vehicles is not considered the public API program interface required by <cite data-path="14.02.01.22|B.|(1)">§B(1) of this regulation</cite>.
(3)
The permit holder shall provide access to at least 50 requests per hour.
(4)
The Department shall post the location of the public API to the Department’s website.
C.
Mobility Data Specification (MDS) Policy API.
(1)
A permit holder shall:
(a)
Provide an MDS Policy API to the Department for a dockless vehicle trip in Baltimore City, including trips which:
(i)
Start in Baltimore City;
(ii)
End in Baltimore City; or
(iii)
Pass through Baltimore City;
(b)
Adhere to an MDS of 1.0 or newer, as set by the OMF;
(c)
Post the MDS Policy API on GitHub under the OMF Mobility Data specification;
(d)
Provide API endpoints, including:
(i)
A trip;
(ii)
A status change;
(iii)
A vehicle; and
(iv)
Real-time data;
(e)
Update or add endpoints to the MDS Policy API within:
(i)
Sixty days of notification from the Department for required published endpoints; and
(ii)
Ninety days for beta endpoints;
(f)
Change vehicle status to ‘Unknown’ if a vehicle is suspected to be:
(i)
Vandalized; or
(ii)
Missing for five or more days;
(g)
Ensure GPS data are transmitted from a dockless vehicle on-trip at a minimum frequency of once per 30 seconds;
(h)
Develop and maintain a working Wi-Fi connection to ingest MDS Policy API endpoints provided by the Department; and
(i)
Share current data through the MDS Policy API at least once per 24 hours.
(2)
The Department may require additional or updated endpoints published by OMF.
(3)
The Department may share the MDS Policy API with a third-party aggregator in accordance with <cite data-path="14.02.01.22|C.|(4)">§C(4) of this regulation</cite> for the purpose of:
(a)
Secure data storage; and
(b)
Analysis.
(4)
To share data with a third-party aggregator in accordance with <cite data-path="14.02.01.22|C.|(3)">§C(3) of this regulation</cite>, the Department shall enter into a memorandum of understanding with a third-party aggregator that:
(a)
Includes a provision governing the public release of data by a third-party aggregator; and
(b)
Is made available for a permit holder to review prior to being finalized.
D.
Reporting.
(1)
Time Sensitive Reports.
A permit holder shall report the following to the Department within 24 hours of notice:
(a)
Non-deployment request at a location by an adjacent property owner for verification by the Department;
(b)
A vehicle that is in a location where the permit holder cannot retrieve it, including a body of water; and
(c)
An issue that could affect public safety, including:
(i)
A report of criminal activity involving a dockless vehicle;
(ii)
A report of a crash involving a dockless vehicle;
(iii)
Contact with the Baltimore City Police Department;
(iv)
Contact with the Baltimore City Fire Department; or
(v)
A defect in equipment.
(2)
Monthly Reports.
A permit holder shall provide the Department with a monthly report by the tenth business day following the final day of the month which:
(a)
Uses the Department’s reporting template;
(b)
Is in Excel or CSV format;
(c)
Includes:
(i)
A report of each dockless vehicle lost due to theft or vandalism;
(ii)
Aggregated repair information on a permit holder’s dockless vehicle fleet by model of vehicle and type of repair;
(iii)
Each illegal parking request from the public;
(iv)
Each customer complaint received with response time noted;
(v)
A record of attendance at a City meeting;
(vi)
The number of people in attendance at a community event;
(vii)
A summary of marketing efforts;
(viii)
The number of users that took a trip on a dockless vehicle during the reporting period;
(ix)
The number of rides by low-income pass users during the reporting period;
(x)
The number of rides by cash users during the reporting period;
(xi)
The number of rides by non-smart phone users during the reporting period;
(xii)
The number of users provided for in <cite data-path="14.02.01.22|D.|(2)|(c)|(ix)">§(2)(c)(ix)</cite><cite data-path="14.02.01.22|D.|(2)|(c)|(xi)">-(xi)</cite> of <cite data-path="14.02.01.22">this regulation</cite> disaggregated by the type of plan and user home zip code;
(xiii)
The number of users of the low-income pass; and
(xiv)
An update to maintenance or operational plan.
(3)
Software Issues and Hacking Events.
A permit holder shall:
(a)
Notify the Department of a change to a data portal, including a response to a notification from the Department regarding:
(i)
A software glitch;
(ii)
An issue with hacking; or
(iii)
A data portal;
(b)
Acknowledge a notification from the Department about data and reporting within 24 hours;
(c)
Provide the Department with a plan for addressing an identified problem;
(d)
Provide a progress update to the Department once per 48 hours while the problem persists; and
(e)
Permanently fix an issues within 60 days of receiving notice of the problem.
(4)
User Privacy.
A permit holder shall protect user privacy by:
(a)
Complying with Payment Card Industry Data Security Standards for an electronic payment;
(b)
Notifying a user of a mobile device feature that the mobile application accesses; and
(c)
Not releasing personal user data to an entity:
(i)
Unrelated to operations; or
(ii)
That intends to use the data in a commercial sale to a third party.