Traffic Loop Count (BETA)

This dataset contains 2 web services which can be used to download the locations of City of Surrey traffic loops and the traffic loop counts.

Traffic Loops web service accepts a single optional parameter proj_epsg which is the EPSG code for the required projection. The default is 4326 which is WGS84. Simply accessing the URL will download the GeoJSON with the locations of traffic loops currently in use. If you would prefer the data in NAD83 UTM Zone 10 instead you could make the request like this:

LANE_DIRECTION indicates the heading of the traffic (NB, SB, EB, WB).

INTERSECTION_ID corresponds to the INTID field in the intersections dataset which can be found on the Surrey Open Data site.

ROAD_FACILITYID indicates which road segment the loop is located on. This corresponds to the FACILITYID in the Road Centrelines dataset on the City of Surrey Open Data site.

Traffic Loop Counts web service provides the counts for each traffic loop in 15 minute intervals. While the data is broken down by 15 minute intervals it is currently only updated once per day. We are currently working on increasing the frequency of updates in order to allow for real time traffic applications. The LOOP_ID and DATETIME combinations are unique in the output.

The service accepts 2 optional parameters startdatetime and enddatetime which are used to specify the time and date range of interest. These follow the ISO 8601 standard. For example March 24 2016 at 1:00 PM Pacific Standard Time would be 2016-03-24T13:00:00-08. The output timestamp will contain the time zone offset, either -08 (PST) or -07 (PDT) depending on whether daylight savings time was observed at the output datetime. In order to work with local time you may omit the time zone offset from the input and truncate it from the output.

To request all the data from beginning of March 22 until the end of March 23 2016 you would send the following request:

If these 2 parameters are not passed in the data from the last 24 hours is returned.

Additional Notes

The LOOP_ID field is common to both datasets and can be used to cross-reference them.

Please note that these services are in BETA and may change without notice. We are aware of a number of data quality issues and are working to resolve them. Please contact us if you have any feedback.

Data and Resources

  • Traffic Loopsapi

    A web service which provides a current snapshot of the traffic loops...

  • Traffic Loop Countsapi

    A web service that provides traffic loop counts.


First Published Date March 24, 2016
Data Update Frequency Daily
Coordinate system NAD 83 UTM Zone 10