ÿþ<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="MD_elevation_metadata_files/filelist.xml"> <link rel=Edit-Time-Data href="MD_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>Maryland Elevation Data underlying analysis by J</title> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <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="address"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <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"/> <!--[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>4</o:Revision> <o:TotalTime>4</o:TotalTime> <o:Created>2009-04-17T11:33:00Z</o:Created> <o:LastSaved>2009-04-17T11:39:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>9364</o:Words> <o:Characters>53379</o:Characters> <o:Company>EPA</o:Company> <o:Lines>444</o:Lines> <o:Paragraphs>125</o:Paragraphs> <o:CharactersWithSpaces>62618</o:CharactersWithSpaces> <o:Version>11.9999</o:Version> </o:DocumentProperties> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <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> <!-- /* Font Definitions */ @font-face {font-family:Wingdings; panose-1:5 0 0 0 0 0 0 0 0 0; mso-font-charset:2; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:0 268435456 0 0 -2147483648 0;} /* 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";} pre {font-size:10.0pt; font-family:"Courier New"; mso-fareast-font-family:"Times New Roman";} span.SpellE {mso-style-name:""; mso-spl-e:yes;} span.GramE {mso-style-name:""; mso-gram-e:yes;} @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:1370372783; mso-list-template-ids:681335380;} @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;} 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'>Maryland</span></st1:State><span style='mso-bookmark:Top'> Elevation Data underlying analysis by J.G. Titus and J. Wang 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;</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 lfo1;tab-stops:list .5in'><a href="#Identification_Information"><span class=SpellE>Identification_Information</span></a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1;tab-stops:list .5in'><a href="#Data_Quality_Information"><span class=SpellE>Data_Quality_Information</span></a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1;tab-stops:list .5in'><a href="#Spatial_Data_Organization_Information"><span class=SpellE>Spatial_Data_Organization_Information</span></a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1;tab-stops:list .5in'><a href="#Spatial_Reference_Information"><span class=SpellE>Spatial_Reference_Information</span></a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1;tab-stops:list .5in'><a href="#Entity_and_Attribute_Information"><span class=SpellE>Entity_and_Attribute_Information</span></a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1;tab-stops:list .5in'><a href="#33918688"><span class=SpellE>Distribution_Information</span> </a></li> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1;tab-stops:list .5in'><a href="#Metadata_Reference_Information"><span class=SpellE>Metadata_Reference_Information</span></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><span class=SpellE><i>Identification_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Citation:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> US Environmental Protection Agency</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> February 2008</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Maryland Elevation Data underlying analysis by J.G. Titus and J. Wang 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;</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Geospatial_Data_Presentation_Form</i></span><i>:</i> raster digital data</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Other_Citation_Details</i></span><i>:</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><span lang=DE style='mso-ansi-language: DE'>Online_Linkage:</span></i><span lang=DE style='mso-ansi-language:DE'> <a href="http://maps.risingsea.net/data.html">http://maps.risingsea.net/data.html</a> <o:p></o:p></span></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Larger_Work_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> US Environmental Protection Agency</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</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'><span class=SpellE><i>Other_Citation_Details</i></span><i>:</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 (<span class=GramE>eds</span>.)]. <span class=GramE>EPA430R07004, <st1:country-region w:st="on">U.S.</st1:country-region> Environmental <st1:place w:st="on"><st1:City w:st="on">Protection Agency</st1:City>, <st1:State w:st="on">Washington</st1:State></st1:place>, DC.</span></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 Maryland Digital Elevation Model (Environmental Systems Research Institute [ESRI] Grid format) represents an elevation map of the <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State> coastal zone created for the purposes of analyzing vulnerability to coastal flooding and rising sea level. The domain of the data set extends from the upper tidal wetland boundary up to 40 foot NGVD29, 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'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>This data set has been derived from several sources of elevation data.<span style='mso-spacerun:yes'>  </span>Along the <st1:place w:st="on">Eastern Shore</st1:place> south of Rock Hall, we used LIDAR developed by the Maryland Department of Natural Resources.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>In the rest of the state (as well as the original version of this study) we used United States Geological Survey (USGS) 1:24,000 Digital Line Graphs (DLG), Digitized USGS <span class=SpellE>DLG's</span> (digitized in China by the Henan Institute of Geography) from Digital Raster Graphics and hardcopy 1:24,000 USGS topographic quadrangles), Maryland Department of Natural Resources (MDNR) elevation data, county elevation data provided by Harford, Baltimore, and Anne Arundel Counties, and a map of Kent Island prepared for the National Flood Insurance Rate Map of <span class=SpellE>Queene</span> Anne's County. In addition, the analysis created a supplemental contour representing the elevation of spring high water (SHW), which is generally between 1 and 3 feet above NGVD29 in <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State>. We defined the horizontal position of that contour by extracting the inland limit of the tidal wetland polygons of a separate Coastal Wetlands data set we created for this project (based on data from the US Fish and Wildlife Service National Wetlands Inventory [NWI] and the MD-DNR). We defined the vertical position of the supplemental contour by creating a &quot;tidal elevation surface&quot; using the National Ocean Service's (NOS) estimated tide ranges, NOS estimated sea level trends, <span class=GramE>the</span> NOS published benchmark sheets and the National Geodetic Survey North American Vertical Datum Conversion Utility (VERTCON) program to convert the Mean Tide Level (MTL) above NAVD88 to NGVD29.<span style='mso-spacerun:yes'>  </span>All elevation information was converted to a common vertical reference, usually NGVD29, and the DEM was generated from that input data using <span class=SpellE>ESRI's</span> interpolation algorithm TOPOGRID (within <span class=SpellE>ArcGIS</span> workstation GRID extension).<span style='mso-spacerun:yes'>   </span>See the companion dataset <span class=SpellE>demmd_nolidar</span> for the original dataset developed before the LIDAR became available.</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;<span style='mso-spacerun:yes'>  </span>For purposes of this data set, we assume that SHW is the upper (inland) boundary of tidal wetlands (including vegetated wetlands and intertidal beaches). Elevation is expressed in cm.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></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. Readme_MD_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. InterpolationMethods_MEMO.doc</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3. <span class=SpellE>MD_Data_Quality.jpg</span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>4. DEM_LidarComparisonTable.doc</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>5. 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. Institute_of_Geography_DLG.xls</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>7. <span class=SpellE>Lidar_dvd_cds.pdf</span>, which is a figure showing location of <span class=SpellE>lidar</span> data used</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>8. Worc02_03LIDAR.jpg, which is a figure showing 2002 vs. 2003 <span class=SpellE>lidar</span> data used</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>9. 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 (9) which are associated with all of the states may have been removed</pre><pre style='margin-left:.5in'><span class=GramE>and</span> included in a file called  <span class=SpellE>Common_supplemental_metadata.zip</span> </pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></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 Maryland Digital Elevation Model provides a base map layer for assessing the</pre><pre style='margin-left:.5in'><span class=GramE>possible</span> influences of potential sea level rise on coast regions.</pre><pre style='margin-left:.5in'>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 (except for those areas where LIDAR or 2-ft contour data is available) unless the audience is likely to understand the limitations of the data</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Supplemental_Information</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Elevations relative to year 2000.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 2000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Currentness_Reference</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>ground</span> 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'><span class=SpellE><i>Maintenance_and_Update_Frequency</i></span><i>:</i> None planned</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Spatial_Domain</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Bounding_Coordinates</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>West_Bounding_Coordinate</i></span><i>:</i> -77.494904</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>East_Bounding_Coordinate</i></span><i>:</i> -74.321993</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>North_Bounding_Coordinate</i></span><i>:</i> 39.874503</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>South_Bounding_Coordinate</i></span><i>:</i> 37.594593</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'><span class=SpellE><i>Theme_Keyword_Thesaurus</i></span><i>:</i> General</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Theme_Keyword</i></span><i>:</i> <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State> Elevation</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Theme_Keyword</i></span><i>:</i> DEM</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Theme_Keyword</i></span><i>:</i> Coastal Elevation</p> <p class=MsoNormal style='margin-left:.5in'><i>Place:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Place_Keyword_Thesaurus</i></span><i>:</i> Geographic Names Information System</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Place_Keyword</i></span><i>:</i> <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State> MD</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Access_Constraints</i></span><i>:</i> None.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Use_Constraints</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>None.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Point_of_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> James G. Titus</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</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'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Project Manager</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Address</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Address_Type</i></span><i>:</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><span class=SpellE>Mailcode</span> 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'><span class=SpellE><i>State_or_Province</i></span><i>:</i> DC</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Postal_Code</i></span><i>:</i> 20460</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 202-343-9307</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 202-343-2338</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> Titus.Jim@epamail.epa.gov</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Hours_of_Service</i></span><i>:</i> 9:00 - 6:00 Eastern</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Data_Set_Credit</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=SpellE><span class=GramE>Jue</span></span><span class=GramE> Wang, GIS Practice, ICF Consulting, Inc.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Native_Data_Set_Environment</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI <span class=SpellE>ArcCatalog</span> 9.3.0.1770</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Cross_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> February 2008</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><span class=SpellE><i>Data_Quality_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Accuracy</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Accuracy_Report</i></span><i>:</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;<span class=SpellE>MD_Data_Quality.jpg</span>&quot; <span class=GramE>for<span style='mso-spacerun:yes'>  </span>an</span> 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 <span class=SpellE>hydrologically</span>-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'><span class=GramE>TOPOGRID Plateau Problem.</span> 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--except for when stream data showed a stream in the correct location.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>Evaluation of other interpolation methods.</span> </pre><pre style='margin-left:.5in'>Several interpolation methods were evaluated before the TOPOGRID function was selected. Specifically, <span class=SpellE>Spline</span>, 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><span class=SpellE><i>Quantitative_Attribute_Accuracy_Assessment</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Accuracy_Explanation</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>An accuracy assessment was made between the <span class=GramE>source<span style='mso-spacerun:yes'>  </span><span class=SpellE>DLG's</span></span> and the DEM for a select number of quads. See &quot;DEM_Comparison_with_DLG_11_quads.xls<span class=GramE>&quot;<span style='mso-spacerun:yes'>  </span>which</span> accompanies this data set in the zip file.</pre><pre style='margin-left:.5in'>An additional assessment was made between the DEM and <span class=SpellE>lidar</span> 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><span class=SpellE><i>Logical_Consistency_Report</i></span><i>:</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 <span class=SpellE>diffent</span> 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><span class=SpellE><i>Completeness_Report</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>This elevation data set generally reflects that of the source data used in the layer development.</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'>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 <span class=SpellE>hydrologically</span>-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. The specifics to each state DEM are described under 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'><span class=GramE>TOPOGRID Plateau Problem.</span><span style='mso-spacerun:yes'>  </span>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.</pre><pre style='margin-left:.5in'>The TOPOGRID function within the ESRI GRID module tends to calculate a trend from neighboring contour lines.<span style='mso-spacerun:yes'>  </span>As a result, TOPOGRID frequently creates 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), no open water or 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--except for when stream data showed a stream in the correct location.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Other Issues:</pre><pre style='margin-left:.5in'>The decision to process 3 elevation areas separately within TOPOGRID (as described in the process step #4 - &quot;Interpolation of Digital Elevation Model&quot;) and then combine them into a single DEM removes the algorithm from its theoretical underpinning, because it separates each elevation zone from the context of the overall environment that TOPOGRID uses to generate a <span class=SpellE>hydrologically</span>-correct DEM.<span style='mso-spacerun:yes'>  </span>Because the objective of this DEM is to estimate elevations of lands close to sea level, rather than characterize drainage correctly, the ad hoc response to the TOPOGRID plateau problem is not as unreasonable as would have been the case were this data to be used for analyzing hydrology. Nevertheless, modification of the tolerance values and other parameters within TOPOGRID, and inclusion of additional vertical data in areas of known errors (determined through the use of diagnostic outputs within the TOPOGRID function), probably could have substantially diminished the plateau problem in the vicinity of the first topographic contour.<span style='mso-spacerun:yes'>  </span>Because the plateau problem around the edge of tidal wetlands was often caused largely by the relative complexity of the wetland supplemental contour compared with other contours, the case for dividing the data as we did is probably greater along the wetland boundary than along 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 into the separate elevation classes in those areas where we had two-foot contours.<span style='mso-spacerun:yes'>  </span>Therefore, this issue is inapplicable to <st1:PlaceName w:st="on">Baltimore</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType>, and <st1:place w:st="on"><st1:PlaceName w:st="on">Kent</st1:PlaceName> <st1:PlaceName w:st="on">Island</st1:PlaceName></st1:place>. Similarly, this approach does not apply to areas where <span class=SpellE>lidar</span> data was used (see the index of sources shown in <span class=SpellE>MD_Data_Quality.jpg</span> provided with this data set).</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Also see the sections on Positional Accuracy (Horizontal and Vertical) and process steps.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Positional_Accuracy</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Horizontal_Positional_Accuracy</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Horizontal_Positional_Accuracy_Report</i></span><i>:</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. 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.<span style='mso-spacerun:yes'>  </span>If the input map has 1:24,000 scale [well defined points within 12.2 meters<span class=GramE>]<span style='mso-spacerun:yes'>  </span>and</span> 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.) 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> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Quantitative_Horizontal_Positional_Accuracy_Assessment</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Horizontal_Positional_Accuracy_Value</i></span><i>:</i> 40-42.4 meters</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Horizontal_Positional_Accuracy_Explanation</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>In the event the horizontal error is as great as the width of a cell, the diagonal would be 42.4 m.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Vertical_Positional_Accuracy</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Vertical_Positional_Accuracy_Report</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>The vertical accuracy of 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.<span style='mso-spacerun:yes'>  </span>The procedures used to interpolate between contours do not necessarily correspond to the actual geometry of the land surfaces.<span style='mso-spacerun:yes'>  </span>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 <span class=GramE>of<span style='mso-spacerun:yes'>  </span><span class=SpellE>DEMs</span></span> generated by ICF Consulting, Russ Jones of Stratus Consulting Inc. compared <span class=SpellE>DEMs</span> 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 <span class=GramE>interval</span> in cases where the contour interval was 1 meter, 5 feet, or 2 meters.</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 <span class=GramE>a<span style='mso-spacerun:yes'>  </span>RMS</span> 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.<span style='mso-spacerun:yes'>  </span>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.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>In areas where we used <span class=SpellE>lidar</span> (see figures <span class=SpellE>lidar_dvd_cds.pdf</span> and Worc02_03LIDAR.jpg), accuracy is much better. According to the accuracy assessment conducted for the Maryland <span class=SpellE>lidar</span> program,<span style='mso-spacerun:yes'>  </span>(Dewberry and Davis, LIDAR 2003 Quality Assurance Report, MD DNR), the <span class=SpellE>lidar</span> for the 2003 data had an RMSE of 16.9 cm.<span style='mso-spacerun:yes'>  </span>When the worst 5% of the data is excluded, the RMSE is 14.3 cm over the remaining 95% of the data. In areas where only 2002 data was available, the data is less accurate according to Kevin Boone at MD DNR. However, the DNR did not conduct a vertical accuracy assessment.</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 input contour intervals and the DEM values, for 11 USGS 7.5' topographical quadrangles in the study area from <st1:State w:st="on">New York</st1:State> to <st1:State w:st="on"><st1:place w:st="on">North Carolina</st1:place></st1:State>. The technical paper by Titus and Wang (2008, listed in the citation section above) analyzes the 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, with the area of the input polygons.<span style='mso-spacerun:yes'>  </span>That error can be considered both in terms of the difference in area estimates, and as a vertical error.<span style='mso-spacerun:yes'>  </span>As a measure of the vertical error, Titus and Wang consider the effective elevation of the DLG contour that the DEM estimates, that is, at what elevation does the DEM find the same amount of land that the DLG polygons show to be below the first contour.</pre><pre style='margin-left:.5in'>The technical paper also calculates a plateau exaggeration factor:<span style='mso-spacerun:yes'>  </span>The ratio of the area (according to the DEM) within 0.1 feet above or below a contour, to the area that one would expect if elevations were uniformly distributed between the contour above and (if it exists) the contour below.<span style='mso-spacerun:yes'>  </span>Suppose for example, spring high water is 2 ft NGVD29, the contour interval is 5 feet, there are 3 ha between spring high water and the 5 ft contour, and 5 ha between the 5- and 10-foot contours, and the DEM finds 2 ha between 4.9 and 5.1 ft.<span style='mso-spacerun:yes'>  </span>The plateau exaggeration factor would be 10, because a uniform elevation distribution would imply 1 ha per foot of elevation change; but around the plateau we have 2 ha in a 0.2 ft elevation increment.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>This metadata discusses only the four quads analyzed in <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State>. In <st1:place w:st="on"><st1:PlaceType w:st="on">Ocean</st1:PlaceType> <st1:PlaceType w:st="on">City</st1:PlaceType></st1:place>, the DEM over-estimates the low land by 6%. Examining an overlay of the DEM and the <span class=SpellE>DLG's</span>, the discrepancy appears to be explained by one-cell boundary errors. The plateau exaggeration factors were 2.8, 3.1, and 4.4, for the spring high water, 5-ft, and 10-ft contours, respectively.<span style='mso-spacerun:yes'>  </span>The <st1:place w:st="on">Middle River</st1:place> (quarter quad) understates the 0-2 foot land by 93%. However, this discrepancy does not seem serious for two reasons:<span style='mso-spacerun:yes'>  </span>First, we did not split the data between lowland and midland for areas with 2 foot contours, so we did not expect a precise conformance. Second, the 26 ha difference is a very small area, and the DEM calculated another 26 ha between 2.0-2.7 feet. The plateau exaggeration factors were 2.3, 1.5, and 2.7, for the spring high water, 2-ft, and 4-ft contours, respectively.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The discrepancies were more serious, however, for two quads in <st1:State w:st="on">Maryland</st1:State>:<span style='mso-spacerun:yes'>  </span><span class=SpellE>Broomes</span> and <st1:place w:st="on">South River</st1:place>. The South River DEM under estimates the amount of land below 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-15 feet, respectively. This error appears to have resulted because the land is sufficiently steep that particular cells will have 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 as the input <span class=SpellE>DLG's</span>.<span style='mso-spacerun:yes'>  </span>Indeed, this appears to be the case for land at 10-15 feet.<span style='mso-spacerun:yes'>  </span>For land below 5 feet, however, there is higher ground but no lower ground to be &quot;averaged in.&quot;<span style='mso-spacerun:yes'>  </span>Therefore, an upward bias is created for the lowest areas.<span style='mso-spacerun:yes'>  </span>Such an upward bias in the lowest contour range could have been avoided with an algorithm that calculated elevations for points rather than cells. The net impact was that the DEM, in effect, estimated the 5-foot contour to be approximately 7.3 feet above the vertical datum for <st1:place w:st="on">South River</st1:place>. The plateau exaggeration factors were 0.8, 2.3, and 2.9, for the spring high water, 5-ft, and 10-ft contours, respectively.</pre><pre style='margin-left:.5in'>The <span class=SpellE>Broomes</span> quad had a similar upward bias, effectively treating the 5-foot contour as a 5.8-foot contour.<span style='mso-spacerun:yes'>  </span>The plateau exaggeration factors were 7.0, 0.9, and 4.2, for the spring high water, 5-ft, and 10-ft contours, respectively.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>The results of the &quot;11 quadrangle&quot; analysis are shown in <span class=GramE>DEM_Comparison_with_DLG_11_quads.xls.,</span> which is included in the zip file distributed with this dataset.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Quantitative_Vertical_Positional_Accuracy_Assessment</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Vertical_Positional_Accuracy_Explanation</i></span><i>:</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'><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> US Geological Survey</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</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) and Digital Raster Graphic (DRG) 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="http://edc.usgs.gov/geodata/dlg_large/states/MD.html" target=viewer><span lang=DE style='mso-ansi-language:DE'>http://edc.usgs.gov/geodata/dlg_large/states/MD.html</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><span lang=DE style='mso-ansi-language: DE'>Online_Linkage:</span></i><span lang=DE style='mso-ansi-language:DE'> </span><a href="http://staging.icfconsulting.com/staging/gis/sealevel/MD/GIS%20Data/USGS%2024K%20Contour%20Interval.jpg" target=viewer><span lang=DE style='mso-ansi-language:DE'>http://staging.icfconsulting.com/staging/gis/sealevel/MD/GIS%20Data/USGS%2024K%20Contour%20Interval.jpg</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'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> Digital data and paper</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'>Multiple</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Spatial data and attributes.</span> Some contours digitized from Digital Raster Graphics (<span class=SpellE>DRGs</span>) and hardcopy.</pre><pre style='margin-left:.5in'>Source contours are 1 meter, 5 feet, 10 feet, and 20 feet depending on the 7.5' topographic quadrangle used. The zip file with which this metadata is distributed includes <span class=GramE>a the</span> file &quot;<span class=SpellE>MD_Data_Quality.jpg</span>&quot; which defines the contour intervals of the input data.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Maryland Department of Natural Resources (MD DNR)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 1992</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Maryland Department of Natural Resources (MD DNR) Elevation Data</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Online_Linkage</i></span><i>:</i> <a href="NA" target=viewer>NA</a> </p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 12,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> Digital data</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 1992</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Spatial data and attributes.</span> MD DNR staff told the project manager that 90% of the elevation points are within 5 feet of true elevation. <span class=GramE>Horizontal accuracy, 33 feet.</span> Vertical Position <span class=SpellE>Accurancy</span>:<span style='mso-spacerun:yes'>  </span>5 feet.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> National Oceanic Service</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> Unknown</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Time</i></span><i>:</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'><span class=SpellE><i>Online_Linkage</i></span><i>:</i> <a href="http://co-ops.nos.noaa.gov/bench.html" target=viewer>http://co-ops.nos.noaa.gov/bench.html</a> </p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Range_of_Dates</i></span><i>/Times:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Beginning_Date</i></span><i>:</i> 1960</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Ending_Date</i></span><i>:</i> 1978</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'>Relative to 1960-1978 Tidal <span class=GramE>Epoch</span></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</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), the elevation of MLLW relative to several benchmarks nearby, and the elevations of these benchmarks above NAVD88 for 25 tide gages in <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State>.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> National Oceanic Service</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</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'><span class=SpellE><i>Geospatial_Data_Presentation_Form</i></span><i>:</i> document</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> NA</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> paper</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 2000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Horizontal location, and spring high tide ranges for more than 150 tide gages in <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State>.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</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> Fish and Wildlife Service</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> Various</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>US Fish and Wildlife National Wetlands Inventory (NWI) 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="http://wetlands.fws.gov/downloads.htm" target=viewer><span lang=DE style='mso-ansi-language:DE'>http://wetlands.fws.gov/downloads.htm</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'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> Various</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation_Abbreviation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'>USFWS NWI</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Horizontal location of upper and lower limits of tidal wetlands.</span> See the metadata for the wetlands data used in this report.<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 (<span class=GramE>eds</span>.)]. <span class=GramE>EPA430R07004, <st1:country-region w:st="on">U.S.</st1:country-region> Environmental <st1:place w:st="on"><st1:City w:st="on">Protection Agency</st1:City>, <st1:State w:st="on">Washington</st1:State></st1:place>, DC.</span> For a graphic depicting the specific counties or USGS 7.5' quadrangles where this data set was used, see the <span class=SpellE>Maryland_DNR_Wetlands_Data_Coverage.jpg</span>. The USFWS data was used wherever that graphic shows no DNR data coverage.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Maryland Department of Natural Resources</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 1991</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Maryland Department of Natural Resources Wetland Coverage</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="http://dnrweb.dnr.state.md.us/gis/data/" target=viewer><span lang=DE style='mso-ansi-language:DE'>http://dnrweb.dnr.state.md.us/gis/data/</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'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Range_of_Dates</i></span><i>/Times:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Beginning_Date</i></span><i>:</i> 1988</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Ending_Date</i></span><i>:</i> 1995</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>ground</span> condition</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Spatial location of upper and lower limits of tidal wetlands.</span></pre><pre style='margin-left:.5in'><span class=GramE>(Note: photograph dates were from 1988 to 1995, but MD DNR listed the publication date of 1991 on the DNR website.)</span> Areas used:<span style='mso-spacerun:yes'>  </span>For a graphic depicting the specific counties or USGS 7.5' quadrangles where this data set was used, see the <span class=SpellE>Maryland_DNR_Wetlands_Data_Coverage.jpg</span>, a graphic file included in the zip file with which this data is distributed. See also the technical report for this project <span class=GramE>for<span style='mso-spacerun:yes'>  </span>specific</span> counties or USGS 7.5' quadrangles where this data set was used. <span class=GramE>J.G. Titus and J. Wang.</span> 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</pre><pre style='margin-left:.5in'>Level Rise [J.G. Titus and E.M. Strange (<span class=GramE>eds</span>.)]. <span class=GramE>EPA430R07004, <st1:country-region w:st="on">U.S.</st1:country-region> Environmental <st1:place w:st="on"><st1:City w:st="on">Protection Agency</st1:City>, <st1:State w:st="on">Washington</st1:State></st1:place>, DC.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> <span class=SpellE>Proudman</span> Oceanographic Laboratory (POL)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</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<span class=GramE>)-</span> Sea Level Rise Trend Data</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Other_Citation_Details</i></span><i>:</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="http://www.nbi.ac.uk/psmsl/datainfo/rlr.trends" target=viewer><span lang=DE style='mso-ansi-language:DE'>http://www.nbi.ac.uk/psmsl/datainfo/rlr.trends</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'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> unknown</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</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><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> GEOD Surveying and Aerial Mapping Corporation, prepared for Federal Emergency Management Agency's Flood Insurance Administration</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 1981</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'><st1:PlaceName w:st="on">Kent</st1:PlaceName> <st1:PlaceName w:st="on">Island</st1:PlaceName>, <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Geospatial_Data_Presentation_Form</i></span><i>:</i> map</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 7,200</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> paper</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 1981</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Used to supplement USGS <span class=SpellE>DLGs</span> on <st1:place w:st="on"><st1:PlaceName w:st="on">Kent</st1:PlaceName> <st1:PlaceName w:st="on">Island</st1:PlaceName></st1:place>.</span> Elevation contours (2 - 12 ft NGVD29). <span class=GramE>Mapped by photogrammetric methods from aerial photographs.</span></pre><pre style='margin-left:.5in'>Contour Interval: 2'</pre><pre style='margin-left: .5in'>This map complies with National Map accuracy standards.</pre><pre style='margin-left:.5in'>Datum is based on mean sea level.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Photo Science, Inc. (now <span class=SpellE>EarthData</span> International, Inc.) for <st1:place w:st="on"><st1:PlaceName w:st="on">Anne</st1:PlaceName> <st1:PlaceName w:st="on">Arundel</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place>, Department of Public Works</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 1995</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'><st1:place w:st="on"><st1:PlaceName w:st="on">Anne</st1:PlaceName> <st1:PlaceName w:st="on">Arundel</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place> 1995 Topographic Mapping</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 2,400</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> paper</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 1995</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>ground</span> condition</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Five foot contour interval elevation map was used to generate a DEM for <st1:place w:st="on"><st1:PlaceName w:st="on">Anne</st1:PlaceName> <st1:PlaceName w:st="on">Arundel</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place>. Contours generated from aerial photos. Complies with National Map Accuracy Standards</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Harford <st1:place w:st="on"><st1:PlaceType w:st="on">County</st1:PlaceType> <st1:PlaceName w:st="on">Government</st1:PlaceName></st1:place> GIS</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> Unknown</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Harford County 5 foot contour elevation maps</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 2,400</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> digital tape media</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> unknown</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>ground</span> condition</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><st1:PlaceName w:st="on">Harford</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType> provided 5 foot (NGVD29) contour interval elevation maps for <st1:place w:st="on"><st1:PlaceName w:st="on">Harford</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place> in <span class=SpellE>ArcInfo</span> Interchange Format (.e00) in <span class=SpellE><span class=GramE>ascii</span></span> <span class=SpellE>breaklines</span> and mass points from a Digital Terrain Model (DTM). According to metadata, NMAS for 5 foot contours states that 90% of the tested elevations shall be in error by less than 1/2 a contour interval, i.e. 2.5 foot.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> <st1:place w:st="on"><st1:PlaceName w:st="on">Baltimore</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place> OIT/GIS Services Unit</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 1997</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'><st1:place w:st="on"><st1:PlaceName w:st="on">Baltimore</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place> <span class=SpellE>Topo</span> Data</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 100</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> digital tape media</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 1997</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevation contours were used to generate a DEM. Two foot contour interval contours relative to NAVD88. <span class=GramE>Complies with standards of the American Society <span class=SpellE>Photogrametry</span> and Remote Sensing, as well as with National Map Accuracy Standards.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Henan Institute of <st1:place w:st="on"><st1:City w:st="on">Geography</st1:City>, <st1:country-region w:st="on">China</st1:country-region></st1:place></p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Coastal Digital Line Graphs (DLG) created from USGS Digital Raster Graphics</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> Digital vector data</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Multiple_Dates</i></span><i>/Times:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> unknown</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Spatial data and attributes.</span> Contours below 40 feet, for areas <span class=GramE>where neither USGS 1:24,000 <span class=SpellE>DLG's</span> nor local data were not available</span>.</pre><pre style='margin-left:.5in'>Contours digitized from USGS 7.5 minute Digital Raster Graphics (<span class=SpellE>DRGs</span>) or hardcopy. See Institute_of_Geography_DLG.doc, included in the zip <span class=GramE>file</span> with which this data is distributed, for a list of the 7.5-minute quads where we used the <st1:place w:st="on"><st1:PlaceType w:st="on">Institute</st1:PlaceType> of <st1:PlaceName w:st="on">Geography <span class=SpellE>DLG</span></st1:PlaceName></st1:place><span class=SpellE>'s</span>. Additionally, the graphic &quot;<span class=SpellE>MD_Data_Quality.jpg</span>&quot; defines the contour intervals of the input data.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</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>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Coastal Wetlands Data: <st1:State w:st="on"><st1:place w:st="on">Maryland</st1:place></st1:State></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> online</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Multiple_Dates</i></span><i>/Times:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> Mostly 1988-95, 1980s for a few counties.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Horizontal location of upper and lower limits of tidal wetlands.</span> Derivative product based on MD-DNR and NWI wetland data sources cited in this metadata.<span style='mso-spacerun:yes'>  </span>See Readme.doc (distributed in the zip file with this data set), for directions on how to download the Coastal Wetlands <span class=GramE>Data .</span><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 (<span class=GramE>eds</span>.)]. <span class=GramE>EPA430R07004, <st1:country-region w:st="on">U.S.</st1:country-region> Environmental <st1:place w:st="on"><st1:City w:st="on">Protection Agency</st1:City>, <st1:State w:st="on">Washington</st1:State></st1:place>, DC.</span> See Readme.doc for additional information.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Originator:</i> Spatial Systems Associates, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 11/30/2003 (and 2002 - most of <st1:City w:st="on"><st1:place w:st="on">Worcester</st1:place></st1:City> and small portion of Wicomico counties)</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'>Elevation Data - LiDAR Bare Earth Gridded DEM</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Place</i></span><i>:</i> <st1:place w:st="on"><st1:City w:st="on">Annapolis</st1:City>, <st1:State w:st="on">Maryland</st1:State></st1:place></p> <p class=MsoNormal style='margin-left:.5in'><i>Publisher:</i> Maryland Department of Natural Resources</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Other_Citation_Details</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>1. Airborne 1 (flight firm) 2.</span> <span class=GramE>Computational Consulting Services, LLC (processing firm) 3.</span> <span class=GramE>Spatial Systems Associates, Inc. (post-processing firm) 4.</span> Dewberry &amp; Davis (QA/QC firm) Note: 2002 <span class=SpellE>Lidar</span> data was provided by Joe Gavin (USACOE)</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="http://www.msgic.state.md.us/techtool" target=viewer><span lang=DE style='mso-ansi-language:DE'>http://www.msgic.state.md.us/techtool</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'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 24,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> DVD</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Multiple_Dates</i></span><i>/Times:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 2002</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 11/30/2003</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>ground</span> condition</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Horizontal coordinates and vertical elevations.</span> Note that data for <st1:City w:st="on"><st1:place w:st="on">Worcester</st1:place></st1:City> and along the border of Worcester/Wicomico counties the data is of less quality and is from 2002.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Source_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Citation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Citation_Information</i></span><i>:</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, Office of Science and Technology</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Date</i></span><i>:</i> 1994</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Publication_Time</i></span><i>:</i> Unknown</p> <p class=MsoNormal style='margin-left:.5in'><i>Title:</i></p> <p class=MsoNormal style='margin-left:.5in'><st1:country-region w:st="on">U.S.</st1:country-region> EPA Reach File 1 (RF1) for the Conterminous <st1:country-region w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region> in BASINS</p> <p class=MsoNormal style='margin-left:.5in'><i>Edition:</i> Version 2.0</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Online_Linkage</i></span><i>:</i> <a href="For%20BASINS%20model%20and%20data%20%3chttp:/www.epa.gov/waterscience/basins/%3e" target=viewer>For BASINS model and data &lt;http://www.epa.gov/waterscience/basins/&gt;</a> </p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Online_Linkage</i></span><i>:</i> <a href="For%20further%20documentation%20and%20reference%20to%20EPA's%20River%20Reach%20Files%20%3chttp:/www.epa.gov/owowwtr1/monitoring/rf/rfindex.html%3e" target=viewer>For further documentation and reference to EPA's River Reach Files &lt;http://www.epa.gov/owowwtr1/monitoring/rf/rfindex.html&gt;</a> </p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Scale_Denominator</i></span><i>:</i> 250,000 to 500,000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Type_of_Source_Media</i></span><i>:</i> CD-ROM</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Time_Period_of_Content</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Time_Period_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Single_Date</i></span><i>/Time:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Calendar_Date</i></span><i>:</i> 1994</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Currentness_Reference</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>publication</span> date</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Source_Contribution</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Spatial data and attributes</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Process_Step</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Description</i></span><i>:</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 scale <span class=SpellE>DLG's</span> from either USGS or 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>. They were appended and then projected into Albers projection except for <st1:City w:st="on">Baltimore</st1:City>, Anne Arundel, and <st1:PlaceName w:st="on">Harford</st1:PlaceName> <st1:PlaceType w:st="on">Counties</st1:PlaceType>, and <st1:place w:st="on"><st1:PlaceName w:st="on">Kent</st1:PlaceName> <st1:PlaceName w:st="on">Island</st1:PlaceName></st1:place> in Queen Anne's County (listed below).</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2) MD-DNR data were only used in areas where the (a) USGS contour interval was larger than 5 feet and (b) we had no local elevation data. Maryland Department of Natural Resources elevation data had a horizontal resolution of 100 by 100 feet and vertical resolution of 0.1 foot. The data were imported from text files and interpolated into <span class=SpellE>DEMs</span> with 30 meter resolution using the TOPOGRID function (ESRI GRID extension). The vertical datum of DNR elevation data was NAVD88, while the vertical datum of USGS DLG data was NGVD29. Therefore, Wang generated a grid representing the difference between the two <span class=SpellE>datums</span> by obtaining difference values for each point with a 0.1 decimal degree resolution (horizontal) over the entire study area from VERTCON program. The data were projected into Albers projection and interpolated into a grid of 30 meter resolution<span class=GramE>,<span style='mso-spacerun:yes'>  </span>which</span> he used to convert the DNR DEM into NGVD29. He then converted the DEM into 5 foot interval contour lines (5, 10, and 15 foot contours), which he used as supplementary input to the final DEM creation. The DNR contours were not used if (a) there was an elevation source other than USGS maps (e.g., <st1:City w:st="on">Baltimore</st1:City>, Anne Arundel, and <st1:place w:st="on"><st1:PlaceName w:st="on">Harford</st1:PlaceName> <st1:PlaceType w:st="on">Counties</st1:PlaceType></st1:place>) or (b) USGS maps had a contour of 5 feet or 1 meter.<span style='mso-spacerun:yes'>  </span>If USGS had a 10 foot contour, the 5 and 15 foot contours from the DNR data were used.<span style='mso-spacerun:yes'>  </span>If the USGS map had a 20 foot contour interval, then all three contours were used.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3) <st1:place w:st="on"><st1:PlaceName w:st="on">Kent</st1:PlaceName> <st1:PlaceName w:st="on">Island</st1:PlaceName></st1:place>: Contour lines from Dewberry &amp; Davis flood line elevation maps developed for FEMA in 1981 were digitized. The contour lines were from 2 feet to 12 feet. When compared with USGS DLG as well as MD DEP elevation data, the vertical datum was determined to be NGVD29. These contour lines were used in lieu of USGS DLG contours and combined with the point covers representing spring high water level and mean tide level to generate the DEM.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>4) <st1:place w:st="on"><st1:PlaceName w:st="on">Anne</st1:PlaceName> <st1:PlaceName w:st="on">Arundel</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place>: The <span class=GramE>county's</span> 5 foot contour interval elevation map was used to generate the DEM. First, the contour layer was projected into Albers projection. Then to resolve the conflicts between the five foot contour and upper limit of tidal wetland, the 5 foot contour was reconstructed using a series of editing processes (such as union and relate within <span class=SpellE>ArcInfo</span>). A 30 meter DEM above 5 feet elevation over NAVD88 was first generated using TOPOGRID. The grid representing the difference between NAVD88 and NGVD29 (described in #2 above) was used to convert the DEM relative to the NGVD29 datum. The new DEM was then converted into a point cover. This point cover was then combined with the point covers representing spring high water level and mean tide level to interpolate the final DEM.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>5) Baltimore County: 2 foot interval county digital line graph elevation maps based on high resolution aerial photography were projected into Albers <span class=SpellE>projection.Wang</span> used the grid representing the difference between NAVD88 and NGVD29 (described in #2 above) to convert the contours from NAVD88 to NGVD29.<span style='mso-spacerun:yes'>  </span>Unlike the other counties, the 2-foot contours obviated the need to split the simulation into lowland and midland.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>6)<span style='mso-spacerun:yes'>  </span><st1:place w:st="on"><st1:PlaceName w:st="on">Harford</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place>.</span><span style='mso-spacerun:yes'>  </span>The County's 5 foot contour interval elevation map was used to generate the DEM. First, the contour layer was projected into Albers projection. Then to resolve the conflicts between the five foot contour and upper limit of tidal wetland, the 5 foot contour was reconstructed using a series of editing processes (such as union and relate within <span class=SpellE>ArcInfo</span>).<span style='mso-spacerun:yes'>  </span>Otherwise, the processing was the same as with areas where we used the Maryland DNR data.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>7) Light Detection and Ranging (<span class=SpellE>Lidar</span>) data. Jones acquired <span class=SpellE>Lidar</span> data representing a bare-earth model in 1,800 x 1,200 meter tiles for portions of <st1:City w:st="on">Worcester</st1:City>, Wicomico, <st1:City w:st="on">Somerset</st1:City>, Dorchester, <st1:place w:st="on"><st1:City w:st="on">Talbot</st1:City>, <st1:country-region w:st="on">Kent</st1:country-region></st1:place>, and Queen <span class=SpellE><span class=GramE>Annes</span></span> counties (see figure &quot;<span class=SpellE>lidar_dvd_cds.pdf</span>&quot; for graphic of spatial distribution of <span class=SpellE>lidar</span> data). According to Kevin Boone (MD DNR), DNR acquired data for Worcester and along the border of Worcester/Wicomico counties in 2002, and the data is of less quality than all other areas that they acquired in 2003 (see figure &quot;Worc02_03lidar.jpg&quot; for areas where 2002 vs. 2003 data were used). Data tiles were provided as either ESRI export format GRIDS (.e00) or as raw ASCII files with horizontal and vertical (<span class=SpellE>x<span class=GramE>,y,z</span></span>) coordinates, and imported into ESRI GRID format. Jones combined the <span class=SpellE>Lidar</span> tiles into raster layers by county using the MOSAIC function and then <span class=SpellE>resampled</span> from a 2 meter <span class=SpellE>cellsize</span> to 30 meters using bilinear interpolation. The <span class=SpellE>resampled</span> county grids were combined into a single seamless raster layer using the MOSAIC function and projected into the Albers projection to match the other data sets. According to the metadata provided with the <span class=SpellE>lidar</span> data, values of zero represented open water. These were removed from the data set prior to further processing. The raster data was exported into a point layer (ESRI coverage format) and elevation units converted from meters to feet. Using the US Army Corps of <span class=SpellE>Engineeers</span> <span class=SpellE>Corpscon</span> (v. 6.0.1) program, the full location information (<span class=SpellE>x<span class=GramE>,y,z</span></span> values) were exported into an ASCII file and the elevations were converted from NAVD88 to NGVD29 . The converted ASCII file was <span class=SpellE>reimported</span> into ESRI GRID format.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Process_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> <span class=SpellE>Jue</span> Wang</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</i> GIS Practice, ICF Consulting, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Address</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Address_Type</i></span><i>:</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'><span class=SpellE><i>State_or_Province</i></span><i>:</i> VA</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Postal_Code</i></span><i>:</i> 22031</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Hours_of_Service</i></span><i>:</i> 9:30 - 5:30 EST</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Step</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Description</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Process of Tidal Record</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 observation data, i.e., the latitudes and longitudes, the elevations of mean tide level (MTL) above mean lower low water (MLLW), the elevations of MLLW relative to several benchmarks, and the elevations above NAVD88 of these benchmarks of 25 tide gages in Maryland were downloaded from the NOS website. The elevations of mean tide level relative to NAVD88 were calculated and then converted to a NGVD29 using the difference surface between NAVD88 and NGVD29. <span class=GramE>A point</span> coverage was then created with such data and projected into Albers projection. Using the point coverage as a reference, artificial contour lines were created with consideration of shorelines via heads-up digitizing and then used to interpolate the mean tide level surface using TOPOGRID. As the tidal epoch used for the MTL data was 1960-1978, a separate sea level rise rate surface was created by interpolating actual sea level rise data (trend) from the <span class=SpellE>Proudman</span> Oceanographic Laboratory website and was used to adjust the mean tide level to years corresponding to other data sets, such as NWI data, so that the wetland boundary would represent spring high tide for the 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.</pre><pre style='margin-left:.5in'>From Table 2 of &quot;Tide Tables 2000, High and Low Water Predictions, East Coast of North and South America including Greenland&quot;, the latitudes, longitudes and spring high tide ranges of more than 150 tide gages were obtained and used to create a point coverage. Using the point coverage as a reference, artificial contour lines were created with consideration of shorelines and then used to interpolate the spring high tide range surface with TOPOGRID 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 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><span class=SpellE><i>Process_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> <span class=SpellE>Jue</span> Wang</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</i> GIS Practice, ICF Consulting, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Step</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Description</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Processing of Tidal Wetland Data from <st1:country-region w:st="on"><st1:place w:st="on">US</st1:place></st1:country-region> FWS NWI and MD DNR Wetland Data to Generate a Supplemental Contour Representing the Elevation of Spring High Water.</span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>1) NWI data were imported into <span class=SpellE>ArcInfo</span> coverage format and projected into Albers projection. A data set representing tidal wetlands was generated using the <span class=SpellE>subtidal</span> and intertidal subsystems for marine and estuarine categories, tidal subsystem for <span class=SpellE>riverine</span> category, and the tidal or non-tidal water regimes for <span class=SpellE>lacustrine</span> and <span class=SpellE>palustrine</span> categories. The upper and lower limits of tidal wetlands were then extracted from this tidal wetland data set.</pre><pre style='margin-left:.5in'>For the marine and estuary categories, the boundaries between M1 (<span class=SpellE>subtidal</span>) and M2 (intertidal)<span class=GramE>,<span style='mso-spacerun:yes'>  </span>E1</span> (<span class=SpellE>subtidal</span>) and E2 (intertidal) determined the lower boundaries of tidal wetland, and the boundaries of M2 and E2 with upland and other non-tidal wetland or non-tidal open water, determined the upper boundaries of tidal wetland.<span style='mso-spacerun:yes'>  </span>For the <span class=SpellE>riverine</span> category, the boundaries between R1 (tidal) and upland as well as other non-tidal wetland or non-tidal open water determined the upper limit. For <span class=SpellE>Lacustrine</span> and <span class=SpellE>Palustrine</span> categories, tidal or non-tidal water regimes determined the upper boundaries of tidal wetland.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2) Maryland Department of Natural Resources (DNR) wetland data were projected into Albers projection. The tidal wetlands were identified using methods similar to those described above for the NWI data and used to generate a layer representing the upper and lower limits of tidal wetlands.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3) The upper and lower limits of tidal wetlands from the Maryland DNR and US FWS NWI wetland data were then combined, with priority given to the former where available and the combined data set was used to generate supplemental contours. <span class=GramE>Elevations assigned to these contours was</span> derived from spring high tide level and mean tide level surface grids respectively. The upper wetland boundary was used as a supplemental contour. The lower boundary was used for reporting the area of wetlands but not for elevations, because the project manager decided not to report wetland elevations.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>See also the metadata accompanying the Maryland Wetland polygon datasets.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Process_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> <span class=SpellE>Jue</span> Wang</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</i> ICF Consulting, Inc., GIS Practice</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Step</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Description</i></span><i>:</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 contours, the study area was divided into four parts (tidal wetlands, lowland, midland, and upland).</pre><pre style='margin-left:.5in'>&quot;Tidal wetlands&quot; represents the tidal wetlands as classified from the wetland layer.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Lowland represents the area between the tidal wetlands and the lowest topographic contour available that is generally above the tidal wetlands. Depending on the contour interval of the input data, this lowest contour may have been 5 feet, 10 feet, 20 feet, or 1 meter -- in all cases relative to NGVD29 where we used USGS maps -- or 5 feet NAVD88 in the case of <st1:place w:st="on"><st1:PlaceName w:st="on">Anne</st1:PlaceName> <st1:PlaceName w:st="on">Arundel</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType></st1:place>, where the 5 foot contours were measured relative to NAVD88.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Midland represents the area above the lowest contour we used and below the highest USGS contour lines (40 foot or 12 meters NGVD29) used.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></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 or 12 meter NGVD29 contour).</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>Boundary <span class=SpellE>coverages</span> were created for tidal wetlands, lowland, and midland using appropriate elevation contours or upper and lower limits of tidal wetland.<span style='mso-spacerun:yes'>  </span>However, we are not making the tidal wetland interpolations available in this dataset due to the lack of a theoretical justification for believing that interpolation to have any information content.<span style='mso-spacerun:yes'>  </span>(At best, the wetland elevation interpolations might be used for graphical representations of the impact of sea level rise.)<span style='mso-spacerun:yes'>  </span>We will retain a companion dataset with elevations stored as floating point double precision, which may be made available for the sole purpose of evaluating any graphical representations that use wetland elevations. We provide a gridded (and a polygon) wetland dataset so that the user can distinguish tidal wetlands from open water for cells with no data. In the case of <st1:PlaceName w:st="on">Baltimore</st1:PlaceName> <st1:PlaceType w:st="on">County</st1:PlaceType> and <st1:place w:st="on"><st1:PlaceName w:st="on">Kent</st1:PlaceName> <st1:PlaceName w:st="on">Island</st1:PlaceName></st1:place>, where the underlying topographic information had a two-foot 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 <span class=SpellE>DEMs</span> were interpolated with a predetermined <span class=SpellE>cellsize</span> of 30 meters for the lowland, midland, and upland areas using contour lines described in the section &quot;Process of Input Elevation Data&quot; and supplemental contours from the combination of NWI and MD DNR wetland data and NOAA tidal record contours. A common starting coordinate was set for all three DEM interpolation processes to ensure alignment of the separate layers after processing. The minimum and maximum limits were set for each process according to the input elevation data to ensure the resulting elevations were in accordance with the input data (see &quot;first contour truncating&quot;, #5, below). The iteration was set to 40, the horizontal standard error tolerance was set to 2 to minimize the depression caused by inappropriate tend calculation, and the drainage enforcement option was turned on to remove isolated depressions. In addition, we used stream data, which takes priority over the other elevation inputs, to add additional topographic detail. </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'><span class=SpellE><span class=GramE>topogrid</span></span> <span class=SpellE>dem_mid_ft</span> 30</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>contour</span> <span class=SpellE>topo_cntr</span> elevation</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=SpellE><span class=GramE>xyzlimits</span></span> 1602000 # 1833000 # 5.0001</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>boundary</span> <span class=SpellE>topo_bnd_up</span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>stream</span> <span class=SpellE>stream</span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>iterations</span> 40</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>tolerances</span> # 2</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>enforce</span> on</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'><span class=GramE>end</span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3) The region with vertical contour interval units in meters was interpolated separately. The contour values were first converted from meters into feet, interpolated into <span class=SpellE>DEMs</span> for both midland and lowland, and then merged together with the region having vertical contour units in feet.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>4) The interpolated <span class=SpellE>DEMs</span> were displayed against input elevation data and visually checked. These visual checks would show gross errors, but not necessarily errors in which the amount of low land is over- or underestimated by 10-40 percent (additionally, see Data Quality, Positional Accuracy section). If obvious errors such as artificial depressions occurred, supplemental elevation lines were added by heads-up 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'>5) 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)<span class=GramE>,</span> we decided to reset the DEM values to coincide with source contours. Whenever 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. Given the rounding of this integer dataset, all such values are effectively rounded to the bounding contour value between midland and lowland (e.g. 5 feet).<span style='mso-spacerun:yes'>  </span>Although this approach leaves us with some plateaus, we have fewer plateaus than we had when we did not divide the data; and dividing the data left us with fewer cases of midland and lowland values being outside of their appropriate ranges. Nevertheless, Dr. Wang was unable to apply our preferred approach in areas where the USGS maps had a 10-foot contour, because of our use of the MD DNR data.<span style='mso-spacerun:yes'>  </span>In some places, the MD DNR 5-foot contour was landward of the USGS 10-foot contour.<span style='mso-spacerun:yes'>  </span>In those areas, we simply did not use the 5-foot contour, due to the superior accuracy of the USGS maps.<span style='mso-spacerun:yes'>  </span>The lack of a 5-foot contour meant that the lowland/midland boundary was sometimes 5 feet and sometimes 10 feet.<span style='mso-spacerun:yes'>  </span>Therefore, the first-contour truncating set all midland values lower than 5 feet to 5.001 feet, while setting midland values greater than 10 feet to precisely 10 feet.<span style='mso-spacerun:yes'>  </span>This data limitation is inapplicable to areas where the USGS contour interval is either 5 or 20 feet, so we could have applied our general approach to those quadrangles. However, Dr. Wang did not do so because he ran TOPOGRID on all areas with 5-, 10-<span class=GramE>,<span style='mso-spacerun:yes'>  </span>or</span> 20-foot USGS contour intervals as a single simulation (because he usually had 5-foot contours from MD-DNR).</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>6) The <span class=SpellE>DEMs</span> of each separate part were eventually merged into the final DEM with the MERGE function within the ESRI GRID module.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Process_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> <span class=SpellE>Jue</span> Wang</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</i> GIS Practice, ICF Consulting, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Step</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Process_Description</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Incorporation of <span class=SpellE>Lidar</span> data with DEM data.</span></pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>1) We created a mask by setting all values in the area covered by LIDAR data to 1.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>2) We shrunk the mask by 30 cells which is 900 meters on each side.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>3) We used the ISNULL function to set values of the interpolated DEM to null over the mask area.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>4) We reprocessed the LIDAR data by extracting the values less than or equal to 40 feet.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>5) We <span class=SpellE>mosaiced</span> the LIDAR DEM and DEM from USGS data together using blend option within Spatial Analyst extension.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>6) We <span class=SpellE>substracted</span> the Spring High Water Level elevation from the <span class=SpellE>mosaiced</span> DEM to create a DEM above the Spring High Water Level.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>7) We changed the unit of measure from feet to meters.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>8) We set the values to null over the areas of tidal wetland and tidal open water.</pre><pre style='margin-left:.5in'><o:p>&nbsp;</o:p></pre><pre style='margin-left:.5in'>9) We changed the <span class=SpellE>mosaiced</span> <span class=SpellE>DEM's</span> unit of measure to centimeters and also its type from floating point to integer.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Process_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> <span class=SpellE>Jue</span> Wang</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</i> GIS Practice, ICF Consulting, Inc.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Senior GIS Analyst</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 703-218-2766</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 703-934-3974</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> jwang@icfconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Cloud_Cover</i></span><i>:</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><span class=SpellE><i>Spatial_Data_Organization_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Direct_Spatial_Reference_Method</i></span><i>:</i> Raster</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Raster_Object_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Raster_Object_Type</i></span><i>:</i> Grid Cell</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Row_Count</i></span><i>:</i> 7038</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Column_Count</i></span><i>:</i> 7805</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Vertical_Count</i></span><i>:</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><span class=SpellE><i>Spatial_Reference_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Horizontal_Coordinate_System_Definition</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><i>Planar:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Map_Projection</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Map_Projection_Name</i></span><i>:</i> Albers Conical Equal Area</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Albers_Conical_Equal_Area</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Standard_Parallel</i></span><i>:</i> 29.500000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Standard_Parallel</i></span><i>:</i> 45.500000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Longitude_of_Central_Meridian</i></span><i>:</i> -96.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Latitude_of_Projection_Origin</i></span><i>:</i> 23.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>False_Easting</i></span><i>:</i> 0.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>False_Northing</i></span><i>:</i> 0.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Planar_Coordinate_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Planar_Coordinate_Encoding_Method</i></span><i>:</i> row and column</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Coordinate_Representation</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Abscissa_Resolution</i></span><i>:</i> 30.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Ordinate_Resolution</i></span><i>:</i> 30.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Planar_Distance_Units</i></span><i>:</i> meters</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Geodetic_Model</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Horizontal_Datum_Name</i></span><i>:</i> North American Datum of 1983</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Ellipsoid_Name</i></span><i>:</i> Geodetic Reference System 80</p> <p class=MsoNormal style='margin-left:.5in'><i>Semi-<span class=SpellE>major_Axis</span>:</i> 6378137.000000</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Denominator_of_Flattening_Ratio</i></span><i>:</i> 298.257222</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Vertical_Coordinate_System_Definition</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Altitude_System_Definition</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Altitude_Datum_Name</i></span><i>:</i> SHW</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Altitude_Resolution</i></span><i>:</i> 1 cm</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Altitude_Distance_Units</i></span><i>:</i> cm</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Altitude_Encoding_Method</i></span><i>:</i> Attribute values</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><span class=SpellE><i>Entity_and_Attribute_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Detailed_Description</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Entity_Type</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Entity_Type_Label</i></span><i>:</i> <span class=SpellE>dem_md_shw_cm.vat</span></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Label</i></span><i>:</i> <span class=SpellE>Rowid</span></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Definition</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Internal feature number.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Attribute_Definition_Source</i></span><i>:</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><span class=SpellE><i>Attribute_Domain_Values</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Unrepresentable_Domain</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>Sequential unique whole numbers that are automatically generated.</span></p> <p class=MsoNormal style='margin-left:.5in'><i>Attribute:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Label</i></span><i>:</i> VALUE</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Definition</i></span><i>:</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><span class=SpellE><i>Attribute_Definition_Source</i></span><i>:</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:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Label</i></span><i>:</i> COUNT</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Attribute_Definition</i></span><i>:</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><span class=SpellE><i>Attribute_Definition_Source</i></span><i>:</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><span class=SpellE><i>Overview_Description</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Entity_and_Attribute_Overview</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original>Elevations generated from input data sets (contours and spot elevations) and interpolated into a raster DEM and rounded to nearest cm.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Entity_and_Attribute_Detail_Citation</i></span><i>:</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> <a name=33918688></a></p> <div class=MsoNormal align=center style='text-align:center'><span style='mso-bookmark:33918688'> <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:33918688'></span></span> <p class=MsoNormal><span class=SpellE><i>Distribution_Information</i></span><i>:</i> </p> <p class=MsoNormal style='margin-left:.5in'><i>Distributor:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</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'><span class=SpellE><i>Contact_Address</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Address_Type</i></span><i>:</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'><span class=SpellE><i>State_or_Province</i></span><i>:</i> DC</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Postal_Code</i></span><i>:</i> 20460</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 202-343-9990</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 202-343-2338</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> climatechange@epa.gov</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Hours_of_Service</i></span><i>:</i> 9:00 - 6:00 Eastern</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Resource_Description</i></span><i>:</i> The dataset is being distributed by the US Environmental Protection Agency.</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Distribution_Liability</i></span><i>:</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 or implied is made regarding the accuracy or utility of the data.<span style='mso-spacerun:yes'>  </span>Neither EPA nor the data developers shall be held liable for any use of the data and information described and/or contained herein.</pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Standard_Order_Process</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Digital_Form</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Digital_Transfer_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Transfer_Size</i></span><i>:</i> 12.213</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Custom_Order_Process</i></span><i>:</i><o:p></o:p></p> <pre style='margin-left:.5in' id=original><span class=GramE>Data available from Alan Cohn at 202-343-9814.</span></pre> <p class=MsoNormal style='margin-left:.5in'><script> fix(original) </script><span class=SpellE><i>Technical_Prerequisites</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=GramE>Requires software capable of displaying raster data.</span></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><span class=SpellE><i>Metadata_Reference_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Metadata_Date</i></span><i>:</i> 20080902</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Metadata_Contact</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Information</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person_Primary</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Person</i></span><i>:</i> Russ Jones, Jim Titus, and <span class=SpellE>Jue</span> Wang</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Organization</i></span><i>:</i> Stratus Consulting Inc. (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Position</i></span><i>:</i> Managing Analyst (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Address</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Address_Type</i></span><i>:</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'><span class=SpellE><i>State_or_Province</i></span><i>:</i> CO</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Postal_Code</i></span><i>:</i> 80306</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 303-381-8000 (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Voice_Telephone</i></span><i>:</i> 202-343-9307 (Titus)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Facsimile_Telephone</i></span><i>:</i> 303-381-8200 (Jones)</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> rjones@stratusconsulting.com</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Contact_Electronic_Mail_Address</i></span><i>:</i> Titus.Jim@epamail.epa.gov</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Hours_of_Service</i></span><i>:</i> 9:00-5:00 MST</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Metadata_Standard_Name</i></span><i>:</i> FGDC Content Standards for Digital Geospatial Metadata</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Metadata_Standard_Version</i></span><i>:</i> FGDC-STD-001-1998</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Metadata_Time_Convention</i></span><i>:</i> local time</p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Metadata_Extensions</i></span><i>:</i></p> <p class=MsoNormal style='margin-left:.5in'><span class=SpellE><i>Online_Linkage</i></span><i>:</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'><span class=SpellE><i>Profile_Name</i></span><i>:</i> ESRI Metadata Profile</p> <p class=MsoNormal><a href="#Top">Back to Top</a> </p> </div> </body> </html>