California Independent Storage Inventory

Monthly inventory each independent storage field in Northern California posts: wild_goose and lodi in Bcf, central_valley in Dth, gill_ranch as percent full.

California independent storageInfrastructure data CAISO market

Open in Data Ask the agent

One row per: facility x month; Monthly cadence
Evidence: Observed market data; Published observations from the named source
Time basis: Date-labelled records; UTC · event_time

Overview

unit says which; never add facilities with different units. Published by each facility operator.

Query contract: Preserve one canonical row per (facility, report_date) before aggregating.
Analysis rules: Read with FINAL.Units differ by facility; never add facilities.
Interpretation: One utility's own system, not California-wide: PG&E and SoCalGas are separate systems, and neither includes the other's demand.Published by the facility operator; attribute it to the facility operator whenever it is reported.

Access

Download: Query it in SQL, download it, or read it with an API key. Download data
MCP: Connect an MCP client and load the contract with describe_data before calling query_data.CAISO MCP API reference
HTTP endpoint: POST /api/v1/datasets/ca_independent_storage_monthly_inventory/query
Full history: Delivered to Snowflake, Databricks or your own storage on a schedule by Data services.
More coverage

Schema

10 columns

Column	Type
`event_time`	`DateTime64(6, 'UTC')`
`facility`	`LowCardinality(String)`
`report_date`	`Date32`
`posted_revision`	`String`
`posted_at`	`Nullable(DateTime64(6, 'UTC'))`
`value`	`Nullable(Float64)`
`unit`	`LowCardinality(String)`
`value_text`	`String`
`source_url`	`String`
`ingested_at`	`DateTime64(6, 'UTC')`

Sample data

event_time	facility	report_date	posted_revision	posted_at	value	unit	value_text	source_url	ingested_at
2026-10-01 00:00:00.000000	gill_ranch	2026-10-01	2026-10-12T16:39:34Z	2026-10-12 16:39:34.000000	81.32	percent	81.32% Full	https://gillranchstorage.com/wp-content/uploads/2026/10/20261012-October-2026-Monthly-Gas-Storage-Inventory.pdf	2026-10-31 06:39:17.581557
2026-09-30 00:00:00.000000	central_valley	2026-09-30	2026-10-15T17:43:21Z	2026-10-15 17:43:21.000000	9615725	Dth	9,615,725	http://www.gasnom.com/ip/centralvalley/Fileviewer.cfm?FromLoc=Links&file=CPUC%20Monthly%20Inventory.pdf	2026-10-31 06:39:05.717191
2026-09-30 00:00:00.000000	lodi	2026-09-30	18	∅	37.184	Bcf	37.184	https://rgsi.com/api/msireports?year=2026&facility=Lodi	2026-10-31 06:38:53.690769
2026-09-30 00:00:00.000000	wild_goose	2026-09-30	19	∅	79.699	Bcf	79.699	https://rgsi.com/api/msireports?year=2026&facility=Wild+Goose	2026-10-31 06:38:51.841070
2026-09-01 00:00:00.000000	gill_ranch	2026-09-01	2026-09-12T18:03:56Z	2026-09-12 18:03:56.000000	84.03	percent	84.03% Full	https://gillranchstorage.com/wp-content/uploads/2026/09/20260912-September-2026-Monthly-Gas-Storage-Inventory.pdf	2026-10-31 06:39:17.581557
2026-09-01 00:00:00.000000	gill_ranch	2026-09-01	2026-10-12T16:39:34Z	2026-10-12 16:39:34.000000	84.03	percent	84.03% Full	https://gillranchstorage.com/wp-content/uploads/2026/10/20261012-October-2026-Monthly-Gas-Storage-Inventory.pdf	2026-10-31 06:39:17.581557

Coverage

Complete: 7.0%
Gap days: 200
Days with data: 15

Show coverage history

Coverage: 7.0%Days with data: 15Gaps: 200

2026

gaplessmore

Related data

Related infrastructure data
Dataset	Description
Advanced MetersEIA · annual (report year)	EIA-861 advanced metering: AMR, AMI and other meter counts, AMI energy served and customer access, by utility and customer class. Advanced_Meters, one row per utility, state, balancing authority and customer class. customer_class is residential, commercial, industrial, transportation (direct_connected in the distributed generation tables) or EIA's own total, so summing classes without excluding total counts everything twice. event_time is 1 January of the report year. release is final or early_release: EIA posts an early release of a year in August and replaces it with the final file in the autumn, and the mirror keeps the newest row per key. A key cell EIA leaves blank is '' or 0, and duplicate_index numbers rows that still share a key, in workbook order.
AESO Asset ListAESO · daily snapshot	AESO's registry of market assets: asset code, name, pool participant, operating status and asset type (source, sink and others), including retired assets.
Alberta (AESO) Price LocationsAESO · slow-moving dimension, refreshed every 6 hours	Every Alberta (AESO) location that carries a price, as three columns: location_id, name, and kind. 1 rows — system (1). This is the dimension the Alberta (AESO) price, and where applicable constraint, tables join to, and it is the one place a location's type is decided: resolve "which hubs exist", "is this a zone or a node", or "give me the readable name for this id" here rather than inferring a type from a name prefix. For Alberta, the one location_id is SYSTEM: the pool price (aeso.pool_price) and system marginal price (aeso.system_marginal_price) are system-wide and carry no location column. Alberta has no nodal, zonal or hub prices; do not look for one. Generating assets are identified by AESO asset code in aeso.unit_status and aeso.asset_list, not here. The same three columns exist for every market, so the equivalent question in another ISO is the same query against that ISO's table.
Baja California (CENACE) Price LocationsBCA · slow-moving dimension, refreshed every 6 hours	Every Baja California (CENACE) location that carries a price, as three columns: location_id, name, and kind. 4 rows — zone (4). This is the dimension the Baja California (CENACE) price, and where applicable constraint, tables join to, and it is the one place a location's type is decided: resolve "which hubs exist", "is this a zone or a node", or "give me the readable name for this id" here rather than inferring a type from a name prefix. For Baja California, location_id is CENACE's load zone (TIJUANA, MEXICALI, ENSENADA, SANLUIS) and joins cenace.zonal_prices.load_zone; name is the city it is named for. CENACE prices Baja California by load zone only; there are no nodes or hubs in this dimension. The same three columns exist for every market, so the equivalent question in another ISO is the same query against that ISO's table.