GRTA using stop names as stop ids?

[Colin McGlynn]

In the latest GTFS release for GRTA the agency seems to be uisng the full stop name as the stop id e.g. "10900 Medlock Bridge Rd (S)".  That's unusual enough that I'm wondering if that was a mistake made when exporting the GTFS? Does anyone from or GRTA or ARC have any insight as to whether this was intenitonal or if I should expect to see the stop ids  switch back to being numbers on the next release? Thanks!

https://transitfeeds-data.s3-us-west-1.amazonaws.com/public/feeds/grta/66/20180503/original/stops.txt

[Landon Reed]

Hi Colin,

I may be speaking out of turn (my information is a few years old), but my understanding is that their AVL provider (RouteMatch, I believe) uses entity IDs (e.g., stop and route IDs) as coded information for things like next stop annunciators.  I imagine this latest change is in support of that system.

I'm definitely not condoning this practice, but that was my understanding as of a couple of years ago.

Best,

Landon

---
Landon Reed

@eltiar

On Wed, May 16, 2018 at 3:00 PM 'Colin McGlynn' via atl-transit-developers <atl-transit...@googlegroups.com> wrote:

In the latest GTFS release for GRTA the agency seems to be uisng the full stop name as the stop id e.g. "10900 Medlock Bridge Rd (S)".  That's unusual enough that I'm wondering if that was a mistake made when exporting the GTFS? Does anyone from or GRTA or ARC have any insight as to whether this was intenitonal or if I should expect to see the stop ids  switch back to being numbers on the next release? Thanks!

https://transitfeeds-data.s3-us-west-1.amazonaws.com/public/feeds/grta/66/20180503/original/stops.txt

--
You received this message because you are subscribed to the Google Groups "atl-transit-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atl-transit-devel...@googlegroups.com.
To post to this group, send email to atl-transit...@googlegroups.com.
Visit this group at https://groups.google.com/group/atl-transit-developers.
For more options, visit https://groups.google.com/d/optout.

[Colin McGlynn]

Thanks Landon, that's good to know

On Thursday, May 17, 2018 at 9:36:55 AM UTC-4, Landon Reed wrote:

Hi Colin,

I may be speaking out of turn (my information is a few years old), but my understanding is that their AVL provider (RouteMatch, I believe) uses entity IDs (e.g., stop and route IDs) as coded information for things like next stop annunciators.  I imagine this latest change is in support of that system.

I'm definitely not condoning this practice, but that was my understanding as of a couple of years ago.

Best,

Landon

---
Landon Reed

@eltiar

On Wed, May 16, 2018 at 3:00 PM 'Colin McGlynn' via atl-transit-developers <atl-transit...@googlegroups.com> wrote:

In the latest GTFS release for GRTA the agency seems to be uisng the full stop name as the stop id e.g. "10900 Medlock Bridge Rd (S)".  That's unusual enough that I'm wondering if that was a mistake made when exporting the GTFS? Does anyone from or GRTA or ARC have any insight as to whether this was intenitonal or if I should expect to see the stop ids  switch back to being numbers on the next release? Thanks!

https://transitfeeds-data.s3-us-west-1.amazonaws.com/public/feeds/grta/66/20180503/original/stops.txt

--
You received this message because you are subscribed to the Google Groups "atl-transit-developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to atl-transit-developers+unsub...@googlegroups.com.