t; >>
> >>
> >> *From:*Jo [mailto:winfi...@gmail.com]
> >> *Sent:* fredag 17. august 2018 10.05
> >> *To:* Public transport/transit/shared taxi related topics
> >>
> >> *Subject:* Re: [Talk-transit] Revisiting the use of ref in bus
>>
>> *From:*Jo [mailto:winfi...@gmail.com]
>> *Sent:* fredag 17. august 2018 10.05
>> *To:* Public transport/transit/shared taxi related topics
>>
>> *Subject:* Re: [Talk-transit] Revisiting the use of ref in bus stops
>>
>>
>>
>> We have 3
ransport/transit/shared taxi related topics
>
> SUBJECT: Re: [Talk-transit] Revisiting the use of ref in bus stops
>
> We have 3 operators here in Belgium. I started by adding stops for 1 first,
> so I used ref.
>
> Then I started working on the other operator and some sto
-transit] Revisiting the use of ref in bus stops
We have 3 operators here in Belgium. I started by adding stops for 1 first, so
I used ref.
Then I started working on the other operator and some stops are indeed shared.
The other operator has 5 subdivisions and annoyingly they all assign their own
We have 3 operators here in Belgium. I started by adding stops for 1 first,
so I used ref.
Then I started working on the other operator and some stops are indeed
shared. The other operator has 5 subdivisions and annoyingly they all
assign their own identifiers, those stops also overlap.
For a whi
On Thu, Aug 16, 2018 at 5:55 PM, Kevin Dalley 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 co
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 d
