20170530
16145000
1.0
FALSE
ACP_Access_Roads_20170526
0.186
537896.533800
727120.726600
4140661.619600
4335915.149100
1
002
Projected
GCS_North_American_1983
Linear Unit: Meter (1.000000)
NAD_1983_UTM_Zone_17N
<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/10.4'><WKT>PROJCS["NAD_1983_UTM_Zone_17N",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["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-81.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26917]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>450445547.3910538</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>26917</WKID><LatestWKID>26917</LatestWKID></ProjectedCoordinateSystem>
20171011
11223300
20171011
11230800
FGDC
FGDC CSDGM Metadata
150000000
5000
Daniel Shaffer
Dominion Pipeline Monitoring Coalition
GIS Analyst
481 Ravens Run Road
Monterey
Virginia
24465
dshaffer@abralliance.org
US
8434523780
ArcGIS Metadata
1.0
2017-06-30T00:00:00
Daniel Shaffer
Dominion Pipeline Monitoring Coalition
GIS Analyst
481 Ravens Run Road
Monterey
Virginia
24465
dshaffer@abralliance.org
US
8434523780
Daniel Shaffer
ACP_Access_Roads_20170526
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The proposed Atlantic Coast Pipeline would extend nearly 600 miles from southern Harrison County, West Virginia to the Lumberton area, in southeastern North Carolina. The construction of such infrastructure in steep, mountainous terrain will require a large number of access roads that will allow contractors to enter and exit the work sites with heavy equipment and materials.In some areas, the length of access roads serving the pipeline construction corridor actually exceeds the length of the pipeline through that area. Access roads will require additional cuts to be made through intact forest habitat and a large number of additional river and stream crossings that will endanger water quality and aquatic life. These impacts are not adequately addressed in the Final Environmental Statement, issued by FERC on 7/21/2017.In addition, the construction of even temporary roads traversing steep slopes requires the construction of supporting embankments. Support embankments will require large amounts of fill (some recovered from road cuts into the hillsides) to be placed and compacted down-slope of the road surface. This will result in major impacts to the forest and aquatic habitats as large areas will need to be cleared for the construction of these roads. Though some of the proposed roads are temporary, the destruction of the habitat through which they will be built will not be. </SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
This layer describes the approximate locations of permanent and temporary Access Roads for the proposed Atlantic Coast Pipeline. The majority of the described locations were last filed with FERC on 7/18/2016, with minor updates, relating to improvements to existing roads filed on 2/24/2017. Latest updates taken from the most recent Project Facility Maps, filed with FERC on June 27, 2017.
This polyline featureclass represents approximate centerlines of proposed Access Roads.
Atlantic Coast Pipeline, LLC. Dominion Transmission, Inc. (DTI), Dominion Pipeline Monitoring Coalition (DPMC)
Virginia, West Virginia, North Carolina
ISO 19115 Topic Categories
environment
utilitiesCommunication
planningCadastre
Atlantic Coast Pipeline, Construction, Access Road, pipeline, gas, Natural Gas, Marcellus, shale, Dominion, utilitiesCommunication, planningCadastre
ACPAtlantic Coast Pipelineaccess roadinfrastructure
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data is for information and educational purposes only. It is provided “As-Is” with no guarantee, expressed or implied, regarding its accuracy or its suitability for any use. DPMC accepts no liability for any loss or damage that may occur as a result of the use of this data for any purpose.</SPAN></P></DIV></DIV></DIV>
-80.572024
-78.367389
37.388824
39.171094
This data should be considered valid from 6/27/2017 until a replacement is issued by DPMC, OR, Dominion Transmission, Inc. (DTI) issues additional Supplemental documentation to FERC further changing the described route.
2017-01-19T00:00:00
The Atlantic Coast Pipeline, as proposed, would begin in the southernmost portion of Harrison County, WV, where Harrison, Doddridge and Lewis counties meet. It would travel south into Lewis County, then generally southeast through Lewis and Upshur Counties. Shortly after crossing into Randolph County, WV, the ACP would turn south toward the Webster County, WV line, again turning generally southeast near Monterville, WV. It would hold this general southeasterly course through Randolph and Pocahontas counties in West Virginia and Highland and Bath counties in Virginia, before turning north up the Deerfield Valley in northeastern Bath County into Augusta County. Upon crossing US 250 in Augusta County, VA, the ACP would then head briefly east, then south and again east around the town of Staunton, VA, crossing the Shanandoah Valley. Between Stuarts Draft and Lyndhurst, the ACP would again turn south, following Back Creek toward the Sherando Recreation Area, along the western flank of the Blue Ridge Mountains. Near the confluence of the North and South forks of Back Creek, the ACP would turn east, stright up the mountain side to the site of the Horizonatal Directional Drilling (HDD) site where, supposedly, Dominion will drill a 48-inch tunnel through ~4,800 feet of granite, sandstone, limestone and loosely agglomerated rock of various types and several significant faults whose positions and magnitudes are barely known. The pipe would re-emerge at the entrance to Wintergreen Resort in Nelson County, Virgina, heading east down a ridge and crossing the Rockfish River south of Nellysford, VA. It would then resume its general southeast course, crossing the James River at Wingina, VA and the Yogaville, Ashram in Buckingham County, VA. It would continue in a southeasterly direction to the Cumberland County line and the end of DPMC's study area.
1
-80.572024
-78.367389
37.388824
39.171094
Daniel Shaffer
Dominion Pipeline Monitoring Coalition
GIS Analyst
481 Ravens Run Road
Monterey
Virginia
24465
dshaffer@abralliance.org
US
8434523780
Daniel Shaffer
Daniel Shaffer
Version 6.2 (Build 9200) ; Esri ArcGIS 10.4.1.5686
1
-80.571761
-78.372006
39.171636
37.384912
<DIV STYLE="text-align:Left;"><DIV><P><SPAN>This data is for information and educational purposes only. It is provided “As-Is” with no guarantee, expressed or implied, regarding its accuracy or its suitability for any use. DPMC accepts no liability for any loss or damage that may occur as a result of the use of this data for any purpose.</SPAN></P></DIV></DIV>
The last major centerline revision was submitted to FERC on July 18, 2016. The above process was followed. On several occasions in 2017, a Supplemental filing was submitted to FERC by DTI, detailing several minor route and Access Road changes. These changes were shown as large-scale images of the new route over aerial imagery, or as vector maps superimposed on a USGS topo background. These images/maps were georeferenced to the best imagery available, which turned out to be the Imagery Basemap or USA Topo Basemap provided by ArcGIS Online services through ArcGIS Desktop. This was the same imagery that DTI used, so georeferncing confidence level was quite high. The changes were digitized at a scale of roughly 1:2,500 and the previous route centerline was updated and exported as a new ESRI shapefile on June 30, 2017.
The source data for the Supplemental Route Adjustment Maps is available here:
https://atlanticcoastpipeline.com/permitting-process/ferc-filings.aspx
...under:
FERC Filings - 2017
Supplemental Information - Updated ACP Facility Maps - June 27, 2017
This data was digitized from georeferenced project location maps provided by Atlantic Coast Pipeline, LLC (Dominion Transmission, Inc.) to the Federal Energy Regulatory Commission (FERC). These maps were exported from the submitted PDF to individual TIFF image files. The TIFF images were then georeferenced to the USA Topo basemap provided by ArcGIS Online services through ArcGIS Desktop 10.4.1. Where possible, RMS error was kept below 1.0 in order to minimize geometric issues associated with products digitized from the georeferenced images. The centerline was digitized at a general scale of 1:5,000, sometimes as large as 1:3,500. The centerline was digitized at the boundary of the proposed permanent Right-of-Way (ROW) and the temporary construction ROW, given that the features will be used to calculate environmetal impacts during construction and early operation of the proposed pipeline. These impacts will be similar, if not identical, in the two areas during construction and the first few years of operation.
Additional route changes, submitted to FERC on 6/27/2017 were digitized from georeferenced aerial photos overlain by the newly-proposed route.
The Access Roads are maintained as individual polyline features.
The data was created and is maintained in the UTM coordinate system, Zone 17 North, NAD 1983 horizontal datum. Units are Meters. There is no vertical datum associated with the data.
The source data is available here:
https://atlanticcoastpipeline.com/permitting-process/ferc-filings.aspx
...under:
FERC Filings - 2017
Supplemental Information - Updated ACP Facility Maps - June 27, 2017
Created
2017-01-27T00:00:00
ACP_Access_Roads_20170526
Polyline feature
Author
Feature Class
599
Shape
Feature geometry.
Esri
Coordinates defining the features.
Shape
Geometry
0
0
0
FID
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
FID
OID
4
0
0
Road_Type
Road_Type
String
30
0
0
Length_m
Length_m
Double
19
0
0
Length_ft
Length_ft
Double
19
0
0
COUNTYNAME
COUNTYNAME
String
32
0
0
ARID
ARID
Integer
5
5
0
Length_mi
Length_mi
Double
19
0
0
Shapefile
0.186
dataset
EPSG
6.13(3.0.1)
599
Simple
FALSE
599
TRUE
FALSE
20171011