<rdf:RDF xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dcat="http://www.w3.org/ns/dcat#" xmlns:dct="http://purl.org/dc/terms/">
  <dcat:Dataset rdf:about="http://catalog.data.gov/dataset/mississippi-sound-ms-la-al-g170-bathymetric-digitalelevation-model-30-meter-resolution-derived-">
    <owl:sameAs rdf:resource="urn:uuid:88ccbc64-0534-45b5-9ab4-0c774e699165"></owl:sameAs>
    <dct:description>Bathymetry for Mississippi Sound was derived from thirty-three surveyscontaining 371,210 soundings. Five overlapping, older, less accurate surveyswere omitted before tinning. The average distance between soundings was 89meters. The thirty-three surveys used dated from 1960 to 1979. The range ofsoundings for the surveys used was 0.8 meters to -17.6 meters at mean lowwater. A mean high water value of 0.5 meters was assigned to the shoreline.Twenty-five points were found that were not consistent with the surroundingpoints. These were removed prior to tinning. DEM grid values outside the shoreline (on land) were assigned null values (-32676).Mississippi Sound has forty-four 7.5 minute DEMs and three one degreeDEMs. The 1 degree DEMs were generated from the higher resolution 7.5minute DEMs which covered the estuary. A Digital Elevation Model(DEM) contains a series of elevations ordered from south to northwith the order of the columns from west to east. The DEM isformatted as one ASCII header record (A- record), followed by aseries of profile records (B- records) each of which include a shortB-record header followed by a series of ASCII integer elevations(typically in units of 1 centimeter) per each profile. The lastphysical record of the DEM is an accuracy record (C-record).The 7.5-minute DEM (30- by 30-m data spacing) is cast on theUniversal Transverse Mercator (UTM) projection. It provides coveragein 7.5- by 7.5-minute blocks. Each product provides the samecoverage as a standard USGS 7.5-minute quadrangle but the DEMcontains over edge data. Coverage is available for many estuaries ofthe contiguous United States but is not complete.</dct:description>
        <dcat:keyword>dem</dcat:keyword>
        <dcat:keyword>digital elevation model</dcat:keyword>
        <dcat:keyword>digital bathymetric model</dcat:keyword>
        <dcat:keyword>digital terrain model</dcat:keyword>
        <dcat:keyword>bathymetry</dcat:keyword>
        <dcat:keyword>altitude</dcat:keyword>
        <dcat:keyword>height</dcat:keyword>
        <dcat:keyword>depth</dcat:keyword>
        <dcat:keyword>elevation</dcat:keyword>
        <dcat:keyword>hydrographic survey</dcat:keyword>
        <dcat:keyword>estuary</dcat:keyword>
        <dcat:keyword>estuarine bathymetry</dcat:keyword>
        <dcat:keyword>marine navigation</dcat:keyword>
        <dcat:keyword>oceans</dcat:keyword>
        <dcat:keyword>elevation</dcat:keyword>
        <dcat:keyword>imagerybasemapsearthcover</dcat:keyword>
    <foaf:homepage rdf:resource="http://catalog.data.gov/dataset/mississippi-sound-ms-la-al-g170-bathymetric-digitalelevation-model-30-meter-resolution-derived-"></foaf:homepage>
    <rdfs:label>mississippi-sound-ms-la-al-g170-bathymetric-digitalelevation-model-30-meter-resolution-derived-</rdfs:label>
    <dct:identifier>mississippi-sound-ms-la-al-g170-bathymetric-digitalelevation-model-30-meter-resolution-derived-</dct:identifier>
    <dct:title>Mississippi Sound, MS/LA/AL (G170) Bathymetric DigitalElevation Model (30 meter resolution) Derived From SourceHydrographic Survey Soundings Collected by NOAA</dct:title>
        <dcat:distribution>
            <dcat:Distribution>
                <dcat:accessURL rdf:resource="http://estuarinebathymetry.noaa.gov/finddata.html"></dcat:accessURL>
                    <dct:format>
                        <dct:IMT>
                            <rdf:value>HTML</rdf:value>
                            <rdfs:label>HTML</rdfs:label>
                        </dct:IMT>
                    </dct:format>
               <dct:title>Web Page</dct:title>
            </dcat:Distribution>
        </dcat:distribution>
        <dcat:distribution>
            <dcat:Distribution>
                <dcat:accessURL rdf:resource="http://estuarinebathymetry.noaa.gov"></dcat:accessURL>
               <dct:title>Web Page</dct:title>
            </dcat:Distribution>
        </dcat:distribution>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-east-long</rdfs:label>
            <rdf:value>-88.561417
</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>temporal-extent-end</rdfs:label>
            <rdf:value>1979-01-01</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>contact-email</rdfs:label>
            <rdf:value>robert.wilson@noaa.gov</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>metadata-language</rdfs:label>
            <rdf:value></rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-west-long</rdfs:label>
            <rdf:value>-90.599712
</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>metadata-date</rdfs:label>
            <rdf:value>2006-07-31</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>dataset-reference-date</rdfs:label>
            <rdf:value>[{"type": "publication", "value": "1998-06-06"}]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>resource-type</rdfs:label>
            <rdf:value>dataset</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>temporal-extent-begin</rdfs:label>
            <rdf:value>1960-01-01</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>spatial-reference-system</rdfs:label>
            <rdf:value></rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-north-lat</rdfs:label>
            <rdf:value>30.492693
</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>coupled-resource</rdfs:label>
            <rdf:value>[]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-south-lat</rdfs:label>
            <rdf:value>29.862668
</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>licence</rdfs:label>
            <rdf:value>["These data were prepared by an agency of theUnited States Government. Neither the United States Government norany agency thereof, nor any of their employees, make any warranty,expressed or implied, or assumes any legal liability orresponsibility for the accuracy, completeness, or usefulness of anyinformation, apparatus, product, or process disclosed in this report,or represents that its use would not infringe privately owned rights.Reference therein to any specific commercial product, process, orservice by trade name, trademark, manufacturer, or otherwise does notnecessarily constitute or imply its endorsement, recommendation, orfavoring by the United States Government or any agency thereof. Anyviews and opinions of authors expressed herein do not necessarilystate or reflect those of the United States Government or any agencythereof. Although all data have been used by NOAA, no warranty,expressed or implied, is made by NOAA as to the accuracy of the dataand/or related materials. The act of distribution shall notconstitute any such warranty, and no responsibility is assumed byNOAA in the use of these data or related materials.\n"]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>metadata_type</rdfs:label>
            <rdf:value>geospatial</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>responsible-party</rdfs:label>
            <rdf:value>[{"name": "National Oceanic and Atmospheric Administration(NOAA), National Ocean Service (NOS), Special Projects (SP)", "roles": ["pointOfContact"]}]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>spatial</rdfs:label>
            <rdf:value>{"type": "Polygon", "coordinates": [[[-90.599712, 29.862668], [-90.599712, 30.492693], [-88.561417, 30.492693], [-88.561417, 29.862668], [-90.599712, 29.862668]]]}</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>guid</rdfs:label>
            <rdf:value></rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>spatial-data-service-type</rdfs:label>
            <rdf:value></rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>access_constraints</rdfs:label>
            <rdf:value>["Use Constraints: Not to be used for Navigation.Acknowledgment of the National Oceanic and AtmosphericAdministration- Nation Ocean Service would be appreciated in productsderived from these data.The datum for these bathymetric DEMs is not the same as that used bythe US Geological survey (USGS) for land based DEMs which results ina discontinuity if the two datasets are merged together. Moreover,the shoreline for the USGS DEMs is indeterminate and not the same asthat used for the Bathymetric DEMs. The data within the bathymetry file is floating point. When using the data within a GIS care must be taken to ensure that the data are being read as floating point and not integer data.", "Access Constraints: none"]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>frequency-of-update</rdfs:label>
            <rdf:value>irregular</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>harvest_object_id</rdfs:label>
            <rdf:value>247fcb63-9078-43c9-8a45-2ae359e67696</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>harvest_source_id</rdfs:label>
            <rdf:value>b810aacb-6ee7-4049-aa9e-b20b799664e8</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>harvest_source_title</rdfs:label>
            <rdf:value>NCDDC-NOS-SPO</rdf:value>
          </rdf:Description>
        </dct:relation>
  </dcat:Dataset>
</rdf:RDF>