{"action":"created","issue":{"url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS/issues/14","repository_url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS","labels_url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS/issues/14/comments","events_url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS/issues/14/events","html_url":"https://github.com/osplanning-data-standards/GTFS-PLUS/issues/14","id":132571095,"number":14,"title":"Relation between lot_id and stop_id","user":{"login":"bhargavasana","id":5088537,"avatar_url":"https://avatars.githubusercontent.com/u/5088537?v=3","gravatar_id":"","url":"https://api.github.com/users/bhargavasana","html_url":"https://github.com/bhargavasana","followers_url":"https://api.github.com/users/bhargavasana/followers","following_url":"https://api.github.com/users/bhargavasana/following{/other_user}","gists_url":"https://api.github.com/users/bhargavasana/gists{/gist_id}","starred_url":"https://api.github.com/users/bhargavasana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bhargavasana/subscriptions","organizations_url":"https://api.github.com/users/bhargavasana/orgs","repos_url":"https://api.github.com/users/bhargavasana/repos","events_url":"https://api.github.com/users/bhargavasana/events{/privacy}","received_events_url":"https://api.github.com/users/bhargavasana/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-02-09T23:53:37Z","updated_at":"2016-02-17T00:13:51Z","closed_at":null,"body":"What is lot_id in drive_access_ft.txt and drive_access_points_ft.txt? FT code assumes that it will be different from stop_id. However, in the description of lot_id there is \"stop_id\". Do we want to make it clear that there should be no overlap between lot_id and stop_id? FT assigns numeric ids to both stops and lots for internal use."},"comment":{"url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS/issues/comments/184935601","html_url":"https://github.com/osplanning-data-standards/GTFS-PLUS/issues/14#issuecomment-184935601","issue_url":"https://api.github.com/repos/osplanning-data-standards/GTFS-PLUS/issues/14","id":184935601,"user":{"login":"bhargavasana","id":5088537,"avatar_url":"https://avatars.githubusercontent.com/u/5088537?v=3","gravatar_id":"","url":"https://api.github.com/users/bhargavasana","html_url":"https://github.com/bhargavasana","followers_url":"https://api.github.com/users/bhargavasana/followers","following_url":"https://api.github.com/users/bhargavasana/following{/other_user}","gists_url":"https://api.github.com/users/bhargavasana/gists{/gist_id}","starred_url":"https://api.github.com/users/bhargavasana/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bhargavasana/subscriptions","organizations_url":"https://api.github.com/users/bhargavasana/orgs","repos_url":"https://api.github.com/users/bhargavasana/repos","events_url":"https://api.github.com/users/bhargavasana/events{/privacy}","received_events_url":"https://api.github.com/users/bhargavasana/received_events","type":"User","site_admin":false},"created_at":"2016-02-17T00:13:50Z","updated_at":"2016-02-17T00:13:50Z","body":"@sdrewc - yes, lot_id must not be the same as stop_id in FT.\r\n\r\nIf we all agree, let us add a suffix/prefix to raw CHAMP lot_ids to make sure they are different from any of the stop_ids. Dependent input files (such as transfers_ft.txt) would need to be updated with new lot_ids in from_stop_id and to_stop_id fields."}}