{"action":"created","issue":{"url":"https://api.github.com/repos/google/transit/issues/111","repository_url":"https://api.github.com/repos/google/transit","labels_url":"https://api.github.com/repos/google/transit/issues/111/labels{/name}","comments_url":"https://api.github.com/repos/google/transit/issues/111/comments","events_url":"https://api.github.com/repos/google/transit/issues/111/events","html_url":"https://github.com/google/transit/pull/111","id":372095664,"node_id":"MDExOlB1bGxSZXF1ZXN0MjI0Mzk0MzAz","number":111,"title":"Ability to control display of real time icon by GTFS-rt producers with prediction_type","user":{"login":"gcamp","id":129745,"node_id":"MDQ6VXNlcjEyOTc0NQ==","avatar_url":"https://avatars0.githubusercontent.com/u/129745?v=4","gravatar_id":"","url":"https://api.github.com/users/gcamp","html_url":"https://github.com/gcamp","followers_url":"https://api.github.com/users/gcamp/followers","following_url":"https://api.github.com/users/gcamp/following{/other_user}","gists_url":"https://api.github.com/users/gcamp/gists{/gist_id}","starred_url":"https://api.github.com/users/gcamp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gcamp/subscriptions","organizations_url":"https://api.github.com/users/gcamp/orgs","repos_url":"https://api.github.com/users/gcamp/repos","events_url":"https://api.github.com/users/gcamp/events{/privacy}","received_events_url":"https://api.github.com/users/gcamp/received_events","type":"User","site_admin":false},"labels":[{"id":236868408,"node_id":"MDU6TGFiZWwyMzY4Njg0MDg=","url":"https://api.github.com/repos/google/transit/labels/cla:%20yes","name":"cla: yes","color":"009800","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":44,"created_at":"2018-10-19T19:56:48Z","updated_at":"2018-11-27T15:00:09Z","closed_at":null,"author_association":"NONE","pull_request":{"url":"https://api.github.com/repos/google/transit/pulls/111","html_url":"https://github.com/google/transit/pull/111","diff_url":"https://github.com/google/transit/pull/111.diff","patch_url":"https://github.com/google/transit/pull/111.patch"},"body":"We have seen that `uncertainty` values in TripUpdates are sometime used to convey the information if a prediction is precise enough to be shown as real time in consumer applications. Different producers have different values where `uncertainty` has different meanings. \r\n\r\nThis causes problems because consumers has to have different interpretation for different producers. It would be better to have a clear value for each prediction that defines if a prediction is precise enough to be shown as real time or not. \r\n\r\nThis is a proposition to add `prediction_type` TripUpdates as an _experimental field_. Predictions can either be \r\n\r\n- `REALTIME` (current default)\r\n- `IMPRECISE_REALTIME` where the vehicle is followed in real time but doesn't have enough precision to be shown as real time to the user. The prediction threshold for the switch between `REALTIME` and and `IMPRECISE_REALTIME` should be the same threshold that the producer uses to hide the real time icon in other interfaces like bus displays. \r\n- `UPDATED_SCHEDULE` where a vehicle is not yet followed in real time but some changes to the schedule was done after the latest GTFS export, very likely due to changes from the control center. \r\n\r\nI would also be curious to know if anybody uses the `uncertainty` value in GTFS-rt without having some magic threshold value. If that's not the case and usage of `prediction_type` is accepted and successful, I would propose to deprecate `uncertainty`\r\n\r\nNote : I might be unresponsive in the next few weeks. @juanborre has my full confidence and can respond in my stead and represent Transit. "},"comment":{"url":"https://api.github.com/repos/google/transit/issues/comments/442089095","html_url":"https://github.com/google/transit/pull/111#issuecomment-442089095","issue_url":"https://api.github.com/repos/google/transit/issues/111","id":442089095,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjA4OTA5NQ==","user":{"login":"gcamp","id":129745,"node_id":"MDQ6VXNlcjEyOTc0NQ==","avatar_url":"https://avatars0.githubusercontent.com/u/129745?v=4","gravatar_id":"","url":"https://api.github.com/users/gcamp","html_url":"https://github.com/gcamp","followers_url":"https://api.github.com/users/gcamp/followers","following_url":"https://api.github.com/users/gcamp/following{/other_user}","gists_url":"https://api.github.com/users/gcamp/gists{/gist_id}","starred_url":"https://api.github.com/users/gcamp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gcamp/subscriptions","organizations_url":"https://api.github.com/users/gcamp/orgs","repos_url":"https://api.github.com/users/gcamp/repos","events_url":"https://api.github.com/users/gcamp/events{/privacy}","received_events_url":"https://api.github.com/users/gcamp/received_events","type":"User","site_admin":false},"created_at":"2018-11-27T15:00:09Z","updated_at":"2018-11-27T15:00:09Z","author_association":"NONE","body":"This pull request didn't have discussion for more than a week and everybody seems to agree on the type of the field and the usefulness. I'd suggest we consider we merge this pull request since I feel the consensus was reached as required by the current Official Process. \r\n\r\n@barbeau if you or anybody else feels more secure to do a vote similar to what I suggested for experimental fields (https://github.com/google/transit/issues/109) I'm ok with this too. "}}
{"actor":{"display_login":"gcamp"}}