search

remulasce / metroapp

Realtime arrival notification utility for LA Metro
2 stars 0 forks source link

Arrivals to some endpoints not displayed #153

Closed remulasce closed 8 years ago

remulasce commented 9 years ago

I think this is mostly Metro's fault. At termini, they're supposed to use 2 different stoptags, each unique. That usually means one per platform. But at the ends of brt lines, there's only one 'platform'. So they add _ar to the end of the stoptag to invent a second platform to use as the destination.

That would work, except they don't bother attaching the stopid to the arrival platform. So it doesn't show up in searches by stopId. Therefore, I never receive the arrival info for these stations.

The solution should be to search by route + stoptag But, I don't actually know what routes go where.

A proper fix would need to do a lot more parsing work on the gtfs stopfiles, which I don't have time for. But, maybe I can either guess at which stops need proper _ar tags, or if it's just the two brt lines, I can hack them in to just work on them.

remulasce commented 9 years ago

It looks like rail is done properly by using different stop tags for each side/platform.

Busses are hit and miss- half the arrivals only work because the directions aren't actually set to use the arrival stopid.

remulasce commented 9 years ago

Note that this only occurs at big bus transfer stations, which use only one platform per line. All the regular bus lines have separate endpoints on opposite sides of the street, and they're all OK.

route+stoptag searching is definitely the answer. We may need to switch to that as part of multi-city support.

remulasce commented 9 years ago

Note that we now use NexTrip scraper tables instead of GTFS mappings.

We still just use the stopID though, so we'd need a little work in the scraper to properly support this kind of search.

Given the combination of NexTrip + gov't agency, though, I wouldn't count on both search methods returning the same thing.

remulasce commented 8 years ago

This got fixed a while ago with route + stoptag