trips
This table is a latest-only cut of the cleaned GTFS data. It contains current-only data for agencies we are currently scraping. Each row is a cleaned row from a trips.txt file. Definitions for the original GTFS fields are available at: https://gtfs.org/reference/static#tripstxt.
Data dictionary
Field definitions supplied by the publishing agency in CKAN.
| Column | Type | Label | Description |
|---|---|---|---|
| base64_url | text | base64_url | — |
| route_id | text | route_id | — |
| service_id | text | service_id | — |
| trip_id | text | trip_id | — |
| trip_headsign | text | trip_headsign | — |
| trip_short_name | text | trip_short_name | — |
| direction_id | numeric | direction_id | — |
| block_id | text | block_id | — |
| shape_id | text | shape_id | — |
| wheelchair_accessible | numeric | wheelchair_accessible | — |
| bikes_allowed | numeric | bikes_allowed | — |
Resource details
| Format | CSV |
|---|---|
| Size | 75 MB |
| Rows | 536,869 |
| Last updated | Sep 26, 2026 |
| Part of | Cal-ITP GTFS-Ingest Pipeline Dataset |
Other resources in this dataset
- Cal-ITP GTFS Schedule Metadata
- Cal-ITP GTFS Schedule Data Dictionary
- agency
- areas
- attributions
- calendar
- calendar_dates
- fare_attributes
- fare_rules
- fare_leg_rules
- fare_media
- fare_products
- fare_transfer_rules
- feed_info
- frequencies
- gtfs_datasets
- levels
- pathways
- routes
- shapes
- stop_areas
- stop_times
- stops
- transfers
- translations
- organizations_latest_with_caltrans_district
- services
- provider_gtfs_data
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=0e4da89e-9330-43f8-8de9-305cb7d4918f&limit=5""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=0e4da89e-9330-43f8-8de9-305cb7d4918f&q=jones""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%220e4da89e-9330-43f8-8de9-305cb7d4918f%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: '0e4da89e-9330-43f8-8de9-305cb7d4918f', 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=0e4da89e-9330-43f8-8de9-305cb7d4918f&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).