BCCP_GeologicalHazard

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

Title: BCCP_GeologicalHazard
Abstract:
Data is from the 'Goals, Policies and Maps Element' of the Boulder County Comprehensive Plan.
  1. How should this data set be cited?

    Boulder County Land Use Department, BCCP_GeologicalHazard: Boulder County Land Use Department, Boulder, CO.

    Online Links:

    • Server=editgis1; Service=5156; Database=lu; Version=dbo.DEFAULT

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -105.695351
    East_Bounding_Coordinate: -105.050936
    North_Bounding_Coordinate: 40.264166
    South_Bounding_Coordinate: 39.912363

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 1904
    Currentness_Reference:
    REQUIRED: The basis on which the time period of content information is determined.

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  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):

      • G-polygon (303)

    2. What coordinate system is used to represent geographic features?

      The map projection used is Lambert Conformal Conic.

      Projection parameters:
      Standard_Parallel: 39.716667
      Standard_Parallel: 40.783333
      Longitude_of_Central_Meridian: -105.500000
      Latitude_of_Projection_Origin: 39.333333
      False_Easting: 3000000.000316
      False_Northing: 999999.999996

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000250
      Ordinates (y-coordinates) are specified to the nearest 0.000250
      Planar coordinates are specified in survey feet

      The horizontal datum used is D_North_American_1983_HARN.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Resolution: 1.000000
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    LU.LU.BCCP_GeologicalHazard

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    BOCO_GEOHAZ_AREA

    PERIMETER

    GHCA_

    GHCA_ID
    Internal feature number (Source: ESRI)

    ValueDefinition
    1Major hazard
    2Moderate hazard
    3Moderate constraint
    4Minor constraint

    SHADE_
    Internal feature number (Source: ESRI)

    ValueDefinition
    1Major hazard
    2Moderate hazard
    3Moderate constraint
    4Minor constraint

    DESCRIPTION

    SHAPE
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    SHAPE.area

    SHAPE.len


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    Boulder County Land Use Department

  3. To whom should users address questions about the data?

    Boulder County Land Use Department
    PO Box 471
    Boulder, CO 80503

    414-441-3930 (voice)
    #LandUsePlanner@bouldercounty.org

    Contact_Instructions: www.bouldercounty.org


Why was the data set created?

Where in the public interest it may be desirable to permit intensive uses, the county shall direct such uses toward Geologic Constraint Areas rather than toward Geologic Hazard Areas.


How was the data set created?

  1. From what previous works were the data drawn?

  2. How were the data generated, processed, and modified?

    (process 1 of 5)
    Metadata imported.

    (process 2 of 5)
    Dataset copied.

    (process 3 of 5)
    Dataset copied.

    Date: 13-Jan-2010 (process 4 of 5)
    Dataset copied.

    Date: 10-Aug-2010 (process 5 of 5)
    Dataset copied.

  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?

  2. How accurate are the geographic locations?

    Source Scale is 1:50,000. Accuracy is estimated at +/- 140 feet

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Unknown

  5. How consistent are the relationships among the observations, including topology?

    Unknown


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: No constraints, public access without cost.
Use_Constraints:
Knowledge of relevant Boulder County Comprehensive policies is recommended.

  1. Who distributes the data set? (Distributor 1 of 1)

    Boulder County Land Use Department
    PO Box 471
    Boulder, CO 80503

    414-441-3930 (voice)
    #LandUsePlanner@bouldercounty.org

    Contact_Instructions: www.bouldercounty.org
  2. What's the catalog number I need to order this data set?

    Internet Mapping

  3. What legal disclaimers am I supposed to read?

    Boulder County Land Use Department makes no warranties regarding the accuracy, completeness, reliability, or suitability of these data. Boulder County Land Use Department disclaims any liability associated with the use or misuse of these data. In accessing and/or relying on these data, the user fully assumes any and all risk associated with this information.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 25-Aug-2010
Metadata author:
Boulder County Land Use Department
PO Box 471
Boulder, CO 80503

414-441-3930 (voice)
#LandUsePlanner@bouldercounty.org

Contact_Instructions: www.bouldercounty.org
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.9.6 on Thu Feb 10 16:39:23 2011