Northwest Hills Planning Region, Connecticut

No Census ZCTA-to-tract crosswalk rows are loaded for this county, so its tracts cannot be grouped into ZIP areas. The census-tract table below is the complete sub-county view.

The most recent fiscal year is partial until VA closes it. This file carries no lender key, so VA volume cannot be attributed to a company.

ALSO CHECKED

22 more data areas were checked for Northwest Hills Planning Region and did not earn a tab. A missing tab and an unasked question look the same on screen, so each one is named with the reason it is missing.

• WRONG GRAIN
  FHA

  FHA Neighborhood Watch DOES publish county rows, but keys them on a free-text county NAME (“CHITTENDEN|VT”), not a FIPS code, and the single-family endorsement snapshot's property_county is likewise free text. Joining either to a county FIPS by name would attribute one county's delinquency to another wherever a name repeats, so FHA is a state-grain tab only until a curated name→FIPS crosswalk exists

• WRONG GRAIN
  Fannie / Freddie

  the FHFA public-use database publishes single-family acquisitions at STATE and CENSUS-TRACT grain; no county rollup is published or loaded, and rolling tracts up to counties would double-count the tracts that straddle a county line

• WRONG GRAIN
  GSE credit-risk transfer

  CAS and STACR loan-level disclosures publish PROPERTY STATE and a 3-digit zip; neither carries a county code, so credit-risk-transfer collateral cannot be attributed to a county

• WRONG GRAIN
  Ginnie Mae

  Ginnie Mae's loan-level disclosure publishes PROPERTY STATE and nothing finer — there is no county, ZIP or tract field in the file, so agency-pool collateral has no county grain at all. The same is true of the UMBS pool file (fhfa_mbs_pool), which carries only CA/NY/FL/TX/PR concentration percentages

• WRONG GRAIN
  Housing finance agency

  a housing finance agency is a STATE-chartered body — county is not a grain it has. Its programmes reach counties, but the agency itself is one row per state: hfa_agency is keyed on state_code and carries no county column, and there is no county-level agency underneath it to aggregate from

• WRONG GRAIN
  CUSO network

  the NCUA CUSO Registry publishes a CUSO's city and STATE and no county at all (cuso_registry, migration 0195). A county FIPS does exist on the member-credit-union side (cuso_credit_union_link.cu_county_fips), but it is the CREDIT UNION'S CHARTER ADDRESS — where the institution is registered, not where the mortgage service it buys is delivered — so a county tab built on it would pin a statewide, often multi-state, service relationship onto the one county a charter document happens to name

• WRONG GRAIN
  Subservicing map

  the same absence, one grain finer: subservicing_relationships holds no property or collateral column at all, so there is nothing to aggregate to a county. Where a client is a state HFA, the state housing finance agency area on this hub carries that agency and its named master servicer at its own state grain

• WRONG GRAIN
  Co-issue MSR

  the same absence, and worse at county grain: Ginnie's loan-level disclosure publishes property STATE and nothing finer — no county, ZIP or tract field exists in the file — so even the collateral split that is rejected above at state grain is not available here at all

• WRONG GRAIN
  MSR transfer graph

  the same absence at a finer grain, with no additional route to one: ginnie_servicing_transfers has no county column and the Ginnie loan-level disclosure it would have to be joined to publishes property state and nothing finer — no county, ZIP or tract field exists in either file

• WRONG GRAIN
  Builder & realtor JV

  the same absence, one grain finer: the affiliation corpus has no geographic column at all, so nothing can be aggregated to a county. The affiliate lender's actual county-level originations are on the HMDA area of the county hub, keyed on the lender rather than on its parent

• WRONG GRAIN
  Non-QM deal calendar

  the same structural gap, one grain finer: a 144A non-QM deal publishes no asset-level file at all, so there is no loan, no property and therefore no county to attribute anything to. This is the one absence on this hub that no future load can close

• WRONG GRAIN
  Agency-MBS demand

  the same absence, and Ginnie's disclosure has no county field at any grain, so even the collateral allocation that is rejected above at state grain cannot be computed here

• WRONG GRAIN
  Complaints-rate stack

  the same broken denominator, plus a numerator that does not reach county either: the CFPB publishes a complaint's state and a partially redacted ZIP and no county, so neither half of this ratio exists at county grain

• WRONG GRAIN
  NMLS licensing

  NMLS licences are issued by a STATE regulator and the industry report is published by state agency and quarter; there is no county in the licensing system to aggregate to

• WRONG GRAIN
  CFPB complaints

  the CFPB publishes a complaint's STATE and a partially redacted ZIP; it publishes no county, and deriving one from a redacted ZIP would put complaints in the wrong county wherever a ZIP straddles a county line

• WRONG GRAIN
  State enforcement

  enforcement orders are issued by a STATE regulator against a licensee; they carry no property or county

• WRONG GRAIN
  WARN notices

  a WARN notice names an employer, a CITY and a region — no county code — and matching city to county by name is ambiguous in most states

• WRONG GRAIN
  Mortgage employment

  the QCEW extract loaded here holds STATE and METRO area types only — the county-level QCEW file is a separate, far larger download that is not loaded, so county mortgage employment cannot be shown honestly

• NONE HERE
  Disasters

  no FEMA declaration designates this county

  FEMA disaster declarations at their county designation grain (fema_disaster_declarations, county_fips)

• NONE HERE
  Valuations & Market

  neither Zillow nor Redfin holds published market data for this county FIPS

  Zillow and Redfin county-month metrics (zillow_county_month, redfin_county_month, geoid)

• NONE HERE
  UAD Appraisals

  neither FHFA UAD aggregate statistics nor the public use file holds data for this county FIPS

  FHFA UAD aggregate statistics (uad_aggregate_county, geoid) and appraisal-level public use file (uad_puf, county_fips)

• NONE HERE
  NFIP Flood Claims

  no FEMA NFIP claims are recorded for this county FIPS

  FEMA NFIP redacted claims (nfip_claim, county_code)