. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Designated Wilderness Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Designated Wilderness Line

Abstract:
WLD_ARC: BLM Wilderness boundary lines with associated attributes that describe the source and accuracy of the boundaries.

  1. How should this data set be cited?

    OR/WA BLM, 20130411, BLM OR Designated Wilderness Line.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -123.930708
    East: -116.772752
    North: 46.427750
    South: 42.006554

  3. What does it look like?

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

    Calendar date: 20130411
    Currentness reference:
    publication date

  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?

      Indirect spatial reference:
      Oregon

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • String (555)

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

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 2e-008. Longitudes are given to the nearest 2e-008. Latitude and longitude values are specified in Decimal Degrees.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    WLD_ARC
    Lines defining Wilderness boundaries. (Source: Bureau of Land Management)

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    DEF_FEATURE
    The physical feature types that forms the Wilderness boundary. (Source: Bureau of Land Management)
                      

    ValueDefinition
    BLM_ADMIN
    Bureau of Land Management administrative boundary
    COAST_3MILE
    Separating coastal water from territorial sea at 3-mile
    ELEVATION
    Line of common elevation
    FENCE
    Fence line
    FOREST_SERVICE_ADMIN
    Forest Service administrative boundaries
    HU
    Hydrologic unit divide
    JETTY
    Jetty
    JURISDICTION
    Surface jurisdiction boundary
    LAVA
    Edge of lava flow
    LEVEE
    Dyke or levee
    MARSH
    Edge of marsh, wetland, swamp, or bog boundary
    MINERAL DISTURBANCE
    Edge of quarry, mine, gravel stockpile or other mineral surface disturbance area
    NLCS BOUNDARY
    Wilderness, Wild and Scenic River, Historic District or other NLCS designation boundary
    POINT-TO-POINT
    Boundary defined by a straight line segment between two points
    POWERLINE
    Power transmission line
    RIDGE
    Ridge
    RIGHT-OF-WAY
    A legal right of way forms boundary
    RIM
    Line generally follows a natural topographic barrier
    ROAD
    Road or primitive road - routes managed for use by low or high-clearance (4WD) vehicles, but not ATV's
    ROAD_OFFSET
    Boundary is offset from a road (not a consistent buffer)
    SHORELINE
    Lake, pond, reservoir, bay or ocean shoreline or meander line
    STREAM_LBANK
    Downstream left stream bank
    STREAM_RBANK
    Downstream right stream bank
    SUBDIVISION
    Public Land Survey System derivied aliquot (1/2's, 1/4's) parts and lots
    TRAIL
    Trail - routes managed for human-powered, stock or off-highway vehicle forms of travel
    UNKNOWN
    Defining feature is unknown
    VEGETATION
    Seeding boundary or other relatively permanent vegetation change
    WATERCOURSE
    Stream, river, ditch, canal or drainage centerline
    GRAZING_BOUNDARY
    Pasture or other administrative grazing boundary that is not fenced and does not follow a subdivision or other legal boundary
    PARKING_AREA
    Motorized vehicle parking area
    CLOSURE
    Closure extension. Used to close small gaps.
    COUNTY
    County boundary
    OTHER
    Known boundary not represented by other domain options.
    WATERCOURSE_OFFSET
    Boundary is offset from a watercourse (not a consistent buffer)

    COORD_SRC
    The actual source of the GIS coordinates for the line segment (Source: Bureau of Land Management)
                      

    ValueDefinition
    CFF
    Lines duplicated or buffered from Cartographic Feature Files (USFS)
    DEM
    Digital Elevation Model (30m or better accuracy) used for creation of contours
    DIS
    Lines generated to connect discontinuous features
    DLG
    Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs
    DOQ
    Screen digitized linework over Digital Orthoquad backdrop
    DRG
    Screen digitized linework over Digital Raster Graphic backdrop
    GCD
    Lines snapped to Geographic Coordinate Database Points
    GPS
    Lines obtained from a Global Positioning System device
    IMG
    Linework derived from interpretation of satellite or other non-photographic imagery
    MAP
    Digitized linework from hardcopy map
    SOURCEL
    Source layer from BLM GIS
    SRV
    Survey methods were used to create the linework (e.g. COGO)
    TIGER
    Tiger Data
    TRS
    Coordinates only given as a legal description (township, range, section)
    UNK
    Unknown coordinate source
    WOD
    WODDB Photogrammetric

    ACCURACY_FT
    How close, in feet, the spatial GIS depiction is to the actual location on the ground.  There are several factors to consider in GIS error: scale and accuracy of map-based sources, accuracy of GPS equipment, and the skill level of the data manipulators.  A value of '0' indicates no entry was made.  This is the correct value when the COORD_SRC is another GIS theme (DLG, GCD, DEM) because the accuracy is determined by that theme.  If COORD_SRC is MAP or GPS, however, a value of '0' indicates a missing value that should be filled in either with a non-zero number or '-1'.  A value of '-1' indicates that the accuracy is unknown and no reliable estimate can be made. (Source: Bureau of Land Management)
                      

    SHAPE.LEN
    Entity and attribute overview:
    Attributes are provided that give basic information about source, type, and accuracy of the line data.
Back to Top

Who produced the data set?

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

    • OR/WA BLM

  2. Who also contributed to the data set?

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

    Jerry Magee
    Bureau of Land Management, Oregon State Office
    Wilderness Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    503-808-6086 (voice)
    503-808-6334 (FAX)
    jmagee@blm.gov
Back to Top

Why was the data set created?

Resource Management Planning

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: unknown (change 1 of 6)
    Current version of dataset was redesigned and loaded into ArcSDE

    Person responsible for change:
    Stanley Frazier
    Bureau of Land Management, Oregon State Office
    State Data Administrator
    P.O. Box 2965
    Portland, OR 97208-2965
    US

    503-808-6009 (voice)
    503-808-6419 (FAX)
    sfrazier@blm.gov

    Date: 20101102 (change 2 of 6)
    Add 5 acres to Wilderness in T 36S R33E section 17 (Marshall acquisition) in accordance with Steens Act of 2000.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management, Burns District
    GIS Coordinator
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4486 (voice)
    pkeller@blm.gov

    Date: 20110331 (change 3 of 6)
    Replaced Juniper Dunes Wilderness boundary lines with updated ownership (LandLines Legal_Description_Arc) per Mike Fallon.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management, Burns District
    GIS Coordinator
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4486 (voice)
    pkeller@blm.gov

    Date: 20111011 (change 4 of 6)
    Adjusted boundary of Oregon Badlands Wilderness in T18S R14E for new BLM land acquisition.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management, Burns District
    GIS Coordinator
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4486 (voice)
    pkeller@blm.gov

    Date: 20111011 (change 5 of 6)
    Per Gavin Hoban, adjusted Oregon Badlands north-central boundary in T18S R14E Sec. 16 and 17 for acquired Clarno exchange lands, using existing GCD points for some subdivision and GPSed monuments along fence for others. The monument points will become subdivision when input into GCD..

    Person responsible for change:
    Pam Keller
    Bureau of Land Management, Burns District
    GIS Coordinator
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4486 (voice)
    pkeller@blm.gov

    Date: 20120606 (change 6 of 6)
    Snapped Wilderness boundary to updated WSA boundary in NE along Kiger Ridge way.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management, Burns District
    GIS Coordinator
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4486 (voice)
    pkeller@blm.gov

Back to Top

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?

    Accuracy requirements are generally determined by the required use of the GIS data by individual field offices.

  3. How accurate are the heights or depths?

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

    Data is currently available for Oregon and Washington

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

    Meets BLM topology rules

Back to Top

How can someone get a copy of the data set?

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

Access constraints: PUBLIC DATA: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and may contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived, and both scale and accuracy may vary across the data set. These data may not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office for which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This information may be updated without notification.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management, Oregon State Office
    Data Administration Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    503-808-6565 (voice)
    503-808-6374 (FAX)
    ehiebent@blm.gov
    Hours of Service: 7:30 a.m. to 4:00 p.m.

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

  3. What legal disclaimers am I supposed to read?

    The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM 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 the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.

  4. How can I download or order the data?

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20111108
Last reviewed: 20120822

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR 97208
US

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
r2mills@blm.gov
Hours of Service: 8:00-4:00
Contact Instructions:
None

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata(FGDC-STD-001-1998)

Back to Top