wui

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

Title: wui
Abstract:
Crook County WUI - Wildland-Urban Interface Original developed boundaries, may be adjusted in the future. Owner: Dave Ownes
An area within or adjacent to an at-risk community identified in recommendations to the Secretary in the Crook County Community Wildfire Protection Plan. And an area that is adjacent to an evacuation route for an at risk community that the Secretary determines - in cooperation with the at-risk community - requires hazardous-fuels reduction to provide safer evacuation.
  1. How should this data set be cited?

    Owens, David, 2005, wui.

    Online Links:

    • \\ds.fs.fed.us\EFS\\library\gis\r06\och\data\wildland_urban_interface.mdb

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -122.167785
    East_Bounding_Coordinate: -118.357101
    North_Bounding_Coordinate: 45.738692
    South_Bounding_Coordinate: 43.169465

  3. What does it look like?

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

    Calendar_Date: 2005
    Currentness_Reference: ground condition

  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 (11)
      • Label point (25)
      • GT-polygon composed of chains (25)
      • Point (8)
      • Composite object (12)
      • Composite object (25)
      • Composite object (9)

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

      The map projection used is Albers Conical Equal Area.

      Projection parameters:
      Standard_Parallel: 43.000000
      Standard_Parallel: 48.000000
      Longitude_of_Central_Meridian: -120.000000
      Latitude_of_Projection_Origin: 34.000000
      False_Easting: 600000.000000
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.001024
      Ordinates (y-coordinates) are specified to the nearest 0.001024
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      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: 0.000010
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates

  7. How does the data set describe geographic features?

    wui

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    OBJECTID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    FID_polygon

    Shape_Length
    Length of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    Shape_Area
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    WUI_NAME

    WUI_CN

    wui.patsites

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    AREA
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    PERIMETER
    Perimeter of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    SITES#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    SITES-ID
    User-defined feature number. (Source: ESRI)

    NAME

    TYPE

    ACRES

    wui.pattype

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    AREA
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    PERIMETER
    Perimeter of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    TYPE#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    TYPE-ID
    User-defined feature number. (Source: ESRI)

    SITES.NAME

    SITES.TYPE

    URBAN.NAME

    URBAN.TYPE

    ACRES

    wui.paturban

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    AREA
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    PERIMETER
    Perimeter of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    URBAN#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    URBAN-ID
    User-defined feature number. (Source: ESRI)

    NAME

    TYPE

    ACRES


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?

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


Why was the data set created?

Wildand fire planning.


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 4)
    Dataset copied.

    Data sources used in this process:

    • c:\lib\gis\och\wui_crook

    (process 2 of 4)
    Dataset copied.

    Data sources used in this process:

    • f:\re_proj\lib\och\wui_crook

    (process 3 of 4)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\BAWRIG~1\LOCALS~1\Temp\xmlAAE.tmp

    (process 4 of 4)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\BAWRIG~1\LOCALS~1\Temp\xml11.tmp

  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?

  3. How accurate are the heights or depths?

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

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


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

  1. Who distributes the data set?[Distributor contact information not provided.]

  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 14-May-2009
Metadata author:
Ochoco National Forest
c/o Dave Owens
Fire Planner
REQUIRED: The city of the address., REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address.

REQUIRED: The telephone number by which individuals can speak to the organization or individual. (voice)

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.9.6 on Mon Sep 14 12:44:08 2009