Make get_or_create less braindead. Instead of looking for a 100% identical match, it looks for one with matching keys/indices. If those match, the old record is returned. Caveat: Returned record not guaranteed to 100% match the entered parameters - only the keys. Could be bad if not accounted for

Worked around Nextbus stop tag shenanigans. Some stops are represented by multiple stop tags, the only commonality being Stop Title. Same-title stops within geographic proximity (as defined in config.py) will be stored as one stop. Tags are still tracked, as they are needed for linking routes to stops.

Nextbus gives the same stop tag for multiple routes, but with *slightly* differring lat/lon coordinates. Instead of having one Stop object per route, we will now gather them into one Stop per Stop Tag (as long as all instances are in a proximity defined by SAME_STOP_LAT and SAME_STOP_LON). Also misc cleanup/comments.

SQLAlchemy query optimizations. Got rid of individual route+stop+direction queries, and made other stuff faster where possible. Eliminated a few queries.

Models for Agency and Region done, started building Nextbus provider code (API client), added get_or_create convenience fn for models. Fetching agencies works!

Added initial database stuff; SQLAlchemy, SQLAlchemy-Migrate, Flask-SQLAlchemy. Also Flask-Script for manage.py (which is now usable for database operations too)