Residential Neighborhoods
Dataset
Description
Residential neighborhoods are geographical areas considered to have similarities in their demographics and housing. Other factors influencing the definition of neighborhoods include local government planning, law enforcement, and transportation. Their use is not consistent across counties. Up to four levels of a neighborhood can be defined. These levels can be identified by the geography type key assigned.
Geo ID | 42,63365 : 0269069ca0c50e87ea417470c14ee63f |
Name | Cypress Village |
Label | Cypress Village, Irvine, Orange County, CA |
Functional Type | Mixed-Use : Planned Community |
Area (sq. miles) | 1.14 |
Longitude | -117.754179 |
Latitude | 33.683861 |
Geocodes
Being area data, each residential neighborhood is geocoded. See Matching Properties to Boundaries
Geography Types
Up to four levels of residential neighborhoods can be defined (see Neighborhood Boundaries). The level can be identified based on the value of GeographyTypeKey
GeographyTypeKey | Description | Abbreviation |
41 | Macro-Neighborhood | N1 |
42 | Neighborhood | N2 |
43 | Sub-Neighborhood | N3 |
44 | Residential Subdivision | N4 |
Geography Key
Each neighborhood is assigned a geography key. The geography key is an integer, unique to a neighborhood of a specific geography type. Both the geography type key and geography key must be combined to uniquely identify a neighborhood. To establish the geography key for a specific property use the PropertyBoundaryMatch table (see below), providing the appropriate value of GeographyTypeKey for the level of the neighborhood being sought.
Note: Properties are not always located within neighborhoods at every level. Some properties, especially in rural areas, may not be located within any neighborhood.
GeoID
A 32-character GeoId (GeoIDV4) uniquely identifies a neighborhood. The GeoId is unique to all boundaries. The GeoId assigned to a neighborhood can be determined from the DimNeighborhood table. This can be done by using PropertyBoundaryMatch to match a property to a neighborhood, or by matching a neighborhood in DimNeighborhood based on the description of the neighborhood.
Tables/Views
The following tables can be used to access neighborhood information. When delivering solutions to customers, some or all of the information found in these tables may be consolidated into one or more views.
DimNeighborhood
Profile for each residential neighborhood, including Macro Neighborhoods, Neighborhoods, Sub-Neighborhoods, and Residential SubdivisionsA register of US census blocks, including their size and location.
Rows: 11.2 million
Columns: 23
Family: Boundary
Type: Area
Geography Type: 41-44 (See above)
PropertyBoundaryMatch
Matches properties (ATTOM ID) to boundaries. The PropertyBoundaryMatch table can be used to:
- Identify the neighborhood for a specific property; and
- Get a list of the properties that fall within a neighborhood
ATTOM ID | 145695081 |
GeographyTypeKey | 41 |
GeographyKey | 17206803 |
PropertyBoundaryMatchMacroNeighborhood
A subset of PropertyBoundaryMatch that is used to access Macro Neighborhoods only. This view is provided when a subset of boundaries has been purchased.
PropertyBoundaryMatchNeighborhood
A subset of PropertyBoundaryMatch that is used to access Neighborhoods only. This view is provided when a subset of boundaries has been purchased.
PropertyBoundaryMatchResidentialSubdivision
A subset of PropertyBoundaryMatch that is used to access Residential Subdivision only. This view is provided when a subset of boundaries has been purchased.
PropertyBoundaryMatchSubNeighborhood
A subset of PropertyBoundaryMatch that is used to access Sub-Neighborhoods only. This view is provided when a subset of boundaries has been purchased.
Dimension Tables
The following dimension tables provide lookups for various codes contained in the tables/views used by this dataset.
DimGeographyType: The complete list of geography types used as boundaries as well as the dimension table used to provide details about each boundary
Examples
Macro Neighborhood Demographics for a Property
The following example demonstrates how to establish the Macro Neighborhood for a property and then obtain the demographics for that neighborhood
/* * Macro Neighborhood demographics for a specific property. * Demonstrates how to match properties to Macro Neighborhood data such as demographics */ SELECT -- Property Details pa.[ATTOM ID], CONCAT(pa.SitusAddress,', ',pa.SitusCity,' ',pa.SitusState,' ',pa.SitusZip) AS Address, -- Macro Neighbiorhood dt.Label, dt.AreaSquareMiles, -- Demographic data cd.Population, cd.Households From adw.PropertyAddresses pa -- Addresses Left Join adw.PropertyBoundaryMatch pbm on pa.[ATTOM ID] = pbm.[ATTOM ID] -- Geocodes Left Join adw.CommunityDemographics cd on pbm.GeographyKey = cd.GeographyKey And pbm.GeographyTypeKey = cd.GeographyTypeKey-- Demographics Left Join adw.DimNeighborhood dt on pbm.GeographyKey = dt.NeighborhoodKey And dt.GeographyTypeKey = cd.GeographyTypeKey -- Neighborhood Where pa.[ATTOM ID] = 156293872 And -- Specific Property pbm.GeographyTypeKey = 41 -- Macro Neighborhood