File Geodatabase Feature Class
Tags
Virginia, administrative, boundary, boundaries, Nation, Polygon
VA_TOWN is a feature class representing town boundaries in the Commonwealth of Virginia. This dataset was derived from Census TIGER data supplemented with locality data made available from the towns involved or the counties containing the towns.
The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_TOWN represents the best available town 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 an extraction of town features 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_TOWN feature class where locality data were a superior representation of town boundaries.
Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project
The VA_TOWN feature class is not an official boundary description and shall not be used as one. Best efforts were undertaken to ensure the correctness of Administrative Boundary data by using the best source available throughout the Commonwealth of Virginia, however, all warranties regarding the accuracy of the map data and any representation or inferences derived there from are hereby expressly disclaimed.
Extent
West | -83.260079 | East | -75.186895 |
North | 39.300237 | South | 36.468652 |
Maximum (zoomed in) | 1:5,000 |
Minimum (zoomed out) | 1:150,000,000 |
Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project
The VA_TOWN feature class is not an official boundary description and shall not be used as one. Best efforts were undertaken to ensure the correctness of Administrative Boundary data by using the best source available throughout the Commonwealth of Virginia, however, all warranties regarding the accuracy of the map data and any representation or inferences derived there from are hereby expressly disclaimed.
VA_TOWN is stored with polygon edges to the center of hydrographic features. It is published using best available authoritative shoreline data.
Data Editing
Local government polygon information is acquired and subsequently used in updating the VA_COUNTY feature class in specified areas.
Polygon Clip
Data was clipped using VIMS shoreline data. The feature class "Virginia Tidal Waters: Chesapeake Bay, Tributaries, and Oceanside" (Alternate title: Virginia Shoreline Inventory Shoreline) for 2014 was supplied by VIMS and used by VGIN.
Field Calculation
Current County and Equivalent National
U.S. Census Bureau
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Feature geometry.
Esri
Coordinates defining the features.
Concatenated TIGER FIPS value for STATEFP & PLACEFP fields
VGIN
Value of GNIS feature based on GNIS database
Current county name
U.S. Census Bureau
Current name and the translated legal/statistical area description for county
U.S. Census Bureau
Geometry Source used when updating the Administratibe Boundary layer
VGIN
Y/N Character field describing use of local government boundary information
VGIN
Calculated Geometry using square miles on the VA Lambert projection
VGIN
Autopopulated by edit tracking function within ArcGIS
VGIN
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
Area of feature in internal units squared.
Esri
Positive real numbers that are automatically generated.
The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_TOWN represents the best available town 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 an extraction of town features 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_TOWN feature class where locality data were a superior representation of town boundaries.
VA_TOWN is a feature class representing town boundaries in the Commonwealth of Virginia. This dataset was derived from Census TIGER data supplemented with locality data made available from the towns involved or the counties containing the towns.
Publication Date
None
The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source.
The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.
Accurate against Federal Information Processing Series (FIPS), FIPS Publication 6-4, and FIPS-55 at the 100% level for the codes and base names. The remaining attribute information has been examined but has not been fully tested for accuracy.
The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. All polygons are tested for closure.
The Census Bureau uses its internally developed geographic update system to enhance and modify spatial and attribute data in the Census MAF/TIGER database. Standard geographic codes, such as FIPS codes for states, counties, municipalities, county subdivisions, places, American Indian/Alaska Native/Native Hawaiian areas, and congressional districts are used when encoding spatial entities. The Census Bureau performed spatial data tests for logical consistency of the codes during the compilation of the original Census MAF/TIGER database files. Most of the codes for geographic entities except states, counties, urban areas, Core Based Statistical Areas (CBSAs), American Indian Areas (AIAs), and congressional districts were provided to the Census Bureau by the USGS, the agency responsible for maintaining FIPS 55. Feature attribute information has been examined but has not been fully tested for consistency.
For the TIGER/Line Shapefiles, the Point and Vector Object Count for the G-polygon SDTS Point and Vector Object Type reflects the number of records in the shapefile attribute table. For multi-polygon features, only one attribute record exists for each multi-polygon rather than one attribute record per individual G-polygon component of the multi-polygon feature. TIGER/Line Shapefile multi-polygons are an exception to the G-polygon object type classification. Therefore, when multi-polygons exist in a shapefile, the object count will be less than the actual number of G-polygons.
Data completeness of the TIGER/Line Shapefiles reflects the contents of the Census MAF/TIGER database at the time the TIGER/Line Shapefiles were created.
All line segments
TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for all of the aforementioned geographic entities are then distributed among the shapefiles each containing attributes for line, polygon, or landmark geographic data.
No warranty, expressed or implied is made with regard to the accuracy of these data, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau in specific as to the spatial or attribute accuracy of the data. The act of distribution shall not constitute any such warranty and no responsibility is assumed by the U.S. government in the use of these files. The boundary information in the TIGER/Line Shapefiles is for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes do not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.
To obtain more information about ordering TIGER/Line Shapefiles visit http://www.census.gov/geo/www/tiger