{"action":"created","issue":{"url":"https://api.github.com/repos/NABSA/gbfs/issues/86","repository_url":"https://api.github.com/repos/NABSA/gbfs","labels_url":"https://api.github.com/repos/NABSA/gbfs/issues/86/labels{/name}","comments_url":"https://api.github.com/repos/NABSA/gbfs/issues/86/comments","events_url":"https://api.github.com/repos/NABSA/gbfs/issues/86/events","html_url":"https://github.com/NABSA/gbfs/pull/86","id":295325946,"number":86,"title":"GBFS V1.1 Adding support for electric bikes and geofenced bike return…","user":{"login":"dsgermain","id":4513911,"avatar_url":"https://avatars3.githubusercontent.com/u/4513911?v=4","gravatar_id":"","url":"https://api.github.com/users/dsgermain","html_url":"https://github.com/dsgermain","followers_url":"https://api.github.com/users/dsgermain/followers","following_url":"https://api.github.com/users/dsgermain/following{/other_user}","gists_url":"https://api.github.com/users/dsgermain/gists{/gist_id}","starred_url":"https://api.github.com/users/dsgermain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dsgermain/subscriptions","organizations_url":"https://api.github.com/users/dsgermain/orgs","repos_url":"https://api.github.com/users/dsgermain/repos","events_url":"https://api.github.com/users/dsgermain/events{/privacy}","received_events_url":"https://api.github.com/users/dsgermain/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2018-02-07T23:04:40Z","updated_at":"2018-02-27T10:31:43Z","closed_at":null,"author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/NABSA/gbfs/pulls/86","html_url":"https://github.com/NABSA/gbfs/pull/86","diff_url":"https://github.com/NABSA/gbfs/pull/86.diff","patch_url":"https://github.com/NABSA/gbfs/pull/86.patch"},"body":"… areas\r\n\r\nTried to decouple geofencing zones from stations as much as possible, while maintaining the ability to link them as that exists in some systems. \r\nfree_bike_status.json can now be used to determine the number of each type of bike available per station and per geofencing zone. \r\n\r\n- Add geofencing_zone_information.json to list low volatility information relating to geofencing zones, such as their position and which station, if any, they are linked to.\r\n\r\n- Add geofencing_status.json to list transient information relating to geofencing zones, such as whether the zone is allowing returns and the number of bikes it contains.\r\n\r\n- Modify free_bike_status.json to include the bike type, as well as a way to differentiate whether bikes are geofenced at a station, or geofenced in a free floating system."},"comment":{"url":"https://api.github.com/repos/NABSA/gbfs/issues/comments/368824214","html_url":"https://github.com/NABSA/gbfs/pull/86#issuecomment-368824214","issue_url":"https://api.github.com/repos/NABSA/gbfs/issues/86","id":368824214,"user":{"login":"nbdh","id":36266644,"avatar_url":"https://avatars3.githubusercontent.com/u/36266644?v=4","gravatar_id":"","url":"https://api.github.com/users/nbdh","html_url":"https://github.com/nbdh","followers_url":"https://api.github.com/users/nbdh/followers","following_url":"https://api.github.com/users/nbdh/following{/other_user}","gists_url":"https://api.github.com/users/nbdh/gists{/gist_id}","starred_url":"https://api.github.com/users/nbdh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nbdh/subscriptions","organizations_url":"https://api.github.com/users/nbdh/orgs","repos_url":"https://api.github.com/users/nbdh/repos","events_url":"https://api.github.com/users/nbdh/events{/privacy}","received_events_url":"https://api.github.com/users/nbdh/received_events","type":"User","site_admin":false},"created_at":"2018-02-27T10:31:43Z","updated_at":"2018-02-27T10:31:43Z","author_association":"NONE","body":"How many zones are there and how large are they? Do you have an example?\r\n\r\nI'm not sure I understand your question correctly. I'm proposing that small geofenced return zones (virtual stations) without docks should fit under the GBFS definition of station. A field in station_information as proposed by @jcn to be able to distinguish between real and virtual station seems to suffice. Consequently bikes parked at a return zone would not be listed in free_bikes_status. \r\n\r\nAs your geofencing_zone_status.json is basically a station_status with less attributes the only new field is zone_area.\r\n \r\nI know only systems with two types of \"return zones\":\r\n1. systems with very few but very large return areas (that's what I'd consider free floating)\r\n2. systems with many rather small return zones which the operator considers as \"dockless stations\"  (usually it's not even communicated to the user that there is no real station with docks and the 'station' is still represented by a single icon and not an polygon in the front-end, but as I said basically all bikes inside of a 25-75ish meter circle will be considered as being parked at the station.\r\n1+2. In mixed systems those dockless return zones can lie within or outside of the free floating return areas.\r\nI was under the impression that we discussed how this large return areas of free floating systems can be embedded in GBFS in #65."}}
{"actor":{"display_login":"nbdh"}}