DRAFT

CityVehicleSpec is the specification for public transit data (stops, routes, timetables, etc) and mobility data (personal or shared scooters, bikes, cars, etc). It is an attempt to improve and join two specifications GTFS and GBFS into one.

The data format is JSON and every entity is described using JSON schema. It also allows to validate entities for basic errors.

All logic errors, like correctness of timetables, uniqueness of identifiers, etc, should be validated separatelly.

Content

• File structure
• Data settings
• Static Entities
  • Operator (transit agency, sharing provider, parkint lot owner, etc)
  • Place (transit stop, entrance, parking lot, etc)
  • Route (bus, metro, train routes, etc)
  • Connection (footpath between places, indoor route between platforms, etc)
  • Translation (translations to other languages)
  • Graphic (3D of places, route polyline, operator icon, etc)
• Realtime Feeds
  • [PlaceUpdates] (updates for places, for example, if it is closed, warnings, broken elevators, number of free parking lots, etc)
  • [RouteUpdates] (delays on routes, cancellations, warnings, deroutings, etc)
  • [VehiclePositions] (bus positions, sharing vehicle positions, etc)