Issue 424 in onebusaway: Stop 1_2663 should be combined into stop 1_29240

[onebu...@googlecode.com]

Status: New
Owner: ----

New issue 424 by hoffman...@gmail.com: Stop 1_2663 should be combined into
stop 1_29240
http://code.google.com/p/onebusaway/issues/detail?id=424

The stops are on top of each other, and share the same sign. This is surely
a sort of data bug from Sound Transit.

[onebu...@googlecode.com]

Comment #1 on issue 424 by cookieguru: Stop 1_2663 should be combined into
stop 1_29240
http://code.google.com/p/onebusaway/issues/detail?id=424

Stop 1_2663 does not exist. Did you mean 40_2663?

This is not a bug from Sound Transit, nor is it a bug from Metro. Both
agencies provide schedule data independently. Each invents their own ID
numbers for a given stop. When data from both agencies are placed on the
map, two stops may appear to be in close proximity to each other since both
agencies may not have assigned the exact same latitude/longitude to a given
stop.

Brian has, in a semi-automated fashion, attempted to combine these stops
since they appear as the same physical stop to the end user. Sometimes
some stops fall through the cracks or a stop gets a new ID number for
whatever reason and thus the procedure to "combine" the stops "breaks".

Anyway, the following stops need updating in PugetSoundStopConsolidation
1_29240 40_2663
1_60900 3_2282
1_80451 3_4367

Also, 1_29242 and 1_29410 are nearly on top of each other despite serving
routes operating in opposing directions.

[onebu...@googlecode.com]

Comment #2 on issue 424 by hoffman...@gmail.com: Stop 1_2663 should be

combined into stop 1_29240
http://code.google.com/p/onebusaway/issues/detail?id=424

Sorry, I meant 3_2663.

[onebu...@googlecode.com]

Comment #3 on issue 424 by hoffman...@gmail.com: Stop 1_2663 should be

combined into stop 1_29240
http://code.google.com/p/onebusaway/issues/detail?id=424

This has been fixed.