. .



Oregon / Washington

GIS Metadata

BLM OR Wilderness Study Area Boundary Line

Frequently-asked questions:

What does this data set describe?

BLM OR Wilderness Study Area Boundary Line

WSA_ARC: This data set represents Wilderness Study Area (WSA) boundaries as inventoried in the mid1980's and defined in the October 1991 "Wilderness Study Report". Wilderness Study Areas are essentially roadless areas under BLM jurisdiction. Wilderness Study Areas have special management restrictions and priorities. They are a one-time designation and new WSA or additions to WSA are rare. For a complete description of this data consult the Wilderness Study Areas Spatial Data Standard. http://www.blm.gov/or/datamanagement/index.php

Supplemental information:
The Lost Forest RNA was created in 1972. An area designated as a Research Natural Area (RNA) is where natural processes are allowed to dominate and which is preserved for research, protection, and education of biological and/or physical features. Under current BLM policy, these areas must meet the relevance and importance criteria of ACECs and are designated and managed as ACECs. After passage of FLPMA in 1976, the Lost Forest RNA became an Instant Study Area (ISA) subject to wilderness review under section 603 (a) of FLPMA. While wilderness character was not found to be present in the RNA as a whole (due to roads criss-crossing the center of the unit), the southern third was evaluated separately as part of the Sand Dunes inventory unit, and became a WSA. By decision made in the High Lakes MFP In 1983, the RNA was incorporated into a much larger Lost Forest/Sand Dunes/Fossil Lake ACEC complex. In 2003, the Lakeview RMP/ROD made a decision to modify the ACEC/RNA boundary (see Maps SMA-9 and SMA-9A). The northern boundary was moved slightly to the south to correspond with BLM Road 6141-00. Since the ISA boundary could only be changed by action of Congress, it was not modified at that time. The existing withdrawal associated with the former RNA (and current ISA) boundary was also not modified. The ACEC boundary was also modified on the south to exclude a triangular-shaped area encompassed by the former USAF Backscatter Radar Site withdrawal (which has since been taken over by the GSA). However, this boundary adjustment had no effect on the Lost Forest RNA portion of the ACEC.

  1. How should this data set be cited?

    OR/WA BLM, 20130711, BLM OR Wilderness Study Area Boundary Line.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -123.941513
    East: -116.784984
    North: 49.000115
    South: 41.907988

  3. What does it look like?

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

    Calendar date: 20130711
    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:

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

    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?

    Lines defining Wilderness Study Area boundaries, attributed for source, type, and accuracy of the line data. (Source: Bureau of Land Management)

    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

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

    Bureau of Land Management administrative boundary
    Separating coastal water from territorial sea at 3-mile
    Line of common elevation
    Fence line
    Forest Service administrative boundaries
    Hydrologic unit divide
    Surface jurisdiction boundary
    Edge of lava flow
    Dike or levee
    Edge of marsh, wetland, swamp, or bog boundary
    Edge of quarry, mine, gravel stockpile or other mineral surface disturbance area
    Wilderness, Wild and Scenic River, Historic District or other NLCS designation boundary
    Boundary defined by a straight line segment between two points
    Power transmission line
    A legal right of way forms boundary
    Line generally follows a natural topographic barrier
    Road or primitive road - routes managed for use by low or high-clearance (4WD) vehicles, but not ATV's
    Boundary is offset from a road (not a consistent buffer)
    Lake, pond, reservoir, bay or ocean shoreline or meander line
    Downstream left stream bank
    Downstream right stream bank
    Public Land Survey System derivied aliquot (1/2's, 1/4's) parts and lots
    Trail - routes managed for human-powered, stock or off-highway vehicle forms of travel
    Defining feature is unknown
    Seeding boundary or other relatively permanent vegetation change
    Stream, river, ditch, canal or drainage centerline
    Boundary is offset from a watercourse (not a consistent buffer)
    Closure extension. Used to close small gaps.
    County boundary
    Pasture or other administrative grazing boundary that is not fenced and does not follow a subdivision or some other legal boundary.
    Known boundary not represented by other domain options.
    Motorized vehicle parking area.

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

    Lines duplicated or buffered from Cartographic Feature Files (USFS)
    Digital Elevation Model (30m or better accuracy) used for creation of contours
    Lines generated to connect discontinuous features
    Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs
    Screen digitized linework over Digital Orthoquad backdrop
    Screen digitized linework over Digital Raster Graphic backdrop
    Lines snapped to Geographic Coordinate Database Points
    Lines obtained from a Global Positioning System device
    Linework derived from interpretation of satellite or other non-photographic imagery
    Digitized linework from hardcopy map
    Lines duplicated from Digital Master Title Plat
    Source Layer from BLM GIS
    Survey methods were used to create the linework (e.g., COGO)
    Tiger Data
    Coordinates only given as a legal description (township, range, section)
    Unknown coordinate source
    WODDB Photogrammetric
    CADNSDI - Coordinates from or snapped to the CADNSDI dataset. CADNSDI is the cadastral national spatial data infrastructure publication data set for rectangular and non-rectangular public land survey system (PLSS) data

    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)

    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
    Natural Resource Specialist
    P.O. Box 2965
    Portland, OR 97208

    (503) 808-6086 (voice)
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 5)
    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

    503-808-6009 (voice)
    503-808-6419 (FAX)

    Date: 20110824 (change 2 of 5)
    Homestead WSA was erroneously edited to eliminate the lands within the WSA that are on USFS property. In making that edit, it was missed that there was an isolated BLM approx 120 acre poly at the south end. The USFS lands are indeed WSA, have been attributed with the RARE number (6291) and re-placed back into the corp theme, along with the BLM parcel. All ARC FLM attributes populated; gcd-based data snapped to corp gcdb.

    Person responsible for change:
    Brent Grasty
    Bureau of Land Management
    Planning & Environmental Coordinatior
    100 Oregon St.
    Vale, OR 97918-9629

    (541) -473-6341 (voice)
    (541) 473-6213 (FAX)

    Date: 20120402 (change 3 of 5)
    Adjusted eastern edge of Sutton Mtn WSA to the actual HWY 207 ROW, 50 feet inside of Highway centerline GPSed by Gavin Hoban

    Person responsible for change:
    Pam Keller
    Bureau of Land Management
    GIS Spec.
    28910 Hwy 20 West
    Hines, OR 97738-9424

    (541) 573-4486 (voice)
    (541) 573-4411 (FAX)

    Date: 20120629 (change 4 of 5)
    Added 4 ISAs. RNAs in existence prior to 1976 FLPMA became Instant Study Areas subject to wilderness review under sec 603(a) of FLPMA. Copied Cherry Creek RNA to Douglas-Fir ISA; Little Sink RNA to Little Sink ISA and Horse Ridge RNA to Western Juniper ISA with no change. Used map from the Wilderness EIS and another larger-scale map Jerry Magee found to create the Brewer Spruce ISA boundary. Lost Forest ISA was already in WSA. Brewer Spruce and Lost Forest ISAs have different boundaries from RNAs and this is correct.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management
    GIS Spec.
    28910 Hwy 20 West
    Hines, OR 97738-9424

    (541) 573-4486 (voice)
    (541) 573-4411 (FAX)

    Date: 20130315 (change 5 of 5)
    Updates to Domain DEF_FEATURE and COOR_SRC.

    Person responsible for change:
    Roger Mills
    Bureau of Land Management
    GIS Spec.
    P.O. Box 2965
    Portland, OR 97208

    (503) 808-6340 (voice)

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 from 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 data may be updated by the BLM without notification.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Management Specialist
    P.O Box 2965
    Portland, OR 97208

    503-808-6340 (voice)
    503-808-6419 (FAX)
    Contact Instructions:
    contact instructions

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

    Downloadable Data

  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?

    • Cost to order the data: Contact distributor.

    • Special instructions:

      Data are only available through the Oregon/Washington State office of the Bureau of Land Management.

  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?

Last modified: 20130111
Last reviewed: 20140312

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

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
Hours of Service: 8:00-4:00
Contact Instructions:

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

Back to Top