<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20180409</CreaDate>
<CreaTime>15343700</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">CFJV_P09_PeatModel_v08</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">268876.783095</westBL>
<eastBL Sync="TRUE">281577.783095</eastBL>
<southBL Sync="TRUE">793850.565692</southBL>
<northBL Sync="TRUE">804080.565692</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_OSGB_1936</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">British_National_Grid</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.5'&gt;&lt;WKT&gt;PROJCS[&amp;quot;British_National_Grid&amp;quot;,GEOGCS[&amp;quot;GCS_OSGB_1936&amp;quot;,DATUM[&amp;quot;D_OSGB_1936&amp;quot;,SPHEROID[&amp;quot;Airy_1830&amp;quot;,6377563.396,299.3249646]],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;,400000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,-100000.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-2.0],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9996012717],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,49.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,27700]]&lt;/WKT&gt;&lt;XOrigin&gt;-5220400&lt;/XOrigin&gt;&lt;YOrigin&gt;-15524400&lt;/YOrigin&gt;&lt;XYScale&gt;450481592.76709664&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;27700&lt;/WKID&gt;&lt;LatestWKID&gt;27700&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20181101</SyncDate>
<SyncTime>11311800</SyncTime>
<ModDate>20181101</ModDate>
<ModTime>11311800</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>INSPIRE</ArcGISProfile>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 10.5.1.7333</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="GBR"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">CFJV_P09_PeatModel_v08</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="011"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="002"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-4.165245</westBL>
<eastBL Sync="TRUE">-3.950832</eastBL>
<northBL Sync="TRUE">57.112581</northBL>
<southBL Sync="TRUE">57.017293</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idPurp>Peat Depth Model Methodology:
The peat depth model has been generated using ArcGIS 10.3.1 geographical information system (GIS) software, a widely available, industry standard software package. ArcGIS provide several different methods of interpolating a surface with varying values (in this case peat depths) across an area from real, measured data points.
The method used to create the peat depth model for this project has involved creating a Triangular Irregular Network (TIN) which connects real measured data points via a series of edges to form a network of triangles (ESRI, 2016). The TIN is subsequently converted from a TIN into a ‘Raster’ (i.e. a grid of cells of equal dimensions bases on a specified resolution, such as 1m by 1m) to allow further analysis (RWE, 2013a)).
This method has been chosen following detailed analysis at the Carnedd Wen Wind Farm site in Mid-Wales, which showed that, of the various methods available in ArcGIS, the TIN to raster method was preferable due to:
• Its mathematical simplicity
• The reduced likelihood of it reducing the size of, or ‘smoothing out’ completely, smaller areas of deeper peat
• It being true to the measured dataset from which it is created, in that the value of the peat model surface at a measured data point will always be equivalent to the value at that data point (RWE, 2013a).
Additionally, work at Carnedd Wen found there to be little discernible impact on the model between specified raster resolutions of 5m, 10m and 20m. At Carnedd Wen, a raster resolution of 5m was used so that the peat depth can be more accurately represented where data points are closely spaced, such as at known proposed infrastructure locations. For the peat model created for the Proposed Scheme, a resolution of 1m has been used. It is acknowledged that such a resolute raster may ‘over-represent’ the resolution of the survey, i.e. give an impression that more data has been collected than is actually the case. However, by using such a resolution, sudden step changes in peat depth (where none is present in reality) are avoided, calculations of volumes are more straightforward as each raster grid cell represents a 1m2 area (rather than a 25m3 area) and inaccuracy in volume calculation caused when the footprint of infrastructure elements overlaps partially with a grid cell. At the Carnedd Wen site, ‘barriers’ were introduced to the model to reduce the peat depth to zero where streams were known to be incised to substrate, and where lakes and streams existed. Such barriers have not been employed for the Proposed Scheme here, as this technique was resulting in areas being interpolated as zero peat depth, where this might not be the case. Instead, any such features including watercourses incised to substrate, existing road or tracks where no peat is present, have been ‘reduced to zero’ from the peat model. Embankments and cutting slopes have deliberately not been ‘reduced to zero’ peat depth to account for the possibility that dressing of these slopes has been undertaken with peat or peaty soil.
Peat Depth Model Iterations and Testing:
Numerous peat model iterations have been produced as new data has been acquired at various stages of survey. Whilst no specific testing has been undertaken to verify the accuracy of the peat model using ‘redundant’ points, where new data has been collected in areas where peat depth has been interpolated the change has usually been marginal and the new data has broadly confirmed rather than contradicted interpolated peat depths. Nonetheless, as new data becomes available, the model should be updated to ensure the highest accuracy possible.
</idPurp>
<idCredit>CFJV</idCredit>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="GBR"/>
</mdLang>
<distInfo>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Raster Dataset</formatName>
</distFormat>
</distInfo>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="27700"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.7(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<rastinfo>
<rasttype Sync="TRUE">Pixel</rasttype>
<rowcount Sync="TRUE">10230</rowcount>
<colcount Sync="TRUE">12701</colcount>
<rastxsz Sync="TRUE">1.000000</rastxsz>
<rastysz Sync="TRUE">1.000000</rastysz>
<rastbpp Sync="TRUE">32</rastbpp>
<vrtcount Sync="TRUE">1</vrtcount>
<rastorig Sync="TRUE">Upper Left</rastorig>
<rastcmap Sync="TRUE">FALSE</rastcmap>
<rastcomp Sync="TRUE">NONE</rastcomp>
<rastband Sync="TRUE">1</rastband>
<rastdtyp Sync="TRUE">pixel codes</rastdtyp>
<rastifor Sync="TRUE">FGDBR</rastifor>
<rastplyr Sync="TRUE">TRUE</rastplyr>
</rastinfo>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">row and column</plance>
<coordrep>
<absres Sync="TRUE">1.000000</absres>
<ordres Sync="TRUE">1.000000</ordres>
</coordrep>
</planci>
</planar>
</horizsys>
</spref>
<mdDateSt Sync="TRUE">20181101</mdDateSt>
</metadata>
