VBMP RCL
vector digital data
withheld
The Virginia Geographic Information Network (VGIN) has coordinated the development of a consistent, seamless, statewide digital road centerline file with address, road name, and route number attribution, as part of the Virginia Base Mapping Program (VBMP). The Road Centerline Program (RCL) leverages the Commonwealth's investment in the VBMP digital orthophotography and is focused on creating a single statewide, consistent digital road file. The RCL data layer is a dynamic dataset supported and maintained by Virginia's Local Governments and VGIN. VBMP RCL is extracted and provided back to local governments and state agencies in many geographic data sets every quarter. Please note the following use restrictions: RCL Geometry is public domain; Minimal Attribution is public domain (RCL Public); Geocoding fields are restricted in use (RCL Master) and to acquire these, please contact VGIN.
The ongoing goal of the VBMP is to establish a consistent, seamless base and foundation for local and state government mapping systems (GIS) that will help all increase efficiency and reduce redundant efforts in developing these systems. The seamless VBMP base is critical to the effective and efficient delivery of wireless E-911 and many other government services and is a critical component in the development of spatial data guidelines and standards, supporting the cost-effective sharing of GIS data and expertise across the Commonwealth.
-83.830748
-75.245577
39.446860
36.426422
None
All RCL Geometry is public domain; Minimal RCL Attribution (RCL Public Attribution) is public domain; RCL Geocoding based fields are restricted in use (RCL Master).
ESRI ArcGIS 10.0.2.3200
Vector
Simple
FALSE
0
TRUE
FALSE
coordinate pair
0.0005555555555555553
0.0005555555555555553
Meter
D North American 1983
GRS 1980
6378137.0
298.257222101
See access and use constraints information.
20111011
FGDC Content Standard for Digital Geospatial Metadata
FGDC-STD-001-1998
Bedford Regional Network Dataset - Centerlines
vector digital data
20140306
VGIN Coordinator
VITA
VGIN Coordinator
VGIN RCL Team
VGIN
VGIN RCL Team
2016-09-28T00:00:00
VGIN Coordinator
VITA
VGIN Coordinator
VGIN Coordinator
Esri ArcGIS 13.5.2.57366
1
-81.530129
-81.514595
37.135316
37.122319
002
APPENDIX B Virginia Geographic Information Network (VGIN) Virginia Base Mapping Program (VBMP) Geospatial Data Sharing VGIN was established in 1997 in Virginia Code to "foster the creative utilization of geographic information and oversee the development of a catalog of GIS data available in the Commonwealth". One of the main core functions of VGIN according to the code is: * Provide services, geographic data products, and access to the repository Source: Virginia Code § 2.2-2026 and § 2.2-2027 Commonwealth wide GIS data initiatives require the active participation by local government entities. Many services and data products are readily available through the Virginia GIS clearinghouse and could not function without local government geospatial data input. These data sets are the source for data sharing between Local, State, Federal, and commercial geospatial entities through VGIN. The following programs or initiatives require the active participation by Virginia Local governments. VBMP Road Centerlines (RCL): The Road Centerline (RCL) dataset provides a consistent and seamless statewide digital dataset of all roads in the Commonwealth of Virginia. The purpose for the continued development of this dataset is to support the base mapping needs of state, regional, and local governments as well as to provide the most accurate representation of centerlines within the Commonwealth to as commercial entities and the general public. The purpose is to achieve a singular, consistent and maintainable base map dataset usable by all entities. The high quality of this product is available for use within a geographic information system (GIS) or a computer aided dispatch (CAD) / 911 system. Address Point data is used to validate the RCL in locations where the RCL data set differs in geometry or attribution than local government centerline data. It is also used in the statewide geocoding web service as a separate locator to provide the end user a more accurate geocoded location. Administrative Boundaries: VGIN is leading an effort to improve Administrative Boundary datasets statewide through its Administrative Boundary Workgroup process. The hope is for the production and maintenance of an improved statewide administrative boundary dataset to be used for GIS purposes. There is also the possibility of streamlining response for statewide boundary updates to US Census. Boundary products that can be provided by localities through the RCL data submission process will help us initially to plan for and produce the best initial statewide dataset as possible and VGIN hopes updated boundary data through the submission process can feed maintenance and updates to a new statewide boundary product as changes warrant. Cadastral: Cadastral data (land ownership and tax parcels) comprise one of seven framework data layers identified in the National Spatial Data Infrastructurei. Parcel data is the responsibility of local governmental jurisdictions in the Commonwealth of Virginia. Over the past several decades local governments have been transitioning from paper maps to digital systems for maintaining parcel data. Most follow similar, but not identical systems, for mapping and identifying tax parcels. The framework initiative action team will work to improve the standardization and the quality of the cadastral framework data by adopting standards and best practices, and promoting cooperation, collaboration, and data sharing. The team will also assess the potential for compiling a statewide database of parcel data, similar to the road centerline program. VGIN would like to formally request the GIS data below from your locality. Based on your locality’s data update cycle, you can provide GIS data updates to VGIN Monthly, Quarterly, Bi-Annually, or Annually. Please indicate the GIS data layers you are sharing with the Commonwealth of Virginia, file format, and data transfer method. Jurisdiction: Jurisdiction Name Submitted Geospatial Data Layers: Jurisdiction Road Centerlines (RCL) Jurisdiction Address Points Jurisdiction Building Footprints Jurisdiction Cadastral data (Parcels) Jurisdiction Boundary Jurisdiction Town Boundaries (If applicable) Jurisdiction Hydrography Submitted Data Format: ESRI Shapefile ESRI Geodatabase (Personal or File) Submitted Delivery method: VGIN FTP Virginia Geospatial Clearinghouse Locality FTP Server i Executive Order 12906, published in the April 13, 1994, edition of the Federal Register, Volume 59, Number 71, pp. 17671-17674; and amended by Executive Order 13286, published in the March 5, 2003, edition of the Federal Register, Volume 68, Number 43, pp. 10619-10633. Framework layers are detailed in OMB Circular A-16. http://www.whitehouse.gov/omb/circulars/a016/a016_rev.html#4#4
VGIN Coordinator
VITA
VGIN Coordinator
Joe Sewash
VITA
VGIN Coordinator
VGIN Coordinator
ItemDescription
1.0
Bedford_Centerline_NetworkDataset
002
-180361.890600
-179012.197800
126547.332800
127960.491700
1
Projected
GCS_North_American_1983
Linear Unit: Meter (1.000000)
NAD_1983_Virginia_Lambert
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>PROJCS["NAD_1983_Virginia_Lambert",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-79.5],PARAMETER["Standard_Parallel_1",37.0],PARAMETER["Standard_Parallel_2",39.5],PARAMETER["Latitude_Of_Origin",36.0],UNIT["Meter",1.0],AUTHORITY["EPSG",3968]]</WKT><XOrigin>-37232800</XOrigin><YOrigin>-28884600</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>3968</WKID><LatestWKID>3968</LatestWKID></ProjectedCoordinateSystem>
20251120
14534600
20260111
16490600
FALSE
150000000
5000
20260111
16454100
2017-12-26T00:00:00
The descriptions used for lineage are to represent basic functions in maintenance and preparation of data. Database is housed in a SQL server in conjunction with SDE. All deltas, QC, and geoprocessing are done in separate file and personal database environments and changes are applied to RCL master database as needed.
Miscellaneous data processing: - SPEED
- ONE_WAY
- GEOMETRY_SOURCE
- EDIT_TYPE
ONE_WAY field populated for the purpose of providing direction of travel for each segment. This field is only provided as a reference and should be reviewed by locality for accuracy. CODED VALUES:
BOTH Bi-Directionality, FT FromTO: With Segment Directionality, TF TOFrom: Against Segment Directionality
2016-09-28T00:00:00
RCL post process geoprocessing model was run for ZIP_LEFT and ZIP_RIGHT. Fields were calculated by using VGIN's custom zip code polygon boundary and using select by location using the centroid of the line segment within the polygon boundary.
2016-09-28T00:00:00
VGIN RCL Team
VGIN
*For data processing details, use the following:
http://vgin.maps.arcgis.com/apps/MapSeries/index.html?appid=b97798fb24cb430388efc38f6e80baad
2016-09-28T00:00:00
RCL_ID values that were 0 or duplicates were calculated based on a post processing script. This processing routine is run as needed. MFIPS values that were NULL or miscalculated during editing process were assigned FIPS codes from the Provider Management Boundary (PMB) using a geoprocessing model. The location of the line segment centroid determined the FIPS assignment.
2016-09-28T00:00:00
VDOT attribute table was received 2012/08/01 – Data Process Completed – 2012/08/01 and updated from VDOT in August of 2012. No further update has been recieved. VDOT attribute table was received 2013/08/01 - VGIN RCL Team has looked at the received attribute table. You will be seeing changes in this release. VDOT attribute table was received 2013/12/01 - VGIN RCL Team has looked at the received attribute table. You will be seeing changes in this release. VDOT attribute table was received 2014/01/01 - VGIN RCL Team has looked at the received attribute table. You will be seeing changes in this release.
VDOT attribute table was received 2015/08/18 - VGIN RCL Team has looked at the received attribute table. You will be seeing changes in this release. VDOT attribute table was received 2016/10/14 - VGIN RCL Team has looked at the received attribute table. You will be seeing changes in this release.
2016-09-28T00:00:00
File Geodatabase Feature Class
ArcGIS 10.1
dataset
EPSG
7.1(10.0.0)
0
20260111
VGIN Coordinator
VITA
VGIN Coordinator - VBMP@vita.virginia.gov
Bedford_Centerline_NetworkDataset
Feature Class
0
OBJECTID
OBJECTID
OID
4
0
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Shape
Shape
Geometry
0
0
0
Feature geometry.
Esri
Coordinates defining the features.
RCL_ID
RCL_ID
Double
8
0
0
LOCAL_ID
LOCAL_ID
Double
8
0
0
VDOT_EDGE_ID
VDOT_EDGE_ID
Double
8
0
0
MFIPS
MFIPS
String
7
0
0
GEOMETRY_EDIT_TYPE
GEOMETRY_EDIT_TYPE
SmallInteger
2
0
0
GEOMETRY_EFFECTIVE_DATE
GEOMETRY_EFFECTIVE_DATE
Date
8
0
0
GEOMETRY_SOURCE
GEOMETRY_SOURCE
String
4
0
0
GEOMETRY_EDIT_DATE
GEOMETRY_EDIT_DATE
Date
8
0
0
LEFT_FROM_ADDRESS
LEFT_FROM_ADDRESS
Integer
4
0
0
LEFT_TO_ADDRESS
LEFT_TO_ADDRESS
Integer
4
0
0
RIGHT_FROM_ADDRESS
RIGHT_FROM_ADDRESS
Integer
4
0
0
RIGHT_TO_ADDRESS
RIGHT_TO_ADDRESS
Integer
4
0
0
ADDRESS_RANGE_FORMAT
ADDRESS_RANGE_FORMAT
String
1
0
0
ADDRESS_RANGE_SOURCE
ADDRESS_RANGE_SOURCE
String
4
0
0
ADDRESS_RANGE_EDIT_DATE
ADDRESS_RANGE_EDIT_DATE
Date
8
0
0
STREET_PREMODIFIER
STREET_PREMODIFIER
String
10
0
0
STREET_PREFIX_DIRECTION
STREET_PREFIX_DIRECTION
String
2
0
0
STREET_NAME
STREET_NAME
String
75
0
0
STREET_SUFFIX
STREET_SUFFIX
String
4
0
0
STREET_SUFFIX_DIRECTION
STREET_SUFFIX_DIRECTION
String
2
0
0
STREET_POSTMODIFIER
STREET_POSTMODIFIER
String
10
0
0
STREET_NAME_FULL
STREET_NAME_FULL
String
100
0
0
STREET_NAME_SOURCE
STREET_NAME_SOURCE
String
4
0
0
STREET_NAME_EDIT_DATE
STREET_NAME_EDIT_DATE
Date
8
0
0
MTFCC
MTFCC
String
10
0
0
SEGMENT_TYPE
SEGMENT_TYPE
SmallInteger
2
0
0
LOCAL_SPEED_MPH
LOCAL_SPEED_MPH
SmallInteger
2
0
0
DUAL_CARRIAGEWAY
DUAL_CARRIAGEWAY
String
1
0
0
ONE_WAY
ONE_WAY
String
2
0
0
REVERSIBLE
REVERSIBLE
String
1
0
0
SEGMENT_EXISTS
SEGMENT_EXISTS
String
1
0
0
Shape_Length
Shape_Length
Double
8
0
0
Length of feature in internal units.
Esri
Positive real numbers that are automatically generated.
MINUTES
MINUTES
Double
8
0
0