{"action":"created","issue":{"url":"https://api.github.com/repos/NABSA/gbfs/issues/127","repository_url":"https://api.github.com/repos/NABSA/gbfs","labels_url":"https://api.github.com/repos/NABSA/gbfs/issues/127/labels{/name}","comments_url":"https://api.github.com/repos/NABSA/gbfs/issues/127/comments","events_url":"https://api.github.com/repos/NABSA/gbfs/issues/127/events","html_url":"https://github.com/NABSA/gbfs/issues/127","id":385873574,"node_id":"MDU6SXNzdWUzODU4NzM1NzQ=","number":127,"title":"Spin has Detroit and DC in same GBFS feed","user":{"login":"brookemckim","id":245680,"node_id":"MDQ6VXNlcjI0NTY4MA==","avatar_url":"https://avatars1.githubusercontent.com/u/245680?v=4","gravatar_id":"","url":"https://api.github.com/users/brookemckim","html_url":"https://github.com/brookemckim","followers_url":"https://api.github.com/users/brookemckim/followers","following_url":"https://api.github.com/users/brookemckim/following{/other_user}","gists_url":"https://api.github.com/users/brookemckim/gists{/gist_id}","starred_url":"https://api.github.com/users/brookemckim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brookemckim/subscriptions","organizations_url":"https://api.github.com/users/brookemckim/orgs","repos_url":"https://api.github.com/users/brookemckim/repos","events_url":"https://api.github.com/users/brookemckim/events{/privacy}","received_events_url":"https://api.github.com/users/brookemckim/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-11-29T18:44:09Z","updated_at":"2018-11-29T20:35:07Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"https://web.spin.pm/api/gbfs/v1/gbfs\r\n\r\n```\r\n{\"last_updated\":1543516918,\"ttl\":0,\"data\":{\"en\":{\"feeds\":[{\"name\":\"system_information\",\"url\":\"https://web.spin.pm/api/gbfs/v1/system_information\"},{\"name\":\"system_regions\",\"url\":\"https://web.spin.pm/api/gbfs/v1/system_regions\"},{\"name\":\"free_bike_status\",\"url\":\"https://web.spin.pm/api/gbfs/v1/detroit/free_bike_status\"},{\"name\":\"free_bike_status\",\"url\":\"https://web.spin.pm/api/gbfs/v1/washington_dc/free_bike_status\"}]}}}\r\n```\r\n\r\n@jcn does this match the spec? How should this be represented in systems.csv?"},"comment":{"url":"https://api.github.com/repos/NABSA/gbfs/issues/comments/442983600","html_url":"https://github.com/NABSA/gbfs/issues/127#issuecomment-442983600","issue_url":"https://api.github.com/repos/NABSA/gbfs/issues/127","id":442983600,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0Mjk4MzYwMA==","user":{"login":"jcn","id":2909,"node_id":"MDQ6VXNlcjI5MDk=","avatar_url":"https://avatars2.githubusercontent.com/u/2909?v=4","gravatar_id":"","url":"https://api.github.com/users/jcn","html_url":"https://github.com/jcn","followers_url":"https://api.github.com/users/jcn/followers","following_url":"https://api.github.com/users/jcn/following{/other_user}","gists_url":"https://api.github.com/users/jcn/gists{/gist_id}","starred_url":"https://api.github.com/users/jcn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcn/subscriptions","organizations_url":"https://api.github.com/users/jcn/orgs","repos_url":"https://api.github.com/users/jcn/repos","events_url":"https://api.github.com/users/jcn/events{/privacy}","received_events_url":"https://api.github.com/users/jcn/received_events","type":"User","site_admin":false},"created_at":"2018-11-29T20:35:07Z","updated_at":"2018-11-29T20:35:07Z","author_association":"CONTRIBUTOR","body":"Hi @jsierles - yes, the intent is for each \"system\" (generally defined as a geographic area) to have its own discovery feed and associated data feeds. And each system should have at most one of each type of feed (i.e. it should only have a single `free_bike_status` feed).\r\n\r\nFor the existing Spin gbfs feed, I'd imagine 2 auto-discovery files: one for Detroit and one for DC, and I would probably leave out region, which is intended for systems that might have different logical distinctions in a single area (for example, a single system that might encompass multiple boroughs or towns) but for which all the data would still be served in a single feed file. "}}
{"actor":{"display_login":"jcn"}}