How to collate multiple routes at the same stop?

[Jason Rosenbaum]

Do folks have any advice into collating multiple routes into the same stop?

I was previously using stopId, but have now realized that this doesn't work all of the time. For example, sometimes the same stopId represents the same stop:

http://webservices.nextbus.com/service/publicXMLFeed?command=predictions&a=dc-circulator&stopId=0114

As you can see there, we have two routes that both service the same stop (8th Street SE And G Street SE), so I can call all predictions at that stop with one stopId.

However, with a call like this it falls down:

http://webservices.nextbus.com/service/publicXMLFeed?command=predictions&a=dc-circulator&stopId=0132

There, we get three routes, but the two stops represented are actually across the city from each other, 13th Street NW And K Street vs. M Street NW And Wisconsin Avenue NW, yet somehow they have the same stopId.

I was looking at other ways of collating stops that have multiple routes, but none seem to work. For example, I was looking at matching on lat/lon (if two different routes return a stop with the same lat/lon, they're clearly the same stop) but that doesn't work either, as stops that are the same return very slightly different lat/lon. 

Anyone have suggestions on how this can be accomplished? I'd like to be able to show my users one pin on a map that represents one physical stop, and when more detail is requested on that stop show users predictions for any routes that service that stop.

Thanks!

--Jason

_________________________________

Jason Rosenbaum

Email/GChat: sem...@theseminal.com

Cell: 914.806.1939

Twitter: http://twitter.com/j_ro