. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Easements and Rights of Way Polygon

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Easements and Rights of Way Polygon

Abstract:
esmtrow_poly: This data set represents areal ROWs and Easements. Rights-of-Way and Easements that are linear in nature, such as roads or power lines, have associated widths that can be used to buffer the linear features and create polygon areas. Area entities include these linear buffer features as well as ROWs and Easements described by parcels. These are a portion of the total ENCUMBRANCE data category which includes entities about rights and restrictions. The rights and restrictions relate to the use of federal public land or to the use of non-federal land by the federal and public entities. Example uses might be construction or simply crossing the land. Rights-of-way in this data set include ROW and other land use authorizations issued by the United States under the authorities of Title V and Sec. 302(b) of Federal Land Policy and Management Act (FLPMA) (and other ROW authorities repealed by FLPMA) ,O Act of August 28, 1937, plus the Federal Highway Act and the Mineral Leasing Act. Easements in this data set are the spatial representation of partial interests in non-federal land acquired or reserved by the United States. In general, ROWs are rights granted by BLM and Easements are rights granted to BLM, but there are exceptions. The data set includes both linear and area entities. This data set is not intended to include all ROWs and Easements, but only those most important for common GIS spatial analysis. In addition, only basic information about the ROWs and Easements is provided. Details and the complete rights and restrictions history are found in the authoritative sources: Master Title Plats, case file records, and the LR2000 database.

Supplemental information:
This version of the Easement and Right of Way dataset was designed, constructed, and populated to the standards established in the "Easments and Rights-of-Way Data Standard Revision" http://www.blm.gov/or/datamanagement/files/ESMTROW_DATA_STANDARD_REVISION.pdf

  1. How should this data set be cited?

    Bureau of Land Management, Oregon State Office, 20140408, BLM OR Easements and Rights of Way Polygon.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.455008
    East: -117.214700
    North: 45.899012
    South: 41.996235

  3. What does it look like?

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

    Calendar date: 20140408
    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 (12252)

    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 8.98315284119521e-009. Longitudes are given to the nearest 8.98315284119521e-009. 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.ESMTROW_POLY
     (Source: BLM)

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    ESMTROW_NM
    Name of the project the ROW or Easement is part of. (Source: BLM)
                      

    ESMTROW_TP
    Indicates whether feature is an Easement or a ROW and the general type. Examples:  ESMT (Easement), ROW (Right-of-Way), RECP (Reciprocal Right-of-Way) CNSC (Conservation/Scenic Easement), OTHER. (Source: BLM)
                      

    ValueDefinition
    ESMT
    Easement
    ROW
    Right-of-Way
    CNSC
    Conservation or Scenic easement
    RROW
    Reciprocal Right-of-Way
    OTHER
    Other type of Easement or Right-of-Way

    ESMTROW_FTR
    Type of geographic or legal feature associated with an Easement or ROW.   Examples:  ROAD, PIPELINE, TRAIL, PARCEL, FENCE, WINDTOWER_AREA, POWERLINE, TELEPHONE, TELE_BURIED, ADMIN_SITE, WATER_GAP, GEOSURVEY, STAGING, DITCHCANAL. (Source: BLM)
                      

    ValueDefinition
    ROAD
    Road
    PIPLELINE
    Pipeline
    TRAIL
    Trail
    PARCEL
    Parcel
    FENCE
    Fence
    WINDTOWER
    Windtower
    POWERLINE
    Powerline
    TELEPHONE
    Telephone
    TELE_BURIED
    Telephone Buried
    ADMIN_SITE
    Administrative Site
    WATER_GAP
    Water Gap
    GEOSURVEY
    Geosurvey
    STAGING
    Staging
    DITCH_CANAL
    Ditch or Canal
    WATER_GAUGE
    Water Gauge
    COMM_SITE
    Communication Site
    MINMAT_SITE
    Mineral Materials Site

    RGT_HOLDER
    Code for the organization (in general terms) that holds the rights granted in the ROW or Easement. Examples:  FS (Forest Service), BL (Bureau of Land Management), FW (Fish and Wildlife Service), BP (Bonneville Power Administration), ST (State), PV (Private). (Source: BLM)
                      

    ACCESS_ESMTROW
    Access rights associated with the Easement or ROW.  There are two types of easements.  Exclusive easements are generally open to the public and Nonexclusive easements are generally administrative only, not open to the public or third parties.  Reciprocal ROW Agreements provide access rights for the haul and management of timber and include third party rights. (Source: BLM)
                      

    RGT_HOLDER_NM
    Name of the organization or person that holds the rights granted in the ROW or Easement. This data is removed from all publication data to comply with BLM privacy policy. (Source: BLM)
                      

    GRANTOR
    The organization (in general terms) that is granted the Easement or ROW. (Source: BLM)
                      

    ValueDefinition
    BL
    Bureau of Land Management
    BP
    Bonneville Power Administration
    BR
    Bureau of Reclamation
    CE
    Corps of Engineers
    CG
    U.S. Coast Guard
    DA
    U.S. Dept. of Agriculture (except the Forest Service)
    DD
    U.S. Dept. of Defense (except the Corps of Engineers)
    FS
    U.S. Forest Service
    FA
    Federal Aviation Administration
    FC
    Federal Energy Regulatory Commission
    FW
    U.S. Fish and Wildlife Service
    GS
    U.S. Geological Survey
    GSA
    General Services Administration
    IA
    Bureau of Indian Affairs and Tribal Units
    LG
    Local Government
    PN
    National Park Service
    PV
    Private Lands
    PVI
    Private, Industrial
    PVN
    Private, NonIndustrial
    PVU
    Private, Urban
    ST
    State Managed Lands
    STF
    State Forests
    SDT
    State Division of Lands
    SDT
    State Transportation Department
    STP
    State Parks
    STW
    State Wildlife Refuges
    UN
    Undetermined

    GRANTOR_NM
    Name of the organization or person that granted the rights in the Easement or ROW. This data is removed from all publication data to comply with BLM privacy policy. (Source: BLM)
                      

    CASEFILE
    Case number assigned by the LR2000 database when an action is begun (either by BLM action or due to receipt of an application).  Includes suffix and case part. (Source: BLM)
                      

    BLM_ORG_CD
    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 even the state level rather than to the resource area level. (Source: BLM)
                      

    ValueDefinition
    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
    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

    CASETP
    A coded number system that identifies a case (e.g., authorizations, conveyances, withdrawals, acquisitions, etc).  The 6-digit code is constructed as follows: *first two digits "00" through "99" denotes major groups generally listed in 43 CFR; *second two digits "00" through "99" denotes major "Parts" generally listed in 43CFR; *last two digits "00" through "99" identifies a unique case type. Examples: 227006 - EX-SPECIFIC PUBLIC LAWS 231125 - WDL-RESERVOIR SITES 285002 - ROW-POWER TRAN LINE 286001 - ROW-COMM SITE, FLPMA (Source: BLM)
                      

    LOCAL_ID
    A local identifier, unique by district, used by western Oregon districts.  Called "Action Remarks" in LR2000. Examples:  RE-R-460C, RE-M-20, R-645 where RE-R, RE-M and RE-C are easements and R-645 is a Reciprocal ROW.  The first letters stand for the District (R = Roseburg, C = Coos Bay, M= Medford, etc.) (Source: BLM)
                      

    AUTH_USE
    Date the facility/site received botanical clearance. YYYYMMDD (Source: BLM)
                      

    ValueDefinition
    Windpower Testing
    Testing of an area/site for potential wind power generation
    Windpower Development
    Development of a wind power generation area/site
    Power Transportation
    Movement of power across an area (e.g., transmission line, gas pipeline)
    Solar Development
    Development of an area/site for solar power generation
    Crossing Access
    Crossing the land with a vehicle or fence is authorized (may include construction and/or timber)
    Crossing Access with Exceptions
    Crossing the land is authorized with one or more exceptions, for example timber
    Water Testing
    Testing for water flow or quantity
    Water Transportation
    Transportation of water across an area (e.g., pipeline)
    Communication Facility
    Development of a communication facility
    Mineral Materials
    Development of a mineral materials site (e.g., for road paving material)
    Forest Products Management and Removal
    Access to forest lands for management and transport of forest products

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

    ValueDefinition
    DEM
    Digital Elevation Model (30 m or better accuracy) used for creation of contours
    DLG
    Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs Typical Accuracies: 40 feet
    DRG
    Screen digitized linework over Digital Raster Graphic (USGS) backdrop
    GCD
    Lines snapped to Geographic Coordinate Database Points
    GPS
    Lines obtained from a Global Positioning System device
    MAP
    Digitized line work 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
    UNK
    Unknown coordinate source
    CADNSDI
    Lines from or snapped to the CADNSDI dataset
    CFF
    Lines duplicated or buffered from Cartographic Feature Files
    IMG
    Linework derived from interpretation of non-photographic imagery
    TIGER
    Tiger data
    TRS
    Coordinates only given as a legal description (township, range,
    WOD
    WODDB (Western Oregon Digital Database) Photogrammetric

    EXCL_TP
    The specific type of easement.  Only applies if attribute ESMTROW_TP = Easement.  There are two types of easements:   Exclusive easements are generally open to the public and nonexclusive Easements are generally administrative only, not open to the public or third parties.  This attribute captures the language of the legal document. (Source: BLM)
                      

    ValueDefinition
    EXCLUSIVE
    Easements generally open to the public
    NONEXCLUSIVE
    Easements generally administrative only, not open to the public or third parties
    UNKNOWN
    The type of the easement (exclusive/nonexclusive) is not identified

    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)
                      

    GLOBALID
    ACCURACY_FT
    How close, in feet, the spatial GIS depiction is to the actual location on the ground or to the legal description. 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 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)
                      

    SHAPE.AREA
    SHAPE.LEN
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)

    • Bureau of Land Management, Oregon State Office

  2. Who also contributed to the data set?

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

    Pamela Chappel
    Bureau of Land Management, Oregon State Office
    Land Law Examiner
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6170 (voice)
    (503) 808-6425 (FAX)
    pchappel@blm.gov
Back to Top

Why was the data set created?

This data set is used for depicting the ROWs and Easements on maps. All BLM planning and management actions must identify any encumbrances on the land. Existing ROWs and Easements are intersected with other resources to determine impact and/or feasibility of the proposed action.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 20100201 (change 1 of 4)
    1. Created ESMTROWDemo.gdb with feature classes, attributes and domains according to the ESMTROW data standard. 2. Copied data from Burns District into the four blank feature classes and adjusted attribute values as needed. 3. Acquired WindEnergy.gdb from Duane Dippon. This was a one-time merge by Prineville GIS of Wind Power ROW applications data from the Prineville, Burns, Vale , Lakeview and Salem. Copied the Prineville, Vale, Lakeview and Salem (one area) data from Parcels_Wind_Energy feature class into ESMTROW_POLY (if Authorization = 'Authorized') and into ESMTROW_P_POLY (if Authorization = 'Proposed'). Placed the West_Butte_ROW_Wind_Energy line into ESMTROW_P_ARC. Adjusted attributes as needed. Did not use the Met_Towers_Wind_Energy point feature class from the WindEnergy.gdb since these belong on a different theme in the ODF (structures, STRCT_PT or STRCT_P_PT). 4. Checked attributes of Vale's LandStatus.gdb feature classes Wind_Energy_Application_to_Test_Areas and Wind_Energy_Applications_to_Develop_Areas against what came from WindEnergy.gdb. 5. Copied Vale's LandStatus.gdb Easement feature class into ESMTROW_ARC. Minimal attributes. 6. Acquired easements from Roseburg (Gary Passow), easement_20070925.gdb, easement feature class. Copied into ESMTROW_ARC. Minimal attributes--- all calc'ed to ESMTROW_TP = 'ESMT', ESMTROW_FTR = 'ROAD', LOCAL_ID calc'ed to Roseburg's EASEMENT_NUM and ROADLINK calc'ed to Roseburg's ROADLINK or ROUTE_ID. 7. Many duplicate arcs removed from Roseburg, some from Burns and Vale. Arc only deleted if all attributes identical and shape_length identical.

    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: 20100201 (change 2 of 4)
    Existing Easements and ROWs are defined and described by the case file record and sometimes depicted on Master Title Plats (MTP). If a digital MTP with GIS features or a digital survey are available, the appropriate spatial features are selected and copied from these. If there is no digital source, the lines and polygons are created from the legal description and other information in the authoritative sources (MTPs, LR2000 and the case file record). Where the feature is described by legal land line parcels or surveyed lines, a vertex is placed at every Geographic Coordinate Data (GCD) point and snapped to it. Where the feature is described as a road or other physical feature and case file description says "as built", the coordinates are obtained from Global Positioning System or Digital Line Graphic (DLG), imagery or other digital data with a total locational accuracy of 100 ft or better. Existing linework is not replaced unless a more accurate spatial representation of the legal description is provided. It is important to note that even if a better road centerline is available in GIS, the associated easement or ROW may not be changed depending on the language in the case file.

    Date: 20111101 (change 3 of 4)
    1. A new ESMTROW.gdb was populated with four feature classes - ESMTROW_POLY, ESMTROW_ARC, ESMTROW_P_POLY and ESMTROW_P_ARC. These features classes contained updated attributes and domains as outlined in the most current ESMTROW data standard. 2. Copied data from SDE - ORSOEDIT. 3. Loaded data into the corresponding blank feature classes in ESMTROW.gdb. Nearly all of the attribute fields and associated domains crosswalked directly with these exceptions: New field 'GRANTOR_NM' - populated with existing 'GRANTOR' values JURIS_CODE domain assigned to 'GRANTOR' field and values calc'ed appropriately (i.e., Vale District = BL) Existing 'STATUS_P' field ported to new field 'STATUS_ESMTROW'. STATUS_ESMTROW domain changed; existing values calc'ed as shown: Initial ? Initial Active ? Pending Suspended ? Closed Rejected ? Rejected Relinquished ? Closed 4. Duplicate arcs identified and removed - one from ESMTROW_P_ARC and one from ESMTROW_ARC

    Person responsible for change:
    Barbara Haney
    Bureau of Land Management, Oregon State Office
    GIS Data Specialist
    PO Box 2965
    Portland, OR 97208
    US

    (503) 808-6313 (voice)
    bhaney@blm.gov

    Date: 20130109 (change 4 of 4)
    Attributes BLM_ORG_CD, GIS_ACRES, EXCL_TP added. Other changes include: Features represent entire ROW, not just where they cross BLM lands. Casefile attribute data now matches LR2000 tabular data. ESMTROW_STATUS FIELD NAME changed to STATUS_P. Increased the field length of GRANTOR_NM, GRANTOR_P_NM, RGT_HOLDER_NM, and RGT_P_HOLDER_NM to 60 characters to enable concatenating multiple names in the field. Increased field size of LOCAL_ID from 10 to 12. Increased field size of LOCAL_ID from 10 to 12. Added domain value "Crossing Access with Exceptions" to the AUTH_USE domain. Added wording to the description of the domain value "Crossing Access" to include timber "may include construction and/or timber."

    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?

    The proposed ROWs and Easements are transitory and have varying degree of accuracy. Required attributes have an accuracy of at least 90%.

  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?

    This data set will never be complete. Over time, more and more approved ROWs and Easements will be added to the data set, but it will never contain the complete record (found in the case files).

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

    Description: Instance of Land Status Proposed group. Geometry: Polygons may overlap each other entirely or in part, and may overlap ESMTROW_POLY features. Topology: No topology enforced. Integration Requirements: If polylines are defined as parcels, they must have a vertex for every CADNSDI point, and be snapped to it. Existing Easements and ROWs are defined and described by the case file record and sometimes depicted on Master Title Plats (MTP). If a digital MTP with GIS features or a digital survey are available, the appropriate spatial features are selected and copied from these. If there is no digital source, the lines and polygons are created from the legal description and other information in the authoritative sources (MTPs, LR2000 and the case file record). Where the feature is described by legal land line parcels or surveyed lines, a vertex is placed at every Geographic Coordinate Data (GCD) point and snapped to it. Where the feature is described as a road or other physical feature and case file description says "as built", the coordinates are obtained from Global Positioning System or Digital Line Graphic (DLG), imagery or other digital data with a total locational accuracy of 100 ft or better. Existing linework is not replaced unless a more accurate spatial representation of the legal description is provided. It is important to note that even if a better road centerline is available in GIS, the associated easement or ROW may not be changed depending on the language in the case file.

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: 20130403
Last reviewed: 20130109

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