<?xml version='1.0' encoding='UTF-8'?>
<metadata xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Josh Woda</origin>
        <origin>Jason Finkelstein</origin>
        <origin>John Williams</origin>
        <pubdate>20220502</pubdate>
        <title>Cincinnatus: Supplementary Points</title>
        <geoform>Data Release</geoform>
        <pubinfo>
          <pubplace>Troy, NY</pubplace>
          <publish>U.S. Geological Survey</publish>
        </pubinfo>
        <onlink>https://doi.org/10.5066/P96R5K5R</onlink>
        <lworkcit>
          <citeinfo>
            <origin>Nicholas Corson-Dosch</origin>
            <origin>Michael N. Fienen</origin>
            <origin>Jason S. Finkelstein</origin>
            <origin>Andrew T. Leaf</origin>
            <origin>Jeremy T. White</origin>
            <origin>Joshua C. Woda</origin>
            <origin>John H. Williams</origin>
            <pubdate>2022</pubdate>
            <title>Areas contributing recharge to priority wells in valley-fill aquifers in the Neversink River and Rondout Creek drainage basins, New York</title>
            <geoform>publication</geoform>
            <pubinfo>
              <pubplace>n/a</pubplace>
              <publish>US Geological Survey</publish>
            </pubinfo>
            <onlink>https://doi.org/10.3133/sir20215112</onlink>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset includes "smoothing points" used in the creation of the Cincinnatus hydrogeologic framework.  Smoothing points were manually added by the project team and were used to enhance interpolated layers using geologic assumptions and include: valley edge points, centerline bedrock points (and where applicable L1 and L2 points), and upland bedrock SSURGO points.</abstract>
      <purpose>The purpose of this dataset was to guide the raster generation models using sound geologic assumptions.</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>2019</begdate>
          <enddate>2020</enddate>
        </rngdates>
      </timeinfo>
      <current>ground condition</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>None planned</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-76.03</westbc>
        <eastbc>-75.75</eastbc>
        <northbc>42.65</northbc>
        <southbc>42.45</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>USGS Thesaurus</themekt>
        <themekey>Sourcewater</themekey>
        <themekey>Valley Fill</themekey>
        <themekey>Bedrock Mapping</themekey>
        <themekey>Aquifer mapping</themekey>
        <themekey>Glacial geology</themekey>
      </theme>
      <theme>
        <themekt>USGS Metadata Identifier</themekt>
        <themekey>USGS:5fc54c74d34e4b9faad8882f</themekey>
      </theme>
      <place>
        <placekt>Getty Thesaurus of Geographic Names</placekt>
        <placekey>Cincinnatus</placekey>
        <placekey>New York</placekey>
        <placekey>Cortland County</placekey>
        <placekey>Chenango County</placekey>
      </place>
    </keywords>
    <accconst>none</accconst>
    <useconst>none</useconst>
    <ptcontac>
      <cntinfo>
        <cntperp>
          <cntper>Joshua C Woda</cntper>
          <cntorg>NORTHEAST REGION: NEW YORK WATER SCI CTR</cntorg>
        </cntperp>
        <cntpos>Hydrologist</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>425 Jordan Road</address>
          <city>Troy</city>
          <state>NY</state>
          <postal>12180</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>518-285-5606</cntvoice>
        <cntemail>jwoda@usgs.gov</cntemail>
      </cntinfo>
    </ptcontac>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>Values were quality checked multiple ways, including outlier detection and physical examination of the data.</attraccr>
    </attracc>
    <logic>A check was performed for duplication. Supplementary point elevation data were checked to ensure for logical geologic sense (i.e. bedrock elevation is not above land surface).</logic>
    <complete>Dataset is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.</complete>
    <posacc>
      <horizpa>
        <horizpar>No formal positional accuracy tests were conducted</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>Values were quality checked  multiple ways, including outlier detection and physical examination of the data.</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>The United States Geologic Survey</origin>
            <pubdate>2020</pubdate>
            <title>NWIS well log data</title>
            <geoform>Database table</geoform>
            <pubinfo>
              <pubplace>https://waterdata.usgs.gov/nwis</pubplace>
              <publish>The United States Geologic Survey</publish>
            </pubinfo>
            <onlink>https://waterdata.usgs.gov/nwis</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Database table</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19760916</begdate>
              <enddate>20190729</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>incomplete</srccurr>
        </srctime>
        <srccitea>NWIS well log data</srccitea>
        <srccontr>This data was used to help define the depth to bedrock</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>The New York Department of Environmental Conservation</origin>
            <pubdate>2020</pubdate>
            <title>NY DEC well logs</title>
            <geoform>Well logs and spreadsheet</geoform>
            <pubinfo>
              <pubplace>Albany, NY</pubplace>
              <publish>The New York Department of Environmental Conservation</publish>
            </pubinfo>
            <onlink>https://webapps.usgs.gov/geologlocator/#!/search</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Well Logs</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19300201</begdate>
              <enddate>20190630</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>incomplete</srccurr>
        </srctime>
        <srccitea>NY DEC well logs</srccitea>
        <srccontr>This data provided by the NY DEC was used to help define hydrogeologic layers, surficial geology, and better understand the subsurface in general</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>The New York Department of Transportation</origin>
            <pubdate>2020</pubdate>
            <title>NY Department of Transportation Boreholes</title>
            <geoform>Boring logs provided as shapefile</geoform>
            <pubinfo>
              <pubplace>N/A</pubplace>
              <publish>The New York Department of Transportation</publish>
            </pubinfo>
            <onlink>https://waterdata.usgs.gov/nwis</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Boring logs provided as shapefile</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19660908</begdate>
              <enddate>20180328</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>incomplete</srccurr>
        </srctime>
        <srccitea>NY DOT Boreholes</srccitea>
        <srccontr>This data provided by the NY DOT was used to help define hydrogeologic layers, surficial geology, and better understand the subsurface in general</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>United States Department of Agriculture</origin>
            <pubdate>2014</pubdate>
            <title>SSURGO soils, Cortland County NY</title>
            <geoform>shapefile Data</geoform>
            <pubinfo>
              <pubplace>Fort Worth, Texas</pubplace>
              <publish>United States Department of Agriculture</publish>
            </pubinfo>
            <onlink>https://cugir.library.cornell.edu/catalog/cugir-007903</onlink>
          </citeinfo>
        </srccite>
        <typesrc>shapefile Data</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20140914</begdate>
              <enddate>20141014</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Complete</srccurr>
        </srctime>
        <srccitea>SSURGO</srccitea>
        <srccontr>Soil Survey Geographic Database for Cortland County, NY</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Axis geospatial LLC</origin>
            <pubdate>2015</pubdate>
            <title>LIDAR coverage Cortland County</title>
            <geoform>point data</geoform>
            <pubinfo>
              <pubplace>Easton, Maryland</pubplace>
              <publish>Axis geospatial LLC</publish>
            </pubinfo>
            <onlink>ftp://ftp.gis.ny.gov/elevation/LIDAR/County_Cortland2005/BareEarth/</onlink>
          </citeinfo>
        </srccite>
        <typesrc>point data</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20150401</begdate>
              <enddate>20150630</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Complete</srccurr>
        </srctime>
        <srccitea>LIDAR coverage</srccitea>
        <srccontr>LIDAR was used as a benchmark to: help define hydrogeologic layer elevations and, adjust and create surficial geology, and provide understanding about the hydrogeologic framework. A raster was generated from point data available online.</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>U.S. Department of Agriculture, Natural Resources Conservation Service</origin>
            <pubdate>2015</pubdate>
            <title>SSURGO soils, Chenango County NY</title>
            <geoform>Shapefile</geoform>
            <pubinfo>
              <pubplace>Fort Worth, Texas</pubplace>
              <publish>U.S. Department of Agriculture, Natural Resources Conservation Service</publish>
            </pubinfo>
            <onlink>https://cugir.library.cornell.edu/catalog/cugir-007902</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Shapefile</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20150101</begdate>
              <enddate>20151231</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Complete</srccurr>
        </srctime>
        <srccitea>SSURGO</srccitea>
        <srccontr>Soil Survey Geographic Database for Chenango County, NY</srccontr>
      </srcinfo>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>Axis GeoSpatial, LLC</origin>
            <pubdate>2015</pubdate>
            <title>New York Tiled LiDAR: Madison and Otsego Counties</title>
            <geoform>Points</geoform>
            <pubinfo>
              <pubplace>Easton, MD</pubplace>
              <publish>Axis GeoSpatial, LLC</publish>
            </pubinfo>
            <onlink>ftp://ftp.gis.ny.gov/elevation/LIDAR/NYSGPO_MadisonOtsego_2015/</onlink>
          </citeinfo>
        </srccite>
        <typesrc>Points</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20150416</begdate>
              <enddate>20150606</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>Complete</srccurr>
        </srctime>
        <srccitea>New York Tiled LIDAR: Madison and Otsego Counties</srccitea>
        <srccontr>1-meter resolution LIDAR</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>The below processes are described for each unique point type, unique point types are combined when process are similar: 
Casing - Minimum Depth Bedrock Uplands: The casing method primarily conducted on wells originating from NWIS. Thus the first step was to bring all groundwater NWIS wells in the study area into ArcGIS.   Drillers commonly set casing lengths to go 10 ft into bedrock. Thus, the assumption was made that in wells where the total well depth was at least 20 ft greater than the casing depth, the unconsolidated thickness was estimated to be 10 ft less than casing length.  This subtraction was performed within ArcGIS.</procdesc>
        <procdate>2019</procdate>
      </procstep>
      <procstep>
        <procdesc>DOT - Minimum Depth Bedrock Valley:  New York Department of Transportation (DOT) wells were provided to the USGS by the DOT in a ready to view shapefile. The shapefile contained an image of geologic layers, description of geologic layers and sediment types at depth. When used, points were manually added to the location of the borehole and geologic layers were added as depths and thicknesses within the point dataset. When data was lacking and in an area and DOT logs did not have a BR depth, it was assumed that the depth of the borehole was the bedrock depth (to ensure that bedrock was not modeled excessively shallow).</procdesc>
        <procdate>2019</procdate>
      </procstep>
      <procstep>
        <procdesc>Minimum Depth Bedrock Valley: Minimum bedrock depths for DEC wells were used when data was lacking. DEC wells were provided to the USGS by the NY DEC. Every log within the study area was looked at and geologic layers pertaining to the hydrogeologic framework were recorded in an excel spreadsheet before being uploaded into ArcGIS as a point dataset. When available, point datasets eventually contained elevations of the bottom of the unconfined aquifer (L1), bottom of the confining unit (L2), and top of bedrock (L3). When data was lacking in an area, but a relatively deep well was present, it was assumed that the depth of the well was the bedrock depth (to ensure that bedrock was not modeled excessively shallow).</procdesc>
        <procdate>2019</procdate>
      </procstep>
      <procstep>
        <procdesc>Smoothing points:  smoothing points were added for both bedrock and valley fill hydrogeologic layers to help guide the interpolation in areas where data was lacking, or to mimic known valley fill shapes (i.e. the U shape of typical valley fill valleys).  For bedrock, equidistant smoothing points (200 feet) were generated in a straight line down the center of the valley.  Smoothing points nearby known bedrock elevations (i.e a bedrock elevation derived from a well log or cross section) were assigned the known value. Points in between these were assigned values calculated from the linear difference between the two known points. These points assure that valley shape (i.e deep part of valley typically in the center of the valley) is preserved. Smoothing points were also added within select regions of the study area for defining the bottom of L1 and L2 where data was extremely sparse.  Smoothing point values were assigned in a similar manner as bedrock, but with larger spacing between points.</procdesc>
        <procdate>2019</procdate>
      </procstep>
      <procstep>
        <procdesc>Valley Edge Points: Valley edge points were first generated by creating points spaced 200 feet apart placed along the aquifer boundary (assumed to be the valley edge).  Bedrock was assumed to be close to the surface at these points (3.35 meters) in order to give the valley a clear U shape (common in valley fill aquifers).  If strong upland bedrock data (i.e multiple well logs near the valley edge) was present that indicated a thickness greater than 3.35 meters, that data was incorporated into the nearby points.</procdesc>
        <procdate>2019</procdate>
      </procstep>
      <procstep>
        <procdesc>SSURGO - Bedrock Uplands: In order to add these points, SSURGO polygons were downloaded from the NY GIS Clearinghouse. Specific polygons were isolated based on known soil types that were shallow to bedrock or based on keywords that indicated that bedrock was at or near the surface. Next, a point grid (spaced 300 feet apart) was added over the entire study area and points were selected that fell within shallow bedrock SSURGO polygons. These points were assigned a depth to bedrock indicative of the minimum thickness used within this study area (i.e. 3 meters).</procdesc>
        <procdate>2019</procdate>
      </procstep>
      <procstep>
        <procdesc>Bedrock elevation values were calculated by first extracting surface elevation from the LIDAR at each well point location. The extracted LIDAR value was subtracted by the depth to bedrock value for each supplemental point, which would equal the bedrock elevation. Other layer elevations were also calculated in this manner.</procdesc>
        <procdate>2019</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spref>
    <horizsys>
      <geograph>
        <latres>1.0E-5</latres>
        <longres>1.0E-5</longres>
        <geogunit>Decimal degrees</geogunit>
      </geograph>
      <geodetic>
        <horizdn>D_North_American_1983</horizdn>
        <ellips>NAD_1983</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
    <vertdef>
      <altsys>
        <altdatum>North American Vertical Datum of 1988</altdatum>
        <altres>0.01</altres>
        <altunits>meter</altunits>
        <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
      </altsys>
    </vertdef>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>Cincinnatus_Supplementary_Points</enttypl>
        <enttypd>This shapefile contains data points with values that are inferred or interpreted based on associated data or geologic assumptions. These data are used to help guide and improve the corresponding interpolations in ways that best represent valley fill aquifers and till covered uplands.</enttypd>
        <enttypds>The authors of this dataset conceived these values</enttypds>
      </enttyp>
      <attr>
        <attrlabl>WellNO</attrlabl>
        <attrdef>This column only applies to 12 wells and/or DOT boreholes. For these wells, a casing method (extensively defined in Finkelstein and others, 2022) was used to establish the minimum depth to bedrock. This column serves to identify the name of these wells/boreholes</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <udom>This column describes names, and thus does not have a set defined value or variable</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Latitude</attrlabl>
        <attrdef>The latitude in decimal degrees of the associated point</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>42.488559</rdommin>
            <rdommax>42.636438</rdommax>
            <attrunit>Decimal degrees</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Longitude</attrlabl>
        <attrdef>The longitude in decimal degrees of the associated point</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>-76.00454</rdommin>
            <rdommax>-75.732029</rdommax>
            <attrunit>Decimal degrees</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Point_Type</attrlabl>
        <attrdef>Describes what kind of supplemental point the row is describing. For ease, multiple point types were compiled into one shapefile rather than having multiple datasets. The name and description of what each point type represent are further described below</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <edom>
            <edomv>Casing - Minimum Depth Bedrock Uplands</edomv>
            <edomvd>These points predict the depth to bedrock, calculated using the casing method described in Finkelstein and others, 2022</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>DOT - Minimum Depth Bedrock Valley</edomv>
            <edomvd>These points predict the minimum possible depth to bedrock, calculated using bridge boring logs provided by the New York Department of Transportation. This approach was only used in area where bedrock data was extremely sparse. Thus using a minimum bedrock depth provided better information for the model</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Minimum Depth Bedrock Valley</edomv>
            <edomvd>These points predict the minimum possible depth to bedrock, calculated using DEC well logs. This approach was only used in area where bedrock data was extremely sparse. Thus using a minimum bedrock depth provided better information for the model</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Smoothing - Bedrock Valley</edomv>
            <edomvd>These are equidistant (200 feet) points generated in a straight line down the center of the valley.  Points nearby known bedrock elevations are assigned the known value. Points in between these are assigned values based on the linear difference between the two known points. These points assure that valley shape (i.e deep part of valley typically in the center of the valley) is preserved</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Smoothing - Layer 1</edomv>
            <edomvd>Smoothing points were added in data sparse regions between two known points to help guide the interpolation</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Smoothing - Layer 2</edomv>
            <edomvd>Smoothing points were added in data sparse regions between two known points to help guide the interpolation</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>SSURGO - Bedrock Uplands</edomv>
            <edomvd>Points spaced 200 feet apart (grid fashion) within SSURGO polygons deemed to have bedrock within 3 meters of the surface.  These points allowed better constraint to upland bedrock surface where data was sparse</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Valley edge - Bedrock Uplands and Valley</edomv>
            <edomvd>Points spaced 200 feet apart placed along the aquifer boundary (assumed to be the valley edge).  Bedrock was assumed to be close to the surface at these points (3.35 meters) in order to give the valley a clear U shape (common in valley fill aquifers).  If strong upland bedrock data was present that indicated a thickness greater than 3.35, that data was incorporated into the nearby points.</edomvd>
            <edomvds>Producer-defined</edomvds>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Comments</attrlabl>
        <attrdef>Assorted comments pertaining to select points, used to provide additional clarity about the smoothing point (when provided)</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <udom>Assorted comments pertaining to select points, used to provide additional clarity about the smoothing point (when provided)</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Elev_Meter</attrlabl>
        <attrdef>The surface elevation of various geologic layers (identified in the "Point_Type" column) in meters.</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>270.669006</rdommin>
            <rdommax>569.369995</rdommax>
            <attrunit>Meters</attrunit>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>DTB_Meters</attrlabl>
        <attrdef>The depth to bedrock calculated from the land surface elevation minus the bedrock surface elevation. Any value of 0 is a NULL value within the provided shapefile. This is not applicable for the accompanying feature class, as the NULL values will be shown.</attrdef>
        <attrdefs>Producer defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>0.441007</rdommin>
            <rdommax>39.878908</rdommax>
            <attrunit>Meters</attrunit>
          </rdom>
        </attrdomv>
      </attr>
    </detailed>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntperp>
          <cntper>ScienceBase</cntper>
          <cntorg>U.S. Geological Survey</cntorg>
        </cntperp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>Denver Federal Center, Building 810, Mail Stop 302</address>
          <city>Denver</city>
          <state>CO</state>
          <postal>80225</postal>
          <country>USA</country>
        </cntaddr>
        <cntvoice>1-888-275-8747</cntvoice>
        <cntemail>sciencebase@usgs.gov</cntemail>
      </cntinfo>
    </distrib>
    <distliab>Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. Not for navigational use. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.</distliab>
  </distinfo>
  <metainfo>
    <metd>20260424</metd>
    <metc>
      <cntinfo>
        <cntperp>
          <cntper>Josh Woda</cntper>
          <cntorg>The United States Geologic Survey</cntorg>
        </cntperp>
        <cntpos>Hydrologist</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>425 Jordan Road</address>
          <city>Troy</city>
          <state>New York</state>
          <postal>12180</postal>
          <country>The United States</country>
        </cntaddr>
        <cntvoice>518-285-5606</cntvoice>
        <cntemail>jwoda@USGS.gov</cntemail>
      </cntinfo>
    </metc>
    <metstdn>Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
  </metainfo>
</metadata>
