On Thu, Aug 16, 2018 at 5:55 PM, Kevin Dalley <[email protected]> wrote:
> I am using GO-Sync, gtfs-osm-sync, to synchronize data for AC Transit. > > For AC Transit, the gtfs_id, or stop_code, can be used to identify the > stop. That's the number on the sign, and can be as a phone code. > > For example, > > stop code is 56669 > > stop_name is: "MacArthur Blvd:Randolph Av" > > stop name does not appear on the sign, though variations of this name > appear on the schedule, usually with a "&" rather than ":". > > stop_code does appear on sign. > > I agree with previous users that, at least for AC Transit, stop_code > should translated to "ref", which a defined meaning for bus_stop. > GO-Sync does not do this, though it would be easy to patch my version, > at least for AC Transit. > > and use stop_name as name, which is what GO-Sync does. > > Are there recent thoughts on this issue? I'm thinking ref on the stop needs to be entirely revisited, given stops may be used by more than one network and therefore have more than one ref. Maybe something like, say, trimet:ref=* for TriMet's stops, and tillamook-wave:ref=* for Tillamook County's The Wave, which share the same stop bays at Sunset Transit Center and several locations in downtown Portland, for example.
_______________________________________________ Talk-transit mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-transit
