Hydrologic Metrics
This dataset describes the hydrologic metrics used to characterize the degree of hydrologic alteration at each of the sites included in this study. The degree of hydrologic alteration at each site is assessed by comparing estimates of present-day and historical flows using a set of regionally calibrated hydrologic models. The hydrologic metrics in this dataset can be compared to the biological condition at corresponding sites (described in the Biological Endpoints dataset) to estimate the probability of good biological conditions along gradients of increasing hydrologic alteration.
Data dictionary
Field definitions supplied by the publishing agency in CKAN.
| Column | Type | Label | Description |
|---|---|---|---|
| StationCode | text | StationCode | — |
| MetricCalcSource | text | MetricCalcSource | — |
| MetricID | text | MetricID | — |
| Precip | text | Precip | — |
| FlowMetric | text | FlowMetric | — |
| KeyMetric | numeric | KeyMetric | — |
| GeneralMetric | numeric | GeneralMetric | — |
| MetricClass | text | MetricClass | — |
| DeltaH | text | DeltaH | — |
| DecThresh_cons | text | DecThresh_cons | — |
| IncThresh_cons | text | IncThresh_cons | — |
| HydroAltScore | text | HydroAltScore | — |
| HydroAltScore_direction | text | HydroAltScore_direction | — |
Resource details
| Format | CSV |
|---|---|
| Size | 5.6 MB |
| Rows | 67,496 |
| Last updated | Sep 27, 2026 |
| Part of | Surface Water - Flow Targets for Southern California Streams |
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=e38d6d48-4be4-4604-9795-a831b2d54986&limit=5""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=e38d6d48-4be4-4604-9795-a831b2d54986&q=jones""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%22e38d6d48-4be4-4604-9795-a831b2d54986%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: 'e38d6d48-4be4-4604-9795-a831b2d54986', 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=e38d6d48-4be4-4604-9795-a831b2d54986&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).