Description: Shoreline for inventories published prior to 2015 were digitized along the land-water interface. Beginning in 2015, the inventory shoreline was digitized along the upland interface with water, marsh, or beach. To create a water interface shoreline for the post 2015 inventories, the upland shoreline was combined with the outlines of the Tidal Marsh Inventory polygons to produce a mapped shoreline that represents the boundary between the water and the upland, or the water and the marsh. This shoreline dataset is the result of combining the most recent digital water interface shoreline from inventories for Virginia.
Description: Following other social vulnerability indexes, including the SoVI® developed by the Hazards & Vulnerability Research Institute at the University of South Carolina, this vulnerability index is based on a principal component analysis (PCA). PCA is a statistical technique that takes as its input a matrix of interrelated socioeconomic variables – in this case those considered to measure various dimensions of social vulnerability – and creates a new set of orthogonal principal components that extract the important variation the underlying input data while reducing the noise and redundancy in the data. After conducting the PCA, the researcher combines the newly created component variables into a composite index that provides a single value for each observation in the dataset, in this case a social vulnerability score. The utility of a PCA-based index is that it encapsulates a lot of information in an easily consumed form and individual observations can be ranked relative to each other. This update uses data from the 2015-2019 American Community Survey at the census block group level where available and at the census tract level where block group data is not available. It is an update of the Social Vulnerability Index on the Adapt VA Portal and uses the same or similar variables to the ones used in that analysis. These variables, shown in the next table, are those that we consider to be the most direct determinants of social vulnerability. VariableDescriptionBlock Group or Tract LevelIncomePer capita income Block GroupBlackPercent of population that is Black or African AmericanBlock GroupHispanicPercent of population that is HispanicBlock GroupNativePercent of population that is Native AmericanBlock GroupOver 65Percent of population that is over 65 years of ageBlock GroupUnemployedPercent of civilian labor force 16 and over that is unemployedBlock GroupPovertyPercent of population for whom poverty status is established that is living in povertyTractNo High SchoolPercent of population 25 and older with no high school degree or equivalentBlock GroupGroup QuartersPercent of population in group quarters including nursing homes and prisonsTractFemale Labor ForcePercent of females 16 and over in civilian labor forceTractFemale HouseholdsPercent of households with female head, no spouseBlock GroupSocial SecurityPercent of households with social security incomeBlock GroupBefore conducting the PCA, the variables were first standardized to z-scores with zero means and unit variances to avoid any confounding effects that might arise from using variables of different magnitudes in the analysis. We then conducted a PCA, keeping those components with eigenvalues greater than 1 (the Kaiser selection criterion). As a next step, we conducted a Varimax rotation of the components to facilitate interpretation of each component because – as is the case with all PCA-based indices – the researcher must determine the directionality of each retained component, that is whether higher values of the component increase the level of social vulnerability (positive directionality) or decrease the level of social vulnerability (negative directionality). Where the directionality of the component was clearly negative, we scaled the component by a factor of -1 before including it in the composite index so that higher values of the scaledcomponent would increase the overall vulnerability index. As is common in the literature, in instances when the effect of the component on vulnerability is ambiguous (as is the case when the different variables that make up the component work in opposite ways), we assume a positive directionality. Each component is then multiplied by the variance it captures from the total input matrix and the weighted components are added together to form the index. To ensure that the index can be compared to other indices, the resulting aggregated values to z-scores with zero means and unit variances. Since all values of the index are relative, it can be used to rank observations relative to each other in terms of vulnerability. However, many studies also identify a group of “highly vulnerable” observations – that is those observations whose standardized index score exceeds a threshold value of 1 (i.e., whose value is one standard deviation above the mean value of the index). We note that vulnerability indices depend on the variables included in the PCA as well as the geographic area of the study and the component selection and weighting criteria. Thus our vulnerability index will not necessarily match the vulnerability indices created by other researchers.The TIGER/Line shapefiles and related database files (.dbf) 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 shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 5001, 5002, 5005,.., 5999 within census tract 1210.02 are also within BG 5 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 5,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, 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.
Copyright Text: U.S. Census Bureau, 2015-2019 American Community Survey, William & Mary
Description: Shoreline for inventories published prior to 2015 were digitized along the land-water interface. Beginning in 2015, the inventory shoreline was digitized along the upland interface with water, marsh, or beach. To create a water interface shoreline for the post 2015 inventories, the upland shoreline was combined with the outlines of the Tidal Marsh Inventory polygons to produce a mapped shoreline that represents the boundary between the water and the upland, or the water and the marsh. This shoreline dataset is the result of combining the most recent digital water interface shoreline from inventories for Virginia.
Description: The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.
Copyright Text: Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project