Overview
Provides comprehensive access to the Data Commons Python API v2 for querying statistical observations, exploring the knowledge graph, and resolving entity identifiers. Data Commons aggregates data from census bureaus, health organizations, environmental agencies, and other authoritative sources into a unified knowledge graph.
Verified against datacommons-client 2.1.6 (current as of 2026-09; Python ≥ 3.10). This is the V2 client (package datacommons_client), not the legacy datacommons (V1) package — the two have different APIs; do not mix them. Keyword names matter: the place-hierarchy helpers take place_dcids, fetch_entity_names takes entity_dcids, and fetch_property_values takes properties — passing node_dcids to them raises TypeError.
When to Use This Skill
- Pulling population, economic, health, education, or environmental statistics for places (countries, states, counties, cities)
- Building cross-place or time-series comparisons from harmonized public sources (census, BLS, WHO, World Bank, EPA, …)
- Resolving place names, coordinates, or Wikidata IDs to Data Commons DCIDs
- Exploring the Data Commons knowledge graph (place hierarchies, properties, statistical-variable definitions)
Does NOT Trigger
| Scenario | Use Instead |
|---|---|
| A specific FRED economic series (GDP, CPI, interest rates) with vintage/revision data | alterlab-fred |
| U.S. Treasury fiscal data (debt, spending, revenue) | alterlab-usfiscaldata |
| NCI Imaging Data Commons (CT/MR/pathology images) — a different "Data Commons" | alterlab-imaging-data-commons |
| Spatial joins, buffers, or mapping of geometries | alterlab-geopandas |
Installation
Install the Data Commons V2 client with Pandas support (extra is lowercase pandas):
uv pip install "datacommons-client[pandas]"
For basic usage without Pandas:
uv pip install datacommons-client
Core Capabilities
The Data Commons API consists of three main endpoints, each detailed in dedicated reference files:
1. Observation Endpoint - Statistical Data Queries
Query time-series statistical data for entities. See references/observation.md for comprehensive documentation.
Primary use cases:
- Retrieve population, economic, health, or environmental statistics
- Access historical time-series data for trend analysis
- Query data for hierarchies (all counties in a state, all countries in a region)
- Compare statistics across multiple entities
- Filter by data source for consistency
Common patterns:
from datacommons_client import DataCommonsClient
client = DataCommonsClient()
# Get latest population data
response = client.observation.fetch(
variable_dcids=["Count_Person"],
entity_dcids=["geoId/06"], # California
date="latest"
)
# Get time series
response = client.observation.fetch(
variable_dcids=["UnemploymentRate_Person"],
entity_dcids=["country/USA"],
date="all"
)
# Query by hierarchy
response = client.observation.fetch(
variable_dcids=["Median_Income_Household"],
entity_expression="geoId/06<-containedInPlace+{typeOf:County}",
date="2020"
)
2. Node Endpoint - Knowledge Graph Exploration
Explore entity relationships and properties within the knowledge graph. See references/node.md for comprehensive documentation.
Primary use cases:
- Discover available properties for entities
- Navigate geographic hierarchies (parent/child relationships)
- Retrieve entity names and metadata
- Explore connections between entities
- List all entity types in the graph
Common patterns:
# Discover properties
labels = client.node.fetch_property_labels(
node_dcids=["geoId/06"],
out=True
)
# Navigate hierarchy (dict: DCID -> list of {"dcid", "name", "types"})
children = client.node.fetch_place_children(
place_dcids="country/USA",
children_type="State",
)
# Get entity names (dict: DCID -> Name(value=..., language=...))
names = client.node.fetch_entity_names(
entity_dcids=["geoId/06", "geoId/48"]
)
3. Resolve Endpoint - Entity Identification
Translate entity names, coordinates, or external IDs into Data Commons IDs (DCIDs). See references/resolve.md for comprehensive documentation.
Primary use cases:
- Convert place names to DCIDs for queries
- Resolve coordinates to places
- Map Wikidata IDs to Data Commons entities
- Handle ambiguous entity names
Common patterns:
# Resolve by name
response = client.resolve.fetch_dcids_by_name(
names=["California", "Texas"],
entity_type="State"
)
# Resolve by coordinates (returns a ResolveResponse, not a bare DCID)
coord_response = client.resolve.fetch_dcid_by_coordinates(
latitude="37.7749",
longitude="-122.4194"
)
# Resolve Wikidata IDs
response = client.resolve.fetch_dcids_by_wikidata_id(
wikidata_ids=["Q30", "Q99"]
)
Typical Workflow
Most Data Commons queries follow this pattern:
-
Resolve entities (if starting with names):
resolve_response = client.resolve.fetch_dcids_by_name( names=["California", "Texas"], entity_type="State" ) # to_dict() -> {"entities": [{"node": "California", "candidates": [{"dcid": ...}]}, ...]} dcids = [e["candidates"][0]["dcid"] for e in resolve_response.to_dict()["entities"] if e.get("candidates")] # or: resolve_response.to_flat_dict() -> {"California": "geoId/06", ...} # (a list of DCIDs when the name is ambiguous) -
Discover available variables (optional):
variables = client.observation.fetch_available_statistical_variables( entity_dcids=dcids ) -
Query statistical data:
response = client.observation.fetch( variable_dcids=["Count_Person", "UnemploymentRate_Person"], entity_dcids=dcids, date="latest" ) -
Process results:
# As dictionary data = response.to_dict() # As flat records (date, entity, variable, value + facet metadata). # to_observation_records() returns a pydantic model — dump it before # building a DataFrame, or the columns come out as 0..N. records = response.to_observation_records().model_dump() df = pd.DataFrame(records)To skip the manual conversion, the client also exposes a dedicated DataFrame accessor that runs the same query and returns a tidy DataFrame directly:
df = client.observations_dataframe( variable_dcids=["Count_Person"], entity_dcids=["geoId/06", "geoId/48"], date="all", )
Finding Statistical Variables
Statistical variables use specific naming patterns in Data Commons:
Common variable patterns:
Count_Person- Total populationCount_Person_Female- Female populationUnemploymentRate_Person- Unemployment rateMedian_Income_Household- Median household incomeCount_Death- Death countMedian_Age_Person- Median age
Discovery methods:
# Check what variables are available for an entity
available = client.observation.fetch_available_statistical_variables(
entity_dcids=["geoId/06"]
)
# Or explore via the web interface
# https://datacommons.org/tools/statvar
Working with Pandas
The idiomatic path is the client's observations_dataframe() accessor, which mirrors
observation.fetch() arguments but returns a tidy DataFrame in one call (requires the
pandas extra):
df = client.observations_dataframe(
variable_dcids=["Count_Person"],
entity_dcids=["geoId/06", "geoId/48"],
date="all",
)
# Columns: date, entity, variable, value (plus facet/provenance columns)
# Reshape for analysis
pivot = df.pivot_table(
values='value',
index='date',
columns='entity'
)
For every entity of a type under a parent place, pass entity_dcids="all" with
entity_type and parent_entity:
df = client.observations_dataframe(
variable_dcids=["Median_Income_Household"],
date="latest",
entity_dcids="all",
entity_type="County",
parent_entity="geoId/06",
)
If you already have a response object, flatten it with to_observation_records()
(singular "observation"; there is no to_observations_as_records) and dump it:
response = client.observation.fetch(
variable_dcids=["Count_Person"],
entity_dcids=["geoId/06", "geoId/48"],
date="all",
)
df = pd.DataFrame(response.to_observation_records().model_dump())
API Authentication
For datacommons.org (default):
- An API key is required for observation and node queries (unauthenticated calls return
HTTP 401
UNAUTHENTICATED); name resolution currently answers without one - Set via environment variable:
export DC_API_KEY="your_key" - Or pass when initializing:
client = DataCommonsClient(api_key="your_key") - Request keys at: https://apikeys.datacommons.org/
For custom Data Commons instances:
- No API key required
- Specify custom endpoint:
client = DataCommonsClient(url="https://custom.datacommons.org")
Reference Documentation
Comprehensive documentation for each endpoint is available in the references/ directory:
references/observation.md: Complete Observation API documentation with all methods, parameters, response formats, and common use casesreferences/node.md: Complete Node API documentation for graph exploration, property queries, and hierarchy navigationreferences/resolve.md: Complete Resolve API documentation for entity identification and DCID resolutionreferences/getting_started.md: Quickstart guide with end-to-end examples and common patterns
Additional Resources
- Official Documentation: https://docs.datacommons.org/api/python/v2/
- Statistical Variable Explorer: https://datacommons.org/tools/statvar
- Data Commons Browser: https://datacommons.org/browser/
- GitHub Repository: https://github.com/datacommonsorg/api-python
Tips for Effective Use
- Always start with resolution: Convert names to DCIDs before querying data
- Use relation expressions for hierarchies: Query all children at once instead of individual queries
- Check data availability first: Use
fetch_available_statistical_variables()to see what's queryable - Leverage Pandas integration: Convert responses to DataFrames for analysis
- Cache resolutions: If querying the same entities repeatedly, store name→DCID mappings
- Filter by facet for consistency: Use
filter_facet_domainsto ensure data from the same source - Read reference docs: Each endpoint has extensive documentation in the
references/directory
Scripts
scripts/query_datacommons.py — runnable helper for the Data Commons REST v2 API (needs a free key in DC_API_KEY):
python scripts/query_datacommons.py resolve "California" --type State
python scripts/query_datacommons.py observe Count_Person geoId/06 --date latest