Data.gov Federal Housing Datasets Catalog
Datadory delivers data gov federal housing datasets catalog data covering 552,271 indexed United States government listings filtered to the housing slice: HUD, Census Bureau, FHFA and SEC records beside county assessor and city permit files, each carrying its DCAT dictionary - publisher, declared cadence, temporal span, resource formats - delivered by API, files, or your warehouse.
What is the Data.gov Federal Housing Datasets Catalog?
The Data.gov Federal Housing Datasets Catalog sits on Datadory's single-family residential REITs shelf as the widest front door into American housing data: one index spanning 552,271 government listings from federal agencies, states, counties, cities, tribes and universities, filtered to the records that matter for single-family rental work. Useful housing queries surface HUD, Census Bureau, FHFA and SEC feeds alongside county registers and city permit files, and every listing arrives with its complete DCAT dictionary: title, publishing organization and type, bureau and program codes, publisher-declared cadence, temporal span, reuse designation, contact point and the formats attached.
Two behaviors shape how the slice works in practice. First, default relevance ranking interleaves trending popular listings regardless of topic, so a naive housing query returns disability tables and vehicle registrations before it reaches anything rentable - disciplined querying with quoted phrases, format facets and organization filters is the difference between noise and a pipeline. Second, every record declares its own cadence and temporal span, so the catalog doubles as a directory of which housing series are monitoring-grade versus baseline-only before anyone commits a pipeline to the wrong feed.
Get a sample of this dataset and see live rows from the housing slice - not a screenshot of rows.
What do sample rows from the housing slice look like?
Three listings pulled straight from the catalog, kept in their raw shape - including the pair that proves the relevance-ranking quirk:
# data.gov federal housing datasets catalog - three records as returned
title: FY 2025 Disability Compensation Recipients by County
organization: Department of Veterans Affairs
organization_type: Federal
resource_formats: json, xml, csv
dataset_last_updated: June 19, 2026
title: Electric Vehicle Population Data
organization: State of Washington
organization_type: State
resource_formats: json, xml, csv, kml, html
title: Form N-PORT Data Sets
organization: U.S. Securities and Exchange Commission
accrual_periodicity: R/P3M (quarterly)
distributions: 27 ZIP files, 2019Q4 - 2026Q2The first two rows are the cautionary tale: a veterans' compensation table and Washington State's EV registry outrank anything housing-specific under default ordering, which is exactly why the slice is curated rather than taken raw. The third row is the payoff - the SEC's Form N-PORT data sets, twenty-seven quarterly ZIP distributions running 2019Q4 through 2026Q2, the institutional-disclosure record that matters when you track who holds single-family exposure. A sample returns rows in exactly this shape, scoped to the publishers and geographies you name.
What fields does each catalog record carry?
Ten named fields ride on every listing, and the dictionary below is the verified one - field names, types, definitions and example values as observed in the housing slice. Records are DCAT-native, so semantics follow the federal metadata standard rather than a vendor's renaming of it, and the ten-field spine stays identical whether a record comes from a federal agency or a county office.
Below the headline dictionary sit search-layer attributes that vary query to query - relevance scores, popularity counts, facet tallies, per-resource media-type detail. They are confirmed present in current pulls but not uniform across records, so they ship as additional fields on request: ask for them by name with your sample and we confirm exactly what each exposes for this slice.
Where does this coverage run, and at what grain?
- Geography · United States across federal, state, county, city and tribal publishers, with a bounding-box geographic filter offering Within and Intersect matching - so a Sun Belt metro pull stays inside its actual footprint instead of dissolving into state averages.
- Temporal · Declared per record: every listing carries its own temporal span, from static archives to rolling quarterly windows, plus both the publisher's modification date and the catalog's re-check timestamp - staleness audited listing by listing rather than assumed.
- Granularity · One catalog record per dataset, each referencing one or more distribution resources. This is a directory layer over the housing-data estate, not a row-level feed - which is precisely why it pairs cleanly with the row-level products sitting next to it on the shelf.
This slice scores 7/10 on Datadory's quality scale: the DCAT dictionary is fully verified, while individual listings vary in depth - the inherent trade of a federated catalog.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
You choose the channel and the cadence; the ten-field dictionary above travels unchanged across all three. Bulk files suit teams loading the whole housing-slice index once and joining it to portfolio or CRM tables. Scoped extracts suit products that surface publisher-matched records inside an app - one agency, one state, one bounding box. Warehouse delivery suits analysts running market-by-market models in SQL against continuously refreshed tables. Cadence changes are a settings conversation, not a re-integration project, and every sample arrives mapped to the exact dictionary above.
Who uses this data, and for what?
Market mapping before site selection. Single-family rental is a two-pure-play public business - Invitation Homes and American Homes 4 Rent - competing metro by metro, and every underwriting model starts with knowing which agencies hold which records. Publisher and organization-type fields turn 552,271 listings into an agency-by-agency map of who publishes housing data where: HUD program counts, Census tenure and vacancy series, FHFA price indexes, county registers. Pair the map with the Census Housing Vacancies and Homeownership (CPS-HVS) feed for the vacancy numbers themselves.
Underwriting input discovery. Instead of hunting agency properties one at a time, the accrual-periodicity field separates monitoring-grade series from static baselines before a pipeline gets built around the wrong feed. The mortgage-side twin, the Data.gov Federal Mortgage Datasets Hub, extends the same directory posture to lien and lending records.
Institutional positioning. The SEC's Form N-PORT data sets - twenty-seven quarterly ZIP distributions spanning 2019Q4 through 2026Q2 - sit inside this slice, making fund-level disclosure tracking a catalog lookup rather than a standing research project.
Metro-footprint monitoring. Bounding-box filtering with Within and Intersect matching scopes pulls to the operating footprint itself, so county and city records arrive matched to metros rather than averaged up to states.
Which personas get the most value?
Market researchers & consultants. The publisher roster plus bureau and program codes make agency-by-agency publishing footprints auditable - who ships housing statistics, at what declared cadence, in which formats. The market researchers breakdown ranks this slice against alternatives for the industry.
Competitive-intel & product teams. Tracking which disclosures the pure-play operators must file means knowing where those disclosures live; the organization field plus contact points resolve the owning office behind every record. Deeper comparisons live at the competitive intel page.
Investors & quants. Accrual periodicity and temporal coverage work as pre-flight checks: screen candidate series for cadence and span before committing them to a model. The investors and quants page carries the industry ranking.
Data scientists & ML engineers. DCAT-native dictionaries drop straight into schemas without manual annotation, and the ten-field spine joins cleanly to the row-level housing feeds already in the warehouse. The data scientists page ranks the slice for feature work.
Which notes pair with this dataset?
Notes and adjacent reading:
- Single-Family Residential REITs data hub - the pooled industry view, from federal catalogs to loan-level tapes.
- Best single-family residential REITs datasets - where this slice sits in the ranked shortlist.
- Single-family residential REITs data guide - the landscape tour before the field-level dive.
- vs Nareit REIT Directory - a government-wide index against the sector association's own member roster.
- Data.gov source profile - the aggregator behind the catalog, and everything else it publishes.
- Census Housing Vacancies and Homeownership (CPS-HVS) - the row-level tenure and vacancy series this catalog points at.
- Data.gov Federal Mortgage Datasets Hub - the same directory posture, aimed at lien and lending records.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
title | string | Listing name as supplied by the publishing agency - the human-readable handle for every record. | Form N-PORT Data Sets |
Organization | string | Publishing agency or government body shown on each result card - the primary dimension for agency-by-agency mapping. | U.S. Securities and Exchange Commission |
Organization Type | enum | Publisher class from the catalog's controlled vocabulary: Federal, City, State, County Government, University, Tribal or Non-Profit. | Federal |
Dataset Last Updated | date | Modified timestamp of the metadata record - the staleness audit for any listing you lean on. | June 19, 2026 |
Accrual Periodicity | string | ISO 8601 frequency code the publisher declares for the record - the monitoring-grade versus baseline-only tell. | R/P3M (quarterly) |
License | string | Reuse designation asserted by the publisher, recorded on the listing's metadata. | <returned in your sample> |
Temporal Coverage | string | Start and end instants describing the period the underlying data covers. | 2019-10-01T11:00:00Z / 2026-06-30T15:13:00Z |
Resource Formats | enum | Distribution formats listed per resource: csv, json, xml, xls, zip, html, kml. | json, xml, csv |
Catalog Last Checked | datetime | Timestamp of the catalog's most recent re-validation of the record - freshness you can read rather than assume. | August 03, 2026 at 12:53 AM |
Harvest Record | string | Handle for the raw harvested metadata document behind each listing - machine-readable metadata without the presentation layer. | <returned in your sample> |
Questions buyers ask
How many datasets does the Data.gov catalog hold?
552,271 listings were displayed as of August 2026, drawn from federal, state, county, city, tribal, university and non-profit publishers. Read the big number as the catalog's scale; the housing slice is the curated subset Datadory maintains, typically hundreds of relevant records per well-phrased query.
Which publishers matter most for single-family rental work?
Four federal bodies dominate the useful end of the housing slice - HUD, the Census Bureau, FHFA and the SEC - with county assessors and city permit offices supplying local ground truth. The Organization and Organization Type fields make the split explicit on every record, so the roster is auditable rather than anecdotal.
Why do irrelevant results appear for housing queries?
Default relevance ranking interleaves trending popular listings regardless of topic: a query for 'housing REIT' surfaces veterans' compensation tables and state EV registries before it reaches anything rentable. Quoted phrases, format facets and organization filters fix most of it; the curated slice removes the rest.
What does a single catalog record contain?
Ten core fields: title, publishing organization, organization type, last-updated date, publisher-declared accrual periodicity, reuse designation, temporal coverage, resource formats, the catalog's own re-check timestamp and the raw-metadata handle. Everything follows the DCAT federal metadata standard, so semantics stay stable across publishers.
Can the slice be cut to specific metros?
Yes. Scope by bounding box with Within or Intersect matching, by publisher, by organization type or by date window, and the extract ships mapped to the same ten-field dictionary - delivered by API, files, or your warehouse, refreshed daily, weekly, or hourly as the workflow needs.
Is it worth buying the catalog slice rather than assembling it?
Assembling it means normalizing hundreds of thousands of DCAT records, taming a relevance ranking that mixes trending noise into housing queries, and auditing per-record staleness yourself. Buying it through Datadory hands you the verified dictionary, cleaned rows and a delivery schedule you set - API, files, or warehouse; daily, weekly or hourly. Teams buy when analyst hours outweigh the feed.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.