<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="./fgdc_classic_fgdl.xsl"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Florida Division of Emergency Management</origin>
        <pubdate>20090101</pubdate>
        <pubtime>unknown</pubtime>
        <title>2FT CONTOUR LINES (MERRICK)</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Tallahassee, Fl</pubplace>
          <publish>Florida Division of Emergency Management</publish>
        </pubinfo>
        <othercit>Glades, Hendry, Martin, Okeechobee, Palm Beach</othercit>
        <onlink>www.floridadisaster.org/gis</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>LiDAR generated 2-foot contours for the Herbert Hoover Dike project.</abstract>
      <purpose>Contours consistent with the deliverables and including a certain level of smoothing. Index, Intermediate, Depression, and Low Confidence contours are coded.</purpose>
      <supplinf>The Herbert Hoover Dike project consists of LIDAR, Digital Orthophotography and DTM ESRI geodatabases for approximately 2337 square miles.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20070908</begdate>
          <begtime>unknown</begtime>
          <enddate>20080125</enddate>
          <endtime>unknown</endtime>
        </rngdates>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-81.340890</westbc>
        <eastbc>-80.111308</eastbc>
        <northbc>27.274724</northbc>
        <southbc>26.295095</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Contour</themekey>
        <themekey>LiDAR</themekey>
        <themekey>LiDARgrammetry</themekey>
        <themekey>Breakline</themekey>
        <themekey>DTM</themekey>
        <themekey>Elevation</themekey>
        <themekey>DSM</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>elevation</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Herbert Hoover Dike</placekey>
        <placekey>Florida</placekey>
      </place>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2008</tempkey>
        <tempkey>2007</tempkey>
      </temporal>
    </keywords>
    <accconst>This data may be used by the requested party for stated purposes and should not be re-distributed.</accconst>
    <useconst>This data is for planning purposes only and should not be used for legal or cadastral purposes. Regional Evacuation Studies are currently being updated and www.floridadisaster.org/gis should be consulted for revisions.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Division of Emergency Management</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2555 Shumard Oak Boulevard</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32399-2100</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>850-413-9907</cntvoice>
        <cntfax>850-488-1016</cntfax>
        <cntemail>gis@dca.state.fl.us</cntemail>
      </cntinfo>
    </ptcontac>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <othercit>http://www.floridadisaster.org/gis/LiDAR/index.htm Baseline Specifications for Orthophotography and LiDAR: http://www.floridadisaster.org/gis/specifications/Documents/BaselineSpecifications_1.2.pdf Standards for 1:24,000 Scale Digital Line Graphs: http://rockyweb.cr.usgs.gov/nmpstds/acrodocs/dlgqmap/7dqm0401.pdf</othercit>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>GeoPlan relied on the integrity of the attribute information within the original data.</attraccr>
    </attracc>
    <logic>Data was verified for correct topology (no intersections, overlaps or dangles. Merrick &amp; Co. performed a full qualitative review of the contour data for smoothness and consistency of feature codes.</logic>
    <complete>A visual qualitative assessment was performed to ensure data completeness.</complete>
    <posacc>
      <horizpa>
        <horizpar>n/a</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>The contours inherit the accuracy of the LiDAR dataset they were acquired from. A complete assessment of the vertical accuracy is available in the Minimum Technical Standard (MTS report) "Final Report of Specific Purpose LiDAR Survey-LiDAR-Generated Breaklines and Contours" submitted to Florida Division of Emergency Management.</vertaccr>
        <qvertpa>
          <vertaccv>0.3 ft</vertaccv>
          <vertacce>This value exceeds the NSSDA standard for one-foot (1') interval contours This was for the entire HHD dataset</vertacce>
        </qvertpa>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Merrick &amp; Co</origin>
            <pubdate>20090101</pubdate>
            <pubtime>unknown</pubtime>
            <title>DACS</title>
            <geoform>raster digital data</geoform>
            <pubinfo>
              <pubplace>Aurora, CO</pubplace>
              <publish>Merrick &amp; Co</publish>
            </pubinfo>
            <othercit>Lidar Survey of Herbert Hoover Dike conducted from 09/08/2007 to 01/25/2008</othercit>
          </citeinfo>
        </srccite>
        <typesrc>None</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20071104</begdate>
              <begtime>unknown</begtime>
              <enddate>20071110</enddate>
              <endtime>unknown</endtime>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>DACS</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Merrick &amp; Co</origin>
            <pubdate>20090101</pubdate>
            <pubtime>unknown</pubtime>
            <title>Ground Control</title>
            <pubinfo>
              <pubplace>Aurora, CO</pubplace>
              <publish>Merrick &amp; Co</publish>
            </pubinfo>
            <othercit>Lidar Survey of Herbert Hoover Dike conducted from 09/08/2007 to 01/25/2008</othercit>
          </citeinfo>
        </srccite>
        <typesrc>None</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20070908</begdate>
              <begtime>unknown</begtime>
              <enddate>20080125</enddate>
              <endtime>unknown</endtime>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>Ground Control</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Merrick &amp; Co</origin>
            <pubdate>20090101</pubdate>
            <pubtime>unknown</pubtime>
            <title>LiDAR</title>
            <geoform>vector digital data</geoform>
            <pubinfo>
              <pubplace>Aurora, CO</pubplace>
              <publish>Merrick &amp; Co</publish>
            </pubinfo>
            <othercit>Lidar Survey of Herbert Hoover Dike conducted from 09/08/2007 to 01/25/2008</othercit>
          </citeinfo>
        </srccite>
        <srcscale>0</srcscale>
        <typesrc>None</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20070908</begdate>
              <begtime>unknown</begtime>
              <enddate>20080125</enddate>
              <endtime>unknown</endtime>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>FDEM</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Using proprietary procedures developed by Merrick &amp; Co., a hydroenforced bare earth TIN was created. The points were gridded ground masspoints derived from the Lidar dataset, the 3D breaklines were included in this TIN.</procdesc>
        <srcused>Lidar ground masspoints</srcused>
        <srcused>3D Breaklines</srcused>
        <procdate>20090101</procdate>
        <srcprod>Hydroenforced TIN</srcprod>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Merrick &amp; Co</cntorg>
              <cntper>Kenny Legleiter</cntper>
            </cntorgp>
            <cntpos>Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2450 S. Peoria St</address>
              <city>Aurora</city>
              <state>CO</state>
              <postal>80014</postal>
              <country>US</country>
            </cntaddr>
            <cntvoice>303-353-3837</cntvoice>
            <cntemail>kenny.legleiter@merrick.com</cntemail>
            <hours>0800-1700 MST</hours>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters are applied as appropriate for the production of bare earth digital terrain models (dtms). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.1 format. The header file for each dataset is complete as defined by the LAS 1.1 specification. In addition the following fields are included: Flight Date Julian, Year, and Class. The LAS files do not include overlap. The data was classified as follows: Class 1 = Unclassified. This class includes vegetation, buildings, noise etc. Class 2 = Ground Class 9 = Water</procdesc>
        <srcused>LiDAR Point Cloud LAS 1.1 format</srcused>
        <procdate>20090101</procdate>
        <srcprod>Classified LiDAR datasets</srcprod>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Merrick &amp; Co</cntorg>
              <cntper>Kenny Legleiter</cntper>
            </cntorgp>
            <cntpos>Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2450 S. Peoria St</address>
              <city>Aurora</city>
              <state>CO</state>
              <postal>80014</postal>
              <country>US</country>
            </cntaddr>
            <cntvoice>303-353-3837</cntvoice>
            <cntemail>kenny.legleiter@merrick.com</cntemail>
            <hours>0800-1700 MST</hours>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>MARS software generated 1 foot contours were modeled from a hydroenforced bare earth TIN and then smoothed and simplified using proprietary procedures developed by Merrick &amp; Co..</procdesc>
        <srcused>Hydroenforced TIN</srcused>
        <procdate>20090101</procdate>
        <srcprod>1ft Contours</srcprod>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Merrick &amp; Co</cntorg>
              <cntper>Kenny Legleiter</cntper>
            </cntorgp>
            <cntpos>Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2450 S. Peoria St</address>
              <city>Aurora</city>
              <state>CO</state>
              <postal>80014</postal>
              <country>US</country>
            </cntaddr>
            <cntvoice>303-353-3837</cntvoice>
            <cntemail>kenny.legleiter@merrick.com</cntemail>
            <hours>0800-1700 MST</hours>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>The ABGPS, IMU, and raw Leica ALS50 Phase 2 Plus LiDAR data are integrated with Leica Incorporated's ALS Post Processor software. The resultant file is in a LAS binary file format . The LAS file version 1.1 format can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the geodetic coordinates referenced to the NAD83 HARN horizontal datum and NAVD88 vertical datum. The date and time for each flight line can be determined using the Julian date and time. The Julian date is a continuous count of days and fractions since noon Universal Time on January 1, 4713 BCE on the Julian Calendar.</procdesc>
        <srcused>LiDAR Scans</srcused>
        <srcused>Airborne Global Positioning System Data</srcused>
        <srcused>Inertial Measurement Unit</srcused>
        <procdate>20090101</procdate>
        <srcprod>LiDAR Point Cloud LAS 1.1 format</srcprod>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Merrick &amp; Co</cntorg>
              <cntper>Kenny Legleiter</cntper>
            </cntorgp>
            <cntpos>Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>2450 S. Peoria St</address>
              <city>Aurora</city>
              <state>CO</state>
              <postal>80014</postal>
              <country>US</country>
            </cntaddr>
            <cntvoice>303-353-3837</cntvoice>
            <cntemail>kenny.legleiter@merrick.com</cntemail>
            <hours>0800-1700 MST</hours>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>GeoPlan received this data via hard drive from Jones Edmunds on 8/27/09. The Florida Division of Emergency Management contracted this data out to Merrick &amp; Co. When received the data was in a series of file geodatabases. The data was merged into 1 file geodatabase and clipped to the appropriate county boundary. The feature class was then projected from NAD83 HARN State Plane East - feet to Albers HPGN. -Added SOURCE field and populated all values to MER -Added FGDLAQDATE field based on date GeoPlan acquired data from source -Changed name from to hhd_area#.Contour_2ft to TOPO2FT_GLADES</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20091104</procdate>
      </procstep>
      <procstep>
        <procdesc>Appended Hendry and Palm Beach</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20101005</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>String</sdtstype>
        <ptvctcnt>764402</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 HARN Florida GDL Albers</mapprojn>
          <albers>
            <stdparll>24.0</stdparll>
            <stdparll>31.5</stdparll>
            <longcm>-84.0</longcm>
            <latprjo>24.0</latprjo>
            <feast>400000.0</feast>
            <fnorth>0.0</fnorth>
          </albers>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.0001</absres>
            <ordres>0.0001</ordres>
          </coordrep>
          <plandu>meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983 HARN</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>TOPO2FT_MERRICK</enttypl>
        <enttypd>TOPO2FT_MERRICK.DBF</enttypd>
        <enttypds>"Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2"</enttypds>
      </enttyp>
      <attr>
        <attrlabl>OBJECTID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>SHAPE</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Contour_El</attrlabl>
        <attrdef>Elevation value</attrdef>
        <attrdefs>Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2</attrdefs>
      </attr>
      <attr>
        <attrlabl>Contour_Ty</attrlabl>
        <attrdef>Description of represented contour type</attrdef>
        <attrdefs>Florida GIS Baseline Specifications for Orthophotography and LiDAR V 1.2</attrdefs>
        <attrdomv>
          <edom>
            <edomv>1</edomv>
            <edomvd>Intermediate Contours - the three or four lines between adjacent index contours are about half the line weight of index contours. They are normally continuous throughout a map, but may be dropped or joined with an index contour where the slope is steep and where there is insufficient space to show all of the intermediate lines.</edomvd>
          </edom>
          <edom>
            <edomv>2</edomv>
            <edomvd>Supplementary Contours - used to portray important relief features that would otherwise not be shown by the index and intermediate contours (basic contours). They are normally added only in areas of low relief, but they may also be used in rugged terrain to emphasize features. Supplementary contours are shown as screened lines so that they are distinguishable from the basic contours, yet not unduly prominent on the published map.</edomvd>
          </edom>
          <edom>
            <edomv>3</edomv>
            <edomvd>Depression Contours - closed contours that surround a basin or sink. They are shown by right-angle ticks placed on the contour lines, pointed inward (down slope). Fill contours are a special type of depression contours, used to indicate an area that has been filled to support a road or railway grade.</edomvd>
          </edom>
          <edom>
            <edomv>4</edomv>
            <edomvd>Index Contours - defined as every 5th contour line. For example, with the Contour_2FT feature class, the first positive intermediate contour would be 0 with the following index contours at 10, 20, 30  feet, etc.</edomvd>
          </edom>
          <edom>
            <edomv>5</edomv>
            <edomvd>INTERMEDIATE LOW CONFIDENCE</edomvd>
          </edom>
          <edom>
            <edomv>6 </edomv>
            <edomvd>SUPPLEMENTARY LOW CONFIDENCE</edomvd>
          </edom>
          <edom>
            <edomv>7</edomv>
            <edomvd>DEPRESSION LOW CONFIDENCE</edomvd>
          </edom>
          <edom>
            <edomv>8</edomv>
            <edomvd>INDEX LOW CONFIDENCE</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Datestamp_</attrlabl>
        <attrdef>The date the feature was added to the geodatabase.</attrdef>
        <attrdefs>Florida GIS - Baseline Specifications for Orthophotography and LiDAR v1.2</attrdefs>
      </attr>
      <attr>
        <attrlabl>SOURCE</attrlabl>
        <attrdef>Abbreviated 3-letter code representing the data source.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
        <attrdomv>
          <edom>
            <edomv>CDM </edomv>
            <edomvd>CDM </edomvd>
          </edom>
          <edom>
            <edomv>CH2 </edomv>
            <edomvd>CH2MHILL</edomvd>
          </edom>
          <edom>
            <edomv>MER </edomv>
            <edomvd>Merrick</edomvd>
          </edom>
          <edom>
            <edomv>PDS </edomv>
            <edomvd>PDS </edomvd>
          </edom>
          <edom>
            <edomv>WOO </edomv>
            <edomvd>Woolpert</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>Data GeoPlan acquired data from source</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
        <attrdef>Unique ID added by GeoPlan</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHAPE.LEN</attrlabl>
        <attrdef>Length in meters</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
    </detailed>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Geographic Data Library (FGDL)</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>Florida</state>
          <postal>32611-5706</postal>
          <country>US</country>
        </cntaddr>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>DOWNLOADABLE DATA</resdesc>
    <distliab>The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html</distliab>
  </distinfo>
  <metainfo>
    <metd>20200303</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Division of Emergency Management</cntorg>
          <cntper>Richard Butgereit</cntper>
        </cntorgp>
        <cntpos>GIS Administrator</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2555 Shumard Oak Boulevard</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32399-2100</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>850-413-9907</cntvoice>
        <cntfax>850-488-1016</cntfax>
        <cntemail>richard.butgereit@em.myflorida.com</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>