CSV

Change in Storage - Principal Aquifer

Data dictionary

Field definitions supplied by the publishing agency in CKAN.

Column	Type	Label	Description
GSPAR_ID	text	—	For GSP Annual Reports, the Annual Report's ID was created by the SGMA Portal. If this field is populated it indicates that the Annual Report is associated with a GSP.
ALTAR_ID	text	—	For Alternative to GSP Annual Reports, the Annual Report's ID was created by the SGMA Portal. If this field is populated it indicates that the Annual Report is associated with an Alternative to GSP.
REPORT_YEAR	numeric	Water Year	The water year (October 1 to September 30) covered in the Annual Report.
BASIN_NAME	text	Basin Name	The name of the basin covered by the Annual Report.
SUBBASIN_NUMBER	text	Basin Number	The number of the basin covered by the Annual Report.
SINGLE_MULTIPLE_AR	text	Single or Multiple	Whether the Annual Report is a single report covering the entire basin or one of multiple annual reports covering a portion of the basin.
ANNUAL_REPORT_AREA	text	Basin Portion	GSP Local ID portion or entire basin.
AQUIFER_NAME	text	Principal Aquifer Name	The principal aquifer as defined in the basin's groundwater sustainability plan(s).
CHANGE_AMOUNT	numeric	Change in Storage	The change in storage, in acre-feet, for the corresponding principal aquifer where negative values indicate a loss in storage and positive values indicate an increase in storage.
CHANGE_IN_STORAGE_METHOD	text	—	—

Resource details

Format	CSV
Last updated	Oct 7, 2026
Part of	Groundwater Sustainability Plan Annual Report Data

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

First five results

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=e6b25127-47dd-4c80-85aa-a8c35a6a6d01&limit=5"

Results containing "jones"

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=e6b25127-47dd-4c80-85aa-a8c35a6a6d01&q=jones"

SQL query

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%22e6b25127-47dd-4c80-85aa-a8c35a6a6d01%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: 'e6b25127-47dd-4c80-85aa-a8c35a6a6d01', 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=e6b25127-47dd-4c80-85aa-a8c35a6a6d01&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).