. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Areas of Critical Environmental Concern Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Areas of Critical Environmental Concern Line

Abstract:
ACEC_ARC: This data set shows the boundary lines for Areas of Critical Environmental Concern under BLM management in Oregon and Washington.

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, 20140630, BLM OR Areas of Critical Environmental Concern Line.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.513434
    East: -116.784579
    North: 48.977140
    South: 41.978511

  3. What does it look like?

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

    Calendar date: 20140630
    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 (1608)
      • String (1608)

    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?

    ACEC_ARC
    Areas of Critical Environmental Concern attributed for basic information including designation process, date, and type. (Source: Bureau of Land Management)

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    COORD_SRC
    The actual source of the GIS coordinates for the line segment (Source: BLM)
                      

    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
    MTP
    Lines duplicated from Digital Master Title Plat
    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
    CADNSDI
    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

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

    GLOBALID
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    Shape
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    DEF_FEATURE
    The physical feature types that forms the ACEC 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
    Dike 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
    WATERCOURSE_OFFSET
    Boundary is offset from a watercourse (not a consistent buffer)
    CLOSURE
    Closure extension. Used to close small gaps.
    COUNTY
    County boundary
    GRAZING_BOUNDARY
    Pasture or other administrative grazing boundary that is not fenced and does not follow a subdivision or some other legal boundary.
    OTHER
    Known boundary not represented by other domain options.
    PARKING_AREA
    Motorized vehicle parking area.

    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?

    Mark R. Mousseaux
    Bureau of Land Management
    ACEC Data Steward
    3040 Biddle Road
    Medford, OR 97504
    US

    (541) 618-2232 (voice)
    mmoussea@blm.gov
Back to Top

Why was the data set created?

The purpose of this dataset is to depict the bounding edges and their description of ACECs in Washington and Oregon for use by BLM staff in land use planning.

Back to Top

How was the data set created?

  1. Where did the data come from?

    BLM FOI (source 1 of 7)

    BLM Oregon State Office, unknown, Forest Operations Inventory: OR BLM, Portland, OR.

    Type of source media: None
    Source scale denominator: 1200
    Source contribution:
    Polygon

    DOQ (source 2 of 7)

    USGS, unknown, Digital Orthophoto Quadrangles: EROS Data Center, Sioux Falls.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Reference

    GCDB (source 3 of 7)

    OR/WA BLM, 19890101, Geographic Coordinate Database Oregon (Point and Line): OR BLM, Portland, OR.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Lines, reference

    Streams (source 4 of 7)

    OR/WA BLM, 19970915, Streams, Linear Features (Line, Node): OR BLM, Portland, OR.

    Type of source media: None
    Source contribution:
    Lines

    LLI (source 5 of 7)

    OR/WA BLM, 19960901, Landlines Oregon (Polygon, Node, Line): OR BLM, Portland, OR.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Lines, Reference

    DRG (source 6 of 7)

    USGS, Digital Raster Graphics.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Reference

    GTRN (source 7 of 7)

    OR/WA BLM, unknown, Ground Transportation Roads and Trails: OR BLM, Portland, OR.

    Type of source media: None
    Source scale denominator: 24000
    Source contribution:
    Lines

  2. What changes have been made?

    Date: unknown (change 1 of 7)
    Updated and realigned ACEC polygons to the Land Lines Index (LLI). BLM land boundaries where used as the primary defining reference. Where BLM jurisdictional lines were not available (i.e. private lands, interior direction changes, island boundaries within major rivers), PLSS lines where used where possible. Boundaries that followed 1/4 sections or smaller units where estimated and should be considered accurate to +- 10 feet. In the case of islands and riverbank boundaries (e.g. islands within the Yakima Islands ACEC) the 2009 NAIP Imagery was used to define boundaries. Accuracy along these boundaries were considered to be +-10 feet. Additionally, previous ACEC parcels were not consistant about whether a parcel that was bisected by a larger river included the river as part of the polygon (e.g. one polygon vs two polygon w/o the river included). In order to be consistant, as well as be in agreement with LLI, large rivers were included within parcels for each ACEC where present. Because Yakima Canyon ACEC and Yakima River Cliffs - Umtanum Ridge ACEC are designated as two separate ACECs, the river was excluded from either of these adjacent parcels.

    Person responsible for change:
    Alan Monek
    Bureau of Land Management, Wenatchee Resource Area
    GIS Specialist
    915 N. Walla Walla
    Wenatchee, WA 98801-1521
    US

    (509) 665-2124 (voice)
    amonek@blm.gov

    Date: 20080101 (change 2 of 7)
    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)
    Stan_Frazier@blm.gov

    Date: 20101101 (change 3 of 7)
    Updated and realigned ACEC polygons to the Land Lines Index (LLI). BLM land boundaries where used as the primary defining reference. Where BLM jurisdictional lines where not available (i.e. private lands, interior direction changes, island boundaries within major rivers), PLSS lines where used where possible. Boundaries that followed 1/4 sections or smaller units where estimated and should be considered accurate to +- 10 feet. In the case of islands and riverbank boundaries (e.g. islands within the Yakima Islands ACEC) the 2009 NAIP Imagery was used to define boundaries. Accuracy along these boundaries were considered to be +-10 feet. Additionally, previous ACEC parcels were not consistant about whether a parcel that was bisected by a larger river included the river as part of the polygon (e.g. one polygon vs two polygon w/o the river included). In order to be consistant, as well as be in agreement with LLI, large rivers were included within parcels for each ACEC where present. Because Yakima Canyon ACEC and Yakima River Cliffs - Umtanum Ridge ACEC are designated as two separate ACECs, the river was excluded from either of these adjacent parcels.

    Person responsible for change:
    Alan Monek
    Bureau of Land Management, Wenatchee Field Office
    GIS Specialist
    915 Walla Walla
    Wenatchee, WA 98801
    US

    (509) 665-2142 (voice)
    (509) 665-2121 (FAX)
    amonek@blm.gov

    Date: 20110101 (change 4 of 7)
    Converted organization codes from the Oregon/Washington developed codes, to 5-character codes based on the DOI Financial and Business Management System (FBMS) standard.

    Person responsible for change:
    Steve Salas
    Bureau of Land Management, Oregon State Office
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    503 808-6416 (voice)
    ssalas@blm.gov

    Date: 20110428 (change 5 of 7)
    Adjusted boundaries to align with Juniper Dunes Wilderness

    Person responsible for change:
    Mike Fallon
    BLM, Spokane District
    GIS Specialist

    Date: 20121123 (change 6 of 7)
    Snapped arcs to CADNSDI PLSS point and updated DEF_FEATURE and COORD_SRC.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management
    GIS Specialist
    28910 Highway 20 West
    Burns, OR 97738
    US

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

    Date: 20130314 (change 7 of 7)
    Updates to Domain DEF_FEATURE.

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

    (503) 808-6340 (voice)
    r2mills@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?

    Description: Instance of Political Admin Surface Management Agency (SMA) Line group. Lines making up the area perimeters of ACEC polygons and segmented as needed to indicate a change in either what defines the section of boundary and/or the source of the actual GIS coordinates. Geometry: Simple, non-overlapping lines that are split between endpoints as needed. Topology: The ACEC_ POLY lines are coincident with ACEC_ ARC lines and together make the feature dataset, Areas_of_Critical_Environmental_Concern. Integration Requirements: Line segments must be coincident with the source data indicated by attributes DEF_FEATURE and COORD_SRC either through duplication or snapping.

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
    US

    503-808-6340 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov
    Contact Instructions:
    contact instructions

  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?

    • 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?

Dates:
Last modified: 20130314
Last reviewed: 20140307

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