Add GBFS Feed Url to providers.csv

[asadowns]

Add GBFS API url to providers.csv

From the README

All MDS compatible provider APIs must expose a public GBFS feed as well.

Currently there is no way to discover MDS provider URLs to ensure compatibility and make this information
available to the public.

As part of being MDS compliant providers MUST provide this information and make it available to the public.

For today, the best way to do this is to add it to the providers.csv and have providers put the URL there
as part of their fulfillment of the MDS specification

This feels like it should be added to the 0.2.1 release tag rather than waiting for the 0.3.0 release as
it is a current requirement

[thekaveman]

Seems like a good change, agreed that there isn't really a better place to put it now and this file makes sense.

A 0.2.1 release might make sense, but I don't know that it would be any faster than 0.3.0 - we'd want to give each provider the chance to fill this in, for example, instead of releasing a partial registry.

[marie-x]

I think at bare minimum you'll want to add a comma to the rest of the providers who have not yet provided their GBFS API URL.

[hunterowens]

Another issue is that due to the way GBFS works, different companies have many URLs for GBFS

For example, here are the URLs for JUMP - how would we want to represent this?

[asadowns]

@hunterowens you raise a good point but I actually think GBFS has indicated what the solution to this is. Providers should provide a single discovery endpoint from which all of their feeds can be accessed.

gbfs.json should not be city specific but should provide all feeds that are available from a given provider. In the example you gave above something like https://jumpbikes.com/opendata/gbfs.json could provide

{
  "last_updated": 1434054678,
  "ttl": 0,
  "data": {
    "en": {
      "feeds": [
        {
          "name": "New York City freebikes",
          "url": "https://nyc.jumpbikes.com/opendata/gbfs.json"
        },
        {
          "name": "Seattle freebikes",
          "url": "https://sea.jumpbikes.com/opendata/gbfs.json"
        }
      ]
    }
  }
}

See: GBFS

Let me know if it would be helpful to amend the provider README.md in any way to make it more clear that there should be a single entry point to all feeds.

[hunterowens]

@asadowns yeah, let's amend the realtime data section in provider to add that you should have the single entrypoint inside providers.csv. Once we do that we can merge this in for 0.3.0.

[asadowns]

@hunterowens I've amended the Realtime data section. Let me know if there's an additional tweaks you'd like.

[hunterowens]

Thanks @asadowns. Merging!