DWR Technical Support Services (TSS) Wells
The Department of Water Resources (DWR) Technical Support Services (TSS) Wells dataset contains information regarding wells completed associated with the TSS program (https://water.ca.gov/Programs/Groundwater-Management/Assistance-and-Engagement). The wells included in this dataset have been completed, a well completion report (WCR) has been submitted through the Online System for Well Completion Reports (OSWCR), and have been registered either through the California Statewide Groundwater Elevation Monitoring (CASGEM) Online System or the Sustainable Groundwater Management Act (SGMA) Portal’s Monitoring Network Module (MNM). In addition, the OSWCR Record ID and CASGEM/MNM Site Codes must be registered in DWR's internal TSS project tracking database.
Data dictionary
Field definitions supplied by the publishing agency in CKAN.
| Column | Type | Label | Description |
|---|---|---|---|
| site_code | text | Site Code | Location based 18 character alphanumeric code assigned to each well. |
| region_office | text | — | — |
| basin_subbasin_name | text | — | — |
| well_name | text | Local Well Name | Local well identification / local well name, number, or code. |
| swn | text | State Well Number | DWR State Well Number |
| stn_id | text | Station ID | Sequential number assigned to each record in the EWM_STATION table; this field based on old export function and may be found arbitrary. |
| wcr_no | text | WCR Number | DWR Well Completion Report Number (OSWCR Legacy Log Number). |
| first_msmt_date | timestamp | — | — |
| last_msmt_date | text | — | — |
| msmt_count | numeric | — | — |
| date_construction_ended | text | — | — |
Resource details
| Format | CSV |
|---|---|
| Last updated | Oct 7, 2026 |
| Part of | DWR Technical Support Services (TSS) |
Other resources in this 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=af23bc39-c744-4bf3-be82-949260f15ba3&limit=5""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=af23bc39-c744-4bf3-be82-949260f15ba3&q=jones""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%22af23bc39-c744-4bf3-be82-949260f15ba3%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: 'af23bc39-c744-4bf3-be82-949260f15ba3', 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=af23bc39-c744-4bf3-be82-949260f15ba3&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).