SEPTA Bus and Trolley Location API
API that provides vehicle positions and routes based on a GPS data feed for each bus and trolley
Organization
Release Date
June 2, 2011
Data Types
GeoJSON,
KML
Categories
Description
This REST API provides real-time SEPTA vehicle positions based on a GPS data feed for each bus and trolley. There are two services - one returning JSON points for the current locations of all vehicles on a particular route and one returning a KML route.
http://www3.septa.org/transitview/bus_route_data/var1
[var1] is the route name. It must be alpha-numeric and must be a valid SEPTA route. Lettered routes are not case sensitive for the JSON service but must be in caps for the KML service.
An example: http://www3.septa.org/transitview/bus_route_data/23
http://www3.septa.org/transitview/kml/var1
[var1] is the name of the route. Lettered routes must be in Caps, such as: http://www3.septa.org/transitview/kml/G
JSON
The JSON API has one variable at the end of the URL in the format:
http://www3.septa.org/transitview/bus_route_data/var1
[var1] is the route name. It must be alpha-numeric and must be a valid SEPTA route. Lettered routes are not case sensitive for the JSON service but must be in caps for the KML service.
An example: http://www3.septa.org/transitview/bus_route_data/23
KML
The KML service trace file shows the patterns that the route follows. The API has one variable in the format:
http://www3.septa.org/transitview/kml/var1
[var1] is the name of the route. Lettered routes must be in Caps, such as: http://www3.septa.org/transitview/kml/G
SEPTA Vehicle Route API 
Organization
Release Date
June 2, 2011
Data Types
GeoJSON,
KML
Categories
Usage
Public use
Description
This REST API provides real-time SEPTA vehicle positions based on a GPS data feed for each bus and trolley. There are two services - one returning JSON points for the current locations of all vehicles on a particular route and one returning a KML route.
http://www3.septa.org/transitview/bus_route_data/var1
[var1] is the route name. It must be alpha-numeric and must be a valid SEPTA route. Lettered routes are not case sensitive for the JSON service but must be in caps for the KML service.
An example: http://www3.septa.org/transitview/bus_route_data/23
http://www3.septa.org/transitview/kml/var1
[var1] is the name of the route. Lettered routes must be in Caps, such as: http://www3.septa.org/transitview/kml/G
JSON
The JSON API has one variable at the end of the URL in the format:
http://www3.septa.org/transitview/bus_route_data/var1
[var1] is the route name. It must be alpha-numeric and must be a valid SEPTA route. Lettered routes are not case sensitive for the JSON service but must be in caps for the KML service.
An example: http://www3.septa.org/transitview/bus_route_data/23
KML
The KML service trace file shows the patterns that the route follows. The API has one variable in the format:
http://www3.septa.org/transitview/kml/var1
[var1] is the name of the route. Lettered routes must be in Caps, such as: http://www3.septa.org/transitview/kml/G
Update Frequency
Continuously
Area of Interest
Southeastern Pennsylvania (Bucks, Chester, Delaware, Montgomery, Philadelphia counties)
Coordinate Systems
4326, World WGS84, Geographic (lat/lon), decimal degrees
Contact Email
Date Added
June 19, 2011, 4:42 p.m.
Last Update
Oct. 2, 2011, 2:55 p.m.
SEPTA Vehicle Route API
Please login to add comments
Comments
rcheetham
06/19/2011
It is really great to see that SEPTA is releasing this data.
jtricarico
10/02/2011
One should note that the "offset" field is the number of minutes since the location was last recorded in the database (usually no more than three).
Average Rating