. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Easements and Rights of Way Line
FGDC Metadata
Show Definitions
Description | Spatial | Data Structure | Data Quality | Data Source | Data Distribution | Metadata
Description
Citation
Information used to reference the data.
Title: BLM OR Easements and Rights of Way Line
Originators: Bureau of Land Management, Oregon State Office
Publication date: 20141118
Data type: vector digital data
Description
A characterization of the data, including its intended use and limitations.
Abstract:
esmtrow_arc: This data is a linear representation of Right of Ways (ROWs) and Easements for the State of Oregon. These are a portion of the total ENCUMBRANCE data category which includes entities about rights and restrictions. 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. 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. Easement and ROWs are legal entities. They are often related to physical entities such as roads and power lines. The Easement or ROW is described in relation to the constructed entity, but is not necessarily identical.
Purpose:
This data is primarily intended 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. Other usage of the data may be to indicate the rights and restrictions that 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.
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
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Organization: Bureau of Land Management, Oregon State Office
Person: Pamela Chappel
Position: Land Law Examiner
Phone: (503) 808-6170
Fax: (503) 808-6425
Email: pchappel@blm.gov
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Data Type
How the data are represented, formatted and maintained by the data producing organization.
Data type: vector digital data
Native dataset environment: Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 20141118
Currentness reference:
publication date
Status
The state of and maintenance information for the data.
Data status: Complete
Update frequency: As needed
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: transportation
Keyword thesaurus: ISO 19115
Theme:
Keywords: Easement, ROW, Right of Way
Keyword thesaurus: None
Theme:
Keywords: Lands
Keyword thesaurus: BLM_Theme
Place:
Keywords: Oregon, Washington
Keyword thesaurus: BLM-State
Data Access Constraints
Restrictions and legal prerequisites for accessing or using the data after access is granted.
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.
Data Security Information
Handling restrictions imposed on the data because of national security, privacy or other concerns.
Security classification: Unclassified
Spatial Reference Information
Horizontal Coordinate System
Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.
Coordinate System Details
Geographic coordinate system
Latitude resolution: 8.98315284119521e-009
Longitude resolution: 8.98315284119521e-009
Geographic coordinate units: Decimal Degrees
Geodetic model
Horizontal datum name: D North American 1983
Ellipsoid name: GRS 1980
Semi-major axis: 6378137.0
Denominator of flattening ratio: 298.257222101
Spatial Domain
The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.
Bounding Coordinates
In Unprojected coordinates (geographic)
Boundary Coordinate
West -124.454281 (latitude)
East -117.037693 (latitude)
North 45.963819 (longitude)
South 41.992590 (longitude)
Data Structure and Attribute Information
Overview
Summary of the information content of the data, including other references to complete descriptions of entity types, attributes, and attribute values for the data.
Direct spatial reference method: Vector
Attributes of OSODBA.ESMTROW_ARC
Detailed descriptions of entity type, attributes, and attribute values for the data.
Source:
BLM
Attributes
OBJECTID
Definition:
Internal feature number.
Attribute values: Sequential unique whole numbers that are automatically generated.
Attribute definition source:
ESRI
Shape
Definition:
Feature geometry.
Attribute values: Coordinates defining the features.
Attribute definition source:
ESRI
ESMTROW_NM
Definition:
Name of the project the ROW or Easement is part of.
Attribute definition source:
BLM
ESMTROW_TP
Definition:
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.
Attribute domain values
Value Definition
ESMT
Easement
Definition Source:
BLM
ROW
Right-of-Way
Definition Source:
BLM
CNSC
Conservation or Scenic easement
Definition Source:
BLM
RROW
Reciprocal Right-of-Way
Definition Source:
BLM
OTHER
Other type of Easement or Right-of-Way
Definition Source:
BLM
Attribute definition source:
BLM
ESMTROW_FTR
Definition:
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.
Attribute domain values
Value Definition
ROAD
Road
Definition Source:
BLM
PIPELINE
Pipeline
Definition Source:
BLM
TRAIL
Trail
Definition Source:
BLM
PARCEL
Parcel
Definition Source:
BLM
FENCE
Fence
Definition Source:
BLM
WINDTOWER
Windtower
Definition Source:
BLM
POWERLINE
Powerline
Definition Source:
BLM
TELEPHONE
Telephone
Definition Source:
BLM
TELE_BURIED
Telephone Buried
Definition Source:
BLM
ADMIN_SITE
Administrative Site
Definition Source:
BLM
WATER_GAP
Water Gap
Definition Source:
BLM
GEOSURVEY
Geosurvey
Definition Source:
BLM
STAGING
Staging
Definition Source:
BLM
DITCH_CANAL
Ditch or Canal
Definition Source:
BLM
WATER_GAUGE
Water Gauge
Definition Source:
BLM
COMM_SITE
Communication Site
Definition Source:
BLM
MINMAT_SITE
Mineral Materials Site
Definition Source:
BLM
Attribute definition source:
BLM
RGT_HOLDER
Definition:
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).
Attribute domain values
Value Definition
Bureau of Land Management (definition not provided)
Private Lands (definition not provided)
Undetermined (definition not provided)
Attribute definition source:
BLM
ACCESS_ESMTROW
Definition:
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.
Attribute domain values
Value Definition
Access only for BLM administrative purposes (definition not provided)
Public access (definition not provided)
Attribute definition source:
BLM
RGT_HOLDER_NM
Definition:
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.
Attribute definition source:
BLM
GRANTOR
Definition:
Juris_code value or the Grantor.
Attribute domain values
Value Definition
BL
Bureau of Land Management
Definition Source:
BLM
BP
Bonneville Power Administration
Definition Source:
BLM
BR
Bureau of Reclamation
Definition Source:
BLM
CE
Corps of Engineers
Definition Source:
BLM
CG
U.S. Coast Guard
Definition Source:
BLM
DA
U.S. Dept. of Agriculture (except the Forest Service)
Definition Source:
BLM
DD
U.S. Dept. of Defense (except the Corps of Engineers)
Definition Source:
BLM
FS
U.S. Forest Service
Definition Source:
BLM
FA
Federal Aviation Administration
Definition Source:
BLM
FC
Federal Energy Regulatory Commission
Definition Source:
BLM
FW
U.S. Fish and Wildlife Service
Definition Source:
BLM
GS
U.S. Geological Survey
Definition Source:
BLM
GSA
General Services Administration
Definition Source:
BLM
IA
Bureau of Indian Affairs and Tribal Units
Definition Source:
BLM
LG
Local Government
Definition Source:
BLM
PN
National Park Service
Definition Source:
BLM
PV
Private Lands
Definition Source:
BLM
PVI
Private, Industrial
Definition Source:
BLM
PVN
Private, NonIndustrial
Definition Source:
BLM
PVU
Private, Urban
Definition Source:
BLM
ST
State Managed Lands
Definition Source:
BLM
STF
State Forests
Definition Source:
BLM
STL
State Division of Lands
Definition Source:
BLM
SDT
State Transportation Department
Definition Source:
BLM
STP
State Parks
Definition Source:
BLM
STW
State Wildlife Refuges
Definition Source:
BLM
UN
Undetermined
Definition Source:
BLM
Attribute definition source:
BLM
GRANTOR_NM
Definition:
The name of the entity (person, organization) that is granting the Easement or ROW.  This data is removed from all publication data to comply with BLM privacy policy.
Attribute definition source:
BLM
CASEFILE
Definition:
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.
Attribute definition source:
BLM
BLM_ORG_CD
Definition:
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.
Attribute domain values
Value Definition
OR000
Oregon/Washington BLM
Definition Source:
BLM
ORB00
Burns District Office
Definition Source:
BLM
ORB05
Three Rivers Field Office
Definition Source:
BLM
ORB06
Andrews Field Office
Definition Source:
BLM
ORC00
Coos Bay District Office
Definition Source:
BLM
ORC03
Umpqua Field Office
Definition Source:
BLM
ORC04
Myrtlewood Field Office
Definition Source:
BLM
ORE00
Eugene District Office
Definition Source:
BLM
ORE05
Siuslaw Field Office
Definition Source:
BLM
ORE06
Upper Willamette Field Office
Definition Source:
BLM
ORL00
Lakeview District Office
Definition Source:
BLM
ORL04
Klamath Falls Field Office
Definition Source:
BLM
ORL05
Lakeview Field Office
Definition Source:
BLM
ORM00
Medford District Office
Definition Source:
BLM
ORM05
Butte Falls Field Office
Definition Source:
BLM
ORM06
Ashland Field Office
Definition Source:
BLM
ORM07
Grants Pass Field Office
Definition Source:
BLM
ORP00
Prineville District Office
Definition Source:
BLM
ORP04
Central Oregon Field Office
Definition Source:
BLM
ORP06
Deschutes Field Office
Definition Source:
BLM
ORR00
Roseburg District Office
Definition Source:
BLM
ORR04
Swiftwater Field Office
Definition Source:
BLM
ORR05
South River Field Office
Definition Source:
BLM
ORS00
Salem District Office
Definition Source:
BLM
ORS04
Cascades Field Office
Definition Source:
BLM
ORS05
Marys Peak Field Office
Definition Source:
BLM
ORS06
Tillamook Field Office
Definition Source:
BLM
ORV00
Vale District Office
Definition Source:
BLM
ORV04
Malheur Field Office
Definition Source:
BLM
ORV05
Baker Field Office
Definition Source:
BLM
ORV06
Jordan Field Office
Definition Source:
BLM
ORW00
Spokane District Office
Definition Source:
BLM
ORW02
Wenatchee Field Office
Definition Source:
BLM
ORW03
Border Field Office
Definition Source:
BLM
Attribute definition source:
BLM
CASETP
Definition:
A coded number system (defined by LR2000) that identifies a case (e.g., authorization, conveyances, withdrawals, acquisitions, etc.).  The six digit code is constructed as follows: First two digits "00" through "99" denotes major groups generally listed in 43 CFR (e.g., 21=acquisitions, 22=exchanges, 23=withdrawals, 28=ROW). Second two digits "00" through "99" denotes major "Parts" (e.g., 2810=ROW, Roads, 2830=ROW, Wind, 2840=ROW, Railroad). Last two digits "00" through "99" identifies a unique case type. Examples:  281007 - ROW-ROADS FEDERAL FAC            	       283003 - ROW-WIND DEV FAC           	       284004 - ROW-RR SPECIAL ACTS For a complete list of Case types go to: http://www.blm.gov/lr2000/codes/CodeCasetype_code.pdf
Attribute definition source:
BLM
LOCAL_ID
Definition:
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.)
Attribute definition source:
BLM
RADMETER
Definition:
Radial width of the ROW or Easement in meters to the nearest hundredth or tenth.  Rudimentary or average widths. The derived acreages will be approximate.  Detailed widths which may vary by segment are found in casefile.
Attribute definition source:
BLM
COORD_SRC
Definition:
The actual source of the GIS coordinates for the line segments.
Attribute domain values
Value Definition
DEM
Digital Elevation Model (30 m or better accuracy) used for creation of contours
Definition Source:
BLM
DLG
Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs Typical Accuracies: 40 feet
Definition Source:
BLM
DRG
Screen digitized linework over Digital Raster Graphic (USGS) backdrop
Definition Source:
BLM
GCD
Lines snapped to Geographic Coordinate Database Points
Definition Source:
BLM
GPS
Lines obtained from a Global Positioning System device
Definition Source:
BLM
MAP
Digitized line work from hardcopy map
Definition Source:
BLM
MTP
Lines duplicated from Digital Master Title Plat
Definition Source:
BLM
SOURCEL
Source layer from BLM GIS
Definition Source:
BLM
SRV
Survey methods were used to create the linework
Definition Source:
BLM
UNK
Unknown coordinate source
Definition Source:
BLM
CADNSDI
Lines from or snapped to the CADNSDI dataset
Definition Source:
BLM
CFF
Lines duplicated or buffered from Cartographic Feature Files
Definition Source:
BLM
DIS
Lines generated to connect discontinuous features
Definition Source:
BLM
DOQ
Screen digitized linework over Digital Orthoquad backdrop
Definition Source:
BLM
TIGER
Tiger data
Definition Source:
BLM
IMG
Linework derived from interpretation of non-photographic imagery
Definition Source:
BLM
TRS
Coordinates only given as a legal description (township, range,
Definition Source:
BLM
WOD
WODDB (Western Oregon Digital Database) Photogrammetric
Definition Source:
BLM
Attribute definition source:
BLM
EXCL_TP
Definition:
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.
Attribute domain values
Value Definition
EXCLUSIVE
Easements generally open to the public.
Definition Source:
BLM
NONEXCLUSIVE
Easements generally administrative only, not open to the public or third parties.
Definition Source:
BLM
UNKNOWN
The type of the easement (exclusive/nonexclusive) is not identified.
Definition Source:
BLM
Attribute definition source:
BLM
ACCURACY_FT
Definition:
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.
Attribute definition source:
BLM
RADMETER_L
Definition:
Left-side radial width of the ROW or Easement in meters to the nearest hundredth or tenth. If this attribute is filled in then RADMETERS must be set to -1 and RADMETER_R must be set to something other than -1 (0 or a positive number). This width and derived acreages are approximate. Detailed widths are found in casefile.
Attribute definition source:
BLM
RADMETER_R
Definition:
Right-side radial width of the ROW or Easement in meters to the nearest hundredth or tenth. If this attribute is filled in then RADMETERS must be set to -1 and RADMETER_L must be set to something other than -1 (0 or a positive number). This width and derived acreages are approximate. Detailed widths are found in casefile.
Attribute definition source:
BLM
AUTH_USE
Definition:
Use that is authorized by the Easement or ROW. Examples:  Windpower Testing, Windpower Development, Solar Development, Crossing Access, Power Transportation.
Attribute domain values
Value Definition
Windpower Testing
Testing of an area/site for potential wind power generation
Definition Source:
BLM
Windpower Development
Development of a wind power generation area/site
Definition Source:
BLM
Power Transportation
Movement of power across an area (i.e. transmission lines, pipelines)
Definition Source:
BLM
Solar Development
Development of an area/site for solar power generation
Definition Source:
BLM
Crossing Access
Crossing the land with a vehicle or fence is authorized (may include construction)
Definition Source:
BLM
Water Testing
Testing for water flow or quantity
Definition Source:
BLM
Water Transportation
Transportation of water across an area (e.g., pipeline)
Definition Source:
BLM
Communication Facility
Development of a communication facility
Definition Source:
BLM
Mineral Materials
Development of a mineral materials site (e.g., for road paving material)
Definition Source:
BLM
Forest Products Management and Removal
Access to forest lands for management and transport of forest products
Definition Source:
BLM
Crossing Access with Exceptions
Crossing the land is authorized with one or more exceptions, for example timber
Definition Source:
BLM
Attribute definition source:
BLM
GIS_MILES
Definition:
Length of a linear feature in miles.  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.
Attribute definition source:
BLM
GLOBALID
ROAD_LINK
Definition:
Unique identifier (e.g., FRMWK_ID, LINLOCID, SEGASSETID) for a road segment copied from GTRN dataset.  Which identifier to use is at the discretion of the district office..
Attribute definition source:
BLM
SHAPE.LEN
SDTS Feature Description
Description of point and vector spatial objects in the data using the Spatial Data Transfer Standards (SDTS) terminology.
Spatial data transfer standard (SDTS) terms
Feature class
Type: String
Count: 14526
Data Quality and Accuracy Information
General
Information about the fidelity of relationships, data quality and accuracy tests, omissions, selection criteria, generalization, and definitions used to derive the data.
Logical consistency report:
Description: Instance of Land Status Existing group. Geometry: Arcs may overlap each other entirely or in part. Topology: No topology enforced. Integration Requirements: There is usually no coincidence between ESMTROW arcs and ESMTROW polys. 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.
Completeness report:
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).
Attribute Accuracy
Accuracy of the identification of data entities, features and assignment of attribute values.
Attribute accuracy report:
The proposed ROWs and Easements are transitory and have varying degree of accuracy. Required attributes have an accuracy of at least 90%.
Data Source and Process Information
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description:
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.
Process date: 20100201
Process Step 2
Process description:
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.
Organization: Bureau of Land Management, Burns District
Person: Pam Keller
Position: GIS Coordinator
Phone: (541) 573-4486
Email: pkeller@blm.gov
Address type: mailing and physical
Address:
28910 Hwy 20 West
City: Hines
State or Province: OR
Postal code: 97738
County: US
Process date: 20100201
Process Step 3
Process description:
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.
Organization: Bureau of Land Management, Oregon/Washington State Office
Person: Barbara Haney
Position: GIS Data Management Specialist
Phone: (503) 808-6313
Email: bhaney@blm.gov
Address type: mailing
Address:
PO Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: 20111101
Process Step 4
Process description:
Attributes BLM_ORG_CD, GIS_MILES, 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."
Organization: Bureau of Land Management
Person: Roger Mills
Position: GIS Spec.
Phone: (503) 808-6340
Email: r2mills@blm.gov
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: 20130109
Data Distribution Information
General
Description of the data known by the party from whom the data may be obtained, liability of party distributing data, and technical capabilities required to use the data.
Distribution liability:
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.
Distribution Point of Contact
Contact information for the individual or organization distributing the data.
Organization: Bureau of Land Management, Oregon State Office
Person: Eric Hiebenthal
Position: GIS Data Management Specialist
Phone: 503-808-6565
Fax: 503-808-6419
Email: ehiebent@blm.gov
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20130403
Last metadata review date: 20130108
Metadata Point of Contact
Contact information for the individual or organization responsible for the metadata information.
Organization: Bureau of Land Management, Oregon State Office
Person: Roger Mills
Position: GIS Specialist
Phone: (503) 808-6340
Fax: (503) 808-6419
Telecommunications Device or Teletypewriter (TDD/TTY) phone: tdd/tty phone
Email: r2mills@blm.gov
Hours of service: 8:00-4:00
Instructions:
None
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Metadata Security Information
Handling restrictions imposed on the metadata because of national security, privacy or other concerns.
Security classifiction system: Not Classified
Security classification: Unclassified
Metadata Standards
Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.
Standard name: FGDC Content Standard for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention: local time
FGDC Plus Metadata Stylesheet
Stylesheet: FGDC Plus Stylesheet
File name: FGDC Plus.xsl
Version: 2.0
Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.
Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.
Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.