ÿþ<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=unicode"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 11"> <meta name=Originator content="Microsoft Word 11"> <link rel=File-List href="PA_elevation_metadata_files/filelist.xml"> <link rel=Edit-Time-Data href="PA_elevation_metadata_files/editdata.mso"> <!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--> <title>Pennsylvania Elevation Data underlying the analysis entitled &quot;Maps of lands close to sea level along the middle Atlantic coast of the United States&quot; by J</title> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceType"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PlaceName"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <!--[if gte mso 9]><xml> <o:DocumentProperties> <o:Author>Jim Titus in 2009</o:Author> <o:LastAuthor>Jim Titus in 2009</o:LastAuthor> <o:Revision>2</o:Revision> <o:TotalTime>2</o:TotalTime> <o:Created>2009-04-17T11:44:00Z</o:Created> <o:LastSaved>2009-04-17T11:44:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>7188</o:Words> <o:Characters>40974</o:Characters> <o:Company>EPA</o:Company> <o:Lines>341</o:Lines> <o:Paragraphs>96</o:Paragraphs> <o:CharactersWithSpaces>48066</o:CharactersWithSpaces> <o:Version>11.9999</o:Version> </o:DocumentProperties> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--><!--[if !mso]><object classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object> <style> st1\:*{behavior:url(#ieooui) } </style> <![endif]--> <style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} h1 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:1; font-size:24.0pt; font-family:"Times New Roman";} h2 {mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; mso-outline-level:2; font-size:18.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:blue; text-decoration:underline; text-underline:single;} pre {margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Courier New"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:154615641; mso-list-template-ids:-204466976;} @list l0:level1 {mso-level-number-format:bullet; mso-level-text:·ð; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} @list l0:level2 {mso-level-tab-stop:1.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level3 {mso-level-tab-stop:1.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level4 {mso-level-tab-stop:2.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level5 {mso-level-tab-stop:2.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level6 {mso-level-tab-stop:3.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level7 {mso-level-tab-stop:3.5in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level8 {mso-level-tab-stop:4.0in; mso-level-number-position:left; text-indent:-.25in;} @list l0:level9 {mso-level-tab-stop:4.5in; mso-level-number-position:left; text-indent:-.25in;} @list l1 {mso-list-id:1332022554; mso-list-template-ids:-1309375348;} @list l1:level1 {mso-level-number-format:bullet; mso-level-text:·ð; mso-level-tab-stop:.5in; mso-level-number-position:left; text-indent:-.25in; mso-ansi-font-size:10.0pt; font-family:Symbol;} ol {margin-bottom:0in;} ul {margin-bottom:0in;} --> </style> <!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> <script> <!-- function fix(e) { var par = e.parentNode; e.id = ""; e.style.marginLeft = "0.42in"; var pos = e.innerText.indexOf("\n"); if (pos > 0) { while (pos > 0) { var t = e.childNodes(0); var n = document.createElement("PRE"); var s = t.splitText(pos); e.insertAdjacentElement("afterEnd", n); n.appendChild(s); n.style.marginLeft = "0.42in"; e = n; pos = e.innerText.indexOf("\n"); } var count = (par.children.length); for (var i = 0; i < count; i++) { e = par.children(i); if (e.tagName == "PRE") { pos = e.innerText.indexOf(">"); if (pos != 0) { n = document.createElement("DD"); e.insertAdjacentElement("afterEnd", n); n.innerText = e.innerText; e.removeNode(true); } } } if (par.children.tags("PRE").length > 0) { count = (par.children.length); for (i = 0; i < count; i++) { e = par.children(i); if (e.tagName == "PRE") { e.id = ""; if (i < (count-1)) { var e2 = par.children(i + 1); if (e2.tagName == "PRE") { e.insertAdjacentText("beforeEnd", e2.innerText+"\n"); e2.removeNode(true); count = count-1; i = i-1; } } } } } } else { n = document.createElement("DD"); par.appendChild(n); n.innerText = e.innerText; e.removeNode(true); } } --> </script> </head> <body lang=EN-US link=blue vlink=blue style='tab-interval:.5in' oncontextmenu="return true"> <div class=Section1> <h1><a name=Top></a><st1:State w:st="on"><span style='mso-bookmark:Top'>Pennsylvania</span></st1:State><span style='mso-bookmark:Top'> Elevation Data underlying the analysis entitled &quot;Maps of lands close to sea level along the middle Atlantic coast of the <st1:country-region w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region>&quot; by J.G. Titus and J. Wang, 2008.</span></h1> <h2><span style='mso-bookmark:Top'>Metadata:</span></h2> <span style='mso-bookmark:Top'></span> <ul type=disc> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#Identification_Information">Identification_Information</a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#Data_Quality_Information">Data_Quality_Information</a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#Spatial_Data_Organization_Information">Spatial_Data_Organization_Information</a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#Spatial_Reference_Information">Spatial_Reference_Information</a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#Entity_and_Attribute_Information">Entity_and_Attribute_Information</a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#34372992">Distribution_Information </a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo3;tab-stops:list .5in'><a href="#Metadata_Reference_Information">Metadata_Reference_Information</a></li> </ul> <div class=MsoNormal align=center style='text-align:center'><a name="Identification_Information"> <hr size=2 width="100%" align=center> </a></div> <span style='font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family: "Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US; mso-bidi-language:AR-SA'><span style='mso-bookmark:Identification_Information'></span></span> <p class=MsoNormal><i>Identification_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> US Environmental Protection Agency</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> February 2008</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Pennsylvania Elevation Data underlying the analysis entitled &quot;Maps of lands close to sea level along the middle Atlantic coast of the <st1:country-region w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region>&quot; by J.G. Titus and J. Wang, 2008.</p> <p class=MsoNormal style='margin-left:.5in'><i>Geospatial_Data_Presentation_Form:</i> raster digital data</p> <p class=MsoNormal style='margin-left:.5in'><i>Other_Citation_Details:</i></p> <p class=MsoNormal style='margin-left:.5in'>Data underlying the analysis reported in J.G. Titus and J. Wang, 2008.</p> <p class=MsoNormal style='margin-left:.5in'><i>Online_Linkage:</i> <span lang=DE style='mso-ansi-language:DE'><a href="http://maps.risingsea.net/data.html"><span lang=EN-US style='mso-ansi-language: EN-US'>http://maps.risingsea.net/data.html</span></a> </span></p> <p class=MsoNormal style='margin-left:.5in'><i>Larger_Work_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> US Environmental Protection Agency</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> February 2008</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Maps of lands close to sea level along the middle Atlantic coast of the <st1:country-region w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region></p> <p class=MsoNormal style='margin-left:.5in'><i>Other_Citation_Details:</i></p> <p class=MsoNormal style='margin-left:.5in'>Full Citation: Titus, J.G. and J. Wang, 2008: Maps of lands close to sea level along the middle Atlantic coast of the <st1:country-region w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region>: an elevation data set to use while waiting for LIDAR. In: Background Documents Supporting Climate Change Science Program Synthesis and Assessment Product 4.1: Coastal Elevations and Sensitivity to Sea Level Rise [J.G. Titus and E.M. Strange (eds.)]. EPA430R07004, U.S. Environmental Protection Agency, Washington, DC.</p> <p class=MsoNormal style='margin-left:.5in'><i>Description:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Abstract:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Coastal <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State> Digital Elevation Model (Environmental Systems Research</pre><pre style='margin-left:.5in'>Institute [ESRI] Grid format) represents an elevation map of the <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State> coastal zone created for the purposes of analyzing vulnerability to rising sea level. The domain of the data set extends from the upper tidal wetland boundary up to the 40-foot NGVD29 contour, but the primary focus of the analytical approach and quality control has focused on land below the 10-foot contour. </pre><pre style='margin-left:.5in'>This data set has been derived from several sources of elevation data, including United States Geological</pre><pre style='margin-left:.5in'>Survey (USGS) 1:24,000 Digital Line Graphs (DLG), US. Corps of Engineer Spot</pre><pre style='margin-left:.5in'>Elevation data, <st1:place w:st="on"><st1:PlaceName w:st="on">Monmouth</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place> elevation data,<span style='mso-spacerun:yes'>  </span>as well as DGL's</pre><pre style='margin-left:.5in'>created by Henan Institute of Geography from USGS 1:24,000 Digital Raster Graphs.</pre><pre style='margin-left:.5in'>In addition, the analysis created a supplemental contour representing the</pre><pre style='margin-left:.5in'>elevation of spring high water (SHW), which ranges from 1.2 to 5.8 feet</pre><pre style='margin-left:.5in'>above NGVD29 in <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State>.<span style='mso-spacerun:yes'>  </span>We defined the horizontal position of that contour</pre><pre style='margin-left:.5in'>by extracting the inland limit of the tidal wetland polygons in a separate Coastal</pre><pre style='margin-left:.5in'>Wetlands data set we created for this project (based on the National Wetlands</pre><pre style='margin-left:.5in'>Inventory) . We defined the vertical position of the supplemental contour by creating a</pre><pre style='margin-left:.5in'>&quot;tidal elevation surface&quot; using the National Ocean Service's (NOS) estimated tide</pre><pre style='margin-left:.5in'>ranges, NOS estimated sea level trends, NOS published benchmark sheets, and the</pre><pre style='margin-left:.5in'>National Geodetic Survey North American Vertical Datum Conversion Utility</pre><pre style='margin-left:.5in'>(VERTCON) program to convert the Mean Tide Level (MTL) relative to NAVD88 to</pre><pre style='margin-left:.5in'>NGVD29. All elevation information was converted to a common vertical reference,</pre><pre style='margin-left:.5in'>usually NGVD29, and the DEM was generated from that input data using ESRI's</pre><pre style='margin-left:.5in'>interpolation algorithm TOPOGRID (within ArcGIS workstation GRID extension).</pre><pre style='margin-left:.5in'>We converted the absolute elevation estimates (usually NGVD29) into elevations relative to SHW using the &quot;tidal elevation surface.&quot;</pre><pre style='margin-left:.5in'>For purposes of this data set, SHW is the upper boundary of tidal wetlands (including vegetated wetlands and</pre><pre style='margin-left:.5in'>intertidal beaches). Elevation is expressed in cm.</pre><pre style='margin-left:.5in'>The zip file associated with this data set should include:</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>1.<span style='mso-tab-count:1'>       </span>README_PA_Elevation.doc, which provides a brief overview of the relationship between this dataset and related data</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2.<span style='mso-tab-count:1'>       </span>InterpolationMethods_MEMO.doc</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3.<span style='mso-tab-count:1'>       </span>PA_Data_Quality.jpg</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>4.<span style='mso-tab-count:1'>       </span>DEM_LidarComparisonTable.doc</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>5.<span style='mso-tab-count:1'>       </span>DEM_Comparison_with_DLG_11_quads.xls</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>6.<span style='mso-tab-count:1'>       </span>Institute_of_Geography_DLG.xls</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>7.<span style='mso-tab-count:1'>       </span>Titus_and_Wang_2008.pdf</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>However, to speed download, in the online versions, (2) and (7) which are associated with all of the states may have been removed</pre><pre style='margin-left:.5in'>and included in a file called  Common_supplemental_metadata.zip </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Purpose:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>The Pennsylvania Digital Elevation Model provides a base map layer for assessing the possible influences of potential sea level rise on coast regions. We recommend against using this data to create maps with scales greater than 1:100,000, regardless of the level of vertical precision portrayed.<span style='mso-spacerun:yes'>  </span>Moreover, if the purpose of using this data is to create graphical depictions of risk with contour intervals of 50-100 cm, we recommend a considerably smaller scale unless the audience is likely to understand the limitations of the data.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Supplemental_Information:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevations relative to year 2000.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Time_Period_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Single_Date/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Calendar_Date:</i> 2000</p> <p class=MsoNormal style='margin-left:.5in'><i>Currentness_Reference:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>ground condition</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Status:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Progress:</i> Complete</p> <p class=MsoNormal style='margin-left:.5in'><i>Maintenance_and_Update_Frequency:</i> None planned</p> <p class=MsoNormal style='margin-left:.5in'><i>Spatial_Domain:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Bounding_Coordinates:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>West_Bounding_Coordinate:</i> -75.938065</p> <p class=MsoNormal style='margin-left:.5in'><i>East_Bounding_Coordinate:</i> -73.516493</p> <p class=MsoNormal style='margin-left:.5in'><i>North_Bounding_Coordinate:</i> 41.360902</p> <p class=MsoNormal style='margin-left:.5in'><i>South_Bounding_Coordinate:</i> 38.754772</p> <p class=MsoNormal style='margin-left:.5in'><i>Keywords:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Theme:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Theme_Keyword_Thesaurus:</i> General</p> <p class=MsoNormal style='margin-left:.5in'><i>Theme_Keyword:</i> <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State> Elevation</p> <p class=MsoNormal style='margin-left:.5in'><i>Theme_Keyword:</i> DEM</p> <p class=MsoNormal style='margin-left:.5in'><i>Theme_Keyword:</i> Coastal Elevation</p> <p class=MsoNormal style='margin-left:.5in'><i>Place:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Place_Keyword:</i> PA</p> <p class=MsoNormal style='margin-left:.5in'><i>Access_Constraints:</i> None</p> <p class=MsoNormal style='margin-left:.5in'><i>Use_Constraints:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>None</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Point_of_Contact:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person_Primary:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person:</i> James G. Titus</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization:</i> <st1:country-region w:st="on"><st1:place w:st="on">U.S.</st1:place></st1:country-region> Environmental Protection Agency, Climate Change Division</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Position:</i> Project Manager</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Address:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Address_Type:</i> mailing address</p> <p class=MsoNormal style='margin-left:.5in'><i>Address:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Mailcode 6207J</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>City:</i> <st1:State w:st="on"><st1:place w:st="on">Washington</st1:place></st1:State></p> <p class=MsoNormal style='margin-left:.5in'><i>State_or_Province:</i> DC</p> <p class=MsoNormal style='margin-left:.5in'><i>Postal_Code:</i> 20460</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 202-343-9307</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Facsimile_Telephone:</i> 202-343-2338</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> Titus.Jim@epamail.epa.gov</p> <p class=MsoNormal style='margin-left:.5in'><i>Hours_of_Service:</i> 9:00 - 6:00 Eastern</p> <p class=MsoNormal style='margin-left:.5in'><i>Data_Set_Credit:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Jue Wang, GIS Practice, ICF Consulting, Inc.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Native_Data_Set_Environment:</i></p> <p class=MsoNormal style='margin-left:.5in'>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.3.0.1770</p> <p class=MsoNormal><a href="#Top">Back to Top</a> <a name="Data_Quality_Information"></a></p> <div class=MsoNormal align=center style='text-align:center'><span style='mso-bookmark:Data_Quality_Information'> <hr size=2 width="100%" align=center> </span></div> <span style='font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family: "Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US; mso-bidi-language:AR-SA'><span style='mso-bookmark:Data_Quality_Information'></span></span> <p class=MsoNormal><i>Data_Quality_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Accuracy:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Accuracy_Report:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>The underlying data used in the creation of this layer may contain errors or omissions. The accuracy of this data set generally corresponds to the source data used in the layer development. See &quot;PA_Data_Quality.jpg&quot; for<span style='mso-spacerun:yes'>  </span>an index of the source data used (that accompanied this data set in the zip file.)</pre><pre style='margin-left:.5in'>See the sections on Positional Accuracy for more detailed information.</pre><pre style='margin-left:.5in'>Additional consideration: The vertical values and their associated positions were generated using the interpolation function &quot;TOPOGRID&quot; within the ESRI GRID module. TOPOGRID uses input elevation data such as contours and elevation point data along with supplemental information such as stream networks, lakes (of known elevation), and bounding areas to generate a hydrologically-correct DEM. Each state DEM was generated using TOPOGRID but the specific parameters were unique to the data sets available and issues related to each state.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>There are known issues relating to the interpolation algorithm TOPOGRID.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>TOPOGRID Plateau Problem. The TOPOGRID function generates disproportionately large areas with the same value of the input contour lines, e.g., if we have 5 and 10 foot contour lines, there would be substantially more areas with values between 4 to 6 and 9 to 11, than 6 to 9 feet. At the upper tips of narrow valleys, the cell values tend to be the same as the bounding contours so the valleys become plateaus. The TOPOGRID function within the ESRI GRID module tends to calculate a trend from neighboring contour lines. As a result, TOPOGRID frequently creates areas of erroneous depressions on the plains adjacent to steep slopes, often substantially below the contours between which those depressions lay. It also creates plateaus along contours, which can be problematic because they overstate the amount of land barely above the wetlands and right at the first contour, while understating the amount of land halfway between the wetlands and the first contour. To address these problems, we processed the areas above and below the first contour separately. However, this caused another problem. In narrow valleys in the area below the first contour, the output DEM values were similar or identical to those of the bounding contour lines due to the lack of elevation information that TOPOGRID needs to calculate trend. The most problematic regions occurred where there was a stream valley below the first contour (e.g. between two parallel 5 foot contours), neither open water nor tidal wetlands along most of the length of the valley, but open water or tidal wetlands at one end of the valley (e.g. a typical non-tidal stream flowing into tidal waters). In some cases, the trend from the wetlands or open water at the mouth toward the bounding first contour would provide values even higher than that first contour farther up the valley. And in general, TOPOGRID would be more likely to assume a flat area between the contours, than to characterize it as a valley.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>We did not use stream data in constructing the DEM for <st1:State w:st="on">Pennsylvania</st1:State> (See comparable DEMs for <st1:State w:st="on">Delaware</st1:State>, <st1:State w:st="on">Maryland</st1:State>, <st1:State w:st="on">New York</st1:State> and <st1:State w:st="on"><st1:place w:st="on">North Carolina</st1:place></st1:State>, where stream data was available.).</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Evaluation of other interpolation methods. </pre><pre style='margin-left:.5in'>Several interpolation methods were evaluated before the TOPOGRID function was selected. Specifically, Spline, Inverse Distance Weighting (IDW), and Triangulated Irregular Network (TIN) methods were evaluated and compared to the TOPOGRID function. Statistics and graphical examples of cross sections specific to each interpolation method are presented in the accompanying &quot;InterpolationMethods_MEMO.doc&quot; memo included in the zip file associated with this data set.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Quantitative_Attribute_Accuracy_Assessment:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Accuracy_Explanation:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>An accuracy assessment was made between the source<span style='mso-spacerun:yes'>  </span>DLG's and the DEM for a select number of quads. See &quot;DEM_Comparison_with_DLG_11_quads.xls&quot;<span style='mso-spacerun:yes'>  </span>which accompanies this data set in the zip file.</pre><pre style='margin-left:.5in'>An additional assessment was made between the DEM and lidar data where it was available in <st1:State w:st="on">Maryland</st1:State> and <st1:State w:st="on"><st1:place w:st="on">North Carolina</st1:place></st1:State>. The results can be found in the &quot;DEM_LidarComparisonTable.doc&quot; that accompanied this data set in the zip file.</pre><pre style='margin-left:.5in'>See the sections on Positional Accuracy (Horizontal and Vertical).</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Logical_Consistency_Report:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Refer to the Titus and Wang 2008 technical report that documents this study for information on the publication date for data and procedures used in the development of this layer.</pre><pre style='margin-left:.5in'>See the sections on Positional Accuracy (Horizontal and Vertical) for additional information.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Note that the discussions presented in the accuracy reports refer to contour intervals using two different systems of measurements (meters and feet). We use the two diffent systems to reflect the actual contour intervals used by USGS over the years, which vary on a quadrangle by quadrangle basis.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Completeness_Report:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>This data set generally corresponds to that of the source data used in the layer </pre><pre style='margin-left:.5in'>development. See the sections on Positional Accuracy (Horizontal and Vertical) for </pre><pre style='margin-left:.5in'>additional information. </pre><pre style='margin-left: .5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The vertical values and their associated positions were generated using the interpolation </pre><pre style='margin-left:.5in'>function &quot;TOPOGRID&quot; within the ESRI GRID module. TOPOGRID uses input </pre><pre style='margin-left:.5in'>elevation data such as contours and elevation point data along with supplemental </pre><pre style='margin-left:.5in'>information such as stream networks, lakes (of known elevation), and bounding areas to </pre><pre style='margin-left:.5in'>generate a hydrologically correct DEM. Each state DEM was generated using </pre><pre style='margin-left:.5in'>TOPOGRID but the specific parameters were unique to the data sets available and </pre><pre style='margin-left:.5in'>issues related to each state. The specifics to each state DEM are described under </pre><pre style='margin-left:.5in'>positional accuracy section of the metadata and in process steps. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>There are known issues relating to the interpolation algorithm TOPOGRID. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>TOPOGRID Plateau Problem. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The TOPOGRID function generates disproportionately large areas with the same value of the input contour lines, e.g., if we </pre><pre style='margin-left:.5in'>have 5 and 10 foot contour lines, there would be substantially more areas with values </pre><pre style='margin-left:.5in'>between 4 to 6 and 9 to 11, than 6 to 9 feet.. At the upper tips of narrow valleys, the </pre><pre style='margin-left:.5in'>cell values tend to be the same as the bounding contours so the valleys become </pre><pre style='margin-left:.5in'>plateaus. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The TOPOGRID function within the ESRI GRID module tends to calculate a trend </pre><pre style='margin-left:.5in'>from neighboring contour lines.<span style='mso-spacerun:yes'>  </span>As a result, TOPOGRID frequently creates erroneous </pre><pre style='margin-left:.5in'>depressions on the plains adjacent to steep slopes, often substantially below the </pre><pre style='margin-left:.5in'>contours between which those depressions lie. It also creates plateaus along contours, </pre><pre style='margin-left:.5in'>which can be problematic because they overstate the amount of land barely above the </pre><pre style='margin-left:.5in'>wetlands and right at the first contour, while understating the amount of land halfway </pre><pre style='margin-left:.5in'>between the wetlands and the first contour. To address these problems, we processed </pre><pre style='margin-left:.5in'>the areas above and below the first contour separately. However, this caused another </pre><pre style='margin-left:.5in'>problem. In narrow valleys in the area below the first contour, the output DEM values </pre><pre style='margin-left:.5in'>were similar or identical to those of the bounding contour lines due to the lack of </pre><pre style='margin-left:.5in'>elevation information that TOPOGRID needs to calculate trend. The most problematic </pre><pre style='margin-left:.5in'>regions occurred where there was a stream valley below the first contour (e.g. between </pre><pre style='margin-left:.5in'>two parallel 5 foot contours), no open water or tidal wetlands along most of the length </pre><pre style='margin-left:.5in'>of the valley, but open water or tidal wetlands at one end of the valley (e.g. a typical </pre><pre style='margin-left:.5in'>nontidal stream flowing into tidal waters). In some cases, the trend from the wetlands or </pre><pre style='margin-left:.5in'>open water at the mouth toward the bounding first contour, would provide values even </pre><pre style='margin-left:.5in'>higher than that first contour farther up the valley. And in general, TOPOGRID would </pre><pre style='margin-left:.5in'>be more likely to assume a flat area between the contours, than to characterize it as a </pre><pre style='margin-left:.5in'>valley--except for when stream data was used. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Omissions: Neither stream networks nor lake features were used as inputs into the </pre><pre style='margin-left:.5in'>TOPOGRID function in creation of the DEM for <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State>. The EPA project </pre><pre style='margin-left:.5in'>manager discovered this omission as a result of questions raised by Russ Jones of </pre><pre style='margin-left:.5in'>Stratus Consulting, who provided EPA with assistance in preparing this metadata.<span style='mso-spacerun:yes'>   </span>ICF </pre><pre style='margin-left:.5in'>has asked EPA to omit further discussion while it investigates the cause of this omission.<span style='mso-spacerun:yes'>  </span></pre><pre style='margin-left:.5in'>(See comparable data sets for <st1:City w:st="on">New York</st1:City>, <st1:State w:st="on">Delaware</st1:State>, <st1:State w:st="on">Maryland</st1:State>, and <st1:State w:st="on"><st1:place w:st="on">North Carolina</st1:place></st1:State>, </pre><pre style='margin-left:.5in'>where we did use stream data.)</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The absence of a hydrologic network may explain a significant proportion of the </pre><pre style='margin-left:.5in'>greatest errors in the vicinity of nontidal streams at elevations below the first contour. </pre><pre style='margin-left:.5in'>TOPOGRID infers stream valleys above the first contour by the pattern of a valley </pre><pre style='margin-left:.5in'>without the stream data. The decision to split the data into land below and above the </pre><pre style='margin-left:.5in'>first contour (discussed in process step #4 &quot;Interpolation of Digital Elevation Model &quot;) </pre><pre style='margin-left:.5in'>had the effect of increasing the potential errors resulting from the absence of stream </pre><pre style='margin-left:.5in'>data. However, the magnitude of any errors induced by this problem was limited by the </pre><pre style='margin-left:.5in'>&quot;first contour truncating&quot; (also discussed in process step #4). The net effect was to put </pre><pre style='margin-left:.5in'>back some of the plateaus eliminated by dividing the data, but not all of those plateaus.<span style='mso-spacerun:yes'>  </span></pre><pre style='margin-left:.5in'>Moreover, errors introduced by of omitting stream were avoided in areas with tidal </pre><pre style='margin-left:.5in'>streams or tidal wetlands, by the use of tidal wetlands data, which served the same </pre><pre style='margin-left:.5in'>function.<span style='mso-spacerun:yes'>  </span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Other Issues: In addition to excluding streams, the decision to process 3 elevation areas </pre><pre style='margin-left:.5in'>separately within TOPOGRID (as described in the process step #4 - &quot;Interpolation of </pre><pre style='margin-left:.5in'>Digital Elevation Model&quot;) and then combine them into a single DEM removes the </pre><pre style='margin-left:.5in'>algorithm from its theoretical underpinning, because it separates each elevation zone </pre><pre style='margin-left:.5in'>from the context of the overall environment that TOPOGRID uses to generate a </pre><pre style='margin-left:.5in'>hydrologically-correct DEM. Because the objective of this DEM is to estimate </pre><pre style='margin-left:.5in'>elevations of lands close to sea level, rather than characterize drainage correctly, the ad </pre><pre style='margin-left:.5in'>hoc response to the TOPOGRID plateau problem is not as unreasonable as would have </pre><pre style='margin-left:.5in'>been the case were this data to be used for analyzing hydrology. Nevertheless, the </pre><pre style='margin-left:.5in'>inclusion of an accurate stream network, modification of the tolerance values and other </pre><pre style='margin-left:.5in'>parameters within TOPOGRID, and inclusion of additional vertical data in areas of </pre><pre style='margin-left:.5in'>known errors (determined through the use of diagnostic outputs within the TOPOGRID </pre><pre style='margin-left:.5in'>function), probably could have substantially diminished the plateau problem in the </pre><pre style='margin-left:.5in'>vicinity of the first topographic contour. Because the plateau problem around the edge </pre><pre style='margin-left:.5in'>of tidal wetlands was often caused largely by the relative complexity of the wetland </pre><pre style='margin-left:.5in'>supplemental contour compared with other contours, and because the tidal wetlands </pre><pre style='margin-left:.5in'>and open water data which we used in effect provide the stream data, the case for </pre><pre style='margin-left:.5in'>dividing the data as we did is probably greater along the wetland boundary than along </pre><pre style='margin-left:.5in'>the first contour. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>We did not divide the data<span style='mso-spacerun:yes'>  </span>into the separate elevation classes in those areas where we </pre><pre style='margin-left:.5in'>had two-foot contours or spot elevation data. Because we had 2-foot contours for </pre><pre style='margin-left:.5in'><st1:City w:st="on"><st1:place w:st="on">Philadelphia</st1:place></st1:City>, this issue is inapplicable there.<span style='mso-spacerun:yes'>    </span>(See PA_Elevation_Data_Quality.jpg , </pre><pre style='margin-left:.5in'>included in the zip file in which this data set was distributed.)<span style='mso-spacerun:yes'>  </span></pre><pre style='margin-left:.5in'>Also see the sections on Positional Accuracy (Horizontal and Vertical) and process </pre><pre style='margin-left:.5in'>steps.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Positional_Accuracy:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Positional_Accuracy:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Positional_Accuracy:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Horizontal_Positional_Accuracy:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Horizontal_Positional_Accuracy_Report:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>The source data generally were 1:24,000 scale or better. Therefore our use of 30-meter cells deteriorated the horizontal accuracy.<span style='mso-spacerun:yes'>  </span>Assuming that 90% of well defined points are within 30 meters of the indicated location would imply a scale of 1:60,000 under National Map Accuracy Standards. (That assumption may be conservative because 100% of the points in a 30 meter cell are less than 21.2 meters of the center of the cell. If the input map has 1:24,000 scale (well defined points within 12.2 meters)<span style='mso-spacerun:yes'>  </span>and errors are random, then more than 90% of the points will be within 24.5 meters of the indicated location, which would imply a scale of 1:50,000.)<span style='mso-spacerun:yes'>  </span>However, our interpolation program may further deteriorate the horizontal accuracy.<span style='mso-spacerun:yes'>  </span>Under some circumstances, the horizontal error appears to be as great as the width of a cell.<span style='mso-spacerun:yes'>  </span>Given that the diagonal in this case would be 42.4 m, if errors are random, then the scale might be as poor as 1:86,000 in areas where those 1-cell errors are common.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Neither stream networks nor lake features were used as inputs into the TOPOGRID function in creation of this data set for reasons discussed in the completeness report. The addition of a hydrologic network would increase the accuracy of the resulting</pre><pre style='margin-left:.5in'>DEM.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Quantitative_Horizontal_Positional_Accuracy_Assessment:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Horizontal_Positional_Accuracy_Value:</i> 40-42.5 meters</p> <p class=MsoNormal style='margin-left:.5in'><i>Horizontal_Positional_Accuracy_Explanation:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Under some circumstances the horizontal error appears can be as great as the width of a cell.<span style='mso-spacerun:yes'>  </span>Given that the diagonal would be 42.4 m.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Vertical_Positional_Accuracy:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Vertical_Positional_Accuracy_Report:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>This data set generally corresponds to that of the source data (described below) used in the layer development, plus errors induced through the various processing steps. The most important processing errors probably concern the procedures used to interpolate between contours, which do not necessarily correspond to the actual geometry of the land surfaces. Therefore, points that are near a contour have greater accuracy than points that are farther away from a contour.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>In order to assess the vertical accuracy of<span style='mso-spacerun:yes'>  </span>DEMs generated by ICF Consulting, Russ Jones of Stratus Consulting Inc. compared DEMs with LIDAR data in two areas: 1) an area south of Rock Hall along the eastern shore of <st1:State w:st="on">Maryland</st1:State>, and 2) portions of <st1:State w:st="on"><st1:place w:st="on">North Carolina</st1:place></st1:State>. Table 1 within DEM_LidarComparisonTable.doc summarizes the comparison. The analysis suggests a Root Mean Square (RMS) discrepancy between LIDAR and this DEM approximately one-half of the input contour interval in cases where the contour interval was 1 meter, 5 feet, or 2 meters.<span style='mso-spacerun:yes'>  </span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>In areas where the USGS contour interval was 20 feet and we used MD DNR data for supplemental contours, the mean discrepancy (LIDAR-DEM) was -2.4 feet with a RMS discrepancy of 6 feet for DEM observations less than 10 feet. The error was much less (mean -1.1 feet, RMS 3.9 feet) for DEM values between 10 and 20 feet NGVD29. Most of the errors appear to be centered in <st1:place w:st="on"><st1:PlaceName w:st="on">Caroline</st1:PlaceName> <st1:PlaceName w:st="on">County</st1:PlaceName></st1:place>, where the Maryland DNR data incorrectly showed a large area below 5 feet NGVD29.<span style='mso-spacerun:yes'>  </span>If the LIDAR comparison is applicable to <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State>, one would expect RMS errors of approximately one-half the USGS contour interval, with a mean error less than 1/10 the contour interval.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Jones also provided histograms showing the relationship between</pre><pre style='margin-left:.5in'>input contour intervals and the DEM values, for 11 USGS 7.5'</pre><pre style='margin-left:.5in'>topographical quadrangles in the study area from <st1:State w:st="on"><st1:place w:st="on">New York</st1:place></st1:State> to North</pre><pre style='margin-left:.5in'><st1:City w:st="on"><st1:place w:st="on">Carolina</st1:place></st1:City>, including Marcus Hook.<span style='mso-spacerun:yes'>  </span>The technical paper by Titus and Wang (2008, listed in the citation section above)<span style='mso-spacerun:yes'>  </span>analyzes the</pre><pre style='margin-left:.5in'>results of that comparison. Note that this comparison was conducted on the initial DEM generated with TOPOGRID. As a result of this analysis, the minimum and maximum elevation limits were constrained to ensure that the resulting elevations were in accordance with the input data. (See &quot;First-contour truncating&quot; in the process step on interpolation of Digital Elevation Model). That paper compares the area of land below the first, second, and third contour according to the DEM,</pre><pre style='margin-left:.5in'>with the area of the input polygons.<span style='mso-spacerun:yes'>  </span>That error can be considered</pre><pre style='margin-left:.5in'>both in terms of the difference in area estimates, and as a</pre><pre style='margin-left:.5in'>vertical error.<span style='mso-spacerun:yes'>  </span>As a measure of the vertical error, Titus and</pre><pre style='margin-left:.5in'>Wang consider the effective elevation of the DLG contour that the</pre><pre style='margin-left:.5in'>DEM estimates, that is, at what elevation does the DEM find the</pre><pre style='margin-left:.5in'>same amount of land that the DLG polygons show to be below the</pre><pre style='margin-left:.5in'>first contour.</pre><pre style='margin-left:.5in'>The technical paper also calculates a plateau exaggeration factor:</pre><pre style='margin-left:.5in'>The ratio of the area (according to the DEM) within 0.1 feet above</pre><pre style='margin-left:.5in'>or below a contour, to the area that one would expect if</pre><pre style='margin-left:.5in'>elevations were uniformly distributed between the contour above</pre><pre style='margin-left:.5in'>and (if it exists) the contour below.<span style='mso-spacerun:yes'>  </span>Suppose for example, </pre><pre style='margin-left:.5in'>spring high water is 2 ft NGVD, the contour interval is 5 feet,</pre><pre style='margin-left:.5in'>there are 3 ha between spring high water and the 5 ft</pre><pre style='margin-left:.5in'>contour, and 5 ha between the 5- and 10-foot contours, and the DEM</pre><pre style='margin-left:.5in'>finds 2 ha between 4.9 and 5.1 ft.<span style='mso-spacerun:yes'>  </span>The plateau exaggeration factor</pre><pre style='margin-left:.5in'>would be 10, because a uniform elevation distribution would imply</pre><pre style='margin-left:.5in'>1 ha per foot of elevation change; but around the plateau we have</pre><pre style='margin-left:.5in'>2 ha in a 0.2 ft elevation increment.</pre><pre style='margin-left:.5in'>This metadata discusses only the one quad in <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State>,<span style='mso-spacerun:yes'>  </span>plus two quads in</pre><pre style='margin-left:.5in'><st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State> that were particularly problematic.</pre><pre style='margin-left:.5in'>For the Marcus Hook quad, the DEM underestimated the low land (below</pre><pre style='margin-left:.5in'>10ft) implied by the DLG by 20%.<span style='mso-spacerun:yes'>   </span>Examining an overlay of the DEM and the DLG's, the discrepancy for land below the 10-foot contour appears to be explained by a couple of factors. First, in some places the land is sufficiently steep that particular cells will have<span style='mso-spacerun:yes'>  </span>more than one contour crossing them. The DEM assigns an average elevation to the cell.<span style='mso-spacerun:yes'>   </span>Assuming that the contours cross the centers of cells randomly, one would normally expect that the amount of higher and lower ground being &quot;averaged in&quot; would approximately offset each other, so that the DEM should find the same amount of land within a given elevation range </pre><pre style='margin-left:.5in'>as the input DLG's. For land below 10 feet, however, there is higher ground but no lower ground<span style='mso-spacerun:yes'>  </span>to be &quot;averaged in.&quot;<span style='mso-spacerun:yes'>  </span>Therefore, an upward bias is created for the lowest areas. Second, in some areas that were completely enclosed by the 10 foot contour, TOPOGRID interpolates the elevation within the contour to elevations just above 10 feet while the contour data does not have sufficient resolution to depict elevations between 10 and 20 feet. The plateau exaggeration factors were 0.8, 12, and 3.5 for the tidal wetland, 10-ft, and 20-ft contours, respectively. This represents an area twice the size of the 20% discrepancy between the polygon input and the grid output.<span style='mso-spacerun:yes'>  </span>Thus, in effect, the DEM estimates the</pre><pre style='margin-left:.5in'>DLG's 10-ft contour to be between 10 and 10.1 feet.<span style='mso-spacerun:yes'>  </span>The discrepancy for lands</pre><pre style='margin-left:.5in'>between 10-20 and 20-30 feet are less than 2%, which suggests that part of the</pre><pre style='margin-left:.5in'>problem for the lowest land may be explained by areas where the dry land below 10 ft</pre><pre style='margin-left:.5in'>is too narrow to take up an entire cell (see discussion of <st1:place w:st="on"><st1:City w:st="on">South River</st1:City>, <st1:State w:st="on">Maryland</st1:State></st1:place>,</pre><pre style='margin-left:.5in'>below).</pre><pre style='margin-left:.5in'>The discrepancies were more serious, however, for two quads in <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State>:<span style='mso-spacerun:yes'>  </span>Broomes</pre><pre style='margin-left:.5in'>and <st1:place w:st="on">South River</st1:place>.<span style='mso-spacerun:yes'>  </span>For South River the DEM under estimates the amount of land below</pre><pre style='margin-left:.5in'>5 ft by 50%.<span style='mso-spacerun:yes'>  </span>However, it is within 5% and 1% for the areas between 5-10 and 10-</pre><pre style='margin-left:.5in'>15ft, respectively.<span style='mso-spacerun:yes'>  </span>This error appears to have resulted because the land is sufficiently</pre><pre style='margin-left:.5in'>steep that particular cells will have more than one contour crossing them.<span style='mso-spacerun:yes'>  </span>The DEM</pre><pre style='margin-left:.5in'>assigns an average elevation to the cell.<span style='mso-spacerun:yes'>  </span>Assuming that the contours cross the centers of</pre><pre style='margin-left:.5in'>cells randomly, one would normally expect that the amount of higher and lower ground</pre><pre style='margin-left:.5in'>being &quot;averaged in&quot; would approximately offset each other, so that the DEM should find</pre><pre style='margin-left:.5in'>the same amount of land within a given elevation range as the input DLG's.<span style='mso-spacerun:yes'>  </span>Indeed, this</pre><pre style='margin-left:.5in'>appears to be the case for land at 10-15 ft.<span style='mso-spacerun:yes'>  </span>For land below 5ft, however, there is</pre><pre style='margin-left:.5in'>higher ground but no lower ground to be &quot;averaged in.&quot;<span style='mso-spacerun:yes'>  </span>Therefore, an upward bias is</pre><pre style='margin-left:.5in'>created for the lowest areas.<span style='mso-spacerun:yes'>  </span>Such an upward bias in the lowest contour range could</pre><pre style='margin-left:.5in'>have been avoided with an algorithm that calculated elevations for points rather than</pre><pre style='margin-left:.5in'>cells or using a much smaller cell size.<span style='mso-spacerun:yes'>  </span>Doing so, however, would have increased the</pre><pre style='margin-left:.5in'>costs of this study several fold The net impact was that the DEM, in effect, estimated</pre><pre style='margin-left:.5in'>the 5-ft contour to be approximately 7.3 ft above the vertical datum for <st1:place w:st="on">South River</st1:place>.</pre><pre style='margin-left:.5in'>The Broomes quad had a similar upward bias, effectively treating the 5-ft contour as a</pre><pre style='margin-left:.5in'>5.8-ft contour.<span style='mso-spacerun:yes'>  </span>The experience with those two quads in <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State> should serve as a</pre><pre style='margin-left:.5in'>caution that in <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State>, our results may be much less accurate in areas with slopes</pre><pre style='margin-left:.5in'>steep enough to have two contours within 30 meters (e.g. slopes greater than 6% with</pre><pre style='margin-left:.5in'>5-ft contours, or 12% with 10ft contours), especially in the area above the lowest</pre><pre style='margin-left:.5in'>contour.<span style='mso-spacerun:yes'>  </span>(Our first-contour truncating mitigates this upward bias below the first contour;</pre><pre style='margin-left:.5in'>for reasons explained in the metadata for the <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State> study (dem_MD_shw_cm). In Pensylvania, that caution may be applicable to much of Bucks County. The results of the &quot;11 quadrangle&quot; analysis are shown in DEM_Comparison_with_DLG_11_quads.xls., which is included in the zip file distributed with this dataset.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Quantitative_Vertical_Positional_Accuracy_Assessment:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Vertical_Positional_Accuracy_Explanation:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>See vertical accuracy report.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Lineage:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> US Geological Survey</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> Multiple</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Large Scale USGS Digital Line Graph (DLG) Other_Citation_Details: Source contours are 10 feet, and 20 feet depending on the 7.5' topographic quadrangle used. The zip file with which this metadata is distributed will include a graphic defining the contour intervals of the input data, PA_Elevation_Data_Quality.jpg</p> <p class=MsoNormal style='margin-left:.5in'><i><span lang=DE style='mso-ansi-language: DE'>Online_Linkage:</span></i><span lang=DE style='mso-ansi-language:DE'> </span><a href="%3chttp://edc.usgs.gov/geodata/dlg_large/states/PA.html%3e" target=viewer><span lang=DE style='mso-ansi-language:DE'>&lt;http://edc.usgs.gov/geodata/dlg_large/states/PA.html&gt;</span></a><span style='mso-ansi-language:DE'> <span lang=DE><o:p></o:p></span></span></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> Digital data and paper</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>Multiple</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevation Contours used in Spatial data and attributes. Some contours digitized from</pre><pre style='margin-left:.5in'>Digital Raster Graphics (DRGs) and hardcopy. The zip file with which this metadata is distributed includes a the file &quot;PA_Data_Quality.jpg&quot; which defines the contour intervals of the input data.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Henan Institute of Geograophy</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> Multiple</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Coastal Digital Line Graphs</p> <p class=MsoNormal style='margin-left:.5in'><i>Online_Linkage:</i> <a href="%3chttp://edc.usgs.gov/geodata/dlg_large/states/PA.html%3e" target=viewer>&lt;http://edc.usgs.gov/geodata/dlg_large/states/PA.html&gt;</a> </p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> Digital data</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>Multiple</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevation Contours used in Spatial data and attributes for USGS quads where USGS</pre><pre style='margin-left:.5in'>DLG was unavailable.<span style='mso-spacerun:yes'>  </span>See &quot;Institute_of_Geography_DLG.doc&quot; for a list of quads</pre><pre style='margin-left:.5in'>where we used these DLG's. Source contours are 10 feet and 20 feet depending on the 7.5' topographic quadrangle</pre><pre style='margin-left:.5in'>used. The zip file with which this metadata is distributed will include a graphic defining</pre><pre style='margin-left:.5in'>contour intervals of the input data: PA_Elevation_Data_Quality.jpg</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> National Oceanic Service</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> Unknown</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Time:</i> Unknown</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>NOS Tide Observation Data</p> <p class=MsoNormal style='margin-left:.5in'><i><span lang=DE style='mso-ansi-language: DE'>Online_Linkage:</span></i><span lang=DE style='mso-ansi-language:DE'> </span><a href="%3chttp://co-ops.nos.noaa.gov/bench.html%3e" target=viewer><span lang=DE style='mso-ansi-language:DE'>&lt;http://co-ops.nos.noaa.gov/bench.html&gt;</span></a><span style='mso-ansi-language:DE'> <span lang=DE><o:p></o:p></span></span></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> 24000</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Time_Period_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Range_of_Dates/Times:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Beginning_Date:</i> 1960</p> <p class=MsoNormal style='margin-left:.5in'><i>Ending_Date:</i> 1978</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>Relative to the 1960-1978 Tidal Epoch</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Spatial coordinates and elevations of MTL relative to mean lower low water (MLLW),</pre><pre style='margin-left:.5in'>the elevation of MLLW relative to several benchmarks nearby, and the elevations of</pre><pre style='margin-left:.5in'>these benchmarks above NAVD88 for 12 tide gages in or around <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> National Oceanic Service</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> 2000</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>NOS Tide Estimation Data. Tide Tables 2000, High and Low Water Predictions, East Coast of North and South America including <st1:place w:st="on">Greenland</st1:place></p> <p class=MsoNormal style='margin-left:.5in'><i>Geospatial_Data_Presentation_Form:</i> document</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> NA</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> paper report, whose tables contained latitude, longitude, and tide range.</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Time_Period_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Single_Date/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Calendar_Date:</i> 2000</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>publication date</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Horizontal location, and spring high tide ranges for 32 tide gages in or around</pre><pre style='margin-left:.5in'><st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> <st1:country-region w:st="on"><st1:place w:st="on">U.S.</st1:place></st1:country-region> Environmental Protection Agency</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> 2006</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Coastal Wetlands Data: <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Time_Period_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Single_Date/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Calendar_Date:</i> 1980</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>__________</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Horizontal location of upper and lower limits of tidal wetlands. See Readme.doc (distributed in the zip file with this data set), for directions on how to</pre><pre style='margin-left:.5in'>download the Coastal Wetlands Data .<span style='mso-spacerun:yes'>  </span>See also the technical report for this project J.G. Titus and J. Wang. Titus, J.G. and J. Wang, 2008: Maps of lands close to sea level along the middle Atlantic coast of the <st1:country-region w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region>: an elevation data set to use while waiting for LIDAR. In: Background Documents Supporting Climate Change Science Program</pre><pre style='margin-left:.5in'>Synthesis and Assessment Product 4.1: Coastal Elevations and Sensitivity to Sea</pre><pre style='margin-left:.5in'>Level Rise [J.G. Titus and E.M. Strange (eds.)]. EPA430R07004, U.S. Environmental Protection Agency, Washington, DC.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Proudman Oceanographic Laboratory (POL)</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> 2000</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Permanent Service for <st1:place w:st="on"><st1:PlaceName w:st="on">Mean</st1:PlaceName> <st1:PlaceType w:st="on">Sea</st1:PlaceType></st1:place> Level (PSMSL)-- Sea Level Rise Trend Data</p> <p class=MsoNormal style='margin-left:.5in'><i>Other_Citation_Details:</i></p> <p class=MsoNormal style='margin-left:.5in'>The PSMSL is a member of the Federation of Astronomical and Geophysical Data Analysis Services (FAGS) established by the International Council of Scientific Unions (ICSU).</p> <p class=MsoNormal style='margin-left:.5in'><i><span lang=DE style='mso-ansi-language: DE'>Online_Linkage:</span></i><span lang=DE style='mso-ansi-language:DE'> </span><a href="%3chttp://www.nbi.ac.uk/psmsl/datainfo/rlr.trends%3e" target=viewer><span lang=DE style='mso-ansi-language:DE'>&lt;http://www.nbi.ac.uk/psmsl/datainfo/rlr.trends&gt;</span></a><span style='mso-ansi-language:DE'> <span lang=DE><o:p></o:p></span></span></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Time_Period_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Single_Date/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Calendar_Date:</i> unknown</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>publication date</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Spatial location and estimates of the rate of sea level rise.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Source_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> City of Philadelphia Water Department - Information Systems and Technology</p> <p class=MsoNormal style='margin-left:.5in'><i>Publication_Date:</i> 1997</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Topographic Contours, 2-foot</p> <p class=MsoNormal style='margin-left:.5in'><i><span lang=DE style='mso-ansi-language: DE'>Online_Linkage:</span></i><span lang=DE style='mso-ansi-language:DE'> </span><a href="%3chttp://www.pasda.psu.edu/philacity/philadownload.cgi/phila-topocontours2ft.zip%3e" target=viewer><span lang=DE style='mso-ansi-language:DE'>&lt;http://www.pasda.psu.edu/philacity/philadownload.cgi/phila-topocontours2ft.zip&gt;</span></a><span style='mso-ansi-language:DE'> <span lang=DE><o:p></o:p></span></span></p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Scale_Denominator:</i> 2,400</p> <p class=MsoNormal style='margin-left:.5in'><i>Type_of_Source_Media:</i> vector digital data</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Time_Period_of_Content:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Time_Period_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Single_Date/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Calendar_Date:</i> 1997</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Currentness_Reference:</i></p> <p class=MsoNormal style='margin-left:.5in'>ground condition</p> <p class=MsoNormal style='margin-left:.5in'><i>Source_Contribution:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>2 foot contour interval elevation map was used to generate a DEM for <st1:City w:st="on"><st1:place w:st="on">Philadelphia</st1:place></st1:City>. The elevation of this data set is based on Philadelphia Vertical</pre><pre style='margin-left:.5in'>Datum<span style='mso-spacerun:yes'>  </span>which is 5.71 feet above NGVD29.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Process_Step:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Description:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Process of Input Elevation Data</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>1) Input elevation contour lines were either 1:24,000 USGS DLGs or 1:24,000 DLG's</pre><pre style='margin-left:.5in'>created by the <st1:place w:st="on"><st1:PlaceType w:st="on">Institute</st1:PlaceType> of <st1:PlaceName w:st="on">Geography</st1:PlaceName></st1:place> (using USGS DRG's). They were appended and</pre><pre style='margin-left:.5in'>then projected into Albers projection except for the City of <st1:City w:st="on"><st1:place w:st="on">Philadelphia</st1:place></st1:City>, where we had</pre><pre style='margin-left:.5in'>2-foot contours.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2) City of <st1:City w:st="on"><st1:place w:st="on">Philadelphia</st1:place></st1:City>. The City's 2 foot-contour interval elevation map was used to</pre><pre style='margin-left:.5in'>generate the DEM. First, the contours was projected into Albers projection. A value of</pre><pre style='margin-left:.5in'>5.71 was added to the elevation value of contour lines to convert from the city datum to</pre><pre style='margin-left:.5in'>NGVD29. Then the upper limit of tidal wetlands was moved seawards where it</pre><pre style='margin-left:.5in'>overlaps with the elevation contour lines.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Process_Contact:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person_Primary:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person:</i> Jue Wang</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization:</i> GIS Practice, ICF Consulting, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Position:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Address:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Address_Type:</i> mailing and physical address</p> <p class=MsoNormal style='margin-left:.5in'><i>Address:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><st1:Street w:st="on"><st1:address w:st="on">9300 Lee Highway</st1:address></st1:Street></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>City:</i> <st1:City w:st="on"><st1:place w:st="on">Fairfax</st1:place></st1:City></p> <p class=MsoNormal style='margin-left:.5in'><i>State_or_Province:</i> VA</p> <p class=MsoNormal style='margin-left:.5in'><i>Postal_Code:</i> 22031</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Facsimile_Telephone:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><i>Hours_of_Service:</i> 9:30 - 5:30 EST</p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Step:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Description:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Process of Tidal Record: Calculating the Elevation of Spring High Water</pre><pre style='margin-left:.5in'>Supplemental Contour</pre><pre style='margin-left: .5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>1) Creation of Mean Tide Level Surface. National Oceanic Service (NOS) tide</pre><pre style='margin-left:.5in'>observation data, i.e., the latitudes and longitudes, the elevations of mean tide level</pre><pre style='margin-left:.5in'>(MTL) above mean lower low water (MLLW), the elevations of MLLW relative to</pre><pre style='margin-left:.5in'>several benchmarks, and the elevations above NAVD88 of these benchmarks of 12</pre><pre style='margin-left:.5in'>tide gages in or near <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State> were downloaded from the NOS website. The</pre><pre style='margin-left:.5in'>elevations of mean tide level relative to NAVD88 were calculated and then converted to</pre><pre style='margin-left:.5in'>a NGVD29 using USGS VERTCON program. A point coverage was then</pre><pre style='margin-left:.5in'>created with such data and projected into Albers projection. Using the point coverage</pre><pre style='margin-left:.5in'>as a reference, artificial contour lines were created with consideration of shorelines via</pre><pre style='margin-left:.5in'>heads-up digitizing and then used to interpolate the mean tide level surface using a</pre><pre style='margin-left:.5in'>Triangular Irregular Network (TIN).<span style='mso-spacerun:yes'>  </span>As the tidal epoch used for the MTL data was</pre><pre style='margin-left:.5in'>1960-1978, a separate sea level rise rate surface was created by interpolating actual</pre><pre style='margin-left:.5in'>sea level rise data (trend) from the Proudman Oceanographic Laboratory website and</pre><pre style='margin-left:.5in'>was used to adjust the mean tide level to years corresponding to other data sets, such</pre><pre style='margin-left:.5in'>as NWI data, so that the wetland boundary would represent spring high tide for the</pre><pre style='margin-left:.5in'>year the map imagery was taken.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2) Creation of <st1:place w:st="on"><st1:PlaceType w:st="on">Spring</st1:PlaceType> <st1:PlaceName w:st="on">Tide</st1:PlaceName> <st1:PlaceType w:st="on">Range</st1:PlaceType></st1:place> Surface. From Table 2 of &quot;Tide Tables 2000, High</pre><pre style='margin-left:.5in'>and Low Water Predictions, East Coast of North and <st1:place w:st="on">South America</st1:place> including</pre><pre style='margin-left: .5in'><st1:place w:st="on">Greenland</st1:place>&quot;, the latitudes, longitudes and spring high tide ranges of 32 tide gauges in or</pre><pre style='margin-left:.5in'>near <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State> were obtained and used to create a point coverage. Using the point</pre><pre style='margin-left:.5in'>coverage as a reference, artificial contour lines were created with consideration of</pre><pre style='margin-left:.5in'>shorelines and then used to interpolate the spring high tide range surface with the TIN</pre><pre style='margin-left:.5in'>method.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3) Creation of a Spring High Water Level Surface. A spring high water level surface</pre><pre style='margin-left:.5in'>was created by adding half of spring tide range onto mean tide level surface.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Process_Contact:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person_Primary:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person:</i> Jue Wang</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization:</i> GIS Practice, ICF Consulting, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Position:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Facsimile_Telephone:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Step:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Description:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Processing Tidal Wetlands:<span style='mso-spacerun:yes'>  </span>Calculating the Horizontal Position</pre><pre style='margin-left:.5in'>of Spring High Water Supplemental Contour</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>(1)We identified the upper limit of tidal wetland by extracting the boundaries between</pre><pre style='margin-left:.5in'>tidal polygons (consisting of tidal wetland and tidal open water) and non-tidal polygons</pre><pre style='margin-left:.5in'>(consisting of dry land, non-tidal wetland, and non-tidal open water).</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>(2) We used the upper and lower limits of tidal wetlands to generate supplemental</pre><pre style='margin-left:.5in'>contours. We assigned these contours elevations derived from spring high tide level and</pre><pre style='margin-left:.5in'>mean tide level surface grids respectively. The upper wetland boundary was used as a</pre><pre style='margin-left:.5in'>supplemental contour. The lower boundary was used for reporting the area of wetlands</pre><pre style='margin-left:.5in'>but not for elevations, because the project manager decided not to report wetland</pre><pre style='margin-left:.5in'>elevations.</pre><pre style='margin-left:.5in'>See also the metadata accompanying the Coastal Wetlands Data: <st1:State w:st="on"><st1:place w:st="on">Pennsylvania</st1:place></st1:State></pre><pre style='margin-left:.5in'>polygon<span style='mso-spacerun:yes'>  </span>dataset</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Process_Contact:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person_Primary:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person:</i> Jue Wang</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization:</i> ICF Consulting, Inc., GIS Practice</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Position:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Facsimile_Telephone:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Step:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Process_Description:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Interpolation of Digital Elevation Model</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>1) With the exception of those areas with two-foot contour intervals (i.e. <st1:City w:st="on"><st1:place w:st="on">Philadelphia</st1:place></st1:City>),</pre><pre style='margin-left:.5in'>the study area was divided into four parts (tidal wetlands, lowland, midland, and</pre><pre style='margin-left:.5in'>upland). &quot;Tidal Wetlands&quot; represents the tidal wetlands as classified from the wetland layer. </pre><pre style='margin-left:.5in'>Lowland represents the area between the tidal wetlands and the lowest USGS</pre><pre style='margin-left:.5in'>contour available, which is generally above the tidal wetlands. Depending on the contour</pre><pre style='margin-left:.5in'>interval of the input data, this lowest contour may have been 5 feet, 10 feet, or 20 feet -</pre><pre style='margin-left:.5in'>- in all cases relative to NGVD29.</pre><pre style='margin-left:.5in'><st1:City w:st="on"><st1:place w:st="on">Midland</st1:place></st1:City> represents the area above the lowest contour we used and below the highest</pre><pre style='margin-left:.5in'>USGS contour lines (40 foot NGVD29) used.</pre><pre style='margin-left:.5in'><st1:City w:st="on"><st1:place w:st="on">Upland</st1:place></st1:City> represents land above the midland contour (i.e., above the 40 foot NGVD29</pre><pre style='margin-left:.5in'>contour).</pre><pre style='margin-left:.5in'>Boundary coverages were created for tidal wetlands, lowland, and midland using</pre><pre style='margin-left:.5in'>appropriate elevation contours or upper and lower limits of tidal wetland. However, we</pre><pre style='margin-left:.5in'>are not making the tidal wetland interpolations available in this dataset due to the lack of</pre><pre style='margin-left:.5in'>a theoretical justification for believing that interpolation to have any information content.</pre><pre style='margin-left:.5in'>(At best, the wetland elevation interpolations might be used for graphical representations</pre><pre style='margin-left:.5in'>of the impact of sea level rise.) We will retain a companion dataset with elevations</pre><pre style='margin-left:.5in'>stored as floating point double precision, which may be made available for the sole</pre><pre style='margin-left:.5in'>purpose of evaluating any graphical representations that use wetland elevations. We</pre><pre style='margin-left:.5in'>provide a<span style='mso-spacerun:yes'>  </span>a polygon wetland dataset so that the user can<span style='mso-spacerun:yes'>  </span>distinguish tidal wetlands</pre><pre style='margin-left:.5in'>from open water for cells with no data.</pre><pre style='margin-left:.5in'>In the case <st1:City w:st="on"><st1:place w:st="on">Philadelphia</st1:place></st1:City>, where the underlying topographic information had a two-foot</pre><pre style='margin-left:.5in'>contour interval, the lowland and midland were treated together as a single category.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2) The DEMs were interpolated with a predetermined cell size of 30 meters for the </pre><pre style='margin-left:.5in'>lowland, midland, and upland areas using contour lines described in Process step 1 (the </pre><pre style='margin-left:.5in'>section &quot;Process of Input Elevation Data&quot;) and the supplemental contours explained in </pre><pre style='margin-left:.5in'>process step 3. A common starting coordinate was set for all three DEM interpolation </pre><pre style='margin-left:.5in'>processes to ensure alignment of the separate layers after processing. The minimum and </pre><pre style='margin-left:.5in'>maximum limits were set for each process according to the input elevation data to </pre><pre style='margin-left:.5in'>ensure the resulting elevations were in accordance with the input data. See &quot;first contour </pre><pre style='margin-left:.5in'>truncating&quot;, paragraph 5, below. This means whenever<span style='mso-spacerun:yes'>  </span>TOPOGRID calculated a value greater than the first contour within the &quot;lowland&quot;, we reset the value to 0.001 less than the first contour. Whenever TOPOGRID calculated a midland value less than the first contour, we reset the value to 0.001 greater than the first contour. The iteration was set to 40, the </pre><pre style='margin-left:.5in'>horizontal standard error tolerance was set to 2 to minimize the depression caused by </pre><pre style='margin-left:.5in'>inappropriate tend calculation, and the drainage enforcement option was turned on to </pre><pre style='margin-left:.5in'>remove isolated depressions. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The following represents the options used in TOPOGRID: </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>topogrid dem_mid_ft 30 </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>contour topo_cntr elevation </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>xyzlimits 1712800 # 1960000 # 5.0001 </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>boundary topo_bnd_mid </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>iterations 40 </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>tolerances # 2 </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>enforce on </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>end </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3) The interpolated DEMs were displayed against input elevation data and visually </pre><pre style='margin-left:.5in'>checked. These visual checks would show gross errors, but not necessarily errors in </pre><pre style='margin-left:.5in'>which the amount of low land is over- or underestimated by 10-40 percent </pre><pre style='margin-left:.5in'>(additionally, see Data Quality, Positional Accuracy section). If obvious errors such as </pre><pre style='margin-left:.5in'>artificial depressions occurred, supplemental elevation lines were added by heads-up </pre><pre style='margin-left:.5in'>digitizing to the input contour lines and the interpolation was repeated. </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>4) First-contour truncating. As a result of the comparison between the initial DEM and the source contours for 11 USGS quadrangles (see vertical accuracy report), we decided to reset the DEM values to coincide with source contours. Our general approach was that whenever TOPOGRID </pre><pre style='margin-left:.5in'>calculated a value greater than the first contour within the &quot;lowland&quot;, we reset the value </pre><pre style='margin-left:.5in'>to 0.001 less than the first contour. Whenever TOPOGRID calculated a midland value </pre><pre style='margin-left:.5in'>less than the first contour, we reset the value to 0.001 greater than the first contour. </pre><pre style='margin-left:.5in'>Given the rounding of this integer dataset, all such values are effectively rounded to the </pre><pre style='margin-left:.5in'>bounding contour value between midland and lowland (e.g. 5 feet). Although this </pre><pre style='margin-left:.5in'>approach leaves us with some plateaus, we have fewer plateaus than we had when we </pre><pre style='margin-left:.5in'>did not divide the data; and dividing the data left us with fewer cases of midland and </pre><pre style='margin-left:.5in'>lowland values being outside of their appropriate ranges.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>5) The DEMs of each separate part were eventually merged into the final DEM with the </pre><pre style='margin-left:.5in'>MERGE function within the ESRI GRID module.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Cloud_Cover:</i> NA</p> <p class=MsoNormal><a href="#Top">Back to Top</a> <a name="Spatial_Data_Organization_Information"></a></p> <div class=MsoNormal align=center style='text-align:center'><span style='mso-bookmark:Spatial_Data_Organization_Information'> <hr size=2 width="100%" align=center> </span></div> <span style='font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family: "Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US; mso-bidi-language:AR-SA'><span style='mso-bookmark:Spatial_Data_Organization_Information'></span></span> <p class=MsoNormal><i>Spatial_Data_Organization_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Direct_Spatial_Reference_Method:</i> Raster</p> <p class=MsoNormal style='margin-left:.5in'><i>Raster_Object_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Raster_Object_Type:</i> Grid Cell</p> <p class=MsoNormal style='margin-left:.5in'><i>Row_Count:</i> 8847</p> <p class=MsoNormal style='margin-left:.5in'><i>Column_Count:</i> 4986</p> <p class=MsoNormal style='margin-left:.5in'><i>Vertical_Count:</i> 1</p> <p class=MsoNormal><a href="#Top">Back to Top</a> <a name="Spatial_Reference_Information"></a></p> <div class=MsoNormal align=center style='text-align:center'><span style='mso-bookmark:Spatial_Reference_Information'> <hr size=2 width="100%" align=center> </span></div> <span style='font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family: "Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US; mso-bidi-language:AR-SA'><span style='mso-bookmark:Spatial_Reference_Information'></span></span> <p class=MsoNormal><i>Spatial_Reference_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Horizontal_Coordinate_System_Definition:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Planar:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Map_Projection:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Map_Projection_Name:</i> Albers Conical Equal Area</p> <p class=MsoNormal style='margin-left:.5in'><i>Albers_Conical_Equal_Area:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Standard_Parallel:</i> 29.500000</p> <p class=MsoNormal style='margin-left:.5in'><i>Standard_Parallel:</i> 45.500000</p> <p class=MsoNormal style='margin-left:.5in'><i>Longitude_of_Central_Meridian:</i> -96.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>Latitude_of_Projection_Origin:</i> 23.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>False_Easting:</i> 0.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>False_Northing:</i> 0.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>Planar_Coordinate_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Planar_Coordinate_Encoding_Method:</i> row and column</p> <p class=MsoNormal style='margin-left:.5in'><i>Coordinate_Representation:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Abscissa_Resolution:</i> 30.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>Ordinate_Resolution:</i> 30.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>Planar_Distance_Units:</i> meters</p> <p class=MsoNormal style='margin-left:.5in'><i>Geodetic_Model:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Horizontal_Datum_Name:</i> North American Datum of 1983</p> <p class=MsoNormal style='margin-left:.5in'><i>Ellipsoid_Name:</i> Geodetic Reference System 80</p> <p class=MsoNormal style='margin-left:.5in'><i>Semi-major_Axis:</i> 6378137.000000</p> <p class=MsoNormal style='margin-left:.5in'><i>Denominator_of_Flattening_Ratio:</i> 298.257222</p> <p class=MsoNormal style='margin-left:.5in'><i>Vertical_Coordinate_System_Definition:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Altitude_System_Definition:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Altitude_Datum_Name:</i> SHW</p> <p class=MsoNormal style='margin-left:.5in'><i>Altitude_Resolution:</i> 1 cm</p> <p class=MsoNormal style='margin-left:.5in'><i>Altitude_Distance_Units:</i> cm</p> <p class=MsoNormal style='margin-left:.5in'><i>Altitude_Encoding_Method:</i> Explicit elevation coordinate included with horizontal coordinates</p> <p class=MsoNormal><a href="#Top">Back to Top</a> <a name="Entity_and_Attribute_Information"></a></p> <div class=MsoNormal align=center style='text-align:center'><span style='mso-bookmark:Entity_and_Attribute_Information'> <hr size=2 width="100%" align=center> </span></div> <span style='font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family: "Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US; mso-bidi-language:AR-SA'><span style='mso-bookmark:Entity_and_Attribute_Information'></span></span> <p class=MsoNormal><i>Entity_and_Attribute_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Detailed_Description:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Entity_Type:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Entity_Type_Label:</i> dem_pa_shw_cm.vat</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Label:</i> Rowid</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Definition:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Internal feature number.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Attribute_Definition_Source:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>ESRI</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Attribute_Domain_Values:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Unrepresentable_Domain:</i></p> <p class=MsoNormal style='margin-left:.5in'>Sequential unique whole numbers that are automatically generated.</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Label:</i> VALUE</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Label:</i> Value</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Definition:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevation</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Attribute_Definition_Source:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Interpolated from input data sets</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Attribute_Value_Accuracy_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Value_Accuracy:</i> 1 cm</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Value_Accuracy_Explanation:</i></p> <p class=MsoNormal style='margin-left:.5in'>Interpolated from source data sets and rounded to nearest 1 cm</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Label:</i> COUNT</p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute_Definition:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Count of cells with common elevation</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Attribute_Definition_Source:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>ESRI</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Overview_Description:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Entity_and_Attribute_Overview:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevations generated from input data sets (contours and spot elevations) and</pre><pre style='margin-left:.5in'>interpolated into a raster DEM and rounded to nearest cm.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Entity_and_Attribute_Detail_Citation:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>See process steps.</pre> <p class=MsoNormal><script> fix(original) </script><a href="#Top">Back to Top</a> </p> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center> </div> <p class=MsoNormal><a name=34372992></a><i>Distribution_Information:</i> </p> <p class=MsoNormal style='margin-left:.5in'><i>Distributor:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization_Primary:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization:</i> US Environmental Protection Agency, Climate Change Division</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Address:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Address_Type:</i> mailing address</p> <p class=MsoNormal style='margin-left:.5in'><i>Address:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>USEPA (6207-J)</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Address:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><st1:Street w:st="on"><st1:address w:st="on">1200 Pennsylvania Ave. NW</st1:address></st1:Street></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>City:</i> <st1:State w:st="on"><st1:place w:st="on">Washington</st1:place></st1:State></p> <p class=MsoNormal style='margin-left:.5in'><i>State_or_Province:</i> DC</p> <p class=MsoNormal style='margin-left:.5in'><i>Postal_Code:</i> 20460</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 202-343-9990</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Facsimile_Telephone:</i> 202-343-2338</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> climatechange@epa.gov</p> <p class=MsoNormal style='margin-left:.5in'><i>Resource_Description:</i> The dataset is being distributed by the US Environmental Protection Agency.</p> <p class=MsoNormal style='margin-left:.5in'><i>Distribution_Liability:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Although this data was created under the direction of the EPA, no warranty expressed</pre><pre style='margin-left:.5in'>or implied is made regarding the accuracy or utility of the data. Neither EPA nor the</pre><pre style='margin-left:.5in'>data developers shall be held liable for any use of the data and</pre><pre style='margin-left:.5in'>information described and/or contained herein.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Standard_Order_Process:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Digital_Form:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Digital_Transfer_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Transfer_Size:</i> 1.413</p> <p class=MsoNormal style='margin-left:.5in'><i>Custom_Order_Process:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Data available to CCSP collaborators from Alan Cohn at 202-343-9814.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>Technical_Prerequisites:</i></p> <p class=MsoNormal style='margin-left:.5in'>Requires software capable of displaying raster data.</p> <p class=MsoNormal><a href="#Top">Back to Top</a> <a name="Metadata_Reference_Information"></a></p> <div class=MsoNormal align=center style='text-align:center'><span style='mso-bookmark:Metadata_Reference_Information'> <hr size=2 width="100%" align=center> </span></div> <span style='font-size:12.0pt;font-family:"Times New Roman";mso-fareast-font-family: "Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US; mso-bidi-language:AR-SA'><span style='mso-bookmark:Metadata_Reference_Information'></span></span> <p class=MsoNormal><i>Metadata_Reference_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Metadata_Date:</i> 20080902</p> <p class=MsoNormal style='margin-left:.5in'><i>Metadata_Contact:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Information:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person_Primary:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Person:</i> Russ Jones, Jim Titus, and Jue Wang</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Organization:</i> Stratus Consulting Inc. (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Position:</i> Managing Analyst (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Address:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Address_Type:</i> mailing and physical address</p> <p class=MsoNormal style='margin-left:.5in'><i>Address:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><st1:Street w:st="on"><st1:address w:st="on">1881 9th St. Suite 201</st1:address></st1:Street> (Jones)</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><i>City:</i> <st1:City w:st="on"><st1:place w:st="on">Boulder</st1:place></st1:City></p> <p class=MsoNormal style='margin-left:.5in'><i>State_or_Province:</i> CO</p> <p class=MsoNormal style='margin-left:.5in'><i>Postal_Code:</i> 80306</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 303-381-80000 (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Voice_Telephone:</i> 202-343-9307 (Titus)</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Facsimile_Telephone:</i> 303-381-8200 (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> rjones@stratusconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><i>Contact_Electronic_Mail_Address:</i> Titus.Jim@epamail.epa.gov</p> <p class=MsoNormal style='margin-left:.5in'><i>Hours_of_Service:</i> 9:00 - 5:00 MST</p> <p class=MsoNormal style='margin-left:.5in'><i>Metadata_Standard_Name:</i> FGDC Content Standards for Digital Geospatial Metadata</p> <p class=MsoNormal style='margin-left:.5in'><i>Metadata_Standard_Version:</i> FGDC-STD-001-1998</p> <p class=MsoNormal style='margin-left:.5in'><i>Metadata_Time_Convention:</i> local time</p> <p class=MsoNormal style='margin-left:.5in'><i>Metadata_Extensions:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Online_Linkage:</i> <a href="http://www.esri.com/metadata/esriprof80.html" target=viewer>http://www.esri.com/metadata/esriprof80.html</a> </p> <p class=MsoNormal style='margin-left:.5in'><i>Profile_Name:</i> ESRI Metadata Profile</p> <p class=MsoNormal><a href="#Top">Back to Top</a> </p> </div> </body> </html>