Description: Geographic boundary, portraying extent and limits of land recognized as Fairfax County, Commonwealth of Virginia. Defined in part by both physical features (Potomac and Occoquan Rivers), and monumented legal boundaries for surrounding jurisdictions (State of Maryland, Arlington, Loudoun, and Prince William Counties, cities of Alexandria and Falls Church).
Copyright Text: The shared efforts of the USGS, NGS and Fairfax County DPW&ES/Surveys branch for verification and upkeep of the actual ground monuments, Fairfax County GIS staff and contractors for portrayal and review of the data.
Description: The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.
Description: The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.
JURISDICTION
(
type: esriFieldTypeString, alias: JURISDICTION, length: 20
,
Coded Values:
[FAIRFAX COUNTY: FAIRFAX COUNTY]
,
[TOWN OF VIENNA: TOWN OF VIENNA]
,
[TOWN OF HERNDON: TOWN OF HERNDON]
)
Description: This layer contains cadastral information for Fairfax County, Virginia. This includes, but is not limited to the portrayal of polygonal features (such as parcels, subdivisions and easements), text (parcel numbers, street names and addresses), and symbols (parkland, schools, "double circles", etc.). This layer was initially developed as a digital copy of the ink-on-mylar property maps maintained by the County since the early 1960's.
Copyright Text: The data set was created by Analytical Surveys Incorporated (ASI) and Landata under contract to Fairfax County. Quality control checks were performed by Engineering Systems Incorporated and Dewberry and Davis. Staff from the GIS branch were also used for quality control checking. Since 2001 Fairfax County staff have been solely responsible for maintaining this data.
Description: The Volunteer Groups (also known as Community Based Organizations) are non-profit organizations that provide basic needs assistance to specific areas of the county. The groups work together to define their boundaries, often utilizing ZIP code boundaries for their edges. Some of the service areas overlap.Contact: Neighborhood and Community Services Fairfax County (https://www.fairfaxcounty.gov/neighborhood-community-services)Data Availability: Publicly availableUpdate Frequency: As neededPublication Date: 11/26/2018
Copyright Text: Fairfax County GIS and Mapping Services, and Neighborhood and Community Services
Description: This layer depicts planned land use at the baseline level. Refer to the Comprehensive Plan text for interpretation and for options above the baseline level.This layer has been updated to include Amendment 2013-25, adopted by the BOS July 29, 2015 and all previous amendments.
Copyright Text: This layer was maintained by conventional cartographic methods from June 1976 until the August 2004 delivery of a digital layer prepared by contractor Baker Corporation. That digital layer has subsequently been maintained by DPZ staff, and exists currently as this SDE layer.