Bugulma GTFS export (VALID but not authoritative)

This feed is generated from your bugulma_transit_v2.json.

What you get:
- 12 routes (route versions only where trips exist).
- 93 trips.
- 449 stop_times rows.
- 8 frequency rules.
- 118 stops used by the exported trips (subset of registry).
- 53 / 118 stops have ESTIMATED coordinates.

Non-negotiable caveats:
1) Stop times are interpolated (distance-based) unless you have true per-stop timetables.
2) Calendar is DAILY for 2024-06-03..2026-12-31 (you must correct weekday/holiday logic).
3) Routes with only headways are represented via frequencies.txt (not explicit timetable trips).

If you want a production-grade GTFS:
- Pull authoritative stop coords from OSM (Overpass) and reconcile IDs.
- Extract exact stop sequences from municipal route scheme PDFs.
- Obtain operator schedule data (or crowd-sourced stop-time logs) to replace interpolation.