Layers:

Layer: VDOT_PSI_Intersections_SmartScale_2016 (0)

Name: VDOT_PSI_Intersections_SmartScale_2016

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: ***Update: Project locations with a documented safety or geometric concern, such as those locations identified in a Regional Long Range Plan, Roadway Safety Assessment, corridor or project planning, scoping or design reports, will also be considered to address a safety need for the initial HB2 screening purposes. Introduction: This map shows approximately 100 fatal and injury crash miles (of highway segments) and 100 fatal and injury intersections in each VDOT district with Potential for Safety Improvements (PSI). The PSI measure compares the "predicted" number of crashes (for a given traffic volume and roadway type) to the observed number of crashes. The Virginia Department of Transportation uses PSI scoring to identify the greatest roadway safety needs in each VDOT district. The high PSI locations for fatalities and injuries (all injury types), shown on the map for 2010-2012, are expected to play a screening role in the HB 2 project development and evaluation process. Each segment and intersection contains various data and PSI ranks by district (1 = most severe) for 2010-2012, which are defined below:-TotalCrash - total crashes -FatalInjurCrash - total fatalities and injuries (all injury types) -RankbyTotalCrashes - PSI rank by VDOT district (all crashes)-RankbyFIPSI - PSI rank by VDOT district (fatalities and injuries)*Please view the Statewide Safety report (found on VTrans website) for additional information on PSI and safety trends.

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9287587.7013
YMin: 4376241.945
XMax: -8431595.9219
YMax: 4776765.8046
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• HTRISNODE ( type: esriFieldTypeDouble, alias: HTRISNODE )
• CONFIG ( type: esriFieldTypeDouble, alias: CONFIG )
• DISTRICT ( type: esriFieldTypeString, alias: DISTRICT, length: 254 )
• PHYSICAL_J ( type: esriFieldTypeString, alias: PHYSICAL_J, length: 254 )
• SYSTEMID1 ( type: esriFieldTypeString, alias: SYSTEMID1, length: 254 )
• SYSTEMID2 ( type: esriFieldTypeString, alias: SYSTEMID2, length: 254 )
• SYSTEMID3 ( type: esriFieldTypeString, alias: SYSTEMID3, length: 254 )
• SYSTEMID4 ( type: esriFieldTypeString, alias: SYSTEMID4, length: 254 )
• AADT1 ( type: esriFieldTypeDouble, alias: AADT1 )
• AADT2 ( type: esriFieldTypeDouble, alias: AADT2 )
• AADT3 ( type: esriFieldTypeDouble, alias: AADT3 )
• AADT4 ( type: esriFieldTypeString, alias: AADT4, length: 254 )
• TOTAL_CRAS ( type: esriFieldTypeDouble, alias: TOTAL_CRAS )
• FATAL_INJU ( type: esriFieldTypeDouble, alias: FATAL_INJU )
• RANK_TOTAL ( type: esriFieldTypeDouble, alias: RANK_TOTAL )
• RANK_FI_PS ( type: esriFieldTypeDouble, alias: RANK_FI_PS )
• LAT ( type: esriFieldTypeDouble, alias: LAT )
• LON ( type: esriFieldTypeDouble, alias: LON )
• ID ( type: esriFieldTypeInteger, alias: ID )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 200 )
• DESC ( type: esriFieldTypeString, alias: DESC, length: 255 )
• NEED_TYPE ( type: esriFieldTypeString, alias: NEED_TYPE, length: 10 )

Layer: VDOT_EDGE_RTE_LRS_ProjectPortal_2016 (1)

Name: VDOT_EDGE_RTE_LRS_ProjectPortal_2016

Display Field: EDGE_RTE_KEY

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: This feature class consists of approximately 400,000 features representing over 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS). Geometry and Attribution: The Linear Referencing System (LRS) data contained within this feature class provides route centerline geometry that is segmented at each intersection and supplies key descriptive attribution for each segment (i.e. edge) record. The feature class also depicts overlapping routes (e.g. Interstate 64 and Interstate 95) as two separate collinear features, one on top of the other. Routes built in the prime and non-prime directions are included. Each road centerline record has a master route record assigned. In addition, local Virginia Geographic Information Network (VGIN) street names are attributed to each edge where possible. Measures: The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions). Note: The overlap, non-prime measures and street names are for reference only. These measures and street names have not been fully validated for accuracy or completeness.

Copyright Text: This data was created as part of a joint effort between the Geographic Information System Program Office and the Roadway Network System Program, both contained under the Information Technology Division of the Virginia Department of Transportation. It also includes street names from the Virginia Geographic Information Network Master Centerlines. © Copyright 2015 Virginia Department of Transportation - All Rights Reserved

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9312577.8338
YMin: 4369590.830799997
XMax: -8387306.6602
YMax: 4785025.195
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [104, 0, 133, 255]
Width: 1
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• EDGE_RTE_KEY ( type: esriFieldTypeString, alias: EDGE_RTE_KEY, length: 100 )
• RTE_NM ( type: esriFieldTypeString, alias: RTE_NM, length: 60 )
• RTE_COMMON_NM ( type: esriFieldTypeString, alias: RTE_COMMON_NM, length: 60 )
• STREET_NM ( type: esriFieldTypeString, alias: STREET_NM, length: 100 )
• RTE_SOURCE_ID ( type: esriFieldTypeString, alias: RTE_SOURCE_ID, length: 60 )
• RTE_SOURCE_CD ( type: esriFieldTypeString, alias: RTE_SOURCE_CD, length: 6 )
• RTE_TRANSPORT_EDGE_SEQ ( type: esriFieldTypeDouble, alias: RTE_TRANSPORT_EDGE_SEQ )
• TRANSPORT_EDGE_ID ( type: esriFieldTypeInteger, alias: TRANSPORT_EDGE_ID )
• TRANSPORT_EDGE_FLIP_IND ( type: esriFieldTypeString, alias: TRANSPORT_EDGE_FLIP_IND, length: 1 )
• TRANSPORT_JUNCTION_FROM_ID ( type: esriFieldTypeDouble, alias: TRANSPORT_JUNCTION_FROM_ID )
• TRANSPORT_JUNCTION_TO_ID ( type: esriFieldTypeDouble, alias: TRANSPORT_JUNCTION_TO_ID )
• MEASURE_SYSTEM_CD ( type: esriFieldTypeString, alias: MEASURE_SYSTEM_CD, length: 5 )
• TRANSPORT_EDGE_FROM_MSR ( type: esriFieldTypeDouble, alias: TRANSPORT_EDGE_FROM_MSR )
• TRANSPORT_EDGE_TO_MSR ( type: esriFieldTypeDouble, alias: TRANSPORT_EDGE_TO_MSR )
• FROM_INTERSECTION_ID ( type: esriFieldTypeDouble, alias: FROM_INTERSECTION_ID )
• TO_INTERSECTION_ID ( type: esriFieldTypeDouble, alias: TO_INTERSECTION_ID )
• RTE_INTERSECTION_FROM_DSC ( type: esriFieldTypeString, alias: RTE_INTERSECTION_FROM_DSC, length: 150 )
• RTE_INTERSECTION_TO_DSC ( type: esriFieldTypeString, alias: RTE_INTERSECTION_TO_DSC, length: 150 )
• RTE_CATEGORY_NM ( type: esriFieldTypeString, alias: RTE_CATEGORY_NM, length: 60 )
• RTE_JURIS_PROPER_NM ( type: esriFieldTypeString, alias: RTE_JURIS_PROPER_NM, length: 60 )
• RTE_NBR ( type: esriFieldTypeInteger, alias: RTE_NBR )
• RTE_TYPE_NM ( type: esriFieldTypeString, alias: RTE_TYPE_NM, length: 60 )
• RTE_TYPE_MODIFIER_NM ( type: esriFieldTypeString, alias: RTE_TYPE_MODIFIER_NM, length: 60 )
• RTE_TYPE_MODIFIER_SEQ ( type: esriFieldTypeSmallInteger, alias: RTE_TYPE_MODIFIER_SEQ )
• RTE_SPCL_FEATURE_TYPE_CD ( type: esriFieldTypeString, alias: RTE_SPCL_FEATURE_TYPE_CD, length: 3 )
• RTE_SPCL_FEATURE_NBR ( type: esriFieldTypeSingle, alias: RTE_SPCL_FEATURE_NBR )
• RTE_RAMP_CD ( type: esriFieldTypeString, alias: RTE_RAMP_CD, length: 3 )
• RTE_CATEGORY_SET_CD ( type: esriFieldTypeString, alias: RTE_CATEGORY_SET_CD, length: 2 )
• FROM_JURISDICTION_NM ( type: esriFieldTypeString, alias: FROM_JURISDICTION_NM, length: 100 )
• TO_JURISDICTION_NM ( type: esriFieldTypeString, alias: TO_JURISDICTION_NM, length: 100 )
• FROM_JURISDICTION_CD ( type: esriFieldTypeString, alias: FROM_JURISDICTION_CD, length: 3 )
• TO_JURISDICTION_CD ( type: esriFieldTypeString, alias: TO_JURISDICTION_CD, length: 3 )
• FROM_STATE_CD ( type: esriFieldTypeString, alias: FROM_STATE_CD, length: 2 )
• TO_STATE_CD ( type: esriFieldTypeString, alias: TO_STATE_CD, length: 2 )
• MASTER_RTE_NM ( type: esriFieldTypeString, alias: MASTER_RTE_NM, length: 60 )
• MASTER_RTE_COMMON_NM ( type: esriFieldTypeString, alias: MASTER_RTE_COMMON_NM, length: 60 )
• MASTER_RTE_SOURCE_ID ( type: esriFieldTypeString, alias: MASTER_RTE_SOURCE_ID, length: 60 )
• RTE_OPPOSITE_DIRECTION_RTE_NM ( type: esriFieldTypeString, alias: RTE_OPPOSITE_DIRECTION_RTE_NM, length: 60 )
• FROM_PHY_JURISDICTION_NM ( type: esriFieldTypeString, alias: FROM_PHY_JURISDICTION_NM, length: 100 )
• TO_PHY_JURISDICTION_NM ( type: esriFieldTypeString, alias: TO_PHY_JURISDICTION_NM, length: 100 )
• FROM_PHY_JURISDICTION_CD ( type: esriFieldTypeString, alias: FROM_PHY_JURISDICTION_CD, length: 3 )
• TO_PHY_JURISDICTION_CD ( type: esriFieldTypeString, alias: TO_PHY_JURISDICTION_CD, length: 3 )
• LRM_CURRENCY_DT ( type: esriFieldTypeDate, alias: LRM_CURRENCY_DT, length: 8 )
• CHANGE_STATUS_CD ( type: esriFieldTypeString, alias: CHANGE_STATUS_CD, length: 2 )
• CHANGE_STATUS_DT ( type: esriFieldTypeDate, alias: CHANGE_STATUS_DT, length: 8 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• SHAPE_Length ( type: esriFieldTypeDouble, alias: SHAPE_Length )

Layer: VDOT_PSI_Segments_SmartScale_2016 (2)

Name: VDOT_PSI_Segments_SmartScale_2016

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: ***Update: Project locations with a documented safety or geometric concern, such as those locations identified in a Regional Long Range Plan, Roadway Safety Assessment, corridor or project planning, scoping or design reports, will also be considered to address a safety need for the initial HB2 screening purposes. Introduction: This map shows approximately 100 fatal and injury crash miles (of highway segments) and 100 fatal and injury intersections in each VDOT district with Potential for Safety Improvements (PSI). The PSI measure compares the "predicted" number of crashes (for a given traffic volume and roadway type) to the observed number of crashes. The Virginia Department of Transportation uses PSI scoring to identify the greatest roadway safety needs in each VDOT district. The high PSI locations for fatalities and injuries (all injury types), shown on the map for 2010-2012, are expected to play a screening role in the HB 2 project development and evaluation process. Each segment and intersection contains various data and PSI ranks by district (1 = most severe) for 2010-2012, which are defined below:-TotalCrash - total crashes -FatalInjurCrash - total fatalities and injuries (all injury types) -RankbyTotalCrashes - PSI rank by VDOT district (all crashes)-RankbyFIPSI - PSI rank by VDOT district (fatalities and injuries)*Please view the Statewide Safety report (found on VTrans website) for additional information on PSI and safety trends.

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9252623.733999997
YMin: 4375990.054500006
XMax: -8457970.353999998
YMax: 4758829.4277000055
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [255, 170, 0, 255]
Width: 2
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• SYSTEMID ( type: esriFieldTypeString, alias: SYSTEMID, length: 254 )
• DISTRICT ( type: esriFieldTypeString, alias: DISTRICT, length: 254 )
• PHY_JUR ( type: esriFieldTypeString, alias: PHY_JUR, length: 254 )
• BEGIN_MP ( type: esriFieldTypeDouble, alias: BEGIN_MP )
• END_MP ( type: esriFieldTypeDouble, alias: END_MP )
• LEN_MI ( type: esriFieldTypeDouble, alias: LEN_MI )
• F2010_12_TO ( type: esriFieldTypeInteger, alias: F2010_12_TO )
• F2010_12_FI ( type: esriFieldTypeInteger, alias: F2010_12_FI )
• RANK_TOT_C ( type: esriFieldTypeInteger, alias: RANK_TOT_C )
• RANK__FI_P ( type: esriFieldTypeInteger, alias: RANK__FI_P )
• ID ( type: esriFieldTypeInteger, alias: ID )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 200 )
• DESC ( type: esriFieldTypeString, alias: DESC, length: 255 )
• Shape_Length ( type: esriFieldTypeDouble, alias: Shape_Length )
• NEED_TYPE ( type: esriFieldTypeString, alias: NEED_TYPE, length: 10 )

Layer: VDOT_Construction_Districts_ProjectPortal_2016 (3)

Name: VDOT_Construction_Districts_ProjectPortal_2016

Display Field: CONST_DIST_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The Virginia Department of Transportation (VDOT) divides the state into nine districts, each of which oversees maintenance and construction on the state-maintained highways, bridges and tunnels in its region. This feature class represents the boundaries for the nine VDOT construction districts as of June 2016.

Copyright Text: VDOT, TMPD

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9314704.5898
YMin: 4375286.3741
XMax: -8367489.268999999
YMax: 4788645.331200004
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [201, 242, 208, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• CONST_DIST_NO ( type: esriFieldTypeString, alias: CONST_DIST_NO, length: 2 )
• CONST_DIST_NAME ( type: esriFieldTypeString, alias: CONST_DIST_NAME, length: 20 )
• CreationDate ( type: esriFieldTypeDate, alias: CreationDate, length: 8 )
• Creator ( type: esriFieldTypeString, alias: Creator, length: 50 )
• EditDate ( type: esriFieldTypeDate, alias: EditDate, length: 8 )
• Editor ( type: esriFieldTypeString, alias: Editor, length: 50 )
• SHAPE_Length ( type: esriFieldTypeDouble, alias: SHAPE_Length )
• SHAPE_Area ( type: esriFieldTypeDouble, alias: SHAPE_Area )

Layer: VDOT_MPO_STUDY_AREA_PojectPortal_2016 (4)

Name: VDOT_MPO_STUDY_AREA_PojectPortal_2016

Display Field: MPO_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: While the earliest beginnings of urban transportation planning go back to the post-World War II years, the federal requirement for urban transportation planning emerged during the early 1960′s. The Federal-Aid Highway Act of 1962 created the federal requirement for urban transportation planning largely in response to the construction of the Interstate Highway System and the planning of routes through and around urban areas,. The Act required, as a condition attached to federal transportation financial assistance, that transportation projects in urbanized areas of 50,000 or more in population be based on a continuing, comprehensive, urban transportation planning process undertaken cooperatively by the states and local governments — the birth of the so-called 3C, “continuing, comprehensive and cooperative planning process. By July, 1965, all the 224 existing urbanized areas had an urban transportation planning process underway. At that time, qualified planning agencies to conduct the transportation planning process were lacking in many urban areas. Therefore, the Bureau of Public Roads (predecessor to the Federal Highway Administration) required the creation of planning agencies or organizational arrangements that would be capable of carrying out the required planning process. Hence, Metropolitan Planning Organizations (MPOs) quickly came into being because of the growing momentum of the highway program and the federal financing of the planning process. The current data inlcudes updates based on the 2010 Decennial Census determination of urban blocks.

Copyright Text: VDOT, TMPD, USDOT, Census

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9204936.325
YMin: 4375287.366599999
XMax: -8437738.9707
YMax: 4768270.049099997
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [222, 208, 247, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• MPO_ID ( type: esriFieldTypeString, alias: MPO_ID, length: 4 )
• MPO_NAME ( type: esriFieldTypeString, alias: MPO_NAME, length: 100 )
• CreationDate ( type: esriFieldTypeDate, alias: CreationDate, length: 8 )
• Creator ( type: esriFieldTypeString, alias: Creator, length: 50 )
• EditDate ( type: esriFieldTypeDate, alias: EditDate, length: 8 )
• Editor ( type: esriFieldTypeString, alias: Editor, length: 50 )
• SHAPE_Length ( type: esriFieldTypeDouble, alias: SHAPE_Length )
• SHAPE_Area ( type: esriFieldTypeDouble, alias: SHAPE_Area )

Layer: VDOT_PDC_ProjectPortal_2016 (5)

Name: VDOT_PDC_ProjectPortal_2016

Display Field: PLAN_DIST_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: In 1968, Virginia was divided into planning districts based on the community of interest among its counties, cities and towns. A Planning District Commission is a political subdivision of the Commonwealth chartered under the Regional Cooperation Act by the local governments of each planning district. As such they are a creation of local government encouraged by the state. There are 21 PDCs in Virginia. They are made up of elected officials and citizens appointed to the Commission by member local governments. The purpose of the PDC is defined in the Code of Virginia: "...to encourage and facilitate local government cooperation and state-local cooperation in addressing on a regional basis problems of greater than local significance. The cooperation resulting from this chapter is intended to facilitate the recognition and analysis of regional opportunities and take account of regional influences in planning and implementing public policies and services. The planning district commission shall also promote the orderly and efficient development of the physical, social and economic elements of the district by planning, and encouraging and assisting localities to plan, for the future." This data is current as of June 2016.

Copyright Text: VDOT, TMPD, VAPDC

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9314705.0534
YMin: 4375287.372500002
XMax: -8367489.453199999
YMax: 4788646.464299999
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [245, 219, 193, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• PLAN_DIST_NO ( type: esriFieldTypeString, alias: PLAN_DIST_NO, length: 2 )
• PLAN_DIST_NAME ( type: esriFieldTypeString, alias: PLAN_DIST_NAME, length: 50 )
• CreationDate ( type: esriFieldTypeDate, alias: CreationDate, length: 8 )
• Creator ( type: esriFieldTypeString, alias: Creator, length: 50 )
• EditDate ( type: esriFieldTypeDate, alias: EditDate, length: 8 )
• Editor ( type: esriFieldTypeString, alias: Editor, length: 50 )
• SHAPE_Length ( type: esriFieldTypeDouble, alias: SHAPE_Length )
• SHAPE_Area ( type: esriFieldTypeDouble, alias: SHAPE_Area )

Layer: VDOT_TMPDJurisdictions_ProjectPortal_2016 (6)

Name: VDOT_TMPDJurisdictions_ProjectPortal_2016

Display Field: DISTRICT_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This dataset is the product of the Virginia Geographic Network (VGIN) and an Administrative Boundary Workgroup consisting of state and local representatives to create a standard geospatial file for the jurisdictions within the Commonwealth of Virginia. "The purpose of VGIN Administrative Boundary Geospatial Data Standardis to define the data file naming conventions, geometry, map projection system, common set of attributes, dataset type and specifications, and level of precision for the Virginia Administrative Boundaries Dataset, which will be the data source of record at the state level for administrative boundary spatial features within the Commonwealth of Virginia." From Virginia Geographic Information Network (VGIN) Administrative Boundary Geospatial Data Standard, May 2014. 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. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1of the shapefile release year, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: -9314712.0832
YMin: 4375287.372900002
XMax: -8367489.4539
YMax: 4788647.204800002
Spatial Reference: 102100  (3857)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [252, 214, 197, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label:
Description:
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• SHAPE ( type: esriFieldTypeGeometry, alias: Shape )
• JURISTYPE ( type: esriFieldTypeString, alias: Jurisdiction Type, length: 2 )
• DISTRICT_CODE ( type: esriFieldTypeString, alias: DISTRICT_CODE, length: 1 )
• DISTRICT_NAME ( type: esriFieldTypeString, alias: DISTRICT_NAME, length: 17 )
• RESIDENCY_CODE ( type: esriFieldTypeString, alias: RESIDENCY_CODE, length: 2 )
• URBAN_AREA_CODE ( type: esriFieldTypeString, alias: URBAN_AREA_CODE, length: 5 )
• URBAN_AREA_NAME ( type: esriFieldTypeString, alias: URBAN_AREA_NAME, length: 46 )
• RESIDENCY_NAME_1 ( type: esriFieldTypeString, alias: RESIDENCY_NAME, length: 20 )
• JURIS_NO ( type: esriFieldTypeString, alias: JURIS_NO, length: 3 )
• JURIS_NAME ( type: esriFieldTypeString, alias: JURIS_NAME, length: 20 )
• POP_2010 ( type: esriFieldTypeInteger, alias: POP_2010 )
• NAMELSAD ( type: esriFieldTypeString, alias: NAMELSAD, length: 100 )
• SHAPE_Length ( type: esriFieldTypeDouble, alias: SHAPE_Length )
• SHAPE_Area ( type: esriFieldTypeDouble, alias: SHAPE_Area )