# Cadastre docs > Cadastre is a data source for real-estate and site-selection data (not listings): public market, labor, demographic, infrastructure, hazard and health datasets for every U.S. metro area, with their sources, licences and methods documented. --- # Cadastre > Cadastre is a data source for real-estate and site-selection data (not listings): public market, labor, demographic, infrastructure, hazard and health datasets for every U.S. metro area, with their sources, licences and methods documented. **Advanced Site Selection.** [Join now](https://getcadastre.com/signup) or [sign in](https://getcadastre.com/login). ## What Cadastre does ### Screen every US metro Set requirements such as population, unemployment, growth, power price and hazard risk, and see which of the 393 US metro areas qualify. Weight the criteria that matter to rank the ones that do. `393 US METRO AREAS` ### Data you can defend Each measure names its source and vintage: Census, BLS, BEA, EIA, FEMA and EPA. A saved snapshot freezes the results and the data behind them, so a report reads the same after a later import. `SOURCE · VINTAGE ON EVERY MEASURE` ### Ready for the client Turn a saved snapshot into a PDF report, an editable PowerPoint deck, or its data as an Excel workbook or CSV. The report and the deck carry the scope, the requirements and the sources. `PDF · PPTX · XLSX · CSV` ## For agents - [llms.txt](https://getcadastre.com/llms.txt): every docs page as Markdown, by section ([llms-full.txt](https://getcadastre.com/llms-full.txt): all of them in one file). - [Docs](https://getcadastre.com/docs): the datasets, how metro values are computed, rights and attribution, and data freshness. Every page is also Markdown at the same address with `.md` added. - [AI agents](https://getcadastre.com/agents.md): connect Claude Code, Codex, Cursor and other agents through the remote MCP server (https://getcadastre.com/mcp, no sign-in needed), with a setup guide for each. - [API](https://getcadastre.com/docs/api.md): the read-only API at https://getcadastre.com/api/v1 (beta, no account needed for the public datasets), its keys, limits and attribution rules. - [MCP server](https://getcadastre.com/docs/mcp.md): the server, its sign-in and its tools. - [CLI](https://getcadastre.com/docs/cli.md): the `cadastre` command line (https://github.com/waratuman/cadastre-cli). - The API, the MCP server and the CLI need no account for the public datasets (30 requests a minute); sign in for higher limits, which need API access turned on per account: ask support@getcadastre.com. ## Account - [Join now](https://getcadastre.com/signup): create an account - [Sign in](https://getcadastre.com/login): to an existing account ## Legal and other pages - [Terms](https://getcadastre.com/terms) - [Privacy](https://getcadastre.com/privacy) - [Open data](https://getcadastre.com/open-data) - [Docs](https://getcadastre.com/docs) - [AI agents](https://getcadastre.com/agents) --- # Introduction > What Cadastre is, and what it offers people, their tools and AI agents. Cadastre is a data source for real-estate and site-selection data. It brings together the public datasets a site-selection decision rests on (markets, labor, demographics, infrastructure, hazards and health) for U.S. metro areas, with each figure traced to its publisher, its licence and the method that produced it. Property and parcel data will join them as it comes online. Cadastre does not carry listings. The same data drives the app, where consultants and developers screen and rank metros and hand clients a report, and it is offered to your own tools and AI agents through a read-only API, a remote MCP server and a command-line tool. ## What's available today - **Metro-level data.** 19 datasets of measures for U.S. metro areas, from U.S. federal agencies and OpenStreetMap: see [Datasets](https://getcadastre.com/docs/datasets). Each dataset page lists its publisher, licence, required credit, period, geographies, measures with their units and how each is assembled for a metro, and its known gaps. - **Screening and ranking in the app.** Requirements and weighted criteria over those measures, a ranked register, saved snapshots, and reports as PDF, PowerPoint, CSV and Excel. - **Documentation an agent can read.** Every page here is also Markdown at the same address with `.md` added (this page is [https://getcadastre.com/docs.md](https://getcadastre.com/docs.md)), [/llms.txt](https://getcadastre.com/llms.txt) lists every page, and [/llms-full.txt](https://getcadastre.com/llms-full.txt) is all of them in one file. - **A read-only API** for the data, screening and ranking, in beta and free while it is, with no account needed for the public datasets; sign in for higher limits, with API access turned on for the account (write to support@getcadastre.com to ask for it). See [API](https://getcadastre.com/docs/api), and [Connect an AI agent](https://getcadastre.com/agents) for setting up each agent. - **Open data.** The OpenStreetMap-derived transmission-line dataset, offered under the ODbL on the [Open data](https://getcadastre.com/open-data) page. - **A remote MCP server** at `https://getcadastre.com/mcp`, so AI assistants such as Claude Code, Codex and Cursor can use the same data with the same access, with no sign-in, or signed in through the browser for higher limits. See [MCP server](https://getcadastre.com/docs/mcp). - **A command-line tool**, `cadastre`, for the terminal and scripts: screens, rankings, comparisons and metro profiles with their attribution, and a command that prints, or writes, your agent's MCP setup. See [CLI](https://getcadastre.com/docs/cli). ## Coming next - **Parcel and property data**, once its sources' rights are cleared. Parcel-level data is not available yet: the launch is metro-level. ## What these docs cover - [Getting started](https://getcadastre.com/docs/getting-started): using the API without an account, signing in, API keys and connecting an agent. - [API](https://getcadastre.com/docs/api), [MCP server](https://getcadastre.com/docs/mcp) and [CLI](https://getcadastre.com/docs/cli): the ways in for your tools and agents. - [Datasets](https://getcadastre.com/docs/datasets): one page per dataset, generated from the code that imports it, so a page cannot say something different from what is imported. - [Methodology](https://getcadastre.com/docs/methodology): how a metro value is made from county data, which vintage is read, and where coverage is missing. - [Rights and attribution](https://getcadastre.com/docs/rights): how each source is licensed, which sources are restricted and why, and the credit each one requires. - [Data freshness](https://getcadastre.com/docs/freshness): the period each dataset describes, when it was last refreshed and when it is next checked. > Docs pages describe data; they do not publish data values. Values come from the app and the API, always with their source's credit. --- # Getting started > Sign in, use the data in the app, make an API key, and connect an AI agent. ## Create an account [Sign up](https://getcadastre.com/signup) with your name and email address. Cadastre emails you a link; the page it opens is where you choose a password and accept the Terms of Service and Privacy Policy. After that, [sign in](https://getcadastre.com/login) with your email and password, or with a passkey once you have added one in Settings. ## Use the data in the app 1. Create a project for the client or question you are working on. 2. On **MSA Selection**, narrow the geographic scope, set requirements (for example a minimum population or a maximum unemployment rate) and add criteria in plain language. Each criterion is matched to the measures described in [Datasets](https://getcadastre.com/docs/datasets), and you approve it before it counts. 3. The register ranks the metros that pass, and the map shades them by score. Save a snapshot to keep a ranking exactly as it was computed. 4. On **Reports**, download the snapshot as a PDF or a PowerPoint deck, or its data as CSV or Excel. Each lists its data sources with the credit they require. ## Programmatic access The read-only [API](https://getcadastre.com/docs/api), the [MCP server](https://getcadastre.com/docs/mcp) and the [CLI](https://getcadastre.com/docs/cli) are live in beta, free while they are, and need no account for the public datasets: call them with no credential, at 30 requests a minute and 2,000 a day per network address. (The app itself needs an account.) ```sh curl "https://getcadastre.com/api/v1/metros?q=austin" ``` For higher limits, sign in, with an account that has API access turned on. A new account does not have it yet: write to support@getcadastre.com to ask for it (API access may become part of a paid plan later). Until it is on, Settings makes no API keys for the account and apps cannot be connected to it. There are two ways to sign in: ### API keys For your own scripts and servers. In [Settings](https://getcadastre.com/account), under **API keys**, make a key (you are asked for your password). It starts `cad_key_`, is shown once, and acts as you in the account you were working in. Send it as a bearer token: ```sh curl -H "Authorization: Bearer $CADASTRE_API_KEY" https://getcadastre.com/api/v1/me ``` Keep a key secret, as you would a password; revoke it in the same place. Keys are for scripts you run, not for software or pages other people can inspect. ### OAuth For AI agents and other apps that sign in on your behalf. The app opens your browser, you sign in to Cadastre, choose the account and approve; the app keeps its own tokens and refreshes them, so there is no key to copy. Discovery starts at [https://getcadastre.com/.well-known/oauth-authorization-server](https://getcadastre.com/.well-known/oauth-authorization-server). Disconnect an app in Settings under **Authorized apps**. To set up a particular agent (Claude Code, Codex, Cursor, GitHub Copilot in VS Code, Claude, ChatGPT, Gemini CLI, or OpenCode), see [Connect an AI agent](https://getcadastre.com/agents) and the [MCP server](https://getcadastre.com/docs/mcp) page. Each key and each approved app has its own rate limits, and every answer carries the credit its sources require: see [API](https://getcadastre.com/docs/api). ### The command line The [Cadastre CLI](https://getcadastre.com/docs/cli), `cadastre`, runs screens, rankings and comparisons in the terminal, with the attribution printed under every answer. It works without signing in; `cadastre login` signs in with OAuth in the browser (or takes an API key) for higher limits: ```sh curl -fsSL https://raw.githubusercontent.com/waratuman/cadastre-cli/main/install.sh | sh cadastre metros --state TX cadastre login # optional: higher limits ``` ## For AI agents and tools These docs are written to be read by agents as well as people: - Every page is Markdown at its own address plus `.md`, for example [https://getcadastre.com/docs/datasets.md](https://getcadastre.com/docs/datasets.md). - [/llms.txt](https://getcadastre.com/llms.txt) lists every page with a one-line description, per the [llms.txt convention](https://llmstxt.org/). - [/llms-full.txt](https://getcadastre.com/llms-full.txt) is the whole of the docs as one Markdown file. ```sh curl https://getcadastre.com/llms.txt curl https://getcadastre.com/docs/datasets/acs.md ``` Pages describe the data and its rights; they carry no data values. --- # Datasets > Every dataset Cadastre imports: publisher, licence, availability and what it measures. Every dataset Cadastre imports has a page here, generated from the code that imports it and from the sources register that records its rights, so the page and the import cannot disagree. A page gives the publisher, the licence and the exact credit the source requires, whether it is available, the period and geographies, each measure with its unit and how a metro value is made, and the known gaps. Pages describe data and carry no data values. **Availability.** **Available** datasets feed the metro screens and reports today and are planned for the API. **Restricted** datasets are described so you know they were reviewed, but their terms do not allow Cadastre's use, so their values reach no screen, report or export, and the API will not serve them. **Parcel level** datasets are imported for parcel screening, which is not available yet. ## Geography | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [TIGER boundaries](https://getcadastre.com/docs/datasets/tiger) | U.S. Census Bureau | Public domain (U.S. federal government work) | Available (boundaries) | None (geometry) | ## Transport | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [DOT Rail Network](https://getcadastre.com/docs/datasets/rail) | U.S. DOT Bureau of Transportation Statistics | Public domain (U.S. federal government work) | Not available yet (parcel level) | None (geometry) | ## Demographics | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [ACS 5-Year](https://getcadastre.com/docs/datasets/acs) | U.S. Census Bureau | Public domain (U.S. federal government work) | Available | 11 | | [County Health Rankings](https://getcadastre.com/docs/datasets/chr) | County Health Rankings & Roadmaps (CHR&R) | Restricted: non-commercial use only without CHR&R written consent | Restricted: not available | 16 | | [Census Building Permits](https://getcadastre.com/docs/datasets/permits) | U.S. Census Bureau | Public domain (U.S. federal government work) | Available | 1 | ## Health | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [CDC PLACES](https://getcadastre.com/docs/datasets/cdc-places) | Centers for Disease Control and Prevention (CDC), Division of Population Health | Public domain (U.S. government work), on CDC's terms: credit "Source: CDC", state that the data is available at no charge at data.cdc.gov, no endorsement implied, no CDC or HHS logos | Available | 14 | | [CDC Mapping Injury, Overdose, and Violence](https://getcadastre.com/docs/datasets/cdc-overdose) | Centers for Disease Control and Prevention (CDC), National Center for Injury Prevention and Control, from NCHS National Vital Statistics System death records | Public domain (U.S. government work), on CDC's terms: credit "Source: CDC", state that the data is available at no charge at data.cdc.gov, no endorsement implied, no CDC or HHS logos | Available | 1 | ## Labor | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [BLS LAUS](https://getcadastre.com/docs/datasets/bls-unemployment) | U.S. Bureau of Labor Statistics | Public domain (U.S. federal government work) | Available | 2 | | [BLS QCEW](https://getcadastre.com/docs/datasets/bls-qcew) | U.S. Bureau of Labor Statistics | Public domain (U.S. federal government work) | Available | 59 | | [BEA GDP](https://getcadastre.com/docs/datasets/bea-gdp) | U.S. Bureau of Economic Analysis | Public domain (U.S. federal government work) | Available | 3 | | [BLS LAUS history](https://getcadastre.com/docs/datasets/bls-laus-history) | U.S. Bureau of Labor Statistics | Public domain (U.S. federal government work) | Available | 7 | | [BLS QCEW history](https://getcadastre.com/docs/datasets/bls-qcew-history) | U.S. Bureau of Labor Statistics | Public domain (U.S. federal government work) | Available | 7 | | [BEA real GDP](https://getcadastre.com/docs/datasets/bea-real-gdp) | U.S. Bureau of Economic Analysis | Public domain (U.S. federal government work) | Available | 2 | ## Utilities | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [EIA Retail Sales](https://getcadastre.com/docs/datasets/eia) | U.S. Energy Information Administration | Public domain (U.S. federal government work) | Available | 1 | | [HIFLD transmission lines via Esri Living Atlas archive](https://getcadastre.com/docs/datasets/hifld-transmission-lines) | U.S. DHS Homeland Infrastructure Foundation-Level Data (HIFLD), republished by Esri | Unresolved: U.S. federal government work (DHS HIFLD) republished under the Esri Master License Agreement | Restricted: not available | 5 | | [OpenStreetMap power lines (© OpenStreetMap contributors, ODbL)](https://getcadastre.com/docs/datasets/osm-power-lines) | OpenStreetMap contributors, extracts by Geofabrik GmbH | Open Database License (ODbL) 1.0, attribution required | Available | 5 | ## Hazard | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [FEMA NFHL](https://getcadastre.com/docs/datasets/nfhl) | FEMA | Public domain (U.S. federal government work) | Not available yet (parcel level) | None (geometry) | | [FEMA NRI](https://getcadastre.com/docs/datasets/nri) | FEMA | Public domain (U.S. federal government work) | Available | 22 | | [EPA Green Book](https://getcadastre.com/docs/datasets/epa-green-book) | U.S. Environmental Protection Agency | Public domain (U.S. federal government work) | Available | 24 | | [EPA Green Book area boundaries](https://getcadastre.com/docs/datasets/epa-green-book-areas) | U.S. Environmental Protection Agency | Public domain (U.S. federal government work) | Available | 8 | | [EPA Class I areas](https://getcadastre.com/docs/datasets/epa-class-one-areas) | U.S. Environmental Protection Agency, OAQPS (from NPS, USDA Forest Service, FWS and BIA boundaries) | Public domain (U.S. federal government work) | Available | 3 | | [Ozone Transport Region (CAA 184, 40 CFR 81.457)](https://getcadastre.com/docs/datasets/ozone-transport-region) | U.S. Congress (Clean Air Act section 184) and EPA (40 CFR 81.457) | Public domain (U.S. statute and regulation) | Available | 1 | | [EPA regulated facilities](https://getcadastre.com/docs/datasets/epa-facilities) | U.S. Environmental Protection Agency (Superfund NPL, Facility Registry Service, Cleanups in my Community, TRI) | Public domain (U.S. federal government work) | Available | 8 | ## Incentives | Dataset | Publisher | Licence | Availability | Measures | | --- | --- | --- | --- | --- | | [CDFI Fund Opportunity Zones](https://getcadastre.com/docs/datasets/cdfi-opportunity-zones) | U.S. Department of the Treasury, CDFI Fund (designations by Treasury under IRC 1400Z-1) | Public domain (U.S. federal government work) | Available | 5 | ## Parcel data Parcel and property data is not available yet. The launch is metro-level: parcel sources are being researched county by county, and each is used only once its rights are cleared. --- # TIGER boundaries The Census Bureau's TIGER/Line boundaries: states, counties, metropolitan and micropolitan statistical areas, combined statistical areas, metropolitan divisions, census tracts, places and other layers. Every metro Cadastre screens, and every map outline, comes from the current vintage. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Census Bureau | | Product | TIGER/Line boundaries | | Source | [https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html](https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html) | | Category | Geography | | Period | 2026 vintage (current) | | Refresh cadence | Annual (release expected in September) | | Geographies | 50 states, the District of Columbia and Puerto Rico. Counties link to their metro or micro area, and metros to their combined statistical area. | | Availability | Available (boundaries) | | Cadastre key | `tiger` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.census.gov/data/developers/about/terms-of-service.html](https://www.census.gov/data/developers/about/terms-of-service.html) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Census Bureau, TIGER/Line boundaries**. ## Known gaps and caveats - TIGER is the Census mapping product, not a legal boundary survey. - Each vintage is its own region tree. Everything users see reads the current vintage; earlier vintages are kept beside it as historical and never replace it. - The other U.S. Island Areas (American Samoa, Guam, the Northern Mariana Islands and the U.S. Virgin Islands) are not imported. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # ACS 5-Year American Community Survey 5-year estimates from the Census API: population, five-year population growth, median household income, median home value, educational attainment, household poverty and severe rent burden. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Census Bureau | | Product | American Community Survey 5-year estimates | | Source | [https://www.census.gov/programs-surveys/acs](https://www.census.gov/programs-surveys/acs) | | Category | Demographics | | Period | 2024 5-year estimates (growth from 2019 to 2024) | | Refresh cadence | Annual (release expected in December) | | Geographies | State, county, place, metro and micro area, and combined statistical area, each queried at its own grain. Metro values are the Census Bureau's own metro estimates, except five-year population growth, which is pooled from the member counties because metro definitions change between surveys. | | Availability | Available | | Cadastre key | `acs` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.census.gov/data/developers/about/terms-of-service.html](https://www.census.gov/data/developers/about/terms-of-service.html) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Census Bureau, American Community Survey 5-year estimates**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `population_growth_5yr` | Five-year population growth | percent over 5 years | growth of member counties combined | | `population` | Population | people | sum over member counties | | `median_household_income` | Median household income | dollars | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `median_home_value` | Median home value | dollars | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `education_high_school_rate` | Adults whose highest education is high school | percent of adults 25+ | population-weighted county mean | | `education_some_college_rate` | Adults whose highest education is some college | percent of adults 25+ | population-weighted county mean | | `education_associate_rate` | Adults whose highest education is an associate degree | percent of adults 25+ | population-weighted county mean | | `education_bachelor_rate` | Adults whose highest education is a bachelor's degree | percent of adults 25+ | population-weighted county mean | | `education_graduate_rate` | Adults whose highest education is a graduate degree | percent of adults 25+ | population-weighted county mean | | `household_poverty_rate` | Household poverty rate | percent of households | population-weighted county mean | | `severe_rent_burden_rate` | Severe rent burden rate | percent of renter households | population-weighted county mean | ## Known gaps and caveats - Medians are never averaged across counties: a population-weighted mean of medians is not a median of anything, so a median is shown only where the Census Bureau publishes it. - Educational attainment shares are by highest level reached, so they do not overlap. - Connecticut replaced its eight counties with nine planning regions, which Census geography now uses; for growth, the prior population of each planning region is rebuilt from its towns. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # County Health Rankings County health measures from the County Health Rankings & Roadmaps analytic data file: premature death, self-reported health, obesity, physical inactivity, provider supply, preventable hospital stays, air pollution, life expectancy and others. > [!WARNING] > **Restricted: not available in Cadastre, and will not be served by the API.** Its terms allow personal or non-profit use only; commercial use needs CHR&R's written consent, which Cadastre does not have. It is described here so you know it was reviewed, but its values reach no screen, report or export, and the API will not serve them. ## Source | Fact | Value | | --- | --- | | Publisher | County Health Rankings & Roadmaps (CHR&R) | | Source | [https://www.countyhealthrankings.org/health-data](https://www.countyhealthrankings.org/health-data) | | Category | Demographics | | Period | 2025 release | | Refresh cadence | Annual (release expected in March) | | Geographies | County. A metro value would be a population-weighted mean of its counties, an estimate rather than a figure CHR&R publishes. | | Availability | Restricted: not available | | Cadastre key | `chr` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Restricted: non-commercial use only without CHR&R written consent | | Terms | [https://www.countyhealthrankings.org/terms-use](https://www.countyhealthrankings.org/terms-use) | | Register status | Restricted in code: no use of its values | Cadastre shows none of its figures, so no credit is printed for it. ## Measures These measures are described for reference only: no value of any of them is served. The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `premature_death_rate` | Premature death rate | years of potential life lost per 100,000 | population-weighted county mean | | `poor_or_fair_health_pct` | Adults in poor or fair health | proportion of adults (0-1) | population-weighted county mean | | `poor_physical_health_days` | Poor physical health days | unhealthy days per month | population-weighted county mean | | `poor_mental_health_days` | Poor mental health days | unhealthy days per month | population-weighted county mean | | `adult_obesity_pct` | Adult obesity rate | proportion of adults (0-1) | population-weighted county mean | | `food_environment_index` | Food environment index | index 0-10 | population-weighted county mean | | `physical_inactivity_pct` | Physical inactivity rate | proportion of adults (0-1) | population-weighted county mean | | `exercise_access_pct` | Access to exercise opportunities | proportion of population (0-1) | population-weighted county mean | | `excessive_drinking_pct` | Excessive drinking rate | proportion of adults (0-1) | population-weighted county mean | | `primary_care_physician_ratio` | Primary care physician supply | primary care physicians per resident | population-weighted county mean | | `mental_health_provider_ratio` | Mental health provider supply | mental health providers per resident | population-weighted county mean | | `preventable_hospital_stays` | Preventable hospital stays | discharges per 100,000 Medicare enrollees | population-weighted county mean | | `air_pollution_pm25` | Fine particulate air pollution (PM2.5) | micrograms per cubic metre | population-weighted county mean | | `life_expectancy` | Life expectancy | years | population-weighted county mean | | `drug_overdose_death_rate` | Drug overdose death rate | deaths per 100,000 | population-weighted county mean | | `school_funding_adequacy` | School funding adequacy | dollars per pupil vs adequate (negative is a shortfall) | population-weighted county mean | ## Known gaps and caveats - [CDC PLACES](https://getcadastre.com/docs/datasets/cdc-places) is the public-domain source for adult health measures that Cadastre uses instead. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # Census Building Permits The Census Building Permits Survey: housing units authorized by building permit in the calendar year, from the metro-area December year-to-date file. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Census Bureau | | Product | Building Permits Survey (annual housing units authorized) | | Source | [https://www.census.gov/construction/bps/](https://www.census.gov/construction/bps/) | | Category | Demographics | | Period | 2025 calendar year | | Refresh cadence | Annual (release expected in February) | | Geographies | Metro and micro area, as published (already at metro grain). | | Availability | Available | | Cadastre key | `permits` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.census.gov/data/developers/about/terms-of-service.html](https://www.census.gov/data/developers/about/terms-of-service.html) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Census Bureau, Building Permits Survey (annual housing units authorized)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `housing_permits` | Housing permits | housing units per year | sum over member counties | ## Known gaps and caveats - Residential permits only: it is not a count of all construction or all development activity. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # CDC PLACES CDC's model-based county estimates of adult health from the Behavioral Risk Factor Surveillance System (BRFSS): obesity, current smoking, no leisure-time physical activity, diabetes, high blood pressure, binge drinking, frequent mental and physical distress, fair or poor health, any disability, uninsured adults 18-64, food insecurity and lack of reliable transportation, each the age-adjusted prevalence. ## Source | Fact | Value | | --- | --- | | Publisher | Centers for Disease Control and Prevention (CDC), Division of Population Health | | Product | PLACES: Local Data for Better Health, County Data (2025 release) | | Source | [https://www.cdc.gov/places/](https://www.cdc.gov/places/) | | Category | Health | | Period | 2025 release, 2023 BRFSS estimates | | Refresh cadence | Annual | | Geographies | County. A metro value is Cadastre's average of CDC's county estimates, weighted by the adults PLACES counts in each county, over the counties with an estimate. | | Availability | Available | | Cadastre key | `cdc-places` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. government work), on CDC's terms: credit "Source: CDC", state that the data is available at no charge at data.cdc.gov, no endorsement implied, no CDC or HHS logos | | Terms | [https://www.cdc.gov/other/agencymaterials.html](https://www.cdc.gov/other/agencymaterials.html) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `derived_analytics`, `public_display`, `redistribution`, `bulk_export`, `api` | Wherever its figures are shown, this source requires the credit **Source: CDC** ([https://data.cdc.gov/d/swc5-untb](https://data.cdc.gov/d/swc5-untb)), printed with this note: > Source: CDC, PLACES: Local Data for Better Health (2025 release, county estimates from 2023 BRFSS). Available at no charge at https://data.cdc.gov/d/swc5-untb. Metro percentages are Cadastre's adult-population-weighted averages of CDC's county estimates, not CDC figures. > > Use of CDC data does not imply endorsement by CDC, ATSDR, HHS or the U.S. Government of Cadastre or its services. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `places_obesity` | Adult obesity, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_current_smoking` | Adult current cigarette smoking, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_no_leisure_physical_activity` | Adults with no leisure-time physical activity, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_diabetes` | Adult diagnosed diabetes, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_high_blood_pressure` | Adult high blood pressure, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_binge_drinking` | Adult binge drinking, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_frequent_mental_distress` | Adults with frequent mental distress, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_frequent_physical_distress` | Adults with frequent physical distress, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_fair_or_poor_health` | Adults in fair or poor general health, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_any_disability` | Adults with any disability, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_uninsured_18_64` | Adults 18-64 without health insurance, age-adjusted (CDC PLACES) | percent of adults aged 18-64, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate); metro value is Cadastre's adult-population-weighted average of CDC county estimates, weighted by adults 18+ (CDC publishes no 18-64 count) | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_food_insecurity` | Adult food insecurity in the past year, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate; asked only in the states that ran BRFSS's social-needs module); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_lack_reliable_transportation` | Adults lacking reliable transportation in the past year, age-adjusted (CDC PLACES) | percent of adults, age-adjusted (CDC PLACES 2025 release, 2023 BRFSS model-based county estimate; asked only in the states that ran BRFSS's social-needs module); metro value is Cadastre's adult-population-weighted average of CDC county estimates | mean of member counties weighted by Adult population, 18 and over (CDC PLACES), over the counties with a value (unavailable where those hold under 80% of it) | | `places_adult_population` | Adult population, 18 and over (CDC PLACES) | people aged 18+ (Census 2023 county estimates as published in CDC PLACES) | sum over member counties | ## Known gaps and caveats - Model-based small-area estimates, not county surveys; CDC cautions against using them to evaluate local programmes. - Kentucky and Pennsylvania have no 2023 estimates in this release, so a metro mostly in those states has no value (it needs counties holding 80% of its adults). - Food insecurity and lack of reliable transportation come from BRFSS's social-needs module, which only 39 states and DC asked. - Age-adjusted rates are for comparing places; they are not the share of a county's actual adults. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # CDC Mapping Injury, Overdose, and Violence CDC's county drug overdose death rates per 100,000 residents from the Mapping Injury, Overdose, and Violence county file, built from NCHS National Vital Statistics System death records by county of residence. ## Source | Fact | Value | | --- | --- | | Publisher | Centers for Disease Control and Prevention (CDC), National Center for Injury Prevention and Control, from NCHS National Vital Statistics System death records | | Product | Mapping Injury, Overdose, and Violence: county drug overdose death rates | | Source | [https://www.cdc.gov/injury-violence-data/data-vis/index.html](https://www.cdc.gov/injury-violence-data/data-vis/index.html) | | Category | Health | | Period | Calendar years as published; metros read the latest | | Refresh cadence | Monthly | | Geographies | County, for every calendar year the file publishes; metros read the latest. A metro rate is Cadastre's population-weighted average of CDC's county rates (the pooled deaths per 100,000). | | Availability | Available | | Cadastre key | `cdc-overdose` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. government work), on CDC's terms: credit "Source: CDC", state that the data is available at no charge at data.cdc.gov, no endorsement implied, no CDC or HHS logos | | Terms | [https://www.cdc.gov/other/agencymaterials.html](https://www.cdc.gov/other/agencymaterials.html) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `derived_analytics`, `public_display`, `redistribution`, `bulk_export`, `api` | Wherever its figures are shown, this source requires the credit **Source: CDC** ([https://data.cdc.gov/d/psx4-wq38](https://data.cdc.gov/d/psx4-wq38)), printed with this note: > Source: CDC, Mapping Injury, Overdose, and Violence (county drug overdose death rates from NCHS National Vital Statistics System death records). Available at no charge at https://data.cdc.gov/d/psx4-wq38. Metro rates are Cadastre's population-weighted averages of CDC's county rates, not CDC figures. > > Use of CDC data does not imply endorsement by CDC, ATSDR, HHS or the U.S. Government of Cadastre or its services. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `cdc_drug_overdose_death_rate` | Drug overdose death rate, per 100,000 (CDC) | deaths per 100,000 residents in the calendar year (CDC county rates from NCHS death records, by county of residence; counties with 1-9 deaths are suppressed by CDC and left out); metro value is Cadastre's population-weighted average of CDC county rates | mean of member counties weighted by Population, over the counties with a value (unavailable where those hold under 80% of it) | ## Known gaps and caveats - CDC suppresses counts of 1 to 9 deaths and publishes a modelled rate in their place. Those counties have no value in Cadastre (never the modelled rate, never 0); a published count of 0 is a real 0. - All drugs, not opioids alone. - Connecticut replaced its eight counties with nine planning regions, which Census geography now uses; this file still uses the legacy counties, so Connecticut metros have no value. - The trailing-twelve-months period is not imported. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # BLS LAUS Local Area Unemployment Statistics (LAUS): the unemployment rate for every metro and micro area, as the latest full-year annual average, with the latest published month kept as a separate measure. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Bureau of Labor Statistics | | Product | Local Area Unemployment Statistics (county and metro unemployment) | | Source | [https://www.bls.gov/lau/](https://www.bls.gov/lau/) | | Category | Labor | | Period | Latest full-year annual average; the latest month separately | | Refresh cadence | Monthly | | Geographies | Metro and micro area, from BLS's own area series; counties are not imported, so a metro is never assembled from them. | | Availability | Available | | Cadastre key | `bls-unemployment` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.bls.gov/bls/linksite.htm](https://www.bls.gov/bls/linksite.htm) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Bureau of Labor Statistics, Local Area Unemployment Statistics (county and metro unemployment)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `unemployment_rate` | Unemployment rate | percent of labor force, annual average | population-weighted county mean | | `unemployment_rate_latest_month` | Unemployment rate, latest month | percent of labor force in the latest month BLS has published (not seasonally adjusted; the month is in the import summary) | population-weighted county mean | ## Known gaps and caveats - BLS does not seasonally adjust metro series, so a single month moves with the seasons. The headline measure is the annual average for that reason. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # BLS QCEW The Quarterly Census of Employment and Wages: annual-average private-sector employment, establishments and location quotients by county and NAICS industry, for a curated list of manufacturing, logistics and related industries, so a question like "does this market have an aerospace base?" can be screened. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Bureau of Labor Statistics | | Product | Quarterly Census of Employment and Wages (annual averages by county and industry) | | Source | [https://www.bls.gov/cew/](https://www.bls.gov/cew/) | | Category | Labor | | Period | 2025 annual averages, private ownership | | Refresh cadence | Quarterly | | Geographies | County. A metro is assembled from its counties: counts are summed over the counties that disclose them, and the location quotient is rebuilt from the counties' jobs rather than averaged. | | Availability | Available | | Cadastre key | `bls-qcew` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.bls.gov/opub/copyright-information.htm](https://www.bls.gov/opub/copyright-information.htm) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Bureau of Labor Statistics, Quarterly Census of Employment and Wages (annual averages by county and industry)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | Basis | | --- | --- | --- | --- | --- | | `qcew_total_employment` | Private-sector employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Private-sector establishments | | `qcew_total_establishments` | Private-sector establishments | establishments | sum over member counties | — | | `qcew_31_33_employment` | Manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Manufacturing establishments | | `qcew_31_33_establishments` | Manufacturing establishments | establishments | sum over member counties | — | | `qcew_31_33_location_quotient` | Manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Manufacturing establishments | | `qcew_311_employment` | Food manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Food manufacturing establishments | | `qcew_311_establishments` | Food manufacturing establishments | establishments | sum over member counties | — | | `qcew_311_location_quotient` | Food manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Food manufacturing establishments | | `qcew_325_employment` | Chemical manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Chemical manufacturing establishments | | `qcew_325_establishments` | Chemical manufacturing establishments | establishments | sum over member counties | — | | `qcew_325_location_quotient` | Chemical manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Chemical manufacturing establishments | | `qcew_3254_employment` | Pharmaceutical and medicine manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Pharmaceutical and medicine manufacturing establishments | | `qcew_3254_establishments` | Pharmaceutical and medicine manufacturing establishments | establishments | sum over member counties | — | | `qcew_3254_location_quotient` | Pharmaceutical and medicine manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Pharmaceutical and medicine manufacturing establishments | | `qcew_332_employment` | Fabricated metal product manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Fabricated metal product manufacturing establishments | | `qcew_332_establishments` | Fabricated metal product manufacturing establishments | establishments | sum over member counties | — | | `qcew_332_location_quotient` | Fabricated metal product manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Fabricated metal product manufacturing establishments | | `qcew_332710_employment` | Machine shop employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Machine shop establishments | | `qcew_332710_establishments` | Machine shop establishments | establishments | sum over member counties | — | | `qcew_332710_location_quotient` | Machine shop location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Machine shop establishments | | `qcew_333_employment` | Machinery manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Machinery manufacturing establishments | | `qcew_333_establishments` | Machinery manufacturing establishments | establishments | sum over member counties | — | | `qcew_333_location_quotient` | Machinery manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Machinery manufacturing establishments | | `qcew_334_employment` | Computer and electronic product manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Computer and electronic product manufacturing establishments | | `qcew_334_establishments` | Computer and electronic product manufacturing establishments | establishments | sum over member counties | — | | `qcew_334_location_quotient` | Computer and electronic product manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Computer and electronic product manufacturing establishments | | `qcew_335_employment` | Electrical equipment and appliance manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Electrical equipment and appliance manufacturing establishments | | `qcew_335_establishments` | Electrical equipment and appliance manufacturing establishments | establishments | sum over member counties | — | | `qcew_335_location_quotient` | Electrical equipment and appliance manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Electrical equipment and appliance manufacturing establishments | | `qcew_336_employment` | Transportation equipment manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Transportation equipment manufacturing establishments | | `qcew_336_establishments` | Transportation equipment manufacturing establishments | establishments | sum over member counties | — | | `qcew_336_location_quotient` | Transportation equipment manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Transportation equipment manufacturing establishments | | `qcew_3361_employment` | Motor vehicle manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Motor vehicle manufacturing establishments | | `qcew_3361_establishments` | Motor vehicle manufacturing establishments | establishments | sum over member counties | — | | `qcew_3361_location_quotient` | Motor vehicle manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Motor vehicle manufacturing establishments | | `qcew_3362_employment` | Motor vehicle body and trailer manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Motor vehicle body and trailer manufacturing establishments | | `qcew_3362_establishments` | Motor vehicle body and trailer manufacturing establishments | establishments | sum over member counties | — | | `qcew_3362_location_quotient` | Motor vehicle body and trailer manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Motor vehicle body and trailer manufacturing establishments | | `qcew_3363_employment` | Motor vehicle parts manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Motor vehicle parts manufacturing establishments | | `qcew_3363_establishments` | Motor vehicle parts manufacturing establishments | establishments | sum over member counties | — | | `qcew_3363_location_quotient` | Motor vehicle parts manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Motor vehicle parts manufacturing establishments | | `qcew_3364_employment` | Aerospace manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Aerospace manufacturing establishments | | `qcew_3364_establishments` | Aerospace manufacturing establishments | establishments | sum over member counties | — | | `qcew_3364_location_quotient` | Aerospace manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Aerospace manufacturing establishments | | `qcew_336411_employment` | Aircraft manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Aircraft manufacturing establishments | | `qcew_336411_establishments` | Aircraft manufacturing establishments | establishments | sum over member counties | — | | `qcew_336411_location_quotient` | Aircraft manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Aircraft manufacturing establishments | | `qcew_336412_employment` | Aircraft engine and engine parts manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Aircraft engine and engine parts manufacturing establishments | | `qcew_336412_establishments` | Aircraft engine and engine parts manufacturing establishments | establishments | sum over member counties | — | | `qcew_336412_location_quotient` | Aircraft engine and engine parts manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Aircraft engine and engine parts manufacturing establishments | | `qcew_336413_employment` | Aircraft parts and auxiliary equipment manufacturing employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Aircraft parts and auxiliary equipment manufacturing establishments | | `qcew_336413_establishments` | Aircraft parts and auxiliary equipment manufacturing establishments | establishments | sum over member counties | — | | `qcew_336413_location_quotient` | Aircraft parts and auxiliary equipment manufacturing location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Aircraft parts and auxiliary equipment manufacturing establishments | | `qcew_493_employment` | Warehousing and storage employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Warehousing and storage establishments | | `qcew_493_establishments` | Warehousing and storage establishments | establishments | sum over member counties | — | | `qcew_493_location_quotient` | Warehousing and storage location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Warehousing and storage establishments | | `qcew_484_employment` | Truck transportation employment | jobs | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | coverage: Truck transportation establishments | | `qcew_484_establishments` | Truck transportation establishments | establishments | sum over member counties | — | | `qcew_484_location_quotient` | Truck transportation location quotient | ratio to the U.S. share of jobs (1 = U.S. average) | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | weight: Private-sector employment; coverage: Truck transportation establishments | ## Known gaps and caveats - BLS withholds a county's employment where a few employers would be identifiable; establishment counts are never withheld. Withheld employment is unknown, never zero. - A metro has no value where the disclosing counties hold less than 80% of its establishments in the industry, so most small metros have no value for the narrow industries. That is BLS disclosure, not a gap in the import. - It counts an industry's own establishments, not a customer's suppliers. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # BEA GDP BEA regional GDP: total GDP, manufacturing GDP and the manufacturing share of GDP. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Bureau of Economic Analysis | | Product | GDP by county and metropolitan area | | Source | [https://www.bea.gov/data/gdp/gdp-county-metro-and-other-areas](https://www.bea.gov/data/gdp/gdp-county-metro-and-other-areas) | | Category | Labor | | Period | 2024, current dollars | | Refresh cadence | Annual (release expected in December) | | Geographies | BEA's API publishes county and state GDP; Cadastre sums the member counties to each metro and micro area and computes the share from those sums. | | Availability | Available | | Cadastre key | `bea-gdp` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.bea.gov/help/faq/506](https://www.bea.gov/help/faq/506) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Bureau of Economic Analysis, GDP by county and metropolitan area**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `gdp_total` | Total GDP | thousands of dollars | sum over member counties | | `gdp_manufacturing` | Manufacturing GDP | thousands of dollars | sum over member counties | | `manufacturing_gdp_share` | Manufacturing share of GDP | percent of GDP | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - BEA publishes most Virginia independent cities only combined with a neighbouring county, and Kalawao with Maui; those combinations are mapped to their counties. A metro is left without a value where a combined area reaches beyond it. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # BLS LAUS history Trend measures from the LAUS annual history: labor-force and resident-employment growth, the unemployment rise in the Great Recession and in 2020, and the ten-year average and volatility of the unemployment rate. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Bureau of Labor Statistics | | Product | Local Area Unemployment Statistics, metro annual history | | Source | [https://www.bls.gov/lau/](https://www.bls.gov/lau/) | | Category | Labor | | Period | Annual averages 1990-2025, not seasonally adjusted | | Refresh cadence | Annual (release expected in April) | | Geographies | Metro and micro area, from BLS's own area series (nothing rolls up). BLS rebuilt the metro history on the 2023 delineations, Connecticut's planning-region metros included, so an area is comparable across the window. | | Availability | Available | | Cadastre key | `bls-laus-history` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.bls.gov/bls/linksite.htm](https://www.bls.gov/bls/linksite.htm) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Bureau of Labor Statistics, Local Area Unemployment Statistics, metro annual history**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `labor_force_growth_10yr` | Labor force growth, 2015-2025 (%) | percent change in the labor force, 2015 to 2025 (annual averages, not seasonally adjusted) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `labor_force_growth_since_2019` | Labor force growth, 2019-2025 (%) | percent change in the labor force, 2019 to 2025 (annual averages, not seasonally adjusted) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `employment_growth_10yr` | Resident employment growth, 2015-2025 (%) | percent change in employed residents, 2015 to 2025 (annual averages, not seasonally adjusted; counts where workers live, not where they work) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `unemployment_rise_great_recession` | Unemployment rise in the Great Recession, 2007 to 2008-2010 peak (points) | percentage points: the highest of the 2008, 2009 and 2010 unemployment rates minus 2007's (annual averages, not seasonally adjusted) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `unemployment_rise_2020` | Unemployment rise in 2020, from 2019 (points) | percentage points: the 2020 unemployment rate minus 2019's (annual averages, not seasonally adjusted) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `unemployment_rate_avg_10yr` | Average unemployment rate, 2016-2025 (%) | percent of labor force, mean of the 10 annual averages 2016-2025 (not seasonally adjusted) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `unemployment_rate_volatility_10yr` | Unemployment rate volatility, 2016-2025 (points) | percentage points: standard deviation of the 10 annual unemployment rates 2016-2025, 2020 included | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - One number per area and measure is stored; each label names its window, so a value is never read as more recent than it is. - Counties are not imported. - Volatility includes 2020, so it dominates the figure. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # BLS QCEW history Trend measures from QCEW annual averages: private-sector and manufacturing employment growth, nominal average-pay growth, the latest average annual pay and the change in the manufacturing location quotient. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Bureau of Labor Statistics | | Product | Quarterly Census of Employment and Wages, annual history | | Source | [https://www.bls.gov/cew/](https://www.bls.gov/cew/) | | Category | Labor | | Period | Private ownership annual averages, 2015, 2019, 2025 | | Refresh cadence | Annual (release expected in September) | | Geographies | County and metro. A county counts toward its metro only where it discloses at both ends of the window. | | Availability | Available | | Cadastre key | `bls-qcew-history` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.bls.gov/opub/copyright-information.htm](https://www.bls.gov/opub/copyright-information.htm) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Bureau of Labor Statistics, Quarterly Census of Employment and Wages, annual history**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `qcew_private_employment_growth_10yr` | Private-sector employment growth, 2015-2025 (%) | percent change in private-sector jobs, 2015 to 2025 (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `qcew_private_employment_growth_since_2019` | Private-sector employment growth, 2019-2025 (%) | percent change in private-sector jobs, 2019 to 2025 (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `qcew_manufacturing_employment_growth_10yr` | Manufacturing employment growth, 2015-2025 (%) | percent change in manufacturing jobs (NAICS 31-33), 2015 to 2025 (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `qcew_manufacturing_employment_growth_since_2019` | Manufacturing employment growth, 2019-2025 (%) | percent change in manufacturing jobs (NAICS 31-33), 2019 to 2025 (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `qcew_avg_private_wage_growth_10yr` | Average private-sector pay growth, 2015-2025 (nominal %) | percent change in average annual pay per private-sector job (total wages / jobs), 2015 to 2025, nominal dollars, not adjusted for inflation (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `qcew_avg_private_annual_pay` | Average private-sector annual pay, 2025 | dollars per private-sector job (total annual wages / annual-average jobs), nominal (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `qcew_manufacturing_lq_change_10yr` | Manufacturing location quotient change, 2015-2025 (points) | change in the manufacturing location quotient (share of private jobs in NAICS 31-33 against the U.S. share that year; 1 = U.S. average), 2025 minus 2015 (private ownership; a metro sums its counties disclosing at both years, none below 80% of its establishments at either; Connecticut has no comparable county data before 2024, so no value there) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - A metro has no value where the disclosing counties hold under 80% of its establishments at either end of the window. - Connecticut replaced its eight counties with nine planning regions, which Census geography now uses; QCEW publishes the planning regions only from 2024, so Connecticut's counties and every metro with one have no growth, pay-growth or quotient-change value (they do have the latest average pay). - Pay is nominal, not adjusted for inflation. - 2020 is never a base year. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # BEA real GDP Ten-year real GDP growth and its compound annual rate, from BEA's real GDP by county in chained 2017 dollars (table CAGDP9). ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Bureau of Economic Analysis | | Product | Real GDP by county (chained 2017 dollars), history | | Source | [https://www.bea.gov/data/gdp/gdp-county-metro-and-other-areas](https://www.bea.gov/data/gdp/gdp-county-metro-and-other-areas) | | Category | Labor | | Period | 2014-2024, chained 2017 dollars | | Refresh cadence | Annual (release expected in December) | | Geographies | Metro and micro area: member counties summed to each area. | | Availability | Available | | Cadastre key | `bea-real-gdp` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.bea.gov/help/faq/506](https://www.bea.gov/help/faq/506) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Bureau of Economic Analysis, Real GDP by county (chained 2017 dollars), history**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `real_gdp_growth_10yr` | Real GDP growth, 2014-2024 (%) | percent change in real GDP, 2014 to 2024 (member counties' real GDP in chained 2017 dollars summed (BEA CAGDP9); no value unless every member county is published at both years) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `real_gdp_cagr_10yr` | Real GDP annual growth rate, 2014-2024 (%/yr) | percent per year: compound annual growth rate of real GDP, 2014 to 2024 (member counties' real GDP in chained 2017 dollars summed (BEA CAGDP9); no value unless every member county is published at both years) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - An area has a value only when every member county is published at both years. - Chained dollars are not strictly additive, so a metro sum approximates what BEA would publish for it. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # EIA Retail Sales The average industrial retail electricity price per state (cents per kWh), from EIA's retail sales data (Forms EIA-861 and EIA-861M). ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Energy Information Administration | | Product | Electric power retail sales and prices by state | | Source | [https://www.eia.gov/electricity/data.php](https://www.eia.gov/electricity/data.php) | | Category | Utilities | | Period | Latest complete annual year | | Refresh cadence | Monthly | | Geographies | State. Each state's price is given to its counties, and a metro is the population-weighted mean of its counties, so a metro spanning states blends their prices. | | Availability | Available | | Cadastre key | `eia` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.eia.gov/about/copyrights_reuse.php](https://www.eia.gov/about/copyrights_reuse.php) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Energy Information Administration, Electric power retail sales and prices by state**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `electricity_industrial_price` | Industrial electricity price | cents per kWh | population-weighted county mean | ## Known gaps and caveats - A state-level benchmark only: it is not a utility tariff or the rate at any site. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # DOT Rail Network The North American Rail Network lines from the U.S. DOT's National Transportation Atlas Database: every U.S. rail line segment, including the industrial leads, spurs and yard tracks that matter for siting. > [!NOTE] > **Not available yet.** This dataset is imported for parcel-level screening. The launch is metro-level, so nothing in the app or the API reads it yet. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. DOT Bureau of Transportation Statistics | | Product | North American Rail Network Lines | | Source | [https://geodata.bts.gov/datasets/usdot::north-american-rail-network-lines](https://geodata.bts.gov/datasets/usdot::north-american-rail-network-lines) | | Category | Transport | | Period | The year it was last imported | | Refresh cadence | Quarterly | | Geographies | Line geometry (United States segments only). There are no metro measures. | | Availability | Not available yet (parcel level) | | Cadastre key | `rail` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.transportation.gov/digital-rights](https://www.transportation.gov/digital-rights) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. DOT Bureau of Transportation Statistics, North American Rail Network Lines**. ## Known gaps and caveats - Imported for parcel-level siting, which is not available yet; nothing at metro level reads it. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # FEMA NFHL FEMA's National Flood Hazard Layer: the effective flood-hazard zones of the Flood Insurance Rate Maps. > [!NOTE] > **Not available yet.** This dataset is imported for parcel-level screening. The launch is metro-level, so nothing in the app or the API reads it yet. ## Source | Fact | Value | | --- | --- | | Publisher | FEMA | | Product | National Flood Hazard Layer | | Source | [https://www.fema.gov/flood-maps/national-flood-hazard-layer](https://www.fema.gov/flood-maps/national-flood-hazard-layer) | | Category | Hazard | | Period | The release date of each state's file | | Refresh cadence | Monthly | | Geographies | Flood-zone polygons, imported state by state (a pilot state so far). There are no metro measures. | | Availability | Not available yet (parcel level) | | Cadastre key | `nfhl` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.fema.gov/about/website-information](https://www.fema.gov/about/website-information) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **FEMA, National Flood Hazard Layer**. ## Known gaps and caveats - Imported for parcel-level screening, which is not available yet; nothing at metro level reads it. - Coverage is not complete nationwide and changes continually. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # FEMA NRI FEMA's National Risk Index: the composite risk index, expected annual loss, social vulnerability and community resilience, and a risk score for each of eighteen natural hazards. ## Source | Fact | Value | | --- | --- | | Publisher | FEMA | | Product | National Risk Index (county) | | Source | [https://hazards.fema.gov/nri/](https://hazards.fema.gov/nri/) | | Category | Hazard | | Period | 2025 release | | Refresh cadence | Quarterly | | Geographies | County and census tract. A metro's scores are population-weighted means of its counties; expected annual loss, a dollar total, is summed. | | Availability | Available | | Cadastre key | `nri` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.fema.gov/about/website-information](https://www.fema.gov/about/website-information) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **FEMA, National Risk Index (county)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `fema_nri_risk_index` | FEMA National Risk Index | risk score 0-100 | population-weighted county mean | | `fema_nri_expected_annual_loss` | FEMA expected annual loss | dollars | sum over member counties | | `fema_nri_social_vulnerability` | FEMA social vulnerability | risk score 0-100 | population-weighted county mean | | `fema_nri_community_resilience` | FEMA community resilience | risk score 0-100 | population-weighted county mean | | `fema_nri_avalanche_risk` | FEMA avalanche risk | risk score 0-100 | population-weighted county mean | | `fema_nri_coastal_flooding_risk` | FEMA coastal flooding risk | risk score 0-100 | population-weighted county mean | | `fema_nri_cold_wave_risk` | FEMA cold wave risk | risk score 0-100 | population-weighted county mean | | `fema_nri_drought_risk` | FEMA drought risk | risk score 0-100 | population-weighted county mean | | `fema_nri_earthquake_risk` | FEMA earthquake risk | risk score 0-100 | population-weighted county mean | | `fema_nri_hail_risk` | FEMA hail risk | risk score 0-100 | population-weighted county mean | | `fema_nri_heat_wave_risk` | FEMA heat wave risk | risk score 0-100 | population-weighted county mean | | `fema_nri_hurricane_risk` | FEMA hurricane risk | risk score 0-100 | population-weighted county mean | | `fema_nri_ice_storm_risk` | FEMA ice storm risk | risk score 0-100 | population-weighted county mean | | `fema_nri_landslide_risk` | FEMA landslide risk | risk score 0-100 | population-weighted county mean | | `fema_nri_lightning_risk` | FEMA lightning risk | risk score 0-100 | population-weighted county mean | | `fema_nri_riverine_flooding_risk` | FEMA riverine flooding risk | risk score 0-100 | population-weighted county mean | | `fema_nri_strong_wind_risk` | FEMA strong wind risk | risk score 0-100 | population-weighted county mean | | `fema_nri_tornado_risk` | FEMA tornado risk | risk score 0-100 | population-weighted county mean | | `fema_nri_tsunami_risk` | FEMA tsunami risk | risk score 0-100 | population-weighted county mean | | `fema_nri_volcanic_activity_risk` | FEMA volcanic activity risk | risk score 0-100 | population-weighted county mean | | `fema_nri_wildfire_risk` | FEMA wildfire risk | risk score 0-100 | population-weighted county mean | | `fema_nri_winter_weather_risk` | FEMA winter weather risk | risk score 0-100 | population-weighted county mean | ## Known gaps and caveats - A planning and risk-screening product: not underwriting, and not a hazard determination for any site. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # EPA Green Book The EPA Green Book: which counties are designated non-attainment, or maintenance areas, for the National Ambient Air Quality Standards, per pollutant (ozone, PM2.5, PM10, sulfur dioxide, lead, carbon monoxide, nitrogen dioxide). A new major source in a non-attainment area needs emission offsets and the strictest controls, which makes permitting slower and dearer. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Environmental Protection Agency | | Product | Green Book: NAAQS non-attainment and maintenance areas by county | | Source | [https://www.epa.gov/green-book](https://www.epa.gov/green-book) | | Category | Hazard | | Period | The export date of the county file | | Refresh cadence | Monthly | | Geographies | County, for every state and territory. A metro takes the class of its worst county, and its share of population in non-attainment counties is population-weighted. | | Availability | Available | | Cadastre key | `epa-green-book` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.epa.gov/web-policies-and-procedures/epa-disclaimers](https://www.epa.gov/web-policies-and-procedures/epa-disclaimers) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry`, `api` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Environmental Protection Agency, Green Book: NAAQS non-attainment and maintenance areas by county**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `epa_ozone_class` | Ozone non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 marginal or moderate, 3 serious, 4 severe, 5 extreme; a county only partly inside an area counts in full) | highest value among member counties | | `epa_ozone_nonattainment` | Population in ozone non-attainment counties (share) | share of population (0-1) in counties in ozone non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_ozone_partial` | Ozone non-attainment covers only part of the county | 0 or 1 (1 = the county's ozone class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_pm25_class` | PM2.5 non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 moderate, 3 serious; a county only partly inside an area counts in full) | highest value among member counties | | `epa_pm25_nonattainment` | Population in PM2.5 non-attainment counties (share) | share of population (0-1) in counties in PM2.5 non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_pm25_partial` | PM2.5 non-attainment covers only part of the county | 0 or 1 (1 = the county's PM2.5 class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_pm10_class` | PM10 non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 moderate, 3 serious; a county only partly inside an area counts in full) | highest value among member counties | | `epa_pm10_nonattainment` | Population in PM10 non-attainment counties (share) | share of population (0-1) in counties in PM10 non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_pm10_partial` | PM10 non-attainment covers only part of the county | 0 or 1 (1 = the county's PM10 class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_so2_class` | Sulfur dioxide non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 non-attainment (not classified); a county only partly inside an area counts in full) | highest value among member counties | | `epa_so2_nonattainment` | Population in sulfur dioxide non-attainment counties (share) | share of population (0-1) in counties in sulfur dioxide non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_so2_partial` | Sulfur dioxide non-attainment covers only part of the county | 0 or 1 (1 = the county's sulfur dioxide class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_lead_class` | Lead non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 non-attainment (not classified); a county only partly inside an area counts in full) | highest value among member counties | | `epa_lead_nonattainment` | Population in lead non-attainment counties (share) | share of population (0-1) in counties in lead non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_lead_partial` | Lead non-attainment covers only part of the county | 0 or 1 (1 = the county's lead class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_co_class` | Carbon monoxide non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 moderate or not classified, 3 serious; a county only partly inside an area counts in full) | highest value among member counties | | `epa_co_nonattainment` | Population in carbon monoxide non-attainment counties (share) | share of population (0-1) in counties in carbon monoxide non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_co_partial` | Carbon monoxide non-attainment covers only part of the county | 0 or 1 (1 = the county's carbon monoxide class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_no2_class` | Nitrogen dioxide non-attainment class (worst county) | class (0 attainment, 1 maintenance, 2 non-attainment (not classified); a county only partly inside an area counts in full) | highest value among member counties | | `epa_no2_nonattainment` | Population in nitrogen dioxide non-attainment counties (share) | share of population (0-1) in counties in nitrogen dioxide non-attainment; a county only partly inside an area counts in full | population-weighted county mean | | `epa_no2_partial` | Nitrogen dioxide non-attainment covers only part of the county | 0 or 1 (1 = the county's nitrogen dioxide class rests only on areas covering part of it) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_any_nonattainment` | Any criteria-pollutant non-attainment (metro) | 0 or 1 (1 = a county is in non-attainment for any criteria pollutant; a county only partly inside an area counts in full) | highest value among member counties | | `epa_nonattainment_pollutants` | Pollutants in non-attainment (county with the most) | pollutants, 0-7 (in non-attainment; a county only partly inside an area counts in full) | highest value among member counties | | `epa_worst_nonattainment_class` | Worst non-attainment class (any pollutant, worst county) | class (0 attainment, 1 maintenance, 2 marginal, moderate or unclassified non-attainment, 3 serious, 4 severe, 5 extreme; a county only partly inside an area counts in full) | highest value among member counties | ## Known gaps and caveats - The class is a 0-5 ladder: 0 attainment, 1 maintenance, 2 marginal, moderate or unclassified non-attainment, 3 serious, 4 severe, 5 extreme. - A county only partly inside a non-attainment area counts in full, so a metro's class is an upper bound for a site in it. - Revoked standards are skipped. - Connecticut replaced its eight counties with nine planning regions, which Census geography now uses; the legacy counties' designations are mapped onto the planning regions by boundary overlap, with the same upper-bound rule. - These are county designations, not monitored air quality, not permit outcomes, and not a statement about a particular site. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # EPA Green Book area boundaries The EPA Green Book's mapped non-attainment and maintenance area boundaries, one shapefile per standard in force, and how much of each county and metro lies inside a non-attainment area, per pollutant. Where the county designations count a county only partly inside an area in full, these measure the part. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Environmental Protection Agency | | Product | Green Book: non-attainment and maintenance area boundaries (GIS shapefiles) | | Source | [https://www.epa.gov/green-book/green-book-gis-download](https://www.epa.gov/green-book/green-book-gis-download) | | Category | Hazard | | Period | The export date of the county file (each area's status and class); each shapefile's own date is stored with it | | Refresh cadence | Monthly | | Geographies | County, for every state and territory, and metro. A county the Green Book designates whole is 1, one it designates in part is measured on the boundary, and a metro is its counties' shares weighted by area. | | Availability | Available | | Cadastre key | `epa-green-book-areas` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.epa.gov/web-policies-and-procedures/epa-disclaimers](https://www.epa.gov/web-policies-and-procedures/epa-disclaimers) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Environmental Protection Agency, Green Book: non-attainment and maintenance area boundaries (GIS shapefiles)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `epa_ozone_nonattainment_area_share` | Area inside ozone non-attainment areas (share) | share of the area (0-1) inside an area in ozone non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_pm25_nonattainment_area_share` | Area inside PM2.5 non-attainment areas (share) | share of the area (0-1) inside an area in PM2.5 non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_pm10_nonattainment_area_share` | Area inside PM10 non-attainment areas (share) | share of the area (0-1) inside an area in PM10 non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_so2_nonattainment_area_share` | Area inside sulfur dioxide non-attainment areas (share) | share of the area (0-1) inside an area in sulfur dioxide non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_lead_nonattainment_area_share` | Area inside lead non-attainment areas (share) | share of the area (0-1) inside an area in lead non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_co_nonattainment_area_share` | Area inside carbon monoxide non-attainment areas (share) | share of the area (0-1) inside an area in carbon monoxide non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_no2_nonattainment_area_share` | Area inside nitrogen dioxide non-attainment areas (share) | share of the area (0-1) inside an area in nitrogen dioxide non-attainment (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `epa_any_nonattainment_area_share` | Area inside any non-attainment area (share) | share of the area (0-1) inside an area in non-attainment for any criteria pollutant (class 2 or more); 1 for a county the Green Book designates whole; a county designated in part is measured on the boundary; a metro is its counties' shares weighted by area; area, not population; measured on EPA's mapped area boundaries, which EPA says are for mapping only and not the legal definition (40 CFR part 81) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - EPA publishes the shapefiles for mapping and visualization only: they are not the legal definition of the areas, which is 40 CFR part 81. - These are shares of area (inland water included), not of population: where people live inside a partial county is not known at this grain. - An area's status and class come from the Green Book county file, read by the same rules as the county designations; revoked standards are skipped. - Connecticut replaced its eight counties with nine planning regions, which Census geography now uses; a planning region at least 98% inside legacy counties designated whole is 1, any other is measured against the boundaries of the legacy counties' areas it overlaps. - A boundary is a designation, not monitored air quality, a permit outcome or a statement about a particular site. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # EPA Class I areas EPA's boundaries of the Class I areas under the Clean Air Act: the national parks and wilderness areas whose air the prevention-of-significant-deterioration (PSD) program protects most. A new major source that may affect one faces Class I increment and air-quality-related-value review and notice to the federal land manager; 100 km is the customary screening distance in EPA and land-manager guidance, so nearness is a cue for how involved air permitting will be. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Environmental Protection Agency, OAQPS (from NPS, USDA Forest Service, FWS and BIA boundaries) | | Product | Class I areas under the Clean Air Act (mandatory federal and tribal) | | Source | [https://www.epa.gov/visibility/regional-haze-program](https://www.epa.gov/visibility/regional-haze-program) | | Category | Hazard | | Period | The layer's last data edit (EPA ArcGIS service) | | Refresh cadence | Quarterly | | Geographies | County and metro. The distance is from each county's centroid, and a metro's is the population-weighted mean of its counties'; the count and the area share within 100 km are measured for counties and metros directly (a metro's share is its counties' weighted by area). | | Availability | Available | | Cadastre key | `epa-class-one-areas` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.arcgis.com/home/item.html?id=86b6748fb99544eeb49ca9e5a1d12d99](https://www.arcgis.com/home/item.html?id=86b6748fb99544eeb49ca9e5a1d12d99) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Environmental Protection Agency, OAQPS (from NPS, USDA Forest Service, FWS and BIA boundaries), Class I areas under the Clean Air Act (mandatory federal and tribal)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `class1_nearest_km` | Distance to the nearest Class I area (km) | km from the county's centroid to the nearest of the 158 mandatory Class I federal areas (national parks and wilderness areas of 1977; tribal Class I areas not counted), 0 inside one; a metro is the population-weighted mean of its counties'; a screening cue for PSD Class I review, not a permitting finding | population-weighted county mean | | `class1_areas_within_100km` | Class I areas within 100 km | areas: how many of the 158 mandatory Class I federal areas (national parks and wilderness areas of 1977; tribal Class I areas not counted) lie within 100 km of any part of the county or metro; a screening cue for PSD Class I review, not a permitting finding | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `class1_within_100km_area_share` | Area within 100 km of a Class I area (share) | share of the area (0-1) within 100 km of one of the 158 mandatory Class I federal areas (national parks and wilderness areas of 1977; tribal Class I areas not counted); a metro is its counties' shares weighted by area; a screening cue for PSD Class I review, not a permitting finding | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - Distance to a Class I area is a screening cue, not a PSD applicability finding: that depends on the source's size, emissions and modeling. - The measures count the 158 mandatory Class I federal areas (the 156 of 40 CFR 81 subpart D and the two where visibility is not an important value); the seven tribal Class I areas are stored but not counted. - A county's distance is from its centroid, not from a particular site; a large county can be much nearer or farther at its edges. - Boundaries are simplified to about 50 m before distances are measured. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # Ozone Transport Region (CAA 184, 40 CFR 81.457) The Ozone Transport Region of the Clean Air Act, where a source of 50 tons a year of volatile organic compounds is a major source, as if the area were in moderate ozone non-attainment, even where the air meets the standard. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Congress (Clean Air Act section 184) and EPA (40 CFR 81.457) | | Product | Ozone Transport Region (statutory boundary, as of 2022-03-14) | | Source | [https://www.ecfr.gov/current/title-40/chapter-I/subchapter-C/part-81/subpart-E/section-81.457](https://www.ecfr.gov/current/title-40/chapter-I/subchapter-C/part-81/subpart-E/section-81.457) | | Category | Hazard | | Period | The boundary as of 2022-03-14 (40 CFR 81.457) | | Refresh cadence | None (statutory table in the code) | | Geographies | County, from the statute's list as codified; a metro is the population-weighted mean of its counties', so it reads as the share of its population in the region. | | Availability | Available | | Cadastre key | `ozone-transport-region` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. statute and regulation) | | Terms | [https://www.law.cornell.edu/uscode/text/42/7511c](https://www.law.cornell.edu/uscode/text/42/7511c) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Congress (Clean Air Act section 184) and EPA (40 CFR 81.457), Ozone Transport Region (statutory boundary, as of 2022-03-14)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `ozone_transport_region` | Population in the Ozone Transport Region (share) | share (0-1): a county is 1 inside the Ozone Transport Region, 0 outside, and a Maine county only partly inside counts by its listed towns' share of its population (ACS); a metro is the population-weighted mean of its counties' (a 50 tpy VOC major-source threshold applies in the region) | population-weighted county mean | ## Known gaps and caveats - Ten whole states (CT, DE, MD, MA, NH, NJ, NY, PA, RI, VT), the District of Columbia and ten Virginia counties and cities of the Washington metro, and only listed towns of Maine since 2022. - A Maine county only partly inside counts by its listed towns' share of its population (ACS 5-year, by county subdivision). Chebeague Island, split from Cumberland town in 2007, is not in the rule's list and counts as outside. - Being in the region tightens VOC and NOx permitting; it is not a non-attainment designation. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # EPA regulated facilities Places U.S. EPA programs track: Superfund National Priorities List sites, RCRA hazardous-waste large quantity generators and corrective-action facilities, Toxics Release Inventory reporters and brownfield properties, counted per county (NPL and TRI also per 100,000 residents). ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Environmental Protection Agency (Superfund NPL, Facility Registry Service, Cleanups in my Community, TRI) | | Product | EPA regulated facilities and cleanup sites (Superfund NPL, RCRA LQG and corrective action, TRI, brownfields) | | Source | [https://www.epa.gov/frs](https://www.epa.gov/frs) | | Category | Hazard | | Period | The month of each run for the EPA services; the latest reporting year for TRI | | Refresh cadence | Monthly | | Geographies | County, from each record's reported point placed in the current census tract (or county) that holds it. A metro's count is the sum of its counties'; its rate per 100,000 is its pooled count over its pooled population. | | Availability | Available | | Cadastre key | `epa-facilities` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.epa.gov/web-policies-and-procedures/epa-disclaimers](https://www.epa.gov/web-policies-and-procedures/epa-disclaimers) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Environmental Protection Agency (Superfund NPL, Facility Registry Service, Cleanups in my Community, TRI), EPA regulated facilities and cleanup sites (Superfund NPL, RCRA LQG and corrective action, TRI, brownfields)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `superfund_npl_sites` | Superfund National Priorities List sites (final) | sites on the final Superfund National Priorities List (proposed and deleted sites are not counted); counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | sum over member counties | | `superfund_npl_sites_per_100k` | Superfund National Priorities List sites (final), per 100,000 residents | sites on the final Superfund National Priorities List (proposed and deleted sites are not counted), per 100,000 residents (ACS population); counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | mean of member counties weighted by Residents counted for the EPA facility rates, over the counties with a value (unavailable where those hold under 80% of it) | | `rcra_lqg_facilities` | RCRA large quantity generators (active) | active RCRA hazardous-waste large quantity generators (FRS); counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | sum over member counties | | `rcra_corrective_action_facilities` | RCRA corrective-action facilities | facilities in EPA's RCRA corrective-action universe (2020 baseline, completed remedies included); counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | sum over member counties | | `tri_facilities` | Toxics Release Inventory reporting facilities | facilities that filed a Toxics Release Inventory report for the latest reporting year; counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | sum over member counties | | `tri_facilities_per_100k` | Toxics Release Inventory reporting facilities, per 100,000 residents | facilities that filed a Toxics Release Inventory report for the latest reporting year, per 100,000 residents (ACS population); counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | mean of member counties weighted by Residents counted for the EPA facility rates, over the counties with a value (unavailable where those hold under 80% of it) | | `brownfield_properties` | Brownfield properties (EPA ACRES) | properties in EPA's brownfields system (ACRES), assessed or cleaned up with EPA brownfield funding; counted in the county holding EPA's reported point; a registry count: being listed, or near a listed place, is not evidence of contamination on any parcel | sum over member counties | | `facility_rate_basis_population` | Residents counted for the EPA facility rates | people (the ACS population the NPL and TRI rates per 100,000 were computed with) | sum over member counties | ## Known gaps and caveats - A registry count, not contamination: a listed place, or one nearby, says nothing about the condition of a particular parcel. - Final NPL sites only; proposed and deleted sites are stored but not counted. Active large quantity generators only. The RCRA corrective-action count is EPA's 2020 baseline universe, completed remedies included. - Points are as EPA reports them; some are geocoded addresses with low stated accuracy, which can put a site near a county line in the neighbouring county. - EPA notes that the TRI Basic Data Files can differ from its TRI National Analysis, and that its geospatial data are not intended for use in establishing liability. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # HIFLD transmission lines via Esri Living Atlas archive Reported electric transmission lines from DHS's Homeland Infrastructure Foundation-Level Data (HIFLD), through Esri's archived republication, and five metro measures of line length and voltage. > [!WARNING] > **Restricted: not available in Cadastre, and will not be served by the API.** Its licence is unresolved: the federal record describes a U.S. government work, but the only live copy is republished under the Esri Master License Agreement. Until that is settled it is used for evaluation only: its values reach no screen, report or export, and the API will not serve them. The OpenStreetMap source answers the same questions. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. DHS Homeland Infrastructure Foundation-Level Data (HIFLD), republished by Esri | | Product | HIFLD Electric Power Transmission Lines (Esri Living Atlas archive) | | Source | [https://www.arcgis.com/home/item.html?id=d4090758322c4d32a4cd002ffaa0aa12](https://www.arcgis.com/home/item.html?id=d4090758322c4d32a4cd002ffaa0aa12) | | Category | Utilities | | Period | Data currency 2024-09-30 (archived upstream) | | Refresh cadence | None (archived upstream) | | Geographies | Metro: each line clipped to the metro outline. | | Availability | Restricted: not available | | Cadastre key | `hifld-transmission-lines` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Unresolved: U.S. federal government work (DHS HIFLD) republished under the Esri Master License Agreement | | Terms | [https://catalog.data.gov/dataset/electric-power-transmission-lines](https://catalog.data.gov/dataset/electric-power-transmission-lines) | | Register status | Candidate; licence unknown | | Allowed uses | `evaluation` | Cadastre shows none of its figures, so no credit is printed for it. ## Measures These measures are described for reference only: no value of any of them is served. The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `power_line_miles_230kv_plus` | Transmission line length, 230 kV and above (miles), HIFLD archive | miles of line inside the metro (lines reported in service and with a reported voltage; lines with unknown voltage are not counted; mapped features are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `power_line_miles_345kv_plus` | Transmission line length, 345 kV and above (miles), HIFLD archive | miles of line inside the metro (lines reported in service and with a reported voltage; lines with unknown voltage are not counted; mapped features are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `power_line_miles_500kv_plus` | Transmission line length, 500 kV and above (miles), HIFLD archive | miles of line inside the metro (lines reported in service and with a reported voltage; lines with unknown voltage are not counted; mapped features are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `power_line_max_voltage_kv` | Highest reported transmission voltage (kV), HIFLD archive | kV of the highest-voltage line with at least 100 m inside the metro (lines reported in service and with a reported voltage; lines with unknown voltage are not counted; mapped features are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `power_line_corridor_miles_230kv_plus` | Transmission corridor length, 230 kV and above (miles), HIFLD archive | miles of line corridor inside the metro (lines reported in service and with a reported voltage; lines with unknown voltage are not counted; parallel circuits counted once: the length of the union of the in-service lines, so a double-circuit corridor drawn as two features, or one way with two circuits, counts once; 230 kV and above only) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - Reported line geometry only: never available capacity, megawatts, redundancy, cost or timing. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # OpenStreetMap power lines (© OpenStreetMap contributors, ODbL) Transmission lines mapped in OpenStreetMap (power=line ways of Geofabrik's U.S. extract), a separate source from HIFLD with its own snapshot, and five metro measures of line length, corridor length and the highest reported voltage. ## Source | Fact | Value | | --- | --- | | Publisher | OpenStreetMap contributors, extracts by Geofabrik GmbH | | Product | OpenStreetMap power lines (power=line ways, Geofabrik US extract) | | Source | [https://www.openstreetmap.org/](https://www.openstreetmap.org/) | | Category | Utilities | | Period | The extract date of the active snapshot | | Refresh cadence | Monthly | | Geographies | Metro: each line clipped to the metro outline and measured on the ground. Never merged with another source. | | Availability | Available | | Cadastre key | `osm-power-lines` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Open Database License (ODbL) 1.0, attribution required | | Terms | [https://www.openstreetmap.org/copyright](https://www.openstreetmap.org/copyright) | | Register status | Verified; licence open | | Allowed uses | `internal`, `derived_analytics`, `public_display`, `public_geometry`, `bulk_export` | Wherever its figures are shown, this source requires the credit **© OpenStreetMap contributors** ([https://www.openstreetmap.org/copyright](https://www.openstreetmap.org/copyright)), printed with this note: > Transmission line data © OpenStreetMap contributors, available under the Open Database License (ODbL 1.0), https://www.openstreetmap.org/copyright. Measures are derived by Cadastre and are not endorsed by OpenStreetMap. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `osm_power_line_miles_230kv_plus` | Transmission line length, 230 kV and above (miles), OpenStreetMap | miles of line inside the metro (ways tagged power=line with no construction, proposed, disused or abandoned tag, and with a voltage tag (the highest of its values); ways with no usable voltage are not counted; mapped ways are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `osm_power_line_miles_345kv_plus` | Transmission line length, 345 kV and above (miles), OpenStreetMap | miles of line inside the metro (ways tagged power=line with no construction, proposed, disused or abandoned tag, and with a voltage tag (the highest of its values); ways with no usable voltage are not counted; mapped ways are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `osm_power_line_miles_500kv_plus` | Transmission line length, 500 kV and above (miles), OpenStreetMap | miles of line inside the metro (ways tagged power=line with no construction, proposed, disused or abandoned tag, and with a voltage tag (the highest of its values); ways with no usable voltage are not counted; mapped ways are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `osm_power_line_max_voltage_kv` | Highest reported transmission voltage (kV), OpenStreetMap | kV of the highest-voltage line with at least 100 m inside the metro (ways tagged power=line with no construction, proposed, disused or abandoned tag, and with a voltage tag (the highest of its values); ways with no usable voltage are not counted; mapped ways are summed as drawn) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | | `osm_power_line_corridor_miles_230kv_plus` | Transmission corridor length, 230 kV and above (miles), OpenStreetMap | miles of line corridor inside the metro (ways tagged power=line with no construction, proposed, disused or abandoned tag, and with a voltage tag (the highest of its values); ways with no usable voltage are not counted; parallel circuits counted once: the length of the union of the in-service lines, so a double-circuit corridor drawn as two features, or one way with two circuits, counts once; 230 kV and above only) | Not assembled from counties: a metro has a value only where one is stored for the metro itself | ## Known gaps and caveats - Reported line geometry only: it says where a line of a stated voltage is mapped, never available capacity, megawatts, redundancy, cost or timing. - OpenStreetMap maps ways, not circuits: a double circuit can be one way. Corridor miles count parallel circuits once and are the comparable figure. - Lines under construction, proposed, disused or abandoned are left out, and a way with no usable voltage never counts. - Edit recency is uneven, and operator names are on a minority of ways. - The derived line dataset itself is offered under the ODbL on the [Open data](https://getcadastre.com/open-data) page. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # CDFI Fund Opportunity Zones Qualified Opportunity Zones: the census tracts Treasury designated in 2018 for the federal Opportunity Zone capital-gains incentive, from the CDFI Fund's list, with each county's count of designated tracts and the share of its residents and land inside them. ## Source | Fact | Value | | --- | --- | | Publisher | U.S. Department of the Treasury, CDFI Fund (designations by Treasury under IRC 1400Z-1) | | Product | Designated Qualified Opportunity Zones (2018 designation, 2010 census tracts) | | Source | [https://www.cdfifund.gov/opportunity-zones](https://www.cdfifund.gov/opportunity-zones) | | Category | Incentives | | Period | 2018 designation, in force through 2028-12-31 | | Refresh cadence | Annual (a new designation round needs a new Round in code) | | Geographies | County, rolled up to metros: a metro's tract count is the sum of its counties', and its shares are pooled over all of its counties' tracts (residents from the ACS 2015-2019, land from the Census Gazetteer 2019). | | Availability | Available | | Cadastre key | `cdfi-opportunity-zones` | ## Licence and attribution | Fact | Value | | --- | --- | | Licence | Public domain (U.S. federal government work) | | Terms | [https://www.law.cornell.edu/uscode/text/17/105](https://www.law.cornell.edu/uscode/text/17/105) | | Register status | Production approved; licence open | | Allowed uses | `evaluation`, `internal`, `public_display`, `derived_analytics`, `redistribution`, `bulk_export`, `public_geometry` | This source requires no credit line beyond naming the publisher. Cite it as **U.S. Department of the Treasury, CDFI Fund (designations by Treasury under IRC 1400Z-1), Designated Qualified Opportunity Zones (2018 designation, 2010 census tracts)**. ## Measures The key is the measure's identifier in Cadastre. A measure stored for the metro itself is read as stored; **Rule from counties** is how a metro is assembled from its counties where it is not (see [Methodology](https://getcadastre.com/docs/methodology)). | Key | Label | Unit | Rule from counties | | --- | --- | --- | --- | | `oz_2018_tracts` | Opportunity Zone tracts, 2018 designation | census tracts designated in 2018 (2010 census tracts; in force through 2028-12-31, Puerto Rico through 2027-12-31); eligibility for the federal Opportunity Zone tax incentive, not an award, an investment or a benefit amount | sum over member counties | | `oz_2018_population_share` | Residents in Opportunity Zone tracts, 2018 designation (%) | percent of residents (ACS 2015-2019 5-year, 2010 census tracts) living in tracts designated in 2018 (2010 census tracts; in force through 2028-12-31, Puerto Rico through 2027-12-31); eligibility for the federal Opportunity Zone tax incentive, not an award, an investment or a benefit amount | mean of member counties weighted by Residents counted for the 2018 Opportunity Zone shares, over the counties with a value (unavailable where those hold under 80% of it) | | `oz_2018_land_share` | Land in Opportunity Zone tracts, 2018 designation (%) | percent of land area (Census Gazetteer 2019, 2010 census tracts) inside tracts designated in 2018 (2010 census tracts; in force through 2028-12-31, Puerto Rico through 2027-12-31); eligibility for the federal Opportunity Zone tax incentive, not an award, an investment or a benefit amount | mean of member counties weighted by Land counted for the 2018 Opportunity Zone shares (sq mi), over the counties with a value (unavailable where those hold under 80% of it) | | `oz_2018_basis_population` | Residents counted for the 2018 Opportunity Zone shares | people (ACS 2015-2019 5-year total population of the county's 2010 census tracts) | sum over member counties | | `oz_2018_basis_land_sqmi` | Land counted for the 2018 Opportunity Zone shares (sq mi) | square miles of land (Census Gazetteer 2019, the county's 2010 census tracts) | sum over member counties | ## Known gaps and caveats - A designation is eligibility for a tax incentive, not an award, an investment or a benefit amount. - The 2018 zones are 2010 census tracts and keep their 2018 boundaries; how each maps onto 2020 tracts is recorded (same, renumbered, split or merged), never area-weighted. - The 2025 law adds rounds every ten years; the first takes effect 2027-01-01 on 2020 tracts. Treasury had not published a national list of those designations when this was written, so they are not here yet; they will be a separate round beside 2018, which stays in force through 2028. - Connecticut replaced its eight counties with nine planning regions, which Census geography now uses; its 2010 tracts are counted in the planning region holding their internal point. - The 75 designated tracts in American Samoa, Guam, the Northern Mariana Islands and the U.S. Virgin Islands count toward their counties' tract totals, but those counties have no shares: there are no 2019 Gazetteer or ACS tract figures for them. - The CDFI Fund's list says it is not the official list, which the Internal Revenue Bulletin publishes (IRS Notice 2018-48 and Notice 2019-42). - One designated tract outside the Island Areas, 04019410502 in Pima County AZ, was split by the Census Bureau's 2012 tract corrections and has no 2019 tract: it is counted, but not in the shares. ## See also - [All datasets](https://getcadastre.com/docs/datasets) - [Rights and attribution](https://getcadastre.com/docs/rights) - [Data freshness](https://getcadastre.com/docs/freshness) --- # Methodology > How metro values are made from county data, vintages and the latest value, and known coverage gaps. Cadastre reports measures for metropolitan statistical areas (metros), and micropolitan areas where a publisher covers them, in the Census Bureau's current delineation in the [TIGER boundaries](https://getcadastre.com/docs/datasets/tiger). Some publishers publish metro figures; many publish only counties or states. This page explains how a metro value is made in each case, which vintage is read, and where values are missing and why. ## Where a metro value comes from A measure reaches a metro in one of two ways: - **Stored for the metro.** The publisher's own metro figure (the American Community Survey's metro estimates, BLS's metro unemployment series), or a figure Cadastre computes for the metro itself (transmission-line miles inside the metro outline, ten-year trends from county data the import reads at both ends of the window). This is used whenever metro rows cover at least 50% of metros. - **Assembled from the metro's counties**, by the rule its dataset declares for that measure, when there is no adequate metro figure. Counties belong to metros by the Census Bureau's delineation in the current TIGER vintage. A measure without a rule is never assembled from counties: a median, for example, cannot be averaged, and a ratio has to be recomputed from its parts. Such a measure has a metro value only where one is stored. ## Rollup rules The rule for each measure is on its dataset's page. These are the rules, in the words the app itself uses, with how many of the available measures use each: | Rule | What it does | Measures | | --- | --- | --- | | `sum` | sum over member counties | 35 | | `population_weighted_mean` | population-weighted county mean | 40 | | `pooled_growth` | growth of member counties combined | 1 | | `max` | highest value among member counties | 10 | | `sum_disclosed` | sum over member counties that disclose it, a lower bound (unavailable where suppression hides much of the industry) | 20 | | `ratio_of_sums` | member counties' combined job share against the U.S. share (unavailable where suppression hides much of the industry) | 19 | | `weighted_mean` | mean of member counties weighted by a declared measure (named on each measure), over the counties with a value (unavailable where those hold under 80% of it) | 18 | | None | Not assembled from counties: a metro has a value only where one is stored for the metro itself | 41 | **Population weighting.** A population-weighted mean weights each county by its total population (the American Community Survey's county population). For a rate whose denominator is not everyone this is an approximation, which is why CDC's adult rates are weighted by the adults CDC counts instead (the `weighted_mean` rule). **Disclosure and coverage.** Publishers withhold some county figures: BLS suppresses a county's employment where a few employers would be identifiable, and CDC suppresses small counts. A withheld figure is stored as unknown, never as zero. The rules that can meet one (`sum_disclosed`, `ratio_of_sums`, `weighted_mean`) use only the counties that disclose, and give the metro no value when those counties hold less than 80% of the metro's coverage basis (its establishments in the industry, or its weight), because the number would then describe a minority of the metro under the name of the whole. At or above that, a sum is a lower bound. **Metro values are Cadastre's computation.** Where a metro value is assembled from counties, it is Cadastre's figure, not the publisher's, and the measure's unit says so where the publisher requires it (CDC's measures end "metro value is Cadastre's ... average of CDC county estimates"). ## Vintages and the latest value Every stored value carries its vintage: the year (or period) it describes. A dataset can hold several vintages for the same place and measure; the screens and reports read the **latest** one for each place and measure, which is the newest vintage (and, where two sources hold the same measure for the same year, the first by source name, so the choice is deterministic). Each dataset page states the period its values describe. Some measures are trends over a window, such as labor-force growth from one year to another. Their labels name the window, so a value is never read as more recent than it is, and each refresh re-derives all of them from one release so revisions are never mixed. A saved snapshot or report keeps the values it was computed from. A later import does not change it. ## Coverage gaps A missing value is shown as missing, never as zero. In the app, a requirement eliminates a metro that has no value for it and says so (for example "No population data"), so a requirement never passes a metro on data it does not have. - **Puerto Rico.** Puerto Rico's metros are in the TIGER boundaries and in the screens. Coverage of Puerto Rico depends on each publisher: where a publisher has no figure for Puerto Rico, Cadastre has none either. The other U.S. Island Areas are not imported. - **Connecticut.** Connecticut replaced its eight counties with nine planning regions, which the current Census geography uses. Publishers that still report the legacy counties cannot be matched for every measure: CDC's overdose rates have no Connecticut value, QCEW history has no Connecticut growth values, and the EPA Green Book's county designations are mapped onto the planning regions by overlap. Each dataset page says what applies. - **Suppression.** Withheld county figures, described above, leave some metros without a value, mostly small metros and narrow industries. - **Partial surveys.** Some measures are not collected everywhere: CDC PLACES has no estimates for Kentucky and Pennsylvania in its current release, and two of its measures come from a module only some states asked. ## Measures are described, not judged Cadastre does not decide whether a higher value is better. Whether a high unemployment rate counts for or against a metro depends on the question being asked, so the direction is set by each criterion in the app, not by the measure. --- # Rights and attribution > How sources are licensed, which are restricted, and the credit each one requires. Being able to download a dataset does not mean it may be redistributed. Every source Cadastre imports is checked against its publisher's terms before its figures are shown, and the result is recorded where every screen, report and export asks: a source's own declaration in the code (its licence, and whether it is restricted) and, for sources with conditions or unsettled terms, a row in the sources register. This page summarises that register; each dataset's page has the details. ## How sources are licensed Most of Cadastre's datasets are works of the U.S. federal government, which are in the public domain: the Census Bureau, the Bureau of Labor Statistics, the Bureau of Economic Analysis, the Energy Information Administration, FEMA, the EPA, the Department of Transportation and CDC. Some publishers attach conditions even to public-domain data (CDC asks for a credit and a disclaimer). OpenStreetMap is licensed under the Open Database License, which requires a credit and has share-alike terms. For each source it holds, the register records a licence label and the uses it allows (a federal work without a register row is judged by its licence alone): | Use | What it allows | | --- | --- | | `evaluation` | Reviewing the data internally before deciding whether to use it | | `internal` | Internal use | | `public_display` | Showing figures from the source in the app and its reports | | `derived_analytics` | Computing figures from it: metro rollups, scores, rankings | | `redistribution` | Passing the data on to others | | `bulk_export` | Including its figures in a file a client takes away (CSV, Excel) | | `public_geometry` | Serving the source's own geometry publicly, such as map tiles | A use the licence does not support cannot be granted: redistribution, bulk export and public geometry need an open licence. ## Restricted sources A restricted source is never redistributed. Its rows may be held, flagged, so the decision can be revisited, but no metric read sees them: no screen, criterion, ranking, report or export shows its values, and the API will not serve them. Its docs page describes it so you know it was reviewed, and says why it is restricted. | Dataset | Why it is restricted | | --- | --- | | [County Health Rankings](https://getcadastre.com/docs/datasets/chr) | Its terms allow personal or non-profit use only; commercial use needs CHR&R's written consent, which Cadastre does not have. It is described here so you know it was reviewed, but its values reach no screen, report or export, and the API will not serve them. | | [HIFLD transmission lines via Esri Living Atlas archive](https://getcadastre.com/docs/datasets/hifld-transmission-lines) | Its licence is unresolved: the federal record describes a U.S. government work, but the only live copy is republished under the Esri Master License Agreement. Until that is settled it is used for evaluation only: its values reach no screen, report or export, and the API will not serve them. The OpenStreetMap source answers the same questions. | ## Attribution Where a source requires a credit, Cadastre prints it on every page and in every file that shows the source's figures: the report's data sources page (web, PDF, PowerPoint), the CSV and Excel sources, and the API's responses when it launches. If you use figures from Cadastre, carry the same credit. ### CDC PLACES Credit: **Source: CDC** ([https://data.cdc.gov/d/swc5-untb](https://data.cdc.gov/d/swc5-untb)) > Source: CDC, PLACES: Local Data for Better Health (2025 release, county estimates from 2023 BRFSS). Available at no charge at https://data.cdc.gov/d/swc5-untb. Metro percentages are Cadastre's adult-population-weighted averages of CDC's county estimates, not CDC figures. > > Use of CDC data does not imply endorsement by CDC, ATSDR, HHS or the U.S. Government of Cadastre or its services. ### CDC Mapping Injury, Overdose, and Violence Credit: **Source: CDC** ([https://data.cdc.gov/d/psx4-wq38](https://data.cdc.gov/d/psx4-wq38)) > Source: CDC, Mapping Injury, Overdose, and Violence (county drug overdose death rates from NCHS National Vital Statistics System death records). Available at no charge at https://data.cdc.gov/d/psx4-wq38. Metro rates are Cadastre's population-weighted averages of CDC's county rates, not CDC figures. > > Use of CDC data does not imply endorsement by CDC, ATSDR, HHS or the U.S. Government of Cadastre or its services. ### OpenStreetMap power lines (© OpenStreetMap contributors, ODbL) Credit: **© OpenStreetMap contributors** ([https://www.openstreetmap.org/copyright](https://www.openstreetmap.org/copyright)) > Transmission line data © OpenStreetMap contributors, available under the Open Database License (ODbL 1.0), https://www.openstreetmap.org/copyright. Measures are derived by Cadastre and are not endorsed by OpenStreetMap. Every other available source is a U.S. federal government work that asks for no credit line beyond naming it. Cite the publisher and the product, as named on each dataset page. **CDC.** CDC's [terms for agency materials](https://www.cdc.gov/other/agencymaterials.html) also ask that the content not be changed (county values are kept as CDC published them; metro values are labelled as Cadastre's aggregates), that the data be stated to be available at no charge, that links to CDC open in a new window, and that no CDC or HHS logo be used. CDC's overdose rates come from death records, so the [NCHS Data User Agreement](https://www.cdc.gov/nchs/policy/data-user-agreement.html) also applies: statistical use only, no attempt to identify any person, and no linking with individually identifiable data. **OpenStreetMap.** The transmission-line measures derived from OpenStreetMap are kept separate from every other source. The line data itself is offered under the ODbL on the [Open data](https://getcadastre.com/open-data) page. ## Your use of Cadastre Your use of Cadastre, its data and its API is governed by the [Terms of Service](https://getcadastre.com/terms). What you may do with what the API returns, and the credit it must carry, is in [API, MCP and developer access](https://getcadastre.com/terms#api). --- # Data freshness > The period each dataset describes, when Cadastre last refreshed it and when it next checks the publisher. Each dataset's **period** is what its values describe; **last refreshed** is when Cadastre last imported it successfully (UTC). A refresh can bring revised figures for the same period, and a publisher's new release moves the period. The **refresh cadence** is how often Cadastre checks the publisher for a new release, set from the publisher's own calendar. **Next check** is when that happens (UTC). A check asks the publisher whether anything changed since the last import, and Cadastre imports again only when it did. A check that is more than two days late is marked overdue. | Dataset | Period | Refresh cadence | Last refreshed | Next check | | --- | --- | --- | --- | --- | | [TIGER boundaries](https://getcadastre.com/docs/datasets/tiger) | 2026 vintage (current) | Annual (release expected in September) | 2026-10-17 | 2027-09-01 | | [ACS 5-Year](https://getcadastre.com/docs/datasets/acs) | 2024 5-year estimates (growth from 2019 to 2024) | Annual (release expected in December) | 2026-10-16 | 2026-12-01 | | [County Health Rankings](https://getcadastre.com/docs/datasets/chr) | 2025 release | Annual (release expected in March) | — | — | | [Census Building Permits](https://getcadastre.com/docs/datasets/permits) | 2025 calendar year | Annual (release expected in February) | 2026-10-15 | 2027-02-01 | | [CDC PLACES](https://getcadastre.com/docs/datasets/cdc-places) | 2025 release, 2023 BRFSS estimates | Annual | 2026-10-15 | 2027-10-15 | | [CDC Mapping Injury, Overdose, and Violence](https://getcadastre.com/docs/datasets/cdc-overdose) | Calendar years as published; metros read the latest | Monthly | 2026-10-15 | 2026-11-15 | | [BLS LAUS](https://getcadastre.com/docs/datasets/bls-unemployment) | Latest full-year annual average; the latest month separately | Monthly | 2026-10-15 | 2026-11-15 | | [BLS QCEW](https://getcadastre.com/docs/datasets/bls-qcew) | 2025 annual averages, private ownership | Quarterly | 2026-10-15 | 2027-01-15 | | [BEA GDP](https://getcadastre.com/docs/datasets/bea-gdp) | 2024, current dollars | Annual (release expected in December) | 2026-10-15 | 2026-12-01 | | [BLS LAUS history](https://getcadastre.com/docs/datasets/bls-laus-history) | Annual averages 1990-2025, not seasonally adjusted | Annual (release expected in April) | 2026-10-15 | 2027-04-01 | | [BLS QCEW history](https://getcadastre.com/docs/datasets/bls-qcew-history) | Private ownership annual averages, 2015, 2019, 2025 | Annual (release expected in September) | 2026-10-15 | 2027-09-01 | | [BEA real GDP](https://getcadastre.com/docs/datasets/bea-real-gdp) | 2014-2024, chained 2017 dollars | Annual (release expected in December) | 2026-10-15 | 2026-12-01 | | [EIA Retail Sales](https://getcadastre.com/docs/datasets/eia) | Latest complete annual year | Monthly | 2026-10-15 | 2026-11-15 | | [DOT Rail Network](https://getcadastre.com/docs/datasets/rail) | The year it was last imported | Quarterly | 2026-10-15 | 2027-01-15 | | [FEMA NFHL](https://getcadastre.com/docs/datasets/nfhl) | The release date of each state's file | Monthly | 2026-10-15 | 2026-11-15 | | [FEMA NRI](https://getcadastre.com/docs/datasets/nri) | 2025 release | Quarterly | 2026-10-15 | 2027-01-15 | | [EPA Green Book](https://getcadastre.com/docs/datasets/epa-green-book) | The export date of the county file | Monthly | 2026-10-15 | 2026-11-15 | | [EPA Green Book area boundaries](https://getcadastre.com/docs/datasets/epa-green-book-areas) | The export date of the county file (each area's status and class); each shapefile's own date is stored with it | Monthly | 2026-10-16 | 2026-11-16 | | [EPA Class I areas](https://getcadastre.com/docs/datasets/epa-class-one-areas) | The layer's last data edit (EPA ArcGIS service) | Quarterly | 2026-10-16 | 2027-01-16 | | [Ozone Transport Region (CAA 184, 40 CFR 81.457)](https://getcadastre.com/docs/datasets/ozone-transport-region) | The boundary as of 2022-03-14 (40 CFR 81.457) | None (statutory table in the code) | No import run recorded | None | | [EPA regulated facilities](https://getcadastre.com/docs/datasets/epa-facilities) | The month of each run for the EPA services; the latest reporting year for TRI | Monthly | 2026-10-17 | 2026-11-17 | | [HIFLD transmission lines via Esri Living Atlas archive](https://getcadastre.com/docs/datasets/hifld-transmission-lines) | Data currency 2024-09-30 (archived upstream) | None (archived upstream) | — | — | | [OpenStreetMap power lines (© OpenStreetMap contributors, ODbL)](https://getcadastre.com/docs/datasets/osm-power-lines) | The extract date of the active snapshot | Monthly | 2026-10-16 | 2026-11-16 | | [CDFI Fund Opportunity Zones](https://getcadastre.com/docs/datasets/cdfi-opportunity-zones) | 2018 designation, in force through 2028-12-31 | Annual (a new designation round needs a new Round in code) | 2026-10-16 | 2027-10-16 | --- # API > The read-only REST API: authentication, endpoints, rate limits, attribution and errors. The Cadastre API is a read-only JSON API over the datasets, measures and metro figures described in these docs, with the same screening and ranking the app uses. It is in beta and free while it is. The public datasets need no account: call it with no credential at all, at 30 requests a minute. Sign in (an API key or an approved app) for higher limits. ## Base URL ```text https://getcadastre.com/api/v1 ``` The API is version 1. The OpenAPI 3.1 description is public at [https://getcadastre.com/api/v1/openapi.json](https://getcadastre.com/api/v1/openapi.json). ## Without an account Every endpoint except `/me` answers a request with no credential: ```sh curl "https://getcadastre.com/api/v1/metros?q=austin" ``` It serves the same datasets as a signed-in request (the public datasets whose terms allow the API), with the same attribution, at 30 requests a minute and 2,000 a day for each network address. Use is governed by the [Terms of Service](https://getcadastre.com/terms#api) either way; by using the API you agree to them. ## Authentication For higher limits, send one credential in the `Authorization` header, as a bearer token: ```sh curl -H "Authorization: Bearer $CADASTRE_API_KEY" https://getcadastre.com/api/v1/me ``` A credential that is not valid (unknown, revoked or expired) is always answered `401`, never served as if there were none, so a client learns its key is bad. - **API keys**, for your own scripts and servers. Make one in [Settings](https://getcadastre.com/account) under **API keys** (you are asked for your password). A key starts `cad_key_` and is shown once: copy it then. It acts as you, in the account you were working in when you made it. Revoke it in the same place. - **OAuth 2.1**, for apps and AI agents that sign in on your behalf: an MCP client, or the [Cadastre CLI](https://getcadastre.com/docs/cli). The app opens your browser, you sign in to Cadastre, choose the account and approve; the app receives an access token (`cad_at_`, one hour) and refreshes it itself. Clients register themselves (dynamic client registration) and use the authorization code flow with PKCE (S256). Discovery starts at the authorization server metadata, [https://getcadastre.com/.well-known/oauth-authorization-server](https://getcadastre.com/.well-known/oauth-authorization-server), and the API's protected resource metadata, [https://getcadastre.com/.well-known/oauth-protected-resource/api/v1](https://getcadastre.com/.well-known/oauth-protected-resource/api/v1). See [Connect an AI agent](https://getcadastre.com/agents) for client setup. Either credential has the one scope there is, `read`. Read Cadastre's datasets, measures and metro figures, and run screens and rankings over them. It cannot see or change your projects, account or settings. It works only while you are a member of that account and have accepted the current Terms of Service. **API access** is turned on per account, and is what gives a credential its higher limits. A new account does not have it: write to support@getcadastre.com to ask for it (it may become part of a paid plan later). Until it is on, Settings makes no keys for the account and the consent page will not connect an app to it; a key or app the account already has gets what a request without a credential gets (the same data, the per-address limits). `GET /me` says which: its `access.tier` is `api` (the account's limits) or `public` (the per-address limits). Disconnect an app in Settings under **Authorized apps**. Never put a key in a query string, a web page or a shared file; anything holding it can act as you. ## Endpoints All paths are under the base URL. Lists are paged with `page` (from 1) and `per_page` (up to 500, default 100); the answer's `meta` carries `total` and `total_pages`. ### Account #### `GET /me` Who the credential acts as. Needs a credential; without one it is 401 with the sign-in challenge. #### `GET /openapi.json` This description. Public: no credential needed. ### Datasets #### `GET /datasets` The datasets the API serves. #### `GET /datasets/{key}` One dataset, with its measures. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `key` (required) | path | string | A dataset key, as GET /datasets lists them | ### Measures #### `GET /measures` Search the measures. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `q` | query | string | Text in the name, label or unit | | `geography` | query | `msa`, `county`, `state` | Only measures with values at this geography | | `dataset` | query | string | Only this dataset's measures (its key) | | `page` | query | integer | Page number, from 1 | | `per_page` | query | integer | Items per page, up to 500 (default 100) | #### `GET /measures/{name}` One measure. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `name` (required) | path | string | A measure name, as GET /measures lists them | #### `GET /measures/{name}/values` A measure's value for every region of a geography. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `name` (required) | path | string | A measure name, as GET /measures lists them | | `geography` | query | `msa`, `county`, `state` | The geography to list; needed (a request without it is a 400) | | `state` | query | string | USPS code: metros partly in it, its counties, or the state | | `page` | query | integer | Page number, from 1 | | `per_page` | query | integer | Items per page, up to 500 (default 100) | ### Metros #### `GET /metros` The metropolitan statistical areas. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `state` | query | string | USPS code | | `q` | query | string | Text in the name | | `page` | query | integer | Page number, from 1 | | `per_page` | query | integer | Items per page, up to 500 (default 100) | #### `GET /metros/compare` Metros side by side. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `ids` (required) | query | string | Up to 25 metro ids, CBSA codes or slugs, comma-separated | | `measures` | query | string | Up to 50 measure names, comma-separated (default: the register's standard figures) | #### `GET /metros/{ref}` A metro's profile. Every measure the API serves that the metro has a value for. `ref` is the metro's id, its five-digit CBSA code or its slug (percent-encode the slug's slashes, `us%2Ftx%2Faustin-12420`). | Parameter | In | Type | Description | | --- | --- | --- | --- | | `ref` (required) | path | string | The metro's id, CBSA code or slug | ### Analysis #### `POST /screen` Screen the metros by scope and Requirements (read-only). The body is JSON, a `ScreenRequest` (fields below, under Screening and ranking). #### `POST /rank` Rank the metros on weighted criteria (read-only). The body is JSON, a `RankRequest` (fields below, under Screening and ranking). ### Incentives #### `GET /incentive_programs` Incentive programs federal, state and local governments offer (paid). Programs read from the jurisdictions' official pages and reviewed by Cadastre, each value with the sentence it was quoted from (`evidence`) and the page (`source_url`); a field the page does not state is null (unknown). A program is what a jurisdiction offers: not an award, an amount anyone received, or a finding that a site qualifies. A jurisdiction with no programs listed is not covered yet. Only records from pages whose terms allow reuse are served. Part of API access: an account without it is answered 403 `api_access_required`. | Parameter | In | Type | Description | | --- | --- | --- | --- | | `state` | query | string | USPS code or state FIPS: federal programs, the state's and its local governments' | | `metro` | query | string | CBSA code, region id or slug: federal programs, the metro's states' and its local governments' | | `mechanism` | query | `tax_credit`, `grant`, `loan`, `loan_guarantee`, `abatement`, `exemption`, `training_grant`, `infrastructure`, `financing_bond`, `zone_designation`, `other` | Only programs of this kind | | `page` | query | integer | Page number, from 1 | | `per_page` | query | integer | Items per page, up to 200 (default 50) | ## Examples ```sh # The datasets the API serves curl -H "Authorization: Bearer $CADASTRE_API_KEY" https://getcadastre.com/api/v1/datasets # Search the measures curl -H "Authorization: Bearer $CADASTRE_API_KEY" "https://getcadastre.com/api/v1/measures?q=unemployment&geography=msa" # A metro's profile, by its CBSA code (Huntsville, AL) curl -H "Authorization: Bearer $CADASTRE_API_KEY" https://getcadastre.com/api/v1/metros/26620 # Three metros side by side on the standard figures curl -H "Authorization: Bearer $CADASTRE_API_KEY" "https://getcadastre.com/api/v1/metros/compare?ids=26620,48620,46140" ``` Screen and rank are POSTs with a JSON body. They compute an answer and save nothing: ```sh curl -X POST https://getcadastre.com/api/v1/screen \ -H "Authorization: Bearer $CADASTRE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"requirements": {"tier": "500k", "min_mfg_share": 8, "max_unemployment": 5.5}}' curl -X POST https://getcadastre.com/api/v1/rank \ -H "Authorization: Bearer $CADASTRE_API_KEY" \ -H "Content-Type: application/json" \ -d '{"requirements": {"tier": "500k"}, "criteria": [{"measure": "unemployment_rate", "direction": "lower_better", "weight": 2}]}' ``` Measure names (`unemployment_rate` above) come from `GET /measures`. ## Screening and ranking `POST /screen` applies a scope and the app's Requirements to the metros and answers with the funnel (how many metros each Requirement leaves) and the metros that pass. `POST /rank` adds weighted criteria and answers with ranks, composite scores and each criterion's value, score and contribution. The same inputs give the same answer as a project in the app. ### Requirements | Field | Type | Meaning | | --- | --- | --- | | `tier` | `1m`, `500k`, `250k` | Minimum population | | `min_mfg_share` | number | Manufacturing share of GDP, percent, at least | | `max_unemployment` | number | Unemployment rate, percent, at most | | `min_growth` | number | Five-year population growth, percent, at least | | `max_hazard` | number | FEMA National Risk Index, at most | | `max_elec_price` | number | Industrial electricity price, cents per kWh, at most | | `rtw_only` | boolean | Only metros entirely in right-to-work states | ### Criteria | Field | Type | Meaning | | --- | --- | --- | | `measure` | string | A measure name from GET /measures | | `direction` | `higher_better`, `lower_better` | Which way scores better | | `weight` | number | Default 1; 0 keeps the criterion as a gate only | | `cutoff` | object | Eliminates the metros it holds for. | `scope.states` limits either to the metros partly in the listed states (USPS codes). A Requirement or criterion that reads a measure the API does not serve is a 422. ## Responses and attribution A successful answer is JSON: `{ "data": ..., "meta": ..., "attribution": [...] }`. `attribution` lists, once each, the credit every dataset behind `data` requires: the publisher's credit, the licence and its link, and any notices, disclaimers and conditions the publisher attaches. - **Show the attribution with the figures**, wherever they go: an analysis, a report, a deck, an app, an AI agent's answer. The [Rights and attribution](https://getcadastre.com/docs/rights) page explains each source's requirements, and the [Terms of Service](https://getcadastre.com/terms#api) make it a condition of using the API. - **Cite `retrieved_at`.** Each attribution entry carries `retrieved_at`, when Cadastre last retrieved that data from its publisher. Give it with the data (the Bureau of Labor Statistics asks API users to cite the retrieval date). - **Label Cadastre's computed values.** A value marked `computed_by_cadastre` is Cadastre's figure (for example a metro total built from county figures), and `calculation` says how. Credit it as "Source: Cadastre, computed from" the publisher's data, not as the publisher's own figure. Only datasets whose terms Cadastre has approved for the API are served; any other is absent from every list and a 404. Sources restricted in the app (see [Rights and attribution](https://getcadastre.com/docs/rights)) are never served. ## Not served - **No geometry.** Answers carry names and codes (region ids, CBSA codes, FIPS), never boundaries, points or lines. Geometry is not available yet; if it is added it will be an explicit option, never a default. - **No parcel data.** The launch is metro-level; parcels are not in the API. - **No listings.** Cadastre does not carry property listings. ## Rate limits - Without a credential, **30 requests a minute** and **2,000 a day** for each network address (an IPv6 /64), the API and the MCP server together. A key or app of an account without API access counts here too. - With a credential of an account with API access, **60 requests a minute** and **10,000 a day** for each API key, and for each app you approved (across its token refreshes). - **50,000 requests a day** for each account, over all its keys and apps, so more keys do not add up to more requests. Every answer carries `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` (seconds). Over a limit the answer is 429 with `Retry-After`: wait that many seconds; without an account, the message says how to sign in for more. These are the beta limits and may change. ## Caching The data GETs (datasets, measures, metros) carry an `ETag` and `Last-Modified`. Send `If-None-Match` with the ETag you have and an unchanged answer is a 304 with no body, which still counts as a request. The data changes when Cadastre imports a new release, not by the minute. An answer to a request without a credential is the same for everyone, so it is `Cache-Control: public, max-age=60` (with `Vary: Authorization`): a cache may keep it for a minute. An answer to a credential is private and revalidated every time. ## Errors An error is JSON: `{ "error": "", "message": "" }`. | Status | `error` | What to do | | --- | --- | --- | | 400 | `bad_request` | A malformed parameter or body. The message names it. | | 401 | `unauthorized`, `invalid_token` | A credential that is unknown, revoked or expired, or whose person left the account, or not sent as a bearer token; or none at all on `/me`. Fix or drop the credential (with none, the public datasets are served). The `WWW-Authenticate` header names the protected resource metadata, so an OAuth client can sign in again. | | 403 | `terms_required` | The Terms of Service were updated. Sign in to Cadastre in a browser and accept them; the key or app works again at once. | | 403 | `insufficient_scope` | The credential lacks the `read` scope. Sign in again or make a new key. | | 404 | `not_found` | No such dataset, measure or metro, or one the API does not serve. | | 415 | `unsupported_media_type` | Send the POST body as `application/json`. | | 422 | `invalid_request`, `unknown_measure` | Well formed but cannot be answered: an unknown measure, or a Requirement whose source the API does not serve. | | 429 | `rate_limited` | Over a rate limit. Wait for `Retry-After` seconds, or sign in for higher limits. | | 503 | `unavailable` | The API is not available on this server. Try again later. | ## Versioning and beta The version is in the path (`/api/v1`). During the beta Cadastre may add, change or remove endpoints, fields, datasets and limits, and will try to give notice of a change that breaks existing use; adding a field or a dataset is not a breaking change, so read answers tolerantly. There is no service level during the beta. See the [Terms of Service](https://getcadastre.com/terms#api). ## AI agents and the MCP server An AI agent can use the API directly, with or without a key, or connect to Cadastre's remote MCP server, which offers the same data as tools, with no sign-in or signed in with OAuth in the browser for higher limits. See [MCP server](https://getcadastre.com/docs/mcp) and the [agent guides](https://getcadastre.com/agents). --- # MCP server > The remote MCP server for AI assistants: connect Claude, Codex or Cursor, sign in in the browser, and the tools it offers. Cadastre's remote MCP server lets AI assistants such as Claude Code, Codex and Cursor read Cadastre's datasets, metro profiles, screens and rankings, with the same access, rights and attribution as the [API](https://getcadastre.com/docs/api). It needs no account: add the address and your assistant can use the public datasets at once, at 30 requests a minute. Sign in once in the browser for higher limits (there is no key to copy or manage). It is read-only and free while in beta. ## Connect The server's address is: ```text https://getcadastre.com/mcp ``` It speaks MCP's Streamable HTTP transport, and answers without a sign-in: your assistant connects with the address alone. **For higher limits, sign in** with the sign-in address instead: ```text https://getcadastre.com/mcp?auth=required ``` It is the same server, but it asks a client without a token to sign in (MCP clients start signing in only when asked). The first time your assistant uses it, the assistant opens a Cadastre page in your browser: sign in if you need to, choose which of your accounts it may use, and approve. That is all. Only an account with API access turned on can be chosen (it is what gives the higher limits; write to support@getcadastre.com to ask for it); the page marks the others. The [Cadastre CLI](https://getcadastre.com/docs/cli) prints, and with `--write` makes, the setup for Claude Code, Codex, Cursor and VS Code: `cadastre mcp add claude-code` (or `codex`, `cursor`, `vscode`). ### Claude Code ```sh claude mcp add --transport http cadastre https://getcadastre.com/mcp ``` That is all; add `--scope user` to have it in every project. To sign in for higher limits, add the sign-in address instead, then run `/mcp` in Claude Code, choose **cadastre** and **Authenticate**: ```sh claude mcp add --transport http cadastre "https://getcadastre.com/mcp?auth=required" ``` ### Codex ```sh codex mcp add cadastre --url https://getcadastre.com/mcp ``` Or in `~/.codex/config.toml`: ```toml [mcp_servers.cadastre] url = "https://getcadastre.com/mcp" ``` To sign in for higher limits, use `https://getcadastre.com/mcp?auth=required` as the URL and run `codex mcp login cadastre`. ### Cursor In `~/.cursor/mcp.json` (or `.cursor/mcp.json` in a project): ```json { "mcpServers": { "cadastre": { "url": "https://getcadastre.com/mcp" } } } ``` With the sign-in address as the `url`, Cursor offers to sign in to the server; that opens Cadastre's sign-in page in your browser. ### VS Code ```sh code --add-mcp '{"name":"cadastre","type":"http","url":"https://getcadastre.com/mcp"}' ``` That adds it to your user profile. For one workspace, put it in `.mcp.json` at the workspace root: ```json { "mcpServers": { "cadastre": { "type": "http", "url": "https://getcadastre.com/mcp" } } } ``` With the sign-in address as the `url`, VS Code opens the sign-in in your browser on first use. ### Any other client Any MCP client that supports Streamable HTTP connects with the address alone, and one that supports the MCP authorization flow signs in with the sign-in address (Gemini CLI, OpenCode and others sign in the same way). Clients register themselves through dynamic client registration; Cadastre does not yet accept client ID metadata documents, so a client that prefers them falls back to registering. Registration is for public clients (`token_endpoint_auth_method` `none`, with PKCE). A client that can only send a fixed header can use an [API key](https://getcadastre.com/account) instead of signing in: ```sh claude mcp add --transport http cadastre https://getcadastre.com/mcp --header "Authorization: Bearer cad_key_..." ``` Treat a key like a password: it acts as you, in the account it was made in, until you revoke it. ## How sign-in works The server follows the [MCP authorization specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization), so clients find everything themselves: 1. At the sign-in address, a request without a token is answered `401` with `WWW-Authenticate: Bearer resource_metadata="https://getcadastre.com/.well-known/oauth-protected-resource/mcp", scope="read"` (at `https://getcadastre.com/mcp` it is served without a sign-in). A token or key that is not valid is answered `401` at either address, never served as if there were none. 2. That [protected resource metadata](https://getcadastre.com/.well-known/oauth-protected-resource/mcp) names the resource (`https://getcadastre.com/mcp`) and the authorization server, whose [metadata](https://getcadastre.com/.well-known/oauth-authorization-server) lists its endpoints. 3. The client registers itself (dynamic client registration), sends you to the consent page with PKCE, and asks for a token for `https://getcadastre.com/mcp`. The only scope is `read`: the assistant can read data and run screens and rankings, never see or change your projects, account or settings. A token for the MCP server does not work on the API, and the reverse. Access tokens last an hour and are refreshed without asking you again; the approval itself lasts 90 days. **Settings > Authorized apps** lists every app you approved, with **Disconnect**. Leaving an account, or changing your password, disconnects its apps at once. If the account's API access is turned off, the app keeps working with the limits of no sign-in (`whoami` says so); write to support@getcadastre.com. If Cadastre's Terms were updated, it answers `403` `terms_required` until you accept them in a browser. ## Tools Every tool is read-only (`readOnlyHint`), returns a short Markdown summary for the assistant to read and the same JSON the API returns as structured content, and ends with the credit its sources require. A tool that cannot answer (an unknown metro, a measure that is not served) returns an error that says what to try instead. ### `whoami` Says who this connection acts as: the Cadastre user, the account whose access it uses (and their role in it), and the credential (an OAuth connection or an API key) with its scopes, or that it is not signed in (anonymous: public datasets only); and its rate limits. Use it to check the connection works and which limits apply. It returns no data figures. No arguments. ### `list_datasets` Lists the datasets Cadastre serves: each one's key, name, publisher, licence, the years (vintages) its values are for, the geographies it has values at (msa = metro areas, county, state) and how many measures it has. Use it to see what data Cadastre has; it lists datasets, not their measures. No arguments. ### `describe_dataset` Describes one dataset: publisher, licence, source link, refresh cadence, vintages, geographies, and every measure it provides (name, label, unit, and the geographies each has values at). | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `dataset` | string | yes | The dataset's key, as list_datasets gives it (e.g. acs, bls-unemployment). | ### `search_measures` Searches the measures (named figures such as unemployment_rate, population or fema_nri_risk_index) by words in their name, label or unit, optionally only those with values at one geography or from one dataset. Returns each measure's name (the identifier a measure is asked for by), label, unit, dataset and the geographies it has values at. With no query it lists every measure, a page at a time. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `query` | string | no | Words to find in a measure's name, label or unit, e.g. unemployment, gdp, obesity, percent. | | `geography` | one of `msa`, `county`, `state` | no | Only measures with values at this geography. msa = U.S. metro areas (OMB core-based statistical areas, by five-digit CBSA code); county = counties (five-digit FIPS); state = states (two-digit FIPS). | | `dataset` | string | no | Only this dataset's measures (a key from list_datasets). | | `page` | integer | no | Page number, from 1. | | `per_page` | integer | no | Rows per page (default 50, at most 200). | ### `describe_measure` Describes one measure: its label, unit and dataset, and at each geography (msa, county, state) how a value is made (published by the source, or computed by Cadastre, e.g. a population-weighted mean of a metro's counties), which years (vintages) the values are for, and how many regions have one. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `measure` | string | yes | The measure's name, as search_measures gives it. | ### `measure_values` Gives every region's value of one measure at one geography: metro areas (the default), counties or states, optionally only those in one state, in order of geographic code. Use it to see a measure across all metros, or across the counties of a state. Says the unit, the vintages and whether Cadastre computed the values. Paged, 50 rows by default. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `measure` | string | yes | The measure's name, as search_measures gives it. | | `geography` | one of `msa`, `county`, `state` | no | The geography to list (default msa). msa = U.S. metro areas (OMB core-based statistical areas, by five-digit CBSA code); county = counties (five-digit FIPS); state = states (two-digit FIPS). | | `state` | string (52 codes) | no | Only regions in this state (USPS code); for metros, those partly in it. | | `page` | integer | no | Page number, from 1. | | `per_page` | integer | no | Rows per page (default 50, at most 200). | ### `find_metros` Finds U.S. metro areas (MSAs, the current OMB delineations) by words in their name and/or by state. Returns each metro's CBSA code (the identifier a metro is asked for by), name, states, whether all its states have right-to-work laws, and population where it is served. With neither filter it lists all of them (about 390), a page at a time. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `query` | string | no | Words in the metro's name, e.g. Dallas, Austin, Salt Lake. | | `state` | string (52 codes) | no | Only metros that lie at least partly in this state (USPS code). | | `page` | integer | no | Page number, from 1. | | `per_page` | integer | no | Rows per page (default 50, at most 200). | ### `get_metro` Gives one metro area's profile: its name, CBSA code, states and right-to-work status, and every measure Cadastre serves that the metro has a value for, with the value, unit, the years (vintages) it is for and how it was made (published for the metro, or computed by Cadastre from its counties). | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `metro` | string or integer | yes | A metro's five-digit CBSA code (e.g. 12420 for Austin-Round Rock-San Marcos, TX), its region id (a UUID) or its slug, as find_metros returns them. | ### `compare_metros` Puts up to 25 metro areas side by side on up to 50 measures. Without measures it uses the standard site-selection figures (population, growth, manufacturing share of GDP, unemployment, hazard risk, industrial power price, where served). | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `metros` | list of strings or integers | yes | The metros to compare. Each one is given as a metro's five-digit CBSA code (e.g. 12420 for Austin-Round Rock-San Marcos, TX), its region id (a UUID) or its slug, as find_metros returns them. | | `measures` | list of strings | no | Measure names (from search_measures) with metro values. Default: the standard figures. | ### `screen_metros` Screens the U.S. metro areas by pass/fail Requirements, as Cadastre's project page does: an optional list of states (a metro partly in one is in scope), a minimum population tier, a minimum manufacturing share of GDP, a maximum unemployment rate, a minimum five-year population growth, a maximum FEMA hazard risk score, a maximum industrial electricity price and right-to-work states only. Returns the funnel (how many metros remain after each step) and the metros that pass, with the values the Requirements read. It filters; it does not order the metros. Read-only. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `states` | list of strings (codes) | no | Limit the scope to metros in these states (USPS codes). Omit for the whole country. | | `requirements` | object: `tier`, `min_mfg_share`, `max_unemployment`, `min_growth`, `max_hazard`, `max_elec_price`, `rtw_only` | no | Pass/fail Requirements; omit any not wanted. Percentages are percent (4.5 means 4.5%). | | `limit` | integer | no | How many passing metros to list (default 25); the count and funnel cover all of them. | ### `rank_metros` Ranks the U.S. metro areas that pass an optional screen (states and pass/fail Requirements: population tier, manufacturing share, unemployment, growth, hazard, power price, right-to-work) on weighted criteria, as Cadastre's project page does: each criterion is a measure with metro values (given by name), a direction (higher_better or lower_better) and a weight; each metro's value is scored 0-100 by percentile among the metros that pass, and the scores are blended by weight into a composite. A criterion's optional cutoff eliminates the metros it holds for. Returns the ranked metros with their composite and, per criterion, value, score and contribution to the composite (the contributions add up to it). Read-only. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `states` | list of strings (codes) | no | Limit the scope to metros in these states (USPS codes). Omit for the whole country. | | `requirements` | object: `tier`, `min_mfg_share`, `max_unemployment`, `min_growth`, `max_hazard`, `max_elec_price`, `rtw_only` | no | Pass/fail Requirements applied before ranking; omit any not wanted. | | `criteria` | list of objects | yes | The weighted criteria, each on a different measure with metro values. | | `include_eliminated` | boolean | no | Also list the metros a criterion's cutoff eliminated, after the ranked ones (default false). | | `limit` | integer | no | How many metros to list (default 25); the count and funnel cover all of them. | ### `incentive_programs` Lists the economic-development incentive programs that federal, state and local governments offer businesses (tax credits, grants, loans, loan guarantees, property tax abatements, sales and use tax exemptions, training grants, infrastructure, bond financing, zones), read from their official pages and reviewed by Cadastre. Filter by state, by metro (federal, the metro's states and its local governments) and by mechanism. Every value comes with the sentence it was quoted from and the page; a field the page does not state is null. A program is not an award or proof that a site qualifies, and a place with none listed is not covered yet. Requires API access. | Argument | Type | Required | What it is | | --- | --- | --- | --- | | `state` | string (52 codes) | no | Federal programs, the state's own and its local governments' (USPS code). | | `metro` | string or integer | no | A metro's five-digit CBSA code (e.g. 12420 for Austin-Round Rock-San Marcos, TX), its region id (a UUID) or its slug, as find_metros returns them. Federal, the metro's states' and its local governments' programs. | | `mechanism` | string (11 codes) | no | Only programs of this kind. | | `page` | integer | no | Page number, from 1. | | `per_page` | integer | no | Rows per page (default 50, at most 200). | Measures are named the way `search_measures` lists them (for example `unemployment_rate` or `population`). Metros are named by their five-digit CBSA code, which `find_metros` gives. Geographies are `msa` (metro areas), `county` and `state`. ## Attribution Every tool result ends with **Sources and required credit**: for each dataset behind the figures, its credit line, publisher, licence, the date Cadastre retrieved it, and any disclaimer or condition its publisher sets (CDC's "Source: CDC" and its no-endorsement statement, for example). The same list is in the structured content as `attribution`. When you, or your assistant, show or publish figures from Cadastre, show that credit with them. Values marked as computed by Cadastre are Cadastre's aggregates of county figures or its own derivations, not figures the publisher printed. Use of the server and what it returns is governed by the [Terms of Service](https://getcadastre.com/terms#api). [Rights and attribution](https://getcadastre.com/docs/rights) explains each source's terms. ## Limits - Without a sign-in, 30 requests a minute and 2,000 a day per network address, shared with the API. - Signed in, with an account that has API access, 60 requests a minute and 10,000 a day per connected app or API key, and 50,000 a day per account across all of them, shared with the API. - Every message counts, including the client's start-up messages (a session starts with about four). Over a limit the server answers `429` with `Retry-After`. - An assistant that connects from its maker's servers (Claude on claude.ai, ChatGPT) has a larger allowance without a sign-in, 600 requests a minute and 50,000 a day per address, but everyone whose requests leave from that address shares it. A shared network (an office, a mobile carrier) shares its address's ordinary allowance. Sign in, with the sign-in address, for an allowance of your own. - Paged tools return 50 rows by default and at most 200; ask for the next `page` or narrow by state, geography or dataset. Screens and rankings list the first 25 metros unless asked for more with `limit`; their counts and funnels always cover every metro. - Comparisons take up to 25 metros and 50 measures; a ranking up to 20 criteria. ## What is not served - **Geometry**: answers carry names and codes, never boundaries, points or lines. - **Parcel data**: property-level records are not part of the MCP server or the API. - **Restricted sources**: datasets whose terms do not allow it (County Health Rankings, for example) are never served; see [Rights and attribution](https://getcadastre.com/docs/rights). - **Listings**: Cadastre does not hold property listings. Only datasets whose terms Cadastre has approved for programmatic access are served; `list_datasets` shows which. --- # CLI > The cadastre command line: install, sign in, screen and rank in the terminal, and add the MCP server to an agent. `cadastre` is Cadastre's command-line client for the [API](https://getcadastre.com/docs/api): screens, rankings, comparisons and metro profiles in your terminal and your scripts, with the credit every answer requires printed under it, and a command that adds the [MCP server](https://getcadastre.com/docs/mcp) to your AI agent. It is open source (Apache-2.0) and in beta, like the API. Its [README](https://github.com/waratuman/cadastre-cli#readme) is the full reference. It reads what the API serves, and works without signing in: the data commands read the public datasets at 30 requests a minute. `cadastre login` gives higher limits, with an account that has API access turned on (write to support@getcadastre.com to ask for it). ## Install ```sh curl -fsSL https://raw.githubusercontent.com/waratuman/cadastre-cli/main/install.sh | sh ``` The script works on macOS and Linux (x86_64 and arm64): it downloads the release for your machine, checks its SHA-256 checksum, and installs `cadastre` to `~/.local/bin` (`/usr/local/bin` as root). It edits no shell profile. Each [release](https://github.com/waratuman/cadastre-cli/releases) has a static binary for Linux (x86_64 and aarch64), macOS (x86_64 and Apple silicon) and Windows (x86_64), with checksums; on Windows, download it from the releases page. The Windows build is listed but has not been tested yet. ## Sign in (optional) Signing in raises the limits; nothing else needs it. ```sh cadastre login # opens your browser: approve "Cadastre CLI" for an account cadastre login --device # no browser on this machine: type the code it shows at https://getcadastre.com/oauth/device cadastre login --key # use an API key from Settings instead (read from stdin, never an argument) cadastre whoami # who the CLI acts as and its limits, or "Not signed in (anonymous ...)" cadastre logout ``` The browser sign-in is the same consent page every app uses: choose the account, and approve. The CLI keeps its tokens in the system keychain where there is one and refreshes them itself. `CADASTRE_API_KEY`, when set, is used instead of any saved sign-in, for CI. Only start a device sign-in yourself: never type a code someone sent you. ## Commands | Command | What it does | | --- | --- | | `cadastre datasets [key]` | The datasets the API serves, or one with its measures | | `cadastre measures [name]` | Search the measures, or show one | | `cadastre metros` | The metro areas, filtered by state or name | | `cadastre metro ` | One metro's profile, by CBSA code, slug or id | | `cadastre compare ...` | Up to 25 metros side by side | | `cadastre screen` | The metros that pass your requirements, with the funnel | | `cadastre rank` | Rank the metros on weighted criteria | | `cadastre mcp add ` | Add the MCP server to Claude Code, Codex, Cursor or VS Code | | `cadastre docs [page]` | Open these docs | `cadastre help ` lists every flag. For example: ```sh cadastre screen --min-pop 500k --max-unemployment 5.5 --states TX,OK cadastre rank --min-pop 250k --criterion unemployment_rate:2:lower --criterion population cadastre compare 26620 48620 46140 --json ``` `screen` and `rank` compute an answer and save nothing, as the API's do. ## Output and attribution Answers print as tables; `--json` prints the API's answer exactly as it came, `attribution` included, for `jq` and for agents. Under every table the CLI prints each source's credit, licence, notices and retrieval date: carry them with the figures wherever you use them, as the [Terms of Service](https://getcadastre.com/terms#api) require. Values marked `*` are Cadastre's own computations from the publisher's figures. [Rights and attribution](https://getcadastre.com/docs/rights) explains each source. ## Connect an AI agent ```sh cadastre mcp add claude-code # or codex, cursor, vscode cadastre mcp add cursor --write # edit the client's config file for you ``` It prints the client's own command (where it has one) and the config file alternative; nothing is written without `--write`, and with it the file is backed up first and only a `cadastre` entry is added. The agent works without signing in. With `--sign-in` the entry uses the server's sign-in address, and the agent signs in through your browser itself, for higher limits. [Connect an AI agent](https://getcadastre.com/agents) has a guide for each client. ## Exit codes | Code | Meaning | | --- | --- | | 0 | Success | | 1 | An error: the API refused the request, not found, or a network failure | | 2 | Usage: an unknown command or flag, or a bad value | | 3 | The sign-in or key no longer works, or the command needs one: run `cadastre login` | | 4 | Accept Cadastre's current Terms of Service in a browser (`terms_required`) | | 5 | Rate limited: wait the seconds the message gives, or sign in for higher limits | | 6 | The account does not have API access for data that needs it (`api_access_required`; none does today): write to support@getcadastre.com | --- # Incentive programs > The catalog of federal, state and local incentive programs, each value quoted from the official page: what it holds, coverage, and the API (part of API access). Cadastre keeps a catalog of the economic-development incentive programs that federal, state and local governments offer businesses: tax credits, grants, loans and loan guarantees, property tax abatements, sales and use tax exemptions, training grants, infrastructure funds, bond financing and zones. Each program is read from the government's own official page and reviewed by Cadastre before it is shown. It is part of **API access** (write to support@getcadastre.com to ask for it). > [!IMPORTANT] > A program is what a government **offers**. It is not an award, an amount any company received, or a finding that a site qualifies. Confirm eligibility and current terms with the agency before relying on them. ## What a record holds Every value comes with the sentence it was quoted from on the page (`evidence`) and the page itself (`source_url`). A field the page does not state is `null`: unknown, never a guess. | Field | What it is | | --- | --- | | `name`, `aliases` | The program's name as the page gives it, and other names or acronyms it uses | | `jurisdiction` | `level` (`federal`, `state`, `local`), `key` (`us`, a state FIPS, or a county or place GEOID), `name`, `state`, `cbsa` for a local government | | `administering_agency` | The agency or authority that runs it | | `mechanism` | `tax_credit`, `grant`, `loan`, `loan_guarantee`, `abatement` (property tax), `exemption` (sales and use tax), `training_grant`, `infrastructure`, `financing_bond`, `zone_designation`, `other` | | `discretion` | `discretionary` (negotiated, competitive, approved case by case) or `statutory` (available to anyone who meets the criteria), when the page says | | `eligibility_summary`, `industries`, `naics_codes` | Who qualifies; NAICS codes only when printed on the page | | `min_jobs`, `min_investment_usd`, `wage_requirement` | Thresholds as stated | | `benefit_summary`, `benefit_max_usd`, `benefit_basis` | What the benefit is, its stated cap and how it is computed | | `statute`, `official_urls`, `status`, `effective_on`, `sunset_on` | As printed on the page | | `last_verified_at`, `verified_by` | When the record was last confirmed against its page: `human` (reviewed by Cadastre) or `agent` (re-read unchanged since) | ## Coverage The catalog reads the official program pages of federal agencies, every state and the District of Columbia, and the local governments of the largest metros. Some agencies' sites refuse automated readers, and some sites' terms do not allow reuse; programs from those pages are not shown. **A government with no programs listed is not covered yet: unknown, not one without incentives.** Programs are never added up across governments, and the catalog is separate from Opportunity Zones, which are designated places, not programs. ## API ```sh curl -H "Authorization: Bearer $CADASTRE_API_KEY" "https://getcadastre.com/api/v1/incentive_programs?metro=26420" curl -H "Authorization: Bearer $CADASTRE_API_KEY" "https://getcadastre.com/api/v1/incentive_programs?state=TX&mechanism=abatement" ``` `state` (a USPS code or FIPS) gives federal programs, the state's own and its local governments'; `metro` (a CBSA code, region id or slug) gives federal programs, those of each state the metro lies in and its local governments'; `mechanism` narrows to one kind; `page` and `per_page` (up to 200, default 50) page through. Each answer's `attribution` lists the agency and page of every program in it, and `meta.note` repeats what a program is and is not. An account without API access is answered `403` `api_access_required`, and a request without a credential `401`. While the catalog awaits approval for the API, the answer is an empty list with `meta.available` set to `false`; the app's page shows the reviewed programs meanwhile. A value Cadastre's reviewers corrected is listed in `edited_fields` and has no quote. The full description is under Incentives in the [API reference](https://getcadastre.com/docs/api). ## MCP and the app The [MCP server](https://getcadastre.com/docs/mcp) offers the same answers as the `incentive_programs` tool. In the app, a project's Markets step links to **Incentive programs**, which lists, for each target market, the federal, state and local programs, each with its mechanism, the figures as the page states them, its quoted sentences and a link to the page.