transitland/distributed-mobility-feed-registry

a JSON-based data schema to catalog mobility/transit/transportation data feeds

Transitland

We use this GitHub repository to have public discussions about the Transitland platform, including:

• announcements about the Transitland platform
• questions and answers about Transitland services, data, and tooling
• show and tell to share projects created using Transitland

distributed-mobility-feed-registry's Issues

feed auth can require registering an IP address with a transit agency

For example:

    {
      "id": "f-foothilltransit~rt",
      "spec": "gtfs-rt",
      "urls": {
        "realtime_vehicle_positions": "https://foothilltransit.rideralerts.com/myStop/GTFS-Realtime.ashx?Type=VehiclePosition",
        "realtime_trip_updates": "https://foothilltransit.rideralerts.com/myStop/GTFS-Realtime.ashx?Type=TripUpdate",
        "realtime_alerts": "https://foothilltransit.rideralerts.com/myStop/GTFS-Realtime.ashx?Type=Alert"
      },
      "license": {
        "url": "http://foothilltransit.org/about/developer-resources/developer-license-agreement/"
      },
      "authorization": {
        "type": "ip_address",
        "info_url": "http://foothilltransit.org/about/developer-resources/"
      }
    }

how to specify unzipped GTFS feeds?

How do I mark up GTFS feeds not stored one .zip archive?

Serving the individual .csv/.txt files via HTTP has great benefits, including following web semantics & efficiency (caching, downloading only necessary files).

I currently run vbb-gtfs.jannisr.de as a "special treatment" for my need to work with Berlin data, but I'd like to a) follow best practices to make the "endpoint" as reusable as possible, and b) make it as portable as possible by using semantic markup such as DMFR/DACT-AP/DataPackage.

evaluate DCAT (Data Catalog Vocabulary)

@LeoFrachet has suggested an interesting comparison: the DCAT (Data Catalog Vocabulary) spec, which is used by open data catalogs: https://www.w3.org/TR/vocab-dcat/

Rather than reinvent a new format to describe mobility-specific feeds, why not use this more general purpose format to describe datasets that are connected to each other? It's an interesting question and worth considering.

A particular follow-up question is how DCAT can be us in JSON: ckan/ckanext-dcat#146