Pedestrian Count Dataset 2024
The Pedestrian Count Dataset documents foot traffic on state highways, originating from Caltrans district pilots initiated in 2024 to monitor active transportation. Data is vendor-collected using technologies like video analytics, then shared with HQ via APIs or files for statewide standardization in CSV format. Core variables include Loc_id (site identifier), Date/Hour (timestamp), Direction (e.g., East Crosswalk), Count (integer volumes), and geospatial (latitude/longitude). Limitations include potential undercounts in adverse weather and incomplete coverage. This supports equity-focused planning under Complete Streets policies, with updates as pilots expand.
Data dictionary
Field definitions supplied by the publishing agency in CKAN.
| Column | Type | Label | Description |
|---|---|---|---|
| loc_id | numeric | loc_id | — |
| district | numeric | district | — |
| latitude | numeric | latitude | — |
| longitude | numeric | longitude | — |
| date | timestamp | date | — |
| mode | text | mode | — |
| direction | text | direction | — |
| count | numeric | count | — |
| count_type | text | count_type | — |
Resource details
| Format | CSV |
|---|---|
| Size | 99 MB |
| Rows | 1,158,488 |
| Last updated | Sep 29, 2026 |
| Part of | Active Transportation Count Dataset |
CKAN Data API
Access resource data through the CKAN DataStore API. The examples below use this resource's ID.
Endpoints
The Data API provides these actions. Creating or updating records requires appropriate permissions; the query actions read public DataStore records.
| Create | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_create |
|---|---|
| Update / insert | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_upsert |
| Query | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search |
| Query via SQL | https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql |
Query examples
"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=8196d82b-b3f8-46bd-b16c-ab20a4f6169d&limit=5""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=8196d82b-b3f8-46bd-b16c-ab20a4f6169d&q=jones""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%228196d82b-b3f8-46bd-b16c-ab20a4f6169d%22%20LIMIT%205"SQL queries depend on whether SQL search is enabled by the portal.
OData query
Use the resource's OData URL and its field names for paging, selecting columns, or filtering rows.
ODATA_RESOURCE_URL?$top=5
ODATA_RESOURCE_URL?$skip=5&$top=5
ODATA_RESOURCE_URL?$select=FIELD_NAME&$filter=FIELD_NAME eq 'VALUE'Replace ODATA_RESOURCE_URL, FIELD_NAME, and VALUE with the details for the selected resource. See the OData query options guide (opens in a new tab) for more examples.
Use the API in code
JavaScript (JSONP)
var data = { resource_id: '8196d82b-b3f8-46bd-b16c-ab20a4f6169d', limit: 5, q: 'jones' };
$.ajax({
url: 'https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search',
data: data,
dataType: 'jsonp',
success: function (response) {
console.log(response.result.total, response.result.records);
}
});Python
import json
from urllib.request import urlopen
url = 'https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=8196d82b-b3f8-46bd-b16c-ab20a4f6169d&limit=5'
with urlopen(url) as response:
result = json.load(response)['result']
print(result['total'], result['records'])For parameters and response fields, see the CKAN DataStore documentation (opens in a new tab).