SB X7-7 Targets for Urban Retail Water Suppliers
The Water Conservation Act of 2009 (Senate Bill X7-7) was enacted in November 2009 and required that all water suppliers increase their water use efficiency. Water Code section 10608.20 directed urban retail water suppliers (suppliers) to develop 2020 urban water use targets.
This table contains the suppliers’ individual SB X7-7 targets. Because some suppliers deducted discrete demands from gross water use when calculating their 2020 urban water use targets, the table also contains the volume of those deducted demands, specifically for indirect recycled water and process water.
Water Code section 10608.20(a)(1) and 10608.28 provided that suppliers may plan, comply, and report on a regional basis, individual basis, or both. Each group of water suppliers agreeing among themselves to plan, comply, and report as a region is referred to as a “regional alliance.” For those suppliers that took part in a regional alliance, this table also lists the regional alliance name and indicates whether the regional alliance has met its target.
All data within this table were derived from the 2020 Urban Water Management Plans Open Data, which were created using data submitted by suppliers to Department. Specifically, this table was created using the following fields:
- Individual SB X7-7 target from Tab SB_X7-7_CF_Table_9, column K
- Indirect recycled water volume from Tab SB_X7-7_CF_Table_4, column J
- Process water volume from Tab SB_X7-7_CF_Table_4, column L
- Recycled and process water units from Tab SB_X7-7_VF_Table_0, column F
- Regional alliance name from Tab SB_X7-7_CF_Table_9
- Whether the regional alliance met its target Tab Regional_Alliance_Summary, column F
As described in the 2020 Urban Water Management Guidebook(Appendix P.3.2), a supplier’s target may be updated if its service area has changed because of a consolidation, merger, annexation, expansion, or contraction. To learn more about this process, please e-mail uwmphelp@water.ca.gov.
Data dictionary
Field definitions supplied by the publishing agency in CKAN.
| Column | Type | Label | Description |
|---|---|---|---|
| ORG_ID | numeric | ORG_ID | — |
| SUPPLIER_NAME | text | SUPPLIER_NAME | — |
| CONFIRMED_TARGET_2020 | numeric | CONFIRMED_TARGET_2020 | — |
| INDIRECT_RECYCLED_WATER_VOL | numeric | INDIRECT_RECYCLED_WATER_VOL | — |
| PROCESS_WATER_VOL | numeric | PROCESS_WATER_VOL | — |
| UNITS_OF_MEASURE | text | UNITS_OF_MEASURE | — |
| REGIONAL_ALLIANCE_NAME | text | REGIONAL_ALLIANCE_NAME | — |
| ALLIANCE_MET_TARGET | text | ALLIANCE_MET_TARGET | — |
Resource details
| Format | CSV |
|---|---|
| Size | 22 KB |
| Rows | 404 |
| Last updated | Sep 30, 2026 |
| Part of | Urban Water Use Objectives – Relevant Data |
Other resources in this dataset
- PWSID-DWR ID Crosswalk
- Res-Indoor Budget: SDWIS Residential Population
- Res-Outdoor Budget: Landscape Area Measurement
- Annual Weather Data
- Seasonal Weather Data
- Real Water Loss Budget: System-Specific Standards
- Real Water Loss: Data from Water Loss Audits
- Potable Water Produced by URWS, per Source
- Potable and Non-Potable Water Deliveries for URWS
- Potable Supply and Sold/Exported for URWS
- CII Service Connections
- Submissions and Approvals for Variances and Temporary Provisions
- Residential Indoor Variances and Temporary Provisions
- Residential Outdoor Variances and Temporary Provisions
- Emergency and High Total Dissolved Solids (TDS) Variances
- [Archived] PWSID-DWRID Crosswalk
- [Archived] Res-Outdoor Budget: Landscape Area Measurement
- [Archived] Submissions and Approvals for Variances and Temporary Provisions
- [Archived] Residential Indoor Variances and Temporary Provisions
- [Archived] Residential Outdoor Variances and Temporary Provisions
- [Archived] Emergency and High Total Dissolved Solids (TDS) Variances
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=16a2fe04-065c-4923-9ce4-ec858e7e89fc&limit=5""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=16a2fe04-065c-4923-9ce4-ec858e7e89fc&q=jones""https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%2216a2fe04-065c-4923-9ce4-ec858e7e89fc%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: '16a2fe04-065c-4923-9ce4-ec858e7e89fc', 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=16a2fe04-065c-4923-9ce4-ec858e7e89fc&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).