<?xml version="1.0" encoding="UTF-8" standalone="no"?><metadata xml:lang="en">
<Esri>
<CreaDate>20180430</CreaDate>
<CreaTime>19533900</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">ACP_Filed_Centerline_125_20170526</itemName>
<nativeExtBox>
<westBL Sync="TRUE">537852.205200</westBL>
<eastBL Sync="TRUE">727540.958600</eastBL>
<southBL Sync="TRUE">4141087.936400</southBL>
<northBL Sync="TRUE">4335873.970300</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemSize Sync="TRUE">0.205</itemSize>
<imsContentType Sync="TRUE">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">NAD_1983_UTM_Zone_17N</projcsn>
<peXml Sync="TRUE">&lt;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'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_UTM_Zone_17N&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,500000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-81.0],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9996],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,26917]]&lt;/WKT&gt;&lt;XOrigin&gt;-5120900&lt;/XOrigin&gt;&lt;YOrigin&gt;-9998100&lt;/YOrigin&gt;&lt;XYScale&gt;450445547.3910538&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;26917&lt;/WKID&gt;&lt;LatestWKID&gt;26917&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20171011</SyncDate>
<SyncTime>10514800</SyncTime>
<ModDate>20171011</ModDate>
<ModTime>10514800</ModTime>
<ArcGISProfile>FGDC</ArcGISProfile>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Daniel Shaffer</rpIndName>
<rpOrgName>Dominion Pipeline Monitoring Coalition</rpOrgName>
<rpPosName>GIS Analyst</rpPosName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress addressType="postal">
<delPoint>481 Ravens Run Road</delPoint>
<city>Monterey</city>
<adminArea>Virginia</adminArea>
<postCode>24465</postCode>
<eMailAdd>dshaffer@abralliance.org</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>8434523780</voiceNum>
</cntPhone>
</rpCntInfo>
</mdContact>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<dataIdInfo>
<idCitation>
<date>
<pubDate>2017-06-30T00:00:00</pubDate>
</date>
<presForm>
<PresFormCd value="002"/>
</presForm>
<citRespParty>
<rpIndName>Daniel Shaffer</rpIndName>
<rpOrgName>Dominion Pipeline Monitoring Coalition</rpOrgName>
<rpPosName>GIS Analyst</rpPosName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress addressType="postal">
<delPoint>481 Ravens Run Road</delPoint>
<city>Monterey</city>
<adminArea>Virginia</adminArea>
<postCode>24465</postCode>
<eMailAdd>dshaffer@abralliance.org</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>8434523780</voiceNum>
</cntPhone>
</rpCntInfo>
<displayName>Daniel Shaffer</displayName>
</citRespParty>
<resTitle Sync="TRUE">ACP_Filed_Centerline_125_20170526</resTitle>
</idCitation>
<idAbs>&lt;div style='text-align:Left;'&gt;&lt;p&gt;&lt;span style='color: rgb(51, 51, 51); font-family: &amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size: 14px; background-color: rgb(247, 247, 247);'&gt;This layer shows areas where trees have been felled in the Construction Right-of-Way for the proposed Atlantic Coast Pipeline.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style='color: rgb(51, 51, 51); font-family: &amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size: 14px; background-color: rgb(247, 247, 247);'&gt;This layer shows conditions on the ground (as photographed from the air by the Pipeline Air Force) as of May 1st, 2018.&lt;/span&gt;&lt;br /&gt;&lt;/p&gt;&lt;/div&gt;</idAbs>
<idPurp>This layer shows areas where trees have been felled in the Construction Right-of-Way for the proposed Atlantic Coast Pipeline.

This layer shows conditions on the ground (as photographed from the air by the Pipeline Air Force) as of May 1st, 2018.</idPurp>
<idCredit>Atlantic Coast Pipeline, LLC. Dominion Transmission, Inc. (DTI), Dominion Pipeline Monitoring Coalition (DPMC)</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<placeKeys>
<keyword>Virginia, West Virginia, North Carolina</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>ISO 19115 Topic Categories</resTitle>
</thesaName>
<keyword>environment</keyword>
<keyword>utilitiesCommunication</keyword>
<keyword>planningCadastre</keyword>
</themeKeys>
<themeKeys>
<keyword>Atlantic Coast Pipeline, Construction, Right-of-Way, pipeline, gas, Natural Gas, Marcellus, shale, Dominion, Duke</keyword>
</themeKeys>
<searchKeys>

















<keyword>ACP</keyword><keyword>Atlantic Coast Pipeline</keyword><keyword>tree</keyword><keyword>felling</keyword><keyword>clearing</keyword><keyword>cutting</keyword></searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-80.572024</westBL>
<eastBL>-78.367389</eastBL>
<southBL>37.388824</southBL>
<northBL>39.171094</northBL>
</GeoBndBox>
</geoEle>
<exDesc>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.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2017-01-19T00:00:00</tmBegin>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<exDesc>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.</exDesc>
<geoEle>
<GeoBndBox>
<exTypeCode>1</exTypeCode>
<westBL>-80.572024</westBL>
<eastBL>-78.367389</eastBL>
<southBL>37.388824</southBL>
<northBL>39.171094</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<idPoC>
<rpIndName>Daniel Shaffer</rpIndName>
<rpOrgName>Dominion Pipeline Monitoring Coalition</rpOrgName>
<rpPosName>GIS Analyst</rpPosName>
<role>
<RoleCd value="011"/>
</role>
<rpCntInfo>
<cntAddress addressType="postal">
<delPoint>481 Ravens Run Road</delPoint>
<city>Monterey</city>
<adminArea>Virginia</adminArea>
<postCode>24465</postCode>
<eMailAdd>dshaffer@abralliance.org</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>8434523780</voiceNum>
</cntPhone>
</rpCntInfo>
<displayName>Daniel Shaffer</displayName>
<displayName>Daniel Shaffer</displayName>
</idPoC>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.4.1.5686</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-80.572240</westBL>
<eastBL Sync="TRUE">-78.367162</eastBL>
<northBL Sync="TRUE">39.171267</northBL>
<southBL Sync="TRUE">37.388648</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
<tpCat>
<TopicCatCd value="007"/>
</tpCat>
<tpCat>
<TopicCatCd value="019"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</mdMaint>
<mdConst>
<Consts>
<useLimit>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.</useLimit>
</Consts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<dataLineage>
<dataSource type="">
<srcDesc>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 changes. These changes were shown as large-scale images of the new route over aerial imagery. These images were georeferenced to the best imagery available, which turned out to be the Imagery 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</srcDesc>
<srcMedName>
<MedNameCd value="031"/>
</srcMedName>
</dataSource>
<statement>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 route is maintained as two polyline features (broken at the proposed HDD site near Wintergreen, VA) with a Name attribute, describing the revision date, and a length attribute, measured in Miles.

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</statement>
<prcStep>
<stepDesc>Feature modified from 7/18/16 route by digitizing with the Reshape Feature tool over georeferenced maps submitted to FERC by DTI.</stepDesc>
<stepDateTm>2017-01-27T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<eainfo>
<detailed Name="ACP_Filed_Centerline_125_20170526">
<enttyp>
<enttypl Sync="TRUE">ACP_Filed_Centerline_125_20170526</enttypl>
<enttypd>Polyline feature</enttypd>
<enttypds>Author</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">2</enttypc>
</enttyp>
<attr>
<attrlabl>Name</attrlabl>
<attrdef>Date of the Route Adjustment</attrdef>
<attrdefs>Date of Suplemental Filing with FERC</attrdefs>
<attalias Sync="TRUE">Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">25</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Length</attrlabl>
<attalias Sync="TRUE">Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">19</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Calculated from feature geometry. Measured in Miles.</attrdef>
<attrdefs>Feature</attrdefs>
</attr>
<attr>
<attrlabl>FID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
<attalias Sync="TRUE">FID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
</eainfo>
<distInfo>
<distFormat>
<formatName Sync="TRUE">Shapefile</formatName>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">0.205</transSize>
</distTranOps>
</distInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="26917"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.13(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="ACP_Filed_Centerline_125_20170526">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">2</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="ACP_Filed_Centerline_125_20170526">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">2</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<mdDateSt Sync="TRUE">20171011</mdDateSt>
</metadata>