Major changes to server.py details.

[darkzeroman]

I've been working on a GT Nextbus app, so I have a some experience in dealing with Nextbus' weird API. I would recommend glancing the README to understand the _title vs _tag variable names.

So first thing I've introduced is this route config file that I had constructed while making the app. It has information about all routes/directions/stops. This was made from different sources and I had to manually edit this a few times.

So this should be used instead of all those conditionals, using this file makes life a lot easier and helps a great deal for expanding this to other routes. I have taken out the route information all other routes beside red/blue because there isn't the walking data for the many of the new stops from other routes (Tech Trolley, Green, etc)

There are some issues in the API that need to be known.

• Each stop has it's own unique stop_tag. For example, the Student Center has two stops, one for each side of the road. If I remember correctly, the stop_tags are centrstud and studcentr, so each side of the road is it's own stop. Therefore, in the GT NextBus app, I had to group the stops by stop_titles instead of stop_tags.
• It's very important to consider the direction in the API calls, for red/blue the direction is not used since there is only one. But for routes like Trolley, the direction matters, so that's why the code works now, but won't if new routes are added.

I've aded another file "v2methods" which includes my current work to integrate the changes into server.py. My changes can be seen here.

Seems like there are some indentation/space/tab issues, I'll get those fixed soon.

[blueintegral]

Looks great. It looks like in v2methods.py, you're GETing NextBus data from a Heroku app of some kind. Is that something you wrote for interfacing with the NextBus API?

[darkzeroman]

At first I used my own API, but now I'm using the method from your original code.

[Tanner]

Awesome. The route config file seems like an awesome asset.

[darkzeroman]

So we need to figure out what's the future with this project.

I'm able to work on the "backend" of the app, but would need someone else to work on the front end.

The next few things that need to be done are:

• Add the new routes/stops. The backend should already be ready for them, but someone needs to add the new routes stops in the list that is chosen by the user. There is concern about which routes are necessary, because adding ALL stops for all routes might just be too messy and confusing for the user. I think the red/blue/trolley/night are the four most used. So there doesn't need to be support for emory/green. It would be preferable to get the route stop information from routeConfig.txt.
• Add more of the points(stops) for the Google determine walking thingy. I am vague about this because I'm not sure how that works to be honest. It seems like GPS coordinates are used, the coordinates from routeConfig are probably not all correct since I don't use them on the GT Nextbus app.
• Need to code/account for the times bus routes are running.

[Tanner]

I would separate those into different issues so they don't clutter this one and can be discussed independently.

[Tanner]

@darkzeroman's second point is covered in #11.