Fix the case with overlapping map stops

[onebusaway]

Fix the case with overlapping map stops

[paulcwatts]

Also reference this older bug: http://code.google.com/p/seattle-bus-bot/issues/detail?id=79

[cookieguru]

Brian had some code that would automatically detect and merge nearby stops when he imported multiple agencies' GTFS files. I don't know where it is, but given that OBA is still running strong I'd assume the script is alive and functional somewhere.

[bbodenmiller]

I think this would be better off at a API level than in each app.

[barbeau]

Yeah, this should really be fixed in the configuration of the bundle-building phase when deploying data with an OBA server. It can either be done with a manual mapping (e.g., and semi-automated using something like this tool we created for Tampa Bay - https://github.com/CUTR-at-USF/onebusaway-stop-consolidation-support), or via an automated process if there are a lot of overlapping stops - see https://groups.google.com/forum/#!topic/onebusaway-developers/FvOOav_C9D4 for a discussion of how this works for Sound Transit. These are much better approaches to fixing the problem, and I haven't actually seen this happen since I've been maintaining the app (so maybe this is already fixed server-side in all regions?) so I'm going to close this out as "Won't fix" for now. If it pops up again we can revisit.