{"action":"create","ckan_id":null,"date_created":"Tue, 31 Mar 2026 00:03:46 GMT","date_finished":null,"harvest_job_id":"52d231e5-aff4-4efa-8a30-b235ca584dc9","harvest_source_id":"4c62556f-0fa3-402d-90f6-6a46cd80a117","id":"35467b3c-68c8-474b-8ee2-68ede9549ab2","identifier":"https://hazards.fema.gov/filedownload/metadata/R10/630869-AcquireBaseMap.xml","parent_identifier":null,"source_hash":"eb9d4c7f4a858bac77f41e2b5ba3335a99145061c20c7a3b1831c09244e52d55","source_raw":"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<metadata>\r\n  <idinfo>\r\n    <citation>\r\n      <citeinfo>\r\n        <origin>Clallam County GIS Department</origin>\r\n        <origin>National Geodetic Survey</origin>\r\n        <origin>Washington State Department of Natural Resources</origin>\r\n        <origin>Washington State Department of Transporation</origin>\r\n        <origin>Tetra Tech, Inc.</origin>\r\n        <pubdate>20080423</pubdate>\r\n        <title>BASEMAP, CLALLAM COUNTY, WASHINGTON, USA</title>\r\n        <geoform>FGDC-Framework-Basemap</geoform>\r\n        <pubinfo>\r\n          <pubplace>Washington, DC</pubplace>\r\n          <publish>Federal Emergency Management Agency</publish>\r\n        </pubinfo>\r\n        <onlink>http://hazards.fema.gov</onlink>\r\n        <lworkcit>\r\n          <citeinfo>\r\n            <origin>Federal Emergency Management Agency</origin>\r\n            <pubdate>Unknown</pubdate>\r\n            <title>FEMA CASE 07-10-0545S</title>\r\n          </citeinfo>\r\n        </lworkcit>\r\n      </citeinfo>\r\n    </citation>\r\n    <descript>\r\n      <abstract>FEMA Framework Basemap datasets comprises six of the seven FGDC themes of geospatial data that are used by most GIS applications (Note: the seventh framework theme, orthographic imagery, is packaged in a separate NFIP Metadata Profile): cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water area &amp; lines. These data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13)</abstract>\r\n      <purpose>The Basemap datasets reflect the reference features (i.e., roads, streets, hydrographic features, political jurisdiction boundaries) needed by users to locate properties on FIRMs. (Source: Guidelines and Specifications Vol 1, p. 68)</purpose>\r\n    </descript>\r\n    <timeperd>\r\n      <timeinfo>\r\n        <sngdate>\r\n          <caldate>20080423</caldate>\r\n        </sngdate>\r\n      </timeinfo>\r\n      <current>MIP Submission Date</current>\r\n    </timeperd>\r\n    <status>\r\n      <progress>In work</progress>\r\n      <update>Unknown</update>\r\n    </status>\r\n    <spdom>\r\n      <bounding>\r\n        <westbc>-124.872028</westbc>\r\n        <eastbc>-122.896612</eastbc>\r\n        <northbc>48.506405</northbc>\r\n        <southbc>47.851789</southbc>\r\n      </bounding>\r\n    </spdom>\r\n    <keywords>\r\n      <theme>\r\n        <themekt>ISO 19115 Topic Category</themekt>\r\n        <themekey>Transportation</themekey>\r\n        <themekey>Hydrography</themekey>\r\n        <themekey>Corporate boundaries</themekey>\r\n        <themekey>Permanent benchmarks</themekey>\r\n        <themekey>PLSS</themekey>\r\n        <themekey>Quad boundaries</themekey>\r\n        <themekey>imageryBaseMapsEarthCover</themekey>\r\n      </theme>\r\n      <theme>\r\n        <themekt>FEMA NFIP Topic Category</themekt>\r\n        <themekey>Basemap</themekey>\r\n        <themekey>Orthoimage</themekey>\r\n        <themekey>DOQ</themekey>\r\n        <themekey>DOQQ</themekey>\r\n        <themekey>FGDC Framework</themekey>\r\n        <themekey>Digital Orthophoto Quad</themekey>\r\n        <themekey>Orthophoto</themekey>\r\n      </theme>\r\n      <place>\r\n        <placekt>None</placekt>\r\n        <placekey>REGION 10</placekey>\r\n        <placekey>STATE WA</placekey>\r\n        <placekey>COUNTY CLALLAM</placekey>\r\n        <placekey>COUNTY-FIPS 53009</placekey>\r\n        <placekey>FEMA-CID 53009C</placekey>\r\n        <placekey>COMMUNITY CLALLAM COUNTY</placekey>\r\n      </place>\r\n    </keywords>\r\n    <accconst>None</accconst>\r\n    <useconst>Acknowledgement of FEMA would be appreciated in products derived from these data.  This digital data is produced for the purposes of updating/creating a DFIRM database.</useconst>\r\n    <native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722</native>\r\n  </idinfo>\r\n  <dataqual>\r\n    <logic>Polygons intersecting the neatline are closed along the border. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. Line segments are a set of sequentially numbered coordinate pairs. No duplicate features exist nor duplicate points in a data string. Intersecting lines are separated into individual line segments at the point of intersection. Point data are represented by two sets of coordinate pairs, each with the same coordinate values. Tests for logical consistency are performed by DFIRM tools topology verification software.</logic>\r\n    <complete>The Basemap datasets represent all the features utilized during the study mapping process to spatially position the DFIRM information.</complete>\r\n    <posacc>\r\n      <horizpa>\r\n        <horizpar>The NSSDA is used to report the horizontal accuracy of the base map data used by FEMA to produce a FIRM. The NSSDA uses radial accuracy (Accuracy) to report the radius of a circle of uncertainty, such that the true or theoretical location of a point falls within that circle 95 percent of the time. (Guidelines and Specifications Vol 1, p. 70)\r\n  See source citations for accuracy specifications of individual datasets.</horizpar>\r\n        <qhorizpa>\r\n          <horizpav>11.5824</horizpav>\r\n          <horizpae>The minimum horizontal positional accuracy for new FIRM base map data is that of the default base map - the USGS DOQs, which have an NSSDA radial accuracy of 38 feet. Data that meet higher accuracy standards are also acceptable. Accuracy of 38 feet is the same as radial root mean square error (RMSEr) of 22 feet. (Guidelines and Specifications Vol 1, p. 70)\r\nSee source citations for accuracy specifications of individual datasets.</horizpae>\r\n        </qhorizpa>\r\n      </horizpa>\r\n    </posacc>\r\n    <lineage>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>NOAA, National Geodetic Survey</origin>\r\n            <pubdate>20070420</pubdate>\r\n            <title>Clallam Benchmarks</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>NOAA Campus, Silver Spring, MD</pubplace>\r\n              <publish>NOAA, National Geodetic Survey</publish>\r\n            </pubinfo>\r\n            <othercit>Questions concerning this data may be addressed to\r\n        \tCraig Larrimore\r\n        \tEMail - Craig.Larrimore@noaa.gov\r\n        \tPhone - 301-713-3257 x152\r\n\t\tThis data contains a set of geodetic control stations maintained by the National Geodetic Survey. Each geodetic control station in this dataset has either a precise Latitude/Longitude used for horizontal control or a precise Orthometric Height used for vertical control, or both.\r\n      \t\tThe National Geodetic Survey (NGS) serves as the Nation's depository for geodetic data. The NGS distributes geodetic data worldwide to a variety of users. These geodetic data include the final results of geodetic surveys, software programs to format, compute, verify, and adjust original survey observations or to convert values from one geodetic datum to another, and publications that describe how to obtain and use Geodetic Data products and services.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>paper, web</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>1994</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE2</srccitea>\r\n        <srccontr>Clallam Benchmarks for the S_PERM_BMK layer.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Clallam County</origin>\r\n            <pubdate>20070118</pubdate>\r\n            <title>Incorporated City Boundaries</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Clallam County</pubplace>\r\n              <publish>Clallam County GIS</publish>\r\n            </pubinfo>\r\n            <othercit>The Cities layer is a polygon layer of the current city limits of each of the three cities in Clallam County: Port Angeles, Sequim, and Forks. It is a derivative of the Zoning layer, and prompt updating after annexations is a high priority. The city limits layer is a derivative of the polygon layer.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>disk</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20070118</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE6</srccitea>\r\n        <srccontr>Incorporated city boundaries for S_POL_AR and S_POL_LN layers.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Washington State Department of Natural Resources</origin>\r\n            <pubdate>20040628</pubdate>\r\n            <title>Cadastre Jurisdiction Clallam County</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Olympia, Washington</pubplace>\r\n              <publish>Washington Department of Natural Resources</publish>\r\n            </pubinfo>\r\n            <othercit>County boundary for Clallam County, including both the land and marine portions of the county.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>online</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20050106</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE7</srccitea>\r\n        <srccontr>County boundary for S_POL_AR and S_POL_LN layers.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Clallam County</origin>\r\n            <pubdate>20080122</pubdate>\r\n            <title>Sections Clallam County</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Clallam County, WA</pubplace>\r\n              <publish>Clallam County</publish>\r\n            </pubinfo>\r\n            <othercit>Sections for Clallam County...</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>online</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20080122</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE3</srccitea>\r\n        <srccontr>Sections for S_PLSS_AR and S_PLSS_LN.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Clallam County</origin>\r\n            <pubdate>20080122</pubdate>\r\n            <title>Olympic National Park in Clallam County</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Clallam County, WA</pubplace>\r\n              <publish>Clallam County</publish>\r\n            </pubinfo>\r\n            <othercit>Olympic National Park boundary.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>online</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20080122</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE12</srccitea>\r\n        <srccontr>Olympic National Park boundary for S_POL_AR and S_POL_LN layers.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Cartography Section, Washington State Department of Transportation</origin>\r\n            <pubdate>20070801</pubdate>\r\n            <title>Ferry Routes</title>\r\n            <pubinfo>\r\n              <pubplace>Olympia, Washington</pubplace>\r\n              <publish>Washington State Department of Transportation</publish>\r\n            </pubinfo>\r\n            <othercit>Routes of vessels providing scheduled, public car ferry service in the waters of Washington State are depicted as linear features.  Known private, provincial, tribal and passenger-only ferry services are also shown.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>online</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20070801</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE5</srccitea>\r\n        <srccontr>Ferry Route features for S_TRANSPORT_LN layer.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Clallam County GIS Department</origin>\r\n            <pubdate>20071001</pubdate>\r\n            <title>County and State Parks of Clallam County</title>\r\n            <pubinfo>\r\n              <pubplace>Clallam County</pubplace>\r\n              <publish>Clallam County GIS Department</publish>\r\n            </pubinfo>\r\n            <othercit>This layer shows all County and State Parks in Clallam County. It is a derivative of the county's parcel layer.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>digital</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20071001</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE8</srccitea>\r\n        <srccontr>County and State park features for the S_POL_AR and S_POL_LN layers.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Washington State Department of Natural Resources</origin>\r\n            <pubdate>20060301</pubdate>\r\n            <title>DNR Hydrography</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Olympia, Washington</pubplace>\r\n              <publish>Washington Department of Natural Resources</publish>\r\n            </pubinfo>\r\n            <othercit>WCHYDRO and WBHYDRO together make up the most complete and up to date hydrography layer for the State of Washington. WCHYDRO contains watercourses represented as arcs or lines. These occur alone as single arc watercourses representing streams, ditches, or pipelines, or as centerlines through  water body polygons such as double-banked streams, lakes, impoundments, reservoirs, wet areas, or glaciers. WCHYDRO and WBHYDRO are edited daily and simultaneously; updates are posted weekly for internal DNR use and monthly for external use. Attribute interrelationships within WCHYDRO and spatial and attribute interrelationships between WCHYDRO and WBHYDRO are maintained.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>online</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20050301</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE10</srccitea>\r\n        <srccontr>DNR Sreams and waterbodies, WCHYDRO for S_WTR_LN layer and WBHYDRO for S_WTR_AR layer.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Clallam County GIS Department</origin>\r\n            <pubdate>20040908</pubdate>\r\n            <title>Clallam County Indian Reservation Boundaries</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Clallam County</pubplace>\r\n              <publish>Clallam County GID Department</publish>\r\n            </pubinfo>\r\n            <othercit>The Tribes layer is a polygon layer of the extent of each of the Indian Reservations in Clallam County. It is a derivative of the Zoning layer, and is kept reasonably up to date.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>digital</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20040908</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE9</srccitea>\r\n        <srccontr>Clallam County Indian Reservation boundaries for S_POL_AR and S_POL_LN layers.</srccontr>\r\n      </srcinfo>\r\n      <srcinfo>\r\n        <srccite>\r\n          <citeinfo>\r\n            <origin>Clallam County</origin>\r\n            <pubdate>20070328</pubdate>\r\n            <title>Clallam County Roads</title>\r\n            <geoform>vector digital data</geoform>\r\n            <pubinfo>\r\n              <pubplace>Clallam County</pubplace>\r\n              <publish>Clallam County GIS Department</publish>\r\n            </pubinfo>\r\n            <othercit>This layer depicts the centerline of all roads in the 911 Addressing System throughout Clallam County, including Cities, Tribes, and Olympic National Park. It includes all public and private streets and roads on which addresses may be assigned, or which lead to such roads.\r\n      The layer was assembled from selected segments of the DNR road layer, as it existed in 1994, with additional roads added from the information collected during the county's re-addressing project (1990-94). Geocoding took place several years later, in order to support E911. Address ranges were determined based on measurements made during the re-addressing project, and on existing address patterns as outlined in city addressing ordinances. All known existing addresses were made to match to an appropriate map location. Since 2001, new road edits have included re-alignment of centerlines in the edit area to match orthophotography. Consequently, spatial accuracy varies widely from 2m - 50m.</othercit>\r\n          </citeinfo>\r\n        </srccite>\r\n        <typesrc>digital</typesrc>\r\n        <srctime>\r\n          <timeinfo>\r\n            <sngdate>\r\n              <caldate>20070328</caldate>\r\n            </sngdate>\r\n          </timeinfo>\r\n          <srccurr>publication date</srccurr>\r\n        </srctime>\r\n        <srccitea>BASE4</srccitea>\r\n        <srccontr>Clallam County road centerlines for S_TRANSPORT_LN layer.</srccontr>\r\n      </srcinfo>\r\n      <procstep>\r\n        <procdesc>All Flood Map Projects that will result in a digital FIRM require a digital base map that reflects reference features (i.e., roads, streets, hydrographic features, political jurisdiction boundaries) needed by users to locate properties on FIRMs. During the Project Scoping phase, the Project Team identified the base map to be used and assign the Mapping Partner responsible for obtaining the base map for use by FEMA for FIRM production. Early coordination with all communities affected by a Flood Map Project is an important part of the Project Scoping Process described in Section 1.3 of these Guidelines. Therefore, the Section 1.4 1-68 Guidelines and Specifications for Flood Hazard Mapping Partners [April 2003] Mapping Partner responsible for preparing the Preliminary version of the FIRM or another assigned Mapping Partner shall send a letter to each affected community that: Describes the FIRM product; Requests pertinent information (pertinent information that is requested includes base map data; a current corporate limits map; elevation data [either electronic or hardcopy] and any engineering information that needs to be updated or added to the FIRM); Describes the minimum requirements for the submittal of data to be included in the new FIRM product, and Identifies the base map source that will be used if community data are not available or suitable. A sample version of this letter and other correspondence that may be generated during the Map Production phase of the project are presented in the FEMA Document Control Procedures Manual (FEMA, 2000).</procdesc>\r\n        <procdate>Not complete</procdate>\r\n      </procstep>\r\n    </lineage>\r\n  </dataqual>\r\n  <spdoinfo>\r\n    <direct>Vector</direct>\r\n    <ptvctinf>\r\n      <sdtsterm>\r\n        <sdtstype>String</sdtstype>\r\n        <ptvctcnt>2265</ptvctcnt>\r\n      </sdtsterm>\r\n    </ptvctinf>\r\n  </spdoinfo>\r\n  <spref>\r\n    <horizsys>\r\n      <planar>\r\n        <gridsys>\r\n          <gridsysn>Universal Transverse Mercator</gridsysn>\r\n          <utm>\r\n            <utmzone>10</utmzone>\r\n            <transmer>\r\n              <sfctrmer>0.999600</sfctrmer>\r\n              <longcm>-123.000000</longcm>\r\n              <latprjo>0.000000</latprjo>\r\n              <feast>500000.000000</feast>\r\n              <fnorth>0.000000</fnorth>\r\n            </transmer>\r\n          </utm>\r\n        </gridsys>\r\n        <planci>\r\n          <plance>coordinate pair</plance>\r\n          <coordrep>\r\n            <absres>0.000064</absres>\r\n            <ordres>0.000064</ordres>\r\n          </coordrep>\r\n          <plandu>meters</plandu>\r\n        </planci>\r\n      </planar>\r\n      <geodetic>\r\n        <horizdn>North American Datum of 1983</horizdn>\r\n        <ellips>Geodetic Reference System 80</ellips>\r\n        <semiaxis>6378137.000000</semiaxis>\r\n        <denflat>298.257222</denflat>\r\n      </geodetic>\r\n    </horizsys>\r\n  </spref>\r\n  <eainfo>\r\n    <overview>\r\n      <eaover>The Basemap submission is made up of several data themes containing both spatial and attribute information. These data together represent the current basemap layers for the subject area as identified by FEMA.</eaover>\r\n      <eadetcit>Appendix L of FEMA Guidelines and Specifications for FEMA Flood Hazard Mapping Partners contains a detailed description of the data themes and references to other relevant information</eadetcit>\r\n    </overview>\r\n  </eainfo>\r\n  <distinfo>\r\n    <distrib>\r\n      <cntinfo>\r\n        <cntorgp>\r\n          <cntorg>FEMA, Mapping Information Platform</cntorg>\r\n        </cntorgp>\r\n        <cntaddr>\r\n          <addrtype>mailing address</addrtype>\r\n          <address>500 C Street, S.W.</address>\r\n          <city>Washington</city>\r\n          <state>District of Columbia</state>\r\n          <postal>20472</postal>\r\n          <country>USA</country>\r\n        </cntaddr>\r\n        <cntvoice>1-877-336-2627</cntvoice>\r\n        <cntemail>miphelp@mapmodteam.com</cntemail>\r\n        <cntinst>Data requests must include the full name of the community or county and the FIRM panel number(s) or the 7.5- minute series quadrangle sheet area(s) covered by the request.</cntinst>\r\n      </cntinfo>\r\n    </distrib>\r\n    <resdesc>Downloadable Data</resdesc>\r\n    <distliab>No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty.</distliab>\r\n    <stdorder>\r\n      <digform>\r\n        <digtinfo>\r\n          <formname>ARCE</formname>\r\n          <transize>2.116</transize>\r\n        </digtinfo>\r\n        <digtopt>\r\n          <onlinopt>\r\n            <computer>\r\n              <networka>\r\n                <networkr>http://hazards.fema.gov</networkr>\r\n              </networka>\r\n            </computer>\r\n          </onlinopt>\r\n        </digtopt>\r\n      </digform>\r\n      <fees>Contact Distributor</fees>\r\n    </stdorder>\r\n  </distinfo>\r\n  <metainfo>\r\n    <metd>20080410</metd>\r\n    <metc>\r\n      <cntinfo>\r\n        <cntperp>\r\n          <cntper>John Doe</cntper>\r\n          <cntorg>Federal Emergency Management Agency</cntorg>\r\n        </cntperp>\r\n        <cntaddr>\r\n          <addrtype>mailing address</addrtype>\r\n          <address>500 C Street, S.W.</address>\r\n          <city>Washington</city>\r\n          <state>District of Columbia</state>\r\n          <postal>20472</postal>\r\n          <country>USA</country>\r\n        </cntaddr>\r\n        <cntvoice>1-877-336-2627</cntvoice>\r\n        <cntemail>miphelp@mapmodteam.com</cntemail>\r\n      </cntinfo>\r\n    </metc>\r\n    <metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>\r\n    <metstdv>FGDC-STD-001-1998</metstdv>\r\n    <mettc>local time</mettc>\r\n    <metextns>\r\n      <onlink>http://hazards.fema.gov</onlink>\r\n      <onlink>http://www.epsg.org</onlink>\r\n      <metprof>FEMA NFIP Metadata Content and Format Standard</metprof>\r\n    </metextns>\r\n  </metainfo>\r\n</metadata>\r\n\r\n","source_transform":null,"status":"error"}
