. .



Oregon / Washington

GIS Metadata

BLM OR Visual Resource Inventory Polygon

Frequently-asked questions:

What does this data set describe?

BLM OR Visual Resource Inventory Polygon

VRI_POLY: This data set represents the Visual Resource Inventory (VRI) classes for BLM-managed lands in Oregon and Washington. The classes are based on scenic quality, sensitivity level, and distance zones. This dataset is subject to the Visual Resources Spatial Data Standard. The data standard provides the definitive documentation for the VRI. http://www.blm.gov/or/datamanagement/index.php

Supplemental information:
BLM - Bureau of Land Management VRM - Visual Resource Managment RMP - Resource Management Plan VRI - Visual Resource Inventory

  1. How should this data set be cited?

    OR/WA BLM, 20140923, BLM OR Visual Resource Inventory Polygon: Portland,OR.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.513434
    East: -116.922270
    North: 49.000115
    South: 41.992470

  3. What does it look like?

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

    Calendar date: 20140923
    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?

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

    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 3.9999999999999998e-007. Longitudes are given to the nearest 3.9999999999999998e-007. 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?

    Visual Resource Inventory Class designations on BLM lands (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.

    VRI Classes are the result of the evaluation of an area for it's visual potential based on several criteria including scenic quality, sensitivity level, and distance zones. (Source: Bureau of Land Management)

    Assigned to all special areas where the current management situations require maintaining a natural environment essentially unaltered by man.
    Assigned where scenic quality is highest, A, or where the scenic quality is B and the distance zone is foreground/middleground.
    Assigned where scenic quality is B, distance zone is background or seldom seen and sensitivity is High or where sensitivity is Medium but the distance zone is foreground/middleground.
    Assigned to areas that don't meet the criteria for I, II, or III.

    Indicates whether the area being inventoried is in the foreground-middle(FM) ground of a person's view, in the background (BG), or seldom seen (SS). (Source: Bureau of Land Management)

    Seldom Seen

    A code to denote most (A), moderately (B), or least (C) scenic quality based on factors such as landform, vegetation, water, color, influence of adjacent scenery, scarcity, and cultural modifications. (Source: Bureau of Land Management)

    Most Scenic; score of 19 or more using procedures in BLM Handbook H-8410-1
    Moderately Scenic; score of 12-18 using procedures in BLM Handbook H-8410-1
    Least Scenic; score of 11 or less using procedures in BLM Handbook H-8410-1

    A fixed length character unique identifier assigned by the contractor who inventoried the six western Oregon BLM districts in 2012.  The designed primary key that will uniquely identify a single occurrence of the entity.  It is a concatenation of: "VRI" + Administrative State Code (2 characters) + Administrative Office Code (6 characters) +  Inventory Area Number (4 digit sequential number).  (Source: BLM)

    A combination of the BLM administrative state and field office which has administrative responsibility for the spatial entity.  This includes which office covers the entity for planning purposes and which office is the lead for GIS edits.  Another agency or individual may have the physical management responsibility for the on-the-ground entity.  This field applies particularly when a spatial entity crosses resource area or district boundaries and the administrative responsibility is assigned to one or the other rather than splitting the spatial unit.  Similarly, OR/WA BLM may have administrative responsibility over some area that is physically located in Nevada, Idaho, and California and vice versa.  When appropriate, the office can be identified only to the district or state level rather than to the resource area level. Domain is a subset of the BLM national domain for organization codes.  Only positions three through seven of the national code are used (leading LL and trailing zeros are dropped).   Examples:  OR000 - Oregon/Washington BLM, ORL00 - Lakeview District Office, ORV06 - Jordan Field Office (Source: BLM)

    GIS_ACRES is automatically calculated when the submitted polygon is approved for incorporation into the dataset.  The standard spatial reference of Geographic (NAD 1983) cannot be used for calculating acres so the features are projected to one of three projections as determined by the BLM_ORG_CD of the record.  These three projections all utilize linear units of meters, so the ESRI Geodatabase-controlled field SHAPE.AREA can be used to convert to acres with the factor based on the U.S. Survey Foot:              GIS_ACRES = SHAPE.AREA * 0.0002471044 (Source: BLM)

    The visual sensitivity of the area being inventoried based on type of users, amount of use, public interest, adjacent land uses, and special areas. (Source: Bureau of Land Management)

    High level of sensitivity
    Moderate level of sensitivity
    Low level of sensitivity

    Entity and attribute overview:
    Attribute domains may be found in the Visual Resources Spatial Data Standard http://www.blm.gov/or/datamanagement/index.php. 
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, characterization and management of scenic/visual quality

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 20070131 (change 1 of 3)
    Current version of geodatabase was loaded into ArcSDE.

    Person responsible for change:
    Barbara W. Haney
    OR BLM/Northrop Grumman Corporation
    Sr. GIS Technical Support Specialist
    PO Box 2965
    Portland, OR 97208

    503-808-6313 (voice)

    Data sources used in this process:
    • C:\DOCUME~1\bhaney\LOCALS~1\Temp\3\xml15.tmp

    Date: 20140909 (change 2 of 3)
    OTAK delivered separate VRI datasets for each Western Oregon district in the national data standard. We appended these datasets into a single feature class and simplified its attribute table to meet the Oregon Data Framework (ODF) data standard. All OTAK attribute domains are dropped from the output feature class. Specifically, we cross-walked: OTAK "VRI_DOM_CLASS_CODE" ? ODF "VRI_CLASS" #OTAK VRI_DOM_CLASS_CODE codes = [N, I, II, III, IV, M] #OTAK codes occurring in otak_vri_merge = [II, III, IV] #ODF dom_VRI_CLASS codes = [I, II, III, IV] OTAK "VDZ_CODE" ? ODF "DISTANCE_ZONE" #OTAK VRI_DOM_VDZ_CODE codes = [BG, SS, N, M, F/M, NF] #OTAK codes occurring in otak_vri_merge = ["", BG, F/M, SS] #ODF dom_DISTANCE_ZONE codes = [FM, BG, SS] OTAK "SQ_CODE" ? "VRI_SCENIC" #OTAK VRI_DOM_SQ_CODE codes = [N, M, C, A, B] #OTAK codes occurring in otak_vri_merge = [NULL, A, B, C] #ODF dom_VRI_SCENIC codes = [A, B, C] OTAK "SL_OVRL_RT" ? "VRI_SENSITIVITY" #OTAK VRI_DOM_SL_RATING codes = [High, Moderate, Low, None, Missing] #OTAK codes occurring in otak_vri_merge = ["", High, Low, Moderate] #ODF dom_VRI_SENSITIVITY codes = [HIGH, MOD, LOW] The "Administrative Office Code" attributes in the OTAK VRI feature classes are not consistent with the dom_BLM_ORG_CD codes. Also, OTAK did not calculate values for "Administrative Office Code" in every feature class (e.g., all rows == NULL in eug_vri). To correct this issue, we calculated the OTAK "ADM_OFC_CD" attribute to match allowed ODF dom_BLM_ORG_CD codes prior to appending the individual datasets together where: BLM_ORG_CDs = {cby_vri : "ORC00", eug_vri : "ORE00", kla_vri : "ORL04", med_vri : "ORM00", rsb_vri : "ORR00", slm_vri : "ORS00"} Finally, all OTAK attribute domains were removed from the output file geodatabase. No revisions to the output dataset's geometry were made. See P:\oso\Recreation\VisualResourceInventory\mdl_VRI_OTAK_to_ODF.py for the complete geoprocessing workflow. Additional Steps to Prepare Data for RWO Project Data Catalog 1. Project [vri_otak_to_odf_poly] to NAD_1983_UTM_Zone_10N 2. Intersect [lup_planbdy_reference_a_v2_poly] 3. Delete extra FID* fields 4. Calculate GIS_Acres

    Person responsible for change:
    Craig Ducey
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208

    (503) 808-6314 (voice)

    Date: 20140915 (change 3 of 3)
    For Western Oregon VRI was created by Field Office collection and office GIS analysis by the contractor (OTAK) in accordance with BLM policy, guidance, and in compliance with the agencies VRI data standard. The full set of data documentation including full FGDC metadata is stored in BLM corporate holdings. Only a subset was crosswalked into the public data.

    Person responsible for change:
    BLM District GIS staff
    OR Bureau of Land Management
    GIS Specialists

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?


  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?

    Geometry: Polygons that form a continuous "wall-to-wall" cover across BLM lands with no gaps or overlaps. Topology: No. Integration Requirements: Metadata process steps should specify if any special management or other special designation polygons are incorporated so that they can be replaced as needed. This is not critical for VRI since these boundaries will generally be replaced when VRM is created.

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?

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

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