Dashboard Deelmobiliteit data quality

Below we document the data quality of the feeds offered by the providers.

Data quality status

Provider	Status ¹	Uses standard ²	Updated <= 30s ³	Correct PROW ⁴	Vehicle type ⁶	Service areas ⁷
BAQME	🟢	:heavy_check_mark: MDS	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	❌
Bolt	🟢	:heavy_check_mark: MDS	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	❌
Bondi	🟡	:heavy_check_mark: GBFS	:heavy_check_mark:	:heavy_check_mark:	❌	❌
Cargoroo	🟡	:heavy_check_mark: GBFS	:heavy_check_mark:	:heavy_check_mark:	❌	❌
CHECK	🟢	:heavy_check_mark: MDS	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:
Cykl	🟡	:heavy_check_mark: GBFS	:heavy_check_mark:	:heavy_check_mark:	❌	❌
Deelfiets Nederland (GAON)	🟢	:heavy_check_mark: GBFS	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	❌
Donkey Republic	🟡	:heavy_check_mark: GBFS	:heavy_check_mark:	❌	❌	❌
Felyx	🟡	:heavy_check_mark: MDS	❌ _^300s	❌	❌	❌
GO Sharing	🟡	:heavy_check_mark: MDS	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	❌
HTM	🔴	❌ MDS	➖	➖	➖	❌
Keobike	🟡	:heavy_check_mark: GBFS	:heavy_check_mark:	❔	❌
Lime	🟢	MDS	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	❌
MoveYou _{^{- GoAbout - Deelfietsen Zeeland}}	🟡	:heavy_check_mark:	:heavy_check_mark:	:heavy_check_mark:	❌
nextbike	🔴	❌	➖	➖	➖
OV-fiets	🔴	❌	➖	➖	➖
Promo-Bikey	➖	➖	➖	➖	➖
SHARE NOW	🔴	❌	➖	➖	➖
TIER	🟢	:heavy_check_mark: MDS	❌	:heavy_check_mark:	:heavy_check_mark:
Urbee	⏳	➖	➖	➖	➖
uwdeelfiets	🟡	:heavy_check_mark: MDS	❔	❔	❌
Vaimoo/GoBike	🔴	❌	➖	➖	➖
Velocity Limburg	➖	➖	➖	➖	➖
Deelbuggy's / Wilmar	➖	➖	➖	➖	➖
X-bike	⏳	➖	➖	➖	➖

🟢 = Perfect 🟡 = Usable though needs improvement 🔴 = Unusable ⏳ = Integration in process

ℹ️ Status ¹

There are four statuses:

🟢 Perfect
🟡 Usable though needs improvement
🔴 Unusable
⏳ Integration in process

ℹ️ Uses standard ²

As documented in the dataspec, data has to be shared using one of the following data standards:

MDS
GBFS
TOMP

There is one additional requirement:

All vehicles must have a static ID

MDS is the prefered data standard to use.

ℹ️ Updated <= 30s ³

As documented in the dataspec, the data feed must be updated at least every 30 seconds.

ℹ️ Correct PROW ⁴

We use the PROW as described in the MDS standard for determining if a vehicle should be included in the data feed or not. Also the MDS standard defines what vehicle status should be shared.

A vehicle should only be included if:

The vehicle is in public space, available and not rented out
The vehicle is in public space and reserved
The vehicle is in public space and disabled
The vehicle is in public space and defect

If a vehicle is reserved, disabled or defect, the vehicle status must be included as described in the data standard.

NOTE: If a vehicle is not present in public space (because it's stolen), the vehicle should be excluded from the data feed.

ℹ️ NL data ⁵

The operator should provide data of all their vehicles in The Netherlands.

ℹ️ Vehicle type ⁶

The operator should communicate what kind of vehicle it's reporting.

To decide on what vehicle type should be reported, use the table in our dataspec.

For every data standard, there's documentation on how to include the vehicle type (GBFS, MDS).

ℹ️ Service areas ⁷

The operator could share its service areas using a GBFS feed as explained here. If the operator shares its service areas, these can be shown in the Dashboard Deelmobiliteit at dashboarddeelmobiliteit.nl/map/servicegebieden. Historical changes are then stored automatically as well, so you can easily see the development through time.