Daily Traffic Loop Counts
Traffic Detector Loop Counts web service provides data from the City’s traffic signal controller volume logs. Loops of wire embedded in the pavement are used to detect vehicles travelling through signalized intersections and the detections are logged by the traffic signal controller. Data is available for each detector loop in 15-minute bins. The LOOP_ID and DATETIME combinations are unique in the output. Daily count datasets are located under "Read More".
The locations for each traffic detector loop can be found here in JSON format.
The data is subject to errors that may arise from malfunctioning equipment, road construction, and limitations of the equipment. Damaged or failed equipment records zeros for the associated LOOP_ID. The average annual daily traffic counts can be found on the City of Surrey's Traffic Data Hub.
Daily Traffic Counts
Datasets available for download
-
Document LinkHTML
Linked dataset resource
-
CSVZIP
Additional resource from ArcGIS Hub
Additional Info
| Field | Value |
|---|---|
| Last Updated | March 24, 2026, 21:09 (UTC) |
| Created | March 24, 2026, 21:09 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
Daily Traffic Loop Counts |
|
Description
A description of the dataset.
|
Traffic Detector Loop Counts web service provides data from the City’s traffic signal controller volume logs. Loops of wire embedded in the pavement are used to detect vehicles travelling through signalized intersections and the detections are logged by the traffic signal controller. Data is available for each detector loop in 15-minute bins. The LOOP_ID and DATETIME combinations are unique in the output. Daily count datasets are located under "Read More". The locations for each traffic detector loop can be found here in JSON format. Daily Traffic Counts |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
0.15 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2025-10-27 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
License not specified |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://opendata-surrey.hub.arcgis.com/datasets/surrey::daily-traffic-loop-counts |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
SurreyGIS |
|
Contact Point
Who to contact regarding access?
|
City of Surrey |
|
Contact Point Email
The email to contact regarding access?
|
|
|
Publisher
Publisher of the dataset.
|
City of Surrey |
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
SurreyGIS |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2026-03-02 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
9db37af303984a74b14f0d256358aa11 |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://opendata-surrey.hub.arcgis.com/datasets/surrey::daily-traffic-loop-counts |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
City of Surrey |
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
|
|
Number of data columns
If tabular dataset, total number of unique columns.
|
|
|
Number of data cells
If tabular dataset, total number of cells with data.
|
|
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments