Cover all rail and bus JSON endpoints

[k5cents]

Cover all the JSON type services:

Bus Route and Stop Methods

• [x] Bus Position
• [x] Path details
• [x] Routes
• [x] Schedule
• [x] Schedule at stop
• [x] Stop search

GTFS

Not JSON:

The General Transit Feed Specification (GTFS), also known as GTFS static or static transit to differentiate it from the GTFS realtime extension, defines a common format for public transportation schedules and associated geographic information. GTFS "feeds" let public transit agencies publish their transit data and developers write applications that consume that data in an interoperable way.

Incidents

• [x] Bus Incidents
• [x] Elevator/Escalator Outages
• [x] Rail Incidents

Misc Methods

• [x] Validate API Key

Rail Station Information

• [x] Lines
• [ ] Parking Information
• [x] Path Between Stations
• [x] Station Entrances
• [x] Station Information
• [x] Station List
• [x] Station Timings
• [x] Station to Station Information

Real-Time Bus Predictions

• [x] Next Buses

Real-Time Rail Predictions

• [x] Next Trains

Train Positions

Different API needed from the typical bus and trail JSON.

• [x] Live Train Positions
• [x] Standard Routes
• [x] Track Circuits

[k5cents]

Need to decide if rail parking should be:

1. function returning a list
2. function returning gross data frame
3. multiple functions

Edit: moved to own issue, see #9.