. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Areas of Critical Environmental Concern Polygon

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Areas of Critical Environmental Concern Polygon

Abstract:
ACEC_POLY: This data set shows the distribution of Areas of Critical Environmental Concern (ACEC) under BLM management in Oregon and Washington.

Supplemental information:
ACEC (Areas of Environmental Concern)

  1. How should this data set be cited?

    OR/WA BLM, 20140731, BLM OR Areas of Critical Environmental Concern Polygon.

  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: 20140731
    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?

      Indirect spatial reference:
      Oregon

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (453)

    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?

    OSODBA.ACEC_POLY
    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.

    ACEC_NAME
    The official name of the Area of Critical Environmental Concern (Source: Bureau of Land Management)
                      

    ACEC_TYPE
    The type of ACEC designation for this area (Source: Bureau of Land Management)
                      

    ValueDefinition
    ACEC
    Area of Critical Environmental Concern
    ONA
    Outstanding Natural Area
    RNA
    Research Natural Area

    ACEC_VALUE
    Values requiring special management attention that factored into the area being designated an ACEC.  More than one value can be present and concatenated together with a "/" separator.  Most important should be listed first. (Source: Bureau of Land Management)
                      

    ValueDefinition
    BOT
    Botanical
    CELL
    Oregon Natural Heritage Program "cell"
    CULT
    Cultural
    FW
    Fish and Wildlife
    GEOL
    Geological
    HAZ
    Natural Hazards
    HIST
    Historical
    NAT
    Generic natural processes if BOT, GEOL, FW not specified
    SCEN
    Scenic

    BLM_ORG_CD
    Combination of the BLM "State" and Resource Area which has administrative responsibility for the Special Management Area. (Source: Bureau of Land Management)
                      

    ValueDefinition
    CA000
    California BLM
    CAN01
    Northern California Field Office
    CAN02
    Alturas Field Office
    CAN03
    Arcata Field Office
    CAN06
    Redding Field Office
    CAN07
    Surprise Field Office
    ID000
    Idaho BLM
    IDB00
    Boise District Office
    IDB01
    Four Rivers Field Office
    IDB03
    Owyhee Field Office
    IDC00
    Coeur d'Alene District Office
    IDC01
    Coeur d'Alene Field Office
    IDC02
    Cottonwood Field Office
    NV000
    Nevada BLM
    NVE00
    Elko District Office
    NVE02
    Tuscarora Field Office
    NVW00
    Winnemucca District Office
    NVW01
    Humboldt River Field Office
    OR000
    Oregon/Washington BLM
    ORB00
    Burns District Office
    ORB05
    Three Rivers Field Office
    ORB06
    Andrews Field Office
    ORC00
    Coos Bay District Office
    ORC03
    Umpqua Field Office
    ORC04
    Myrtlewood Field Office
    ORE00
    Eugene District Office
    ORE05
    Siuslaw Field Office
    ORE06
    Upper Willamette Field Office
    ORL00
    Lakeview District Office
    ORL04
    Klamath Falls Field Office
    ORL05
    Lakeview Field Office
    ORM00
    Medford District Office
    ORM05
    Butte Falls Field Office
    ORM06
    Ashland Field Office
    ORM07
    Grants Pass Field Office
    ORM08
    Glendale Field Office
    ORP00
    Prineville District Office
    ORP04
    Central Oregon Field Office
    ORP06
    Deschutes Field Office
    ORR00
    Roseburg District Office
    ORR04
    Swiftwater Field Office
    ORR05
    South River Field Office
    ORS00
    Salem District Office
    ORS04
    Cascades Field Office
    ORS05
    Marys Peak Field Office
    ORS06
    Tillamook Field Office
    ORV00
    Vale District Office
    ORV04
    Malheur Field Office
    ORV05
    Baker Field Office
    ORV06
    Jordan Field Office
    ORW00
    Spokane District Office
    ORW02
    Wenatchee Field Office
    ORW03
    Border Field Office

    ACT_PL_DT
    The date of the monitoring or activity plan (if any) for the particular ACEC.   YYYYMMDD format.  Provide as much date information as is available but must  include, at a minimum, the year (YYYY). (Source: Bureau of Land Management)
                      

    Coordinates defining the features.

    GIS_ACRES
    The area of a polygon as calculated by GIS in acres.  Must be recalculated with  every edit submission.  The acres will be automatically calculated when the  feature classes are published.  The BLM_ORG_CD will be used to determine the  appropriate projection (Source: BLM)
                      

    DSG_AC
    The official designated acres of the ACEC as recorded in the Federal Register.  This is not the GIS derived acres and does not change. (Source: Bureau of Land Management)
                      

    Coordinates defining the features.

    SHAPE.LEN
    LUP_NAME
    The official name of the land use plan that originally created the Special Management Area (Source: BLM)
                      

    Coordinates defining the features.

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    SHAPE.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, Medford District
    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 current status of ACECs in Washington and Oregon in order to assist BLM staff in the resource management and planning process. ACECs are administratively designated areas where special management attention is needed to protect and prevent irreparable damage to important historic, cultural and scenic values; fish, wildlife resources or other natural systems or processes; or to protect human life and safety from natural hazards. BLM authority to designate these areas has been mandated by Congress through the Federal Land Policy and Management Act (FLPMA). (Purpose Statement Source - Utah BLM FAC sheet).

Back to Top

How was the data set created?

  1. Where did the data come from?

    GCDB (source 1 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 2 of 7)

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

    Type of source media: None
    Source contribution:
    Lines

    BLM FOI (source 3 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

    LLI (source 4 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

    DOQ (source 5 of 7)

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

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    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: 20130204 (change 6 of 7)
    Changes in data standard. Added attributes GIS ACRES, LUP_NAME. PLANID field removed.

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

    (503) 808-6340 (voice)
    r2mills@blm.gov

    Date: 20130813 (change 7 of 7)
    Fixed ACEC to match maps and descriptions published in 1987/1992 ROD for Juniper Forest. These areas were erroneously mapped.

    Person responsible for change:
    Mike Fallon
    Bureau of Land Management, Spokane District Office
    GIS Specialist

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?

    Geometry: Polygons do not form a continuous "wall-to-wall" cover across BLM lands. Polygons do not overlap, but may have gaps and donut holes. . Topology: ACEC_ POLY lines are coincident with ACEC_ARC lines and together make the feature dataset, Areas_of_Critical_Environmental_Concern. Integration Requirements: ACEC is created from merging together many different input themes. Attributes on the ACEC_ARC provide the information needed to update lines using the correct sources (either by replacement or snapping) and maintain integration across feature classes

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

    Meet 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
    GIS Data Management Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    503-808-6565 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov

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