CSV

Res-Indoor Budget: SDWIS Residential Population

Consistent with Health and Safety Code section 116530 and California Code of Regulations title 22 §64412, public water systems report the population served during a specified reporting period and the population type, which can be reported as either Residential (R), Non-Transient (N), Transient (T), or Wholesale (W).

This table contains residential (R) population data for public water systems owned and operated by urban retail water suppliers. "Residential" refers to the number of persons who reside within the water system service area for more than half of the year. For each system, the R-population value represents the most recently reported and most contemporary value for the prior state fiscal year (July to June), as denoted in the FY_START_DATE and FY_END_DATE columns.

Public Water System data, including population, can be viewed using Drinking Water Watch.

If the population values identified in this dataset need to be revised, please contact the appropriate State Water Resources Control Board’s Division of Drinking Water district office and update accordingly. The Division of Drinking Water has documented the procedure to request population changes outside of the Electronic Annual Report here.

Download Resource< Back to dataset

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	—
PWSID	text	PWSID	—
PWS_NAME	text	PWS_NAME	—
COUNTY	text	COUNTY	—
EFF_BEGIN_DT	text	EFF_BEGIN_DT	—
EFF_END_DT	text	EFF_END_DT	—
AVG_DAILY_CNT	numeric	AVG_DAILY_CNT	—
FY_START_DATE	date	FY_START_DATE	—
FY_END_DATE	date	FY_END_DATE	—

Resource details

Format	CSV
Size	197 KB
Rows	1,586
Last updated	Sep 27, 2026
Part of	Urban Water Use Objectives – Relevant 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=7e539a61-9a33-49e5-a5d3-463e43f06109&limit=5"

Results containing "jones"

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search?resource_id=7e539a61-9a33-49e5-a5d3-463e43f06109&q=jones"

SQL query

"https://ckan.cdt.dev.datopian.com/api/3/action/datastore_search_sql?sql=SELECT%20%2A%20FROM%20%227e539a61-9a33-49e5-a5d3-463e43f06109%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: '7e539a61-9a33-49e5-a5d3-463e43f06109', 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=7e539a61-9a33-49e5-a5d3-463e43f06109&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).