<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/digital-data-sets-that-describe-aquifer-characteristics-of-the-alluvial-and-terrace-deposits-al18b8f">
    <owl:sameAs rdf:resource="urn:uuid:8ca9b511-f631-4661-8bfa-595c7b1de6bf"></owl:sameAs>
    <dct:description>This data set consists of digital hydraulic conductivity values for the alluvial and terrace deposits along the Beaver-North Canadian River from the panhandle to Canton Lake in northwestern Oklahoma. Ground water in 830 square miles of the Quaternary-age alluvial and terrace aquifer is an important source of water for irrigation, industrial, municipal, stock, and domestic supplies. The aquifer consists of poorly sorted, fine to coarse, unconsolidated quartz sand with minor amounts of clay, silt, and basal gravel. The hydraulically connected alluvial and terrace deposits unconformably overlie the Tertiary-age Ogallala Formation and Permian-age formations. Six zones of ranges of hydraulic conductivity values for the alluvial and terrace deposits reported in a ground-water modeling report are used in this data set. The hydraulic conductivity values range from 0 to 160 feet per day, and average 59 feet per day. The features in the data set representing aquifer boundaries along geological contacts were extracted from a published digital surficial geology data set based on a scale of 1:250,000. The geographic limits of the aquifer and zones representing ranges of hydraulic conductivity values were digitized from folded paper maps, at a scale of 1:250,000 from a ground-water modeling report. Ground-water flow models are numerical representations that simplify and aggregate natural systems. Models are not unique; different combinations of aquifer characteristics may produce similar results. Therefore, values of hydraulic conductivity used in the model and presented in this data set are not precise, but are within a reasonable range when compared to independently collected data.</dct:description>
        <dcat:keyword>inlandwaters</dcat:keyword>
        <dcat:keyword>alluvium</dcat:keyword>
        <dcat:keyword>northwestern oklahoma</dcat:keyword>
        <dcat:keyword>ground water</dcat:keyword>
        <dcat:keyword>hydraulic conductivity</dcat:keyword>
        <dcat:keyword>beaver river alluvial and terrace aquifer</dcat:keyword>
        <dcat:keyword>north canadian alluvial and terrace aquifer</dcat:keyword>
        <dcat:keyword>terrace deposits</dcat:keyword>
        <dcat:keyword>groundwater vulnerability</dcat:keyword>
        <dcat:keyword>terrace aquifer</dcat:keyword>
        <dcat:keyword>alluvial aquifer</dcat:keyword>
        <dcat:keyword>beaver alluvial and terrace aquifer</dcat:keyword>
        <dcat:keyword>groundwater</dcat:keyword>
        <dcat:keyword>ground-water vulnerability</dcat:keyword>
        <dcat:keyword>north canadian river alluvial and terrace aquifer</dcat:keyword>
        <dcat:keyword>alluvial and terrace aquifer</dcat:keyword>
        <dcat:keyword>aquifers</dcat:keyword>
        <dcat:keyword>terrace</dcat:keyword>
    <foaf:homepage rdf:resource="http://catalog.data.gov/dataset/digital-data-sets-that-describe-aquifer-characteristics-of-the-alluvial-and-terrace-deposits-al18b8f"></foaf:homepage>
    <rdfs:label>digital-data-sets-that-describe-aquifer-characteristics-of-the-alluvial-and-terrace-deposits-al18b8f</rdfs:label>
    <dct:identifier>digital-data-sets-that-describe-aquifer-characteristics-of-the-alluvial-and-terrace-deposits-al18b8f</dct:identifier>
    <dct:title>Digital data sets that describe aquifer characteristics of the alluvial and terrace deposits along the Beaver-North Canadian River from the panhandle to Canton Lake in northwestern Oklahoma</dct:title>
        <dcat:distribution>
            <dcat:Distribution>
                <dcat:accessURL rdf:resource="http://water.usgs.gov/GIS/dsdl/ofr96-446_cond.e00.gz"></dcat:accessURL>
                    <dct:format>
                        <dct:IMT>
                            <rdf:value>export</rdf:value>
                            <rdfs:label>export</rdfs:label>
                        </dct:IMT>
                    </dct:format>
               <dct:title>Export</dct:title>
            </dcat:Distribution>
        </dcat:distribution>
        <dcat:distribution>
            <dcat:Distribution>
                <dcat:accessURL rdf:resource="http://water.usgs.gov/GIS/dsdl/ofr96-446_cond.dlg.gz"></dcat:accessURL>
                    <dct:format>
                        <dct:IMT>
                            <rdf:value>export</rdf:value>
                            <rdfs:label>export</rdfs:label>
                        </dct:IMT>
                    </dct:format>
               <dct:title>Other</dct:title>
            </dcat:Distribution>
        </dcat:distribution>
        <dcat:distribution>
            <dcat:Distribution>
                <dcat:accessURL rdf:resource="http://water.usgs.gov/lookup/getspatial?ofr96-446_cond"></dcat:accessURL>
                    <dct:format>
                        <dct:IMT>
                            <rdf:value>export</rdf:value>
                            <rdfs:label>export</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://wwwok.cr.usgs.gov/gis/geology/index.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>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-east-long</rdfs:label>
            <rdf:value>-98.5487</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>bbox-north-lat</rdfs:label>
            <rdf:value>36.9727</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>graphic-preview-type</rdfs:label>
            <rdf:value>GIF</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>graphic-preview-file</rdfs:label>
            <rdf:value>http://water.usgs.gov/lookup/get?OFR96-446/browse.gif</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-south-lat</rdfs:label>
            <rdf:value>36.0439</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>spatial_harvester</rdfs:label>
            <rdf:value>True</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>spatial</rdfs:label>
            <rdf:value>{"type": "Polygon", "coordinates": [[[-99.965, 36.0439], [-98.5487, 36.0439], [-98.5487, 36.9727], [-99.965, 36.9727], [-99.965, 36.0439]]]}</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>progress</rdfs:label>
            <rdf:value>completed</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>access_constraints</rdfs:label>
            <rdf:value>["Use Constraints: Lines representing geological contacts were extracted from the digital geology data set by Cederstrand (1996), based on a scale of 1:250,000. Lines representing the geographic limits of the aquifer were digitized from a folded paper map (30 inches by 22 inches) at a scale of 1:250,000 from Davis and Christenson (1981, plate 7). The lines digitized from the source map had a maximum registration root-mean-squared-error (RMSE) of 0.018 map inches (0.046 centimeters) or 377.76 feet (115.14 meters) ground distance. Boundaries represented at these scales are indicative of broad, regional trends and should not be interpreted as site specific. Ground-water flow models are numerical representations that simplify and aggregate natural systems. Models are not unique; different combinations of aquifer characteristics may produce similar results. The hydraulic conductivity and recharge are closely interrelated. As long as these two model inputs are in balance the model has a small mean residual; it represents the natural system numerically. If the hydraulic conductivity is accurately known, the model can be used to accurately determine recharge. Likewise, if the hydraulic conductivity is poorly known, then the recharge will be poorly determined. Therefore, values of hydraulic conductivity used in the model and presented in this data set are not precise, but are within a reasonable range when compared to independently collected data. In most aquifers, hydraulic conductivity measurements made in wells or in cores will range over several orders of magnitude, even over short horizontal and vertical distances. Hydraulic conductivity values derived from ground-water flow models represent areal generalizations and do not reflect the large local variance in well or core measurements.", "Access Constraints: None."]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>contact-email</rdfs:label>
            <rdf:value>dlrunkle@usgs.gov</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>bbox-west-long</rdfs:label>
            <rdf:value>-99.9650</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>metadata-date</rdfs:label>
            <rdf:value>2004-11-08</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>dataset-reference-date</rdfs:label>
            <rdf:value>[{"type": "publication", "value": "1997-01-01"}]</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>graphic-preview-description</rdfs:label>
            <rdf:value>A browse image of the four aquifer data sets.</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>frequency-of-update</rdfs:label>
            <rdf:value>notPlanned</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>licence</rdfs:label>
            <rdf:value>["Although this data set has been used by the U.S. Geological\nSurvey, U.S. Department of the Interior, no warranty expressed or\nimplied is made by the U.S. Geological Survey as to the accuracy\nof the data and related materials. The act of distribution shall not \nconstitute any such warranty, and no responsibility is assumed by \nthe U.S. Geological Survey in the use of this data, software, or \nrelated materials.\n\nAny use of trade, product, or firm names is for descriptive\npurposes only and does not imply endorsement by the U.S.\nGovernment."]</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": "U.S. Geological Survey", "roles": ["pointOfContact"]}]</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>metadata-language</rdfs:label>
            <rdf:value></rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>harvest_object_id</rdfs:label>
            <rdf:value>aab05138-4fc3-4ac3-a78a-9c99fac2058a</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>harvest_source_id</rdfs:label>
            <rdf:value>e11eb0c1-b794-4812-9369-1bd7306336cd</rdf:value>
          </rdf:Description>
        </dct:relation>
        <dct:relation>
          <rdf:Description>
            <rdfs:label>harvest_source_title</rdfs:label>
            <rdf:value>Water NSDI Node Spatial Datasets</rdf:value>
          </rdf:Description>
        </dct:relation>
  </dcat:Dataset>
</rdf:RDF>