Call-prep brief · checked 2026-07-18
Ginko (Besançon)
Grade D · 68.1 / 100
First check for this agency, so there is no trend yet.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
No category changes since the last check.
Top three things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
1412 of 2039 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Effort: A column in stops.txt; your scheduling software likely has it.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Effort: A small file for most flat-fare systems.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
9880 of 17262 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
Effort: A default or per-trip field in your export.
Key facts
- Feed URL
- https://api.ginko.voyage/gtfs-ginko.zip
- Last checked
- 2026-07-18
- Service window
- 44 days of service data remain. Last service date 2026-08-31.
- Location
- Bourgogne-Franche-Comté, France
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.2, validator 8.0.1.