Lead-rich sediments, Coeur d'Alene River valley, Idaho; Area, volume, tonnage, and lead content: River reach data (by segment)

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:


What does this data set describe?

Title:
Lead-rich sediments, Coeur d'Alene River valley, Idaho; Area, volume, tonnage, and lead content: River reach data (by segment)
Abstract:
This metadata file (pbrchseg.met) describes three shape files used. Shape file rivreach.shp contains the upstream and downstream boundaries of seven reaches of the river. Natural features define river-reach boundaries at the confluence of the North and South forks of the Coeur d'Alene (CdA) River, the transition from a gravel- to a sand- bottomed channel, the mouth of the river, and the base of the delta front. Other river-reach boundaries are at midpoints between river-channel drill transects. River-reach boundaries provide end limits for Estimation Units, for which thickness, volume, tonnage, and lead content of Pb-rich sediment were estimated.
Shape file segments.shp contains up- and down-valley boundaries of 3 sections of the CdA River valley (upper, middle, and lower), each subdivided into three segments (a, b, and c). We defined these valley sections and segments to facilitate definition and description of along-valley differences in the character of deposits of metal- enriched sediment. These boundaries also define east- and west-end limits of Estimation Units, for which thickness, volume, tonnage, and lead content of Pb-rich sediment were estimated.
Shape file Pb1000.shp outlines the area within which samples of surface sediment contain at least 1,000 parts per million (ppm). This outline is the 1,000 ppm Pb contour, which defines the geochemical limit (or cutoff concentration for Pb) of Estimation Units, for which thickness, volume, tonnage, and lead content of Pb-rich floodplain sediment were estimated.
Supplemental_Information:
This Metadata (pbrchseg.met) describes three shape files (segments.shp, rivreach.shp, and Pb1000.shp) of the six shape files used. The segments.shp shape file contains the locations of boundary lines between floodplain segments (or reaches). The rivereach.shp shape file contains the river-reach boundaries for the area of study. The Pb1000 shape file contains the information needed to generate a theme in ArcView, outlining the area covered by Pb-rich surface sediment, containing at least 1,000 ppm of lead.
Metadata cdafldpl.met describes three shape files used (cdasurf4_utm.shp, fldpln2.shp, and fpaream2.shp).
Metadata pbsamthk.met describes two dBase4 files used (alsamPb.dbf and thkpb11.dbf).
  1. How might this data set be cited?
    Bookstom, Arthur A., Box, Stephen E., Campbell, Julie K., Foster, Kathryn I., and Jackson, Berne L., 2001, Lead-rich sediments, Coeur d'Alene River valley, Idaho; Area, volume, tonnage, and lead content: River reach data (by segment): U.S. Geological Survey Open-File Report 01-140, U.S. Geological Survey, Menlo Park, CA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -116.8170
    East_Bounding_Coordinate: -116.2540
    North_Bounding_Coordinate: 47.5927
    South_Bounding_Coordinate: 47.4399
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 1999
    Ending_Date: 2001
    Currentness_Reference:
    publication date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Map
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Complete Chain (20)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 11
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -117.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using Coordinate pair
      Planar coordinates are specified in Meters
      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.4.
      The flattening of the ellipsoid used is 1/294.98.
  7. How does the data set describe geographic features?
    rivreach.dbf
    The shape-file, rivreach.shp, contains the locations of river-reach boundary lines.
    EBDRYREACH
    Number of the river reach, the east boundary of which the line indicates.
    ValueDefinition
    0 
    1 
    2 
    3 
    4 
    5 
    6 
    7 
    segments.dbf
    The ArcView shape-file segments.shp contains the locations of boundary lines between floodplain segments (or reaches).
    E_BDRY_SEG
    East boundary line of floodplain segments
    ValueDefinition
    UaUpper a (Kingston)
    UbUpper b (Cataldo)
    UcUpper c (Dudley)
    MaMiddle a (Rose Lake)
    MbMiddle b (Lane)
    McMiddle c (Killarney)
    LaLower a (Medimont)
    LbLower b (Blue Lake)
    LcLower c (Harrison)
    LdLower d (delta front)
    Ldudelta front, upper (east boundary)
    Ldldelta front, lower (west boundary)
    LINE_NO
    Computer-assigned number of line fragment
    Range of values
    Minimum:0
    Maximum:19
    Units:nominal; the numbers are identifiers
    Resolution:1
    Entity_and_Attribute_Overview:
    The shape file, pb1000.shp, contains polygons that are inside the boundary of the area within which surface-sediment samples contain at least 1,000 ppm of Pb (ie. inside the 1,000 ppm contour for Pb).

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Bookstom,Arthur A.
    • Box, Stephen E.
    • Campbell,Julie K.
    • Foster, Kathryn I.
    • Jackson,Berne L.
  2. Who also contributed to the data set?
    Scott Prevatte helped with the preparation of ArcView GIS files used in our preliminary definition of Estimation units. John Wallis wrote the metadata, Gary Raines reviewed the digital data files and Metadata.
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: Arthur A. Bookstrom
    Geologist
    904 W. Riverside Ave. Rm. 202
    Spokane, Washington
    USA

    1-509-368-3119 (voice)
    1-509-368-3199 (FAX)
    abookstrom@usgs.gov

Why was the data set created?

This data set was prepared as part of an effort to portray the distribution, character, quantity, and Pb content of Pb-rich sediment in the CdA River valley. This is basic information needed to estimate the extent of environmental damage, and evaluate alternative strategies for environmental remediation and restoration.

How was the data set created?

  1. From what previous works were the data drawn?
    Bookstrom and others (1999) (source 1 of 1)
    Bookstom, Arthur A., Box, Stephen E., Campbell, Julie K., Foster, Kathryn I., and Jackson, Berne L., 1999, Digital Map of Surficial Geology, Wetlands, and Deepwater Habitats, Coeur d'Alene River Valley, Idaho.: U.S. Geological Survey Open-File Report 99-548, U.S. Geological Survey, Menlo Park, CA.

    Online Links:

    Type_of_Source_Media: map
    Source_Scale_Denominator: 24000
    Source_Contribution:
    This map was used as a template on which new GIS themes could be overlayed.
  2. How were the data generated, processed, and modified?
    Date: 2000 (process 1 of 2)
    The shape file, rivreach.shp, was created in ArcView by digitizing author-defined river-reach boundary lines on-screen, at scales of 1:24,000 or larger, using a hand-operated mouse. These boundaries were drawn in the context of information in the following themes: 1. generalized map of surficial geology and wetlands (cdasurf4_utm.shp), 2. geochemical sample sites (alsamPb.dbf), and 3. Pb-rich sediment-thickness sites (thkpb11.dbf).
    The shape file, segments.shp, was created in ArcView by digitizing author-defined valley-section and valley-segment boundaries on-screen, at scales of 1:24,000 or larger, using a hand-operated mouse. These boundaries were drawn in the context of information in the following themes:1. generalized map of surficial geology and wetlands (cdasurf4_utm.shp), 2. geochemical sample sites (alsamPb.dbf), and 3. Pb-rich sediment-thickness sites (thkpb11.dbf).
    The shape file, Pb1000.shp, was created in ArcView by digitizing an author-defined 1,000-ppm-Pb contour line, primarily controlled by data points contained in alsamPb.dbf. Digitization was done on-screen, at scales of 1:24,000 or larger, using a hand-operated mouse. For purposes of area estimation, a preliminary shape file was digitized for each river reach and valley segment (as defined in rivreach.shp and segments.shp). Each of these preliminary shape files was used to measure the combined areas of polygons of particular map units (of cdasurf4_utm.shp) within an Estimation Unit (defined to include polygons of a certain map unit, within the 1,000 ppm Pb contour, and between the ends of a particular river reach or valley segment). To prevent double-counting of parts of polygons that overlap boundaries of Estimation Units, those parts of polygons extending outside an Estimation Unit were clipped, and their areas were subtracted from that unit. However, to generate shape file Pb1000.shp, all river-reach and valley-segment files were combined into one file (Pb1000.shp). In that file, entire areas of polygons that overlap Estimation-Unit boundaries are included in adjoining river reaches or valley segments. Therefore, this file (Pb1000.shp) cannot be used to measure the square kilometers of surface area covered by Pb-rich sediment, because parts of polygons that overlap Estimation-Unit boundaries are doubly included. Person who carried out this activity:
    Arthur A. Bookstrom
    U.S. Geological Survey
    Geologist
    904 W. Riverside Ave., Rm 202
    Spokane, WA
    USA

    1-509-368-3119 (voice)
    1-509-368-3199 (FAX)
    abookstrom@usgs.gov
    Data sources used in this process:
    • Bookstrom and others (1999)
    Date: 29-Mar-2001 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    U.S. Geological Survey
    Attn: Art Bookstrom
    Geologist
    904 W. Riverside Ave. Rm. 202
    Spokane, Washington
    USA

    1-509-368-3119 (voice)
    1-509-368-3199 (FAX)
    abookstrom@usgs.gov
  3. What similar or related data should the user be aware of?

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Attribute accuracy was verified by manual comparison of the source data with hardcopy printouts, x - y plots, and on screen evaluations.
  2. How accurate are the geographic locations?
    The horizontal positional accuracy for the digital data is no better than about 15 meters based on digitizing RMS error.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Original vector data was assumed to be complete.
  5. How consistent are the relationships among the observations, including topology?
    These data are believed to be logically consistent, though no tests were performed except to use them in analysis.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: none
Use_Constraints:
Any hardcopies utilizing these data sets shall clearly indicate their source. If the users have modified the data in any way they are obligated to describe the type of modifications they have performed. User specifically agrees not to misrepresent these data sets, nor to imply that changes they made were approved by the U.S. Geological Survey.
  1. Who distributes the data set? (Distributor 1 of 1)
    Arthur A Bookstrom
    U.S. Geological Survey, GEO-WRG-MRS
    W 904 Riverside Avenue
    Spokane, WA
    USA

    509-368-3119 x (voice)
    509-368-3199 (FAX)
    abookstrom@usgs.gov
  2. What's the catalog number I need to order this data set?
  3. What legal disclaimers am I supposed to read?
    The U.S. Geological Survey (USGS) provides this data "as is". The USGS makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. The USGS further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although this data has been processed successfully on computers at the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of this data on any other system, nor does the fact of distribution constitute or imply any such warranty. In no event shall the USGS have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by the USGS.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: Lead concentration points and polygons, river features for geographic context in format Shapefile (version 1.0) Size: 3.4
      Network links: http://pubs.usgs.gov/of/2001/of01-140/of01-140.ZIP
    • Cost to order the data: none


Who wrote the metadata?

Dates:
Last modified: 05-Feb-2016
Metadata author:
Peter N Schweitzer
USGS Midwest Area
Collection manager, USGS Geoscience Data Clearinghouse, http://geo-nsdi.er.usgs.gov/
Mail Stop 954
12201 Sunrise Valley Dr
Reston, VA
USA

703-648-6533 (voice)
703-648-6252 (FAX)
pschweitzer@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://geo-nsdi.er.usgs.gov/metadata/open-file/01-140/pbrchseg.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:34 2018