United States Department of the Interior
BUREAU OF LAND MANAGEMENT
Oregon State Office
P.O. Box 2965
Portland, Oregon 97208
In Reply Refer to:
1283/ 2801/2812/2101 (OR936/OR955) P
March 5, 2010
EMS TRANSMISSION 03/08/2010
Instruction Memorandum No. OR-2010-023
Expires: 9/30/2011
To:
DMs, DSDs, Staff and Branch Chiefs
From:
State Director, Oregon/Washington
Subject:
Easements and Rights-of-Way Spatial Data Standard
Program Area: Lands and Realty.
Purpose: This instruction memorandum establishes the Oregon/Washington (OR/WA) spatial
data standard for Easements and Rights-of-Way (ROW). The data standard defines how this
type of data is to be captured in a geographic information system (geodatabase), defines
attributes used, and defines coding schemes (domains). The Easements and ROWs lines and
polygons have been added to the corporate spatial data editing system. The data can now be
edited (see the data standard for the appropriate times and reasons for edits to be made) by
approved field personnel following established procedures. This data is also now available for
display and analytical purposes by all users.
Policy/Action: This data standard is to be followed for all Easement and ROW geospatial data.
This data set does not include all Easements and ROWs, only those that are needed for spatial
analysis or display. Also, only a limited set of information about each Easement or ROW is
captured as part of this data set. For complete information please refer to the case files, the
Master Title Plat, or the LR 2000 database.
Timeframe: This data standard is effective immediately.
Budget Impact: None.
Background: Field offices have a need to edit existing (or add new) spatial data for Easements
and ROWs. In order for that to happen, the data needs to be standardized so it can be made
available to the field in the corporate edit environment.
Manual/Handbook Sections Affected: None.
2
Coordination: This standard was reviewed by field and State Office staff (Geographical
Information Systems (GIS) and Realty). In addition, an online review session was held to
identify issues or questions that needed to be answered. Coordination with the OR/WA Records
Administrator also took place to develop the Privacy Impact Assessment for this data set.
Contacts: Cathie Jensen, State Data Steward for Easements and ROWs, at 503-808-6310, or
Pamela Keller, GIS Technical Support, at 541-573-4486, or Stanley Frazier, State Data
Administrator, at 503-808-6009.
Districts with Unions are reminded to notify their unions of this Instruction Memorandum and
satisfy any bargaining obligations before implementation. Your servicing Human Resources
Office or Labor Relations Specialist can provide you assistance in this matter.
Signed by
Michael S. Mottice
Associate State Director
Authenticated by
Rhondalyn J. Darnell
Records Section
3 Attachments
1 – Easements and Rights-of-Way Comments Resolution (3 pp)
2 – Easements and Rights-of-Way Data Standard (33 pp)
3 – Easements and Rights-of-Way Privacy Impact Assessment (7 pp)
Distribution
OC 120 (Chatfield)
EASEMENTS AND RIGHTS-OF-WAY SPATIAL DATA STANDARD
COMMENT RESOLUTION
2/2/2010
COMMENT
Accuracy statement is too vague
Add RADMETER_R and
RADMETER_L
Serial Number
Scanned Documents
“Exclusive” Easement/ROW
PROPOSAL
Since the geometry will come from a variety of
sources, then identify each of those sources and
make a statement about each, for example,
“digitized data from topo maps are accurate to 40
feet, 90% of the time.” Another example for
attribution may be, “The Rights-of-Way (ROW) and
Easements are defined from the legal descriptions
from source documents found in the casefiles.
Legal descriptions in those casefiles can at times be
quite vague thus very difficult to interpret.” !n
effort should be made to create a scale that defines
levels of complexity relating to the legal
descriptions, for example, aliquot part = 1 easy
metes & bounds=3 more difficult and “across
section 03= 5 ambigious.
The buffer distance on each side of a ROW or
Easement can be different and need to be able to
track that difference.
Need serial number in addition to casefile number.
Need a field to put a link to the scanned documents.
You can have an Exclusive Easement or ROW that
has no or limited public access.
ACTION TAKEN
Wording added to indicate that spatial accuracy is to
be at a minimum of 100ft or better and the
ACCURACY_FT attribute added to the schema to track
the accuracy. A statement was added to say that
attribute accuracy is to be at least ninety percent.
Attributes added.
Casefile Number and Serial Number mean the same
thing. Nothing changed.
Comment withdrawn as not being practical.
The data standard (and the data) can only reflect the
stated access rights for the Easement or ROW. The
casefile documents are always the source to
Attachment 1-1
Exclusive/Non-Exclusive
LOCAL_ID
The draft data standard has these two terms
backwards – Non-Exclusive is administrative and
Exclusive generally means public access.
Need additional wording to say the dataset is not
intended to include all Easement and ROW
information.
Might want to clarify the examples given.
RADMETER data type
Change the (8,2) to (8.2)
Relationship to other themes
What is the relationship of the Easements to the
cultural, utilities, and transportation data themes?
The standard should clarify whether the accuracy is
spatial, attributes, or both.
Why doesn’t the dataset allow for tracking of the
spatial accuracy?
Does not adequately allow for traditional survey
methods to be used.
Can users digitize an Easement from National
Agriculture Imagery Program photography?
Specifies that Global Positioning System (GPS) data
must be 1:24k but most GPS is better than that.
Perhaps remove the 1:24k reference.
Data Set Description
Accuracy
Accuracy
Collection and Input Protocols
Collection and Input Protocols
Collection and Input Protocols
Snapping Guidelines
Collection and Input Protocols
How can one snap to the most accurate line
segment if the data set does not allow one to track
this information?
O&C ROW are never found on Master Tile
determine just what that means in each case.
Definition for ACCESS_ESMTROW corrected.
Wording added to indicate that not all Easements and
ROWs are intended to be included and that only basic
information is provided for those that are included.
Wording added to the attribute to show what the
coding means.
The format shown in the standard (8,2) is how the
software is used to document the data standard
displays the data type. The two forms mean the same
thing so no changes were made.
A paragraph on relationship to other themes was
added to the data standard.
Wording added to indicate the required accuracy for
spatial (at least within 100 ft) and attributes (90%).
ACCURACY_FT attribute added for tracking of spatial
accuracy.
Additional wording added to included surveys as a
source of data.
Imagery was added as a source of “as built” Easements
and ROWs.
The 1:24k reference was removed and replaced with a
requirement for a minimum of 100 ft accuracy, no
matter how collected. ACCURACY_FT attribute added
to track spatial accuracy. Lines are replaced when the
source provides a more accurate location than that
shown in ACCURACY_FT.
ACCURACY_FT added to track spatial accuracy.
Wording changed to indicate that these are
Attachment 1-2
Statewide Monitoring
Domains – CASETP
Plat (MTP). Federal Land Policy and Management
Act ROW and Easements are on MTP.
O&C ROW are not mapped anywhere. Are you
expecting all of the O&C ROW to be mapped and
added to Geographic Information System (GIS)?
This would be a huge workload.
Says it is not all-inclusive but lists everything. Leads
us to believe that you want all of the ROW data not
just the data with public access.
“sometimes” found on the MTP.
Wording added to the data set description to note
that not all ROWs and Easements will be in this
dataset, only those needed for common GIS analysis.
We would expect data to be added on an as-needed
basis.
The data set is designed to contain information about
ROWs and Easement with public access as well as
those with only administrative access. See previous
comment response.
Attachment 1-3
OR/WA State Data Dictionary
Bureau of Land Management
Easements / Rights of
Way Spatial Data
Standard
March 8, 2010
EASEMENTS/ROW
3/8/2010
Attachment 2-1
OR/WA State Data Dictionary
Bureau of Land Management
EASEMENTS/RIGHTS-OF-WAY
TABLE OF CONTENTS
SECTION
General Information
Responsibilities
FOIA Category
Records Retention Schedule
Security/Access/Sensitivity
Data Set Overview
Description
Usage
Sponsor/Affected Parties
Data Category/Architecture Link
Data Organization/Structure
Relationship to DOI Enterprise Architecture
Data Organization Graphic
Data Collection and Maintenance Protocols
Accuracy Requirements
Collection and Input Protocols
Maintenance Protocols
Update Transactions
Update Frequency
Relationship to Other Themes
Statewide Monitoring
Quality Assurance
Geodatabase Schema
Projection and Spatial Extent
Spatial Entity Characteristics
Attribute Characteristics and Definitions
Associated Files or Databases
Layer Files (Publication Views)
Editing Procedures
Oregon Data Framework Overview
Abbreviations and Acronyms Used
Appendix A – Domains Used
EASEMENTS/ROW
3/8/2010
PAGE
NUMBER
3
3
3
3
3
4
4
4
4
4
5
5
6
7
7
7
7
7
7
7
7
7
8
10
10
11
24
24
25
27
28
29
Attachment 2-2
OR/WA State Data Dictionary
Bureau of Land Management
GENERAL INFORMATION
Data Set (Theme) Name: Easements and Rights-of-Way
Data Set (Theme) Abbreviation: ESMTROW
RESPONSIBILITIES
State Data Steward - The State Data Steward is responsible for approving data standards and business rules for data themes they are responsible for, for developing quality assurance/quality control procedures, and ensuring that data is managed as a corporate resource. The State Data Steward coordinates with field office data stewards, the State Data
Administrator, Geographic Information System (GIS) Coordinators, and with national data stewards. The State Data
Steward reviews geospatial metadata for completeness and quality.
Lead GIS Specialist - The Lead GIS Specialist works with data stewards to interpret business needs into GIS
applications and derive data requirements and participates in the development of data standards. The GIS specialist
coordinates with System Administrators and GIS Coordinators to manage the GIS databases.
State Data Administrator - The State Data Administrator provides information management leadership, data modeling expertise, and custodianship of the state data models. The State Data Administrator ensures that defined processes for development of data standards and metadata are followed and that they are consistent and complete. The data administrator is responsible for making data standards and metadata accessible to all users. The data administrator coordinates with data stewards and GIS coordinators to respond to national spatial data requests.
State Records Administrator - The State Records Administrator is responsible for identifying any Privacy issues related to spatial data. The records administrator also provides direction and guidance on data release and fees. The
records administrator assures that data has been classified under the proper records retention schedule and determine
appropriate Freedom of Information Act category.
FOIA CATEGORY
Public
RECORDS RETENTION SCHEDULE(s)
GRS BLM 20-5
TEMPORARY. Delete when no longer needed for administrative, legal, audit, or other operational purposes.
SECURITY/ACCESS/SENSITIVITY
The Easements and Rights-of-Way (ROW) set of themes do not require any additional security other than that provided by the General Support System (the hardware/software infrastructure of the Oregon/Washington (OR/WA)
Bureau of Land Management (BLM).
This data is not sensitive and there are no restrictions on access to this data either from within the BLM or external to
the BLM.
There are no Privacy issues or concerns associated with these data themes. Privacy Impact Assessment has been
completed. This data set falls under the Privacy Act System of Records Notice LLM-32, Land and Minerals
Authorization Tracking System.
EASEMENTS/ROW
3/8/2010
Attachment 2-3
OR/WA State Data Dictionary
Bureau of Land Management
DATA SET DESCRIPTION
This data set represents ROWs and Easements. 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&C 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. 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. 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.
USAGE
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.
SPONSOR/AFFECTED PARTIES
The sponsor for this data set is the Deputy State Director, Resource Use, Planning and Protection. A ROW or
Easement is defined by and specific to BLM. Matching interagency data across the landscape is not necessary, but
correcting discrepancies between BLM and non-BLM databases is important.
DATA CATEGORY/ARCHITECTURE LINK
These data themes are a portion of the Oregon Data Framework (ODF). The ODF utilizes the concept of inheritance
to define specific instances of data. The Framework divides all OR/WA resource-related data into three general
categories: Activities, Resources, and Boundaries. These general categories are broken into sub-categories that
inherit spatial characteristics and attributes from their parent category. These sub-categories may be further broken
into more specific groups until you get to a basic data set that cannot be further sub-divided. Those basic data sets
inherit all characteristics of all groups/categories above them. The basic data sets are where physical data gets
populated (those groups/categories above them do not contain actual data but set parameters that all data of that type
must follow).
See the Oregon Data Framework Overview section for a simplified schematic of the entire Oregon Data Framework
showing the overall organization and entity inheritance. The Easement and ROW entities are highlighted. For
additional information about the Oregon Data Framework, contact:
OR/WA State Data Administrator
Stan Frazier
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
EASEMENTS/ROW
3/8/2010
Attachment 2-4
OR/WA State Data Dictionary
Bureau of Land Management
ROW/EASEMENT DATA ORGANIZATION / STRUCTURE
For EASEMENT/ROW, the categories/groups that the data set are part of are:
EASEMENT/ROW Polygon:
Oregon Data Framework
Boundaries
Land Status
Existing Land Status Encumbrance Area
ESMTROW_POLY
Proposed Land Status
Proposed Encumbrance Area
ESMTROW_P_POLY
EASEMENT/ROW Line:
Oregon Data Framework
Boundaries
Land Status
Existing Land Status
Encumbrance Linear
ESMTROW_ARC
Proposed Land Status
Proposed Encumbrance Linear
ESMTROW_P_ARC
RELATIONSHIP TO THE DEPARTMENT OF THE INTERIOR ENTERPRISE ARCHITECTURE - DATA
RESOURCE MODEL
The Department of the Interior's (DOI) Enterprise Architecture contains a component called the Data Resource
Model. This model addresses the concepts of Data Sharing, Data Description, and Data Context. This data
standard provides information needed to address each of those areas. Data sharing is addressed through complete
documentation and simple data structures which make sharing easier. Data description is addressed through the
section on Attribute Descriptions. Data context is addressed through the data organization and structure portions of
this document. In addition, the DOI Data Resource Model categorizes data by use of standardized Data Subject
Areas and Information Classes. For this data set, these are as follows:
Data Subject Area: Geospatial
Information Class: Location
For a complete list of all DOI Data Subject Areas and Information Classes contact:
OR/WA State Data Administrator
Stan Frazier
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
EASEMENTS/ROW
3/8/2010
Attachment 2-5
OR/WA State Data Dictionary
Bureau of Land Management
DATA ORGANIZATION GRAPHIC
ORE GONDATAFRAMEWORK
VE RS ION_NA~E
Va ri abl!
c1l11a ct!~(M)
-(
PROPO SEDLANDSTAT US
EXIS TIN GLANDSTATUS
f
l,J
PR OPOS ED
EXIS TIN GEN C U ~8 RAN C E S
E S ~TRO't(N ~
E S~ TR OWJ P
ESIA TROWJTR
AUTH_USE
RGT_HOLDER
R G T _HOLD E R_N ~
GRANT OR
AC CESUS~ T ROW
CASEFILE
CASE TP
LOCALJD
ACCURACYJ T
EN C U ~ 8 RANC E S
E S ~ TROW] _NA~E
Va ri abl eelimct!~(JO)
Va ri abl ec1l11act!~(10)
Va ri abl! elimctl~(20)
Va ri ableelimct!~(JO)
Va ri abl! c1l11act!~(3)
Va ri abl! cn m ct!~(JO)
Variabl! clim ct!~(W)
Va ri ableenmct!~(10)
Variabll enlllct!~(1~)
ES~ T ROW_T P
ES~ T R OWJ T R
AUTH_USE
M T] _HOLDER_N ~
GRAN TOR]
ACCESUS~ T ROW
CASEFILE
STATU S]
ALT ERNATrvE
AR CH_C LEAR
aOT_C LEAR
VI1 LD_C LEAR
ACCURACYJT
Cnmctl~(e)
Va ri abll enmctl~(10)
S n o ~ intlglr
Va ri abl! cn mct!~(JO)
Va ri abl eelimct!~(10)
Va ri abl ecn mctl~(20)
Variabll elimctl~(W)
Variabll cn mctl~(W)
Variabll cn mct!~(W)
Variabll enmctl~(10)
Variabll enmctl~(15)
Va ri abll cn mctl~(10)
Cnmcti~(.l)
C n mctl~(8)
C n mctl~(8)
C n mctl~(8)
S n o~
inti i ! r
~
ES ~ TROW_AR C
E S~ T R OW]O LY
RAD ~E TER
E S~ TR OW]]O LY
Dl cim al (8 ,~)
RAD ~ E T E R
RAD ~ ETER_L D I ~ m a l (8,~)
EASEMENTS/ROW
Va ri abll
D ! ~ma l
(8,2)
(8,2)
D!~ma l (8,2)
RAD ~E T E R_L D e ~m a l
RAD ~ ETER_R D I ~m a l (8,~)
ROAD_LINK
ESr.l TROW] _ARC
RAD ~ E T ERJ
enmcli~(.lO)
~
3/8/2010
Attachment 2-6
OR/WA State Data Dictionary
Bureau of Land Management
DATA MANAGEMENT PROTOCOLS
ACCURACY REQUIREMENTS: This data set requires the highest possible accuracy. Accuracy is determined by
availability of survey data and Geographic Coordinate Data Base for the area. Where ROWs and Easements follow
road or other physical features, the coordinates are obtained from the most accurate source available (see Collection
and Input Protocols).
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).
The proposed ROWs and Easements are transitory and have varying degree of accuracy.
COLLECTION AND INPUT PROTOCOLS: 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 (GPS) 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.
Required attributes have an accuracy of at least ninety percent.
Polygons representing the widths of Easement and ROW linear features do not need to be created since they can be
created “on-the-fly” as needed using the RADMETER attribute. Proposed Easements and ROWs are created from
legal descriptions in the same way. If a proposed Easement or ROW becomes fact, it is copied to the corresponding
existing ESMTROW feature class and deleted from the proposed feature class.
MAINTENANCE PROTOCOLS: If there is a GCD update which shifts the points the ESMTROW lines and
polygons need to be re-snapped. Other updates to correct or improve locational accuracy are done when discovered.
UPDATE TRANSACTIONS: The unit of processing for the ESMTROW group of themes is the individual
Easement or ROW.
UPDATE FREQUENCY: Variable and as needed.
RELATIONSHIP TO OTHER THEMES: 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. To associate facilities with the rights and restrictions attached to them, an
ESMTROW “flag” can be added as an attribute on the relevant constructed feature arc segment or point. Similarly,
to associate an Easement or ROW with the road it encumbers, there is a “ROADLINK” attribute.
STATEWIDE MONITORING: District Realty Specialists are required to check the themes for spatial and attribute
accuracy within their districts and to keep the themes consistent and current with LR2000 and the case files and to
confirm that proposed Easements and ROWs were moved to existing Easements and ROWs after approval. The
State Data Steward is responsible for checking consistency across districts. At least once yearly, ESMTROW_ARC
and ESMTROW_POLY will be checked by comparing to LR2000. Number of cases in LR2000 and not in
ESMTROW_ARC/POLY and vice versa will be used to determine completeness. Over time, the gap should narrow.
EASEMENTS/ROW
3/8/2010
Attachment 2-7
OR/WA State Data Dictionary
Bureau of Land Management
EASEMENT ROW GEODATABASE SCHEMA (simplified)
General Information: Attributes are listed in the order they appear in the geodatabase feature class. The order is an
indication of the importance of the attribute for theme definition and use. There are no aliases unless specifically
noted. The domains used in this data standard can be found in Appendix A. These are the domains at the time the
data standard was approved. Domains can be changed without a re-issue of the data standard so those shown in the
Appendix may not be current. Contact the OR/WA State Data Administrator for the current lists.
OR/WA State Data Administrator
Stan Frazier
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
ESMTROW_POLY (Easement/ROW Polygons)
Attribute Name
Data Type
Length
ESMTROW_NM
ESMTROW_TP
ESMTROW_FTR
AUTH_USE
RGT_HOLDER
RGT_HOLDER_NM
GRANTOR
ACCESS_ESMTROW
CASEFILE
CASETP
LOCAL_ID
ACCURACY_FT
VERSION_NAME
String
String
String
String
String
String
String
String
String
String
String
Short Integer
String
30
10
20
30
3
30
30
10
15
6
10
50
ESMTROW_ARC (Easement/ROW Arcs)
Attribute Name
Data Type
Length
ESMTROW_NM
ESMTROW_TP
ESMTROW_FTR
AUTH_USE
RGT_HOLDER
RGT_HOLDER_NM
GRANTOR
ACCESS_ESMTROW
CASEFILE
CASETP
LOCAL_ID
ACCURACY_FT
RADMETER
EASEMENTS/ROW
String
String
String
String
String
String
String
String
String
String
String
Short Integer
Number
30
10
20
30
3
30
30
10
15
6
10
8,2
Default
Value
-1
InitialLoad
Default
Value
-1
-1
3/8/2010
Required?
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
No
No
No
Yes
Required?
Yes
Yes
Yes
No
Yes
No
Yes
Yes
Yes
No
No
No
No
Domain
dom_ESMTROW_TP
dom_ESMTROW_FTR
dom_AUTH_USE
dom_JURISCODE
dom_JURISNAME
dom_ACCESS_ESMTROW
dom_CASETP
Domain
dom_ESMTROW_TP
dom_ ESMTROW_FTR
dom_AUTH_USE
dom_JURISCODE
dom_JURISNAME
dom_ACCESS_ESMTROW
dom_CASETP
Attachment 2-8
OR/WA State Data Dictionary
RADMETER_L
RADMETER_R
ROAD_LINK
VERSION_NAME
Bureau of Land Management
Number
Number
String
String
8,2
8,2
20
50
-1
-1
InitialLoad
ESMTROW_P_POLY (Easement/ROW Proposed Polygons)
Attribute Name
Data Type
Length
Default
Value
ESMTROW_P_NM
String
30
ESMTROW_TP
String
10
ESMTROW_FTR
String
20
AUTH_USE
String
30
RGT_P_HOLDER_NM String
30
GRANTOR_P
String
30
ACCESS_ESMTROW String
10
CASEFILE
String
15
STATUS_P
String
10
ALTERNATIVE
String
2
ARCH_CLEAR
String
8
BOT_CLEAR
String
8
WILD_CLEAR
String
8
ACCURACY_FT
Short Integer
-1
VERSION_NAME
String
50
InitialLoad
ESMTROW_P_ARC (Easement/ROW Proposed Arcs)
Attribute Name
Data Type
Length
Default
Value
ESMTROW_P_NM
String
30
ESMTROW_TP
String
10
ESMTROW_FTR
String
20
AUTH_USE
String
30
RGT_P_HOLDER_NM String
30
GRANTOR_P
String
30
ACCESS_ESMTROW String
10
CASEFILE
String
15
STATUS_P
String
10
RADMETER
Number
8,2
-1
RADMETER_L
Number
8,2
-1
RADMETER_R
Number
8,2
-1
ALTERNATIVE
String
2
ARCH_CLEAR
String
8
BOT_CLEAR
String
8
WILD_CLEAR
String
8
ACCURACY_FT
Short Integer
-1
VERSION_NAME
String
50
InitialLoad
EASEMENTS/ROW
3/8/2010
No
No
No
Yes
Required?
Yes
Yes
Yes
No
No
Yes
Yes
No
Yes
No
No
No
No
No
Yes
Required?
Yes
Yes
Yes
No
No
Yes
Yes
No
Yes
No
No
No
No
No
No
No
No
Yes
Domain
dom_ESMTROW_TP
dom_ ESMTROW_FTR
dom_AUTH_USE
dom_ACCESS_ESMTROW
dom_STATUS_P
Domain
dom_ESMTROW_TP
dom_ ESMTROW_FTR
dom_AUTH_USE
dom_ACCESS_ESMTROW
dom_STATUS_P
Attachment 2-9
OR/WA State Data Dictionary
Bureau of Land Management
PROJECTION AND SPATIAL EXTENT
All feature classes and feature datasets are in Geographic, NAD83. Units are decimal degrees. Spatial extent (area
of coverage) includes all lands managed by the BLM in the states of OR/WA but is not "wall-to-wall," and may cover
only a small percentage of the total. See the metadata for this data set for more precise description of the extent.
SPATIAL ENTITY CHARACTERISTCS
ESMTROW_POLY
Description: Instance of Land Status Existing group. Geometry: Polygons may overlap entirely or in part.
Topology: No.
Integration Requirements: If polylines are defined as parcels, they must have a vertex for every GCD point and be
snapped to it. There is usually no coincidence between ESMTROW arcs and ESMTROW polys.
ESMTROW_P_POLY
Description: Instance of Land Status Proposed group.
Geometry: Polygons may overlap each other entirely or in part and may overlap ESTMROW_POLY features.
Topology: No. Integration Requirements: If polylines are defined as parcels, they must have a vertex for every GCD point and be
snapped to it. ESMTROW_ARC
Description: Instance of Land Status Existing group.
Geometry: Arcs may overlap each other entirely or in part.
Topology: No.
Integration Requirements: There is usually no coincidence between ESMTROW arcs and ESMTROW polygons.
ESMTROW_P_ARC
Description: Instance of Land Status Proposed group. Geometry: Arcs may overlap each other entirely or in part, and may overlap ESMTROW_ARC features.
Topology: No.
Integration Requirements: There is usually no coincidence between ESMTROW arcs and ESMTROW polygons.
EASEMENTS/ROW
3/8/2010
Attachment 2-10
OR/WA State Data Dictionary
Bureau of Land Management
ATTRIBUTE CHARACTERISTICS AND DEFINTIONS
(in alphabetical order)
ACCESS_ESMTROW
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
ACCESS_ESMTROW
ACCESS_ESMTROW_CODE
Inherited from EXISTING ENCUMBRANCES or PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
ESMTROW_P_POLY
ESMTROW_P_ARC
dom_ACCESS_ESMTROW
Variable characters (10)
Description
[Required]
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.
Examples: PUBLIC, ADMIN
ACCURACY_FT
Name
Code
Comment
Domain
Data Type
Length
Precision
ACCURACY_FT
ACCURACY_FEET_MEASURE
Inherited from EXISTING ENCUMBRANCES or PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
ESMTROW_P_POLY
ESMTROW_P_ARC
None
SI
Description
[Optional]
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.
EASEMENTS/ROW
3/8/2010
Attachment 2-11
OR/WA State Data Dictionary
ALTERNATIVE
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
ALTERNATIVE
ALTERNATIVE_TEXT
Inherited from PROPOSED ENCUMBRANCES
Used by Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Characters (2)
Description
[Optional]
Identifier for the alternative during the planning process (e.g. A, B, C, D, E). Free choice values for different plans
but not more than 2 characters.
ARCH_CLEAR
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
ARCH_CLEAR
ARCHAEOLOGICAL_CLEARANCE_DATE
Inherited from PROPOSED ENCUMBRANCES
Used by Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Characters (8)
Description
[Optional]
Date the facility/site received archaeological clearance.
YYYYMMDD
EASEMENTS/ROW
3/8/2010
Attachment 2-12
OR/WA State Data Dictionary
AUTH_USE
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
AUTH_USE
AUTHORIZED_USE_TEXT
Inherited from EXISTING ENCUMBRANCES or PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
ESMTROW_P_POLY
ESMTROW_P_ARC
dom_AUTH_USE
Characters (30)
Description
[Optional]
Use that is authorized by the Easement or ROW.
Examples: Windpower Testing, Windpower Development, Solar Development, Crossing Access, Power
Transportation.
BOT_CLEAR
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
BOT_CLEAR
BOTANICAL_CLEARANCE_DATE
Inherited from PROPOSED ENCUMBRANCES
Used by Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Characters (8)
Description
[Optional]
Date the facility/site received botanical clearance.
YYYYMMDD
EASEMENTS/ROW
3/8/2010
Attachment 2-13
OR/WA State Data Dictionary
CASEFILE
Geodatabase Name
BLM Structured Name
Notes
Bureau of Land Management
CASEFILE
CASEFILE_NUMBER
Inherited from EXISTING ENCUMBRANCES or PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Variable characters (15)
Data Type
Description
[Required for Existing]
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.
CASETP
Geodatabase Name
BLM Structured Name
Notes
CASETP
CASE_TYPE_CODE
Inherited from EXISTING ENCUMBRANCES
Domain
Used by Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
dom_CASETP
Data Type
Characters (6)
Description
[Optional]
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
EASEMENTS/ROW
3/8/2010
Attachment 2-14
OR/WA State Data Dictionary
ESMTROW_FTR
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
ESMTROW_FTR
EASEMENT_ROW_FEATURE_CODE
Inherited from EXISTING ENCUMBRANCES OR PROPOSED
ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
ESMTROW_P_POLY
ESMTROW_P_ARC
dom_ESMTROW_FTR
Variable characters (20)
Description
[Required]
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.
ESMTROW_NM
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
ESMTROW_NM
EASEMENT_ROW_NAME
Inherited from EXISTING ENCUMBRANCES.
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
None
Variable characters (30)
Description
[Required]
Name of the project the ROW or Easement is part of.
EASEMENTS/ROW
3/8/2010
Attachment 2-15
OR/WA State Data Dictionary
ESMTROW_P_NM
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
ESMTROW_P_NM
EASEMENT_ROW_PROPOSED_NAME
Inherited from PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Variable characters (30)
Description
[Required]
Unique identifying name for a proposed ROW or Easement project.
Examples: Kiger Fence, Ponderosa Timber Access, Horizon Wind Access, Steens Easement, Public Hiking Trail,
Hodges ROW.
ESMTROW_TP
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
ESMTROW_TP
EASEMENT_ROW_TYPE_CODE
Inherited from EXISTING ENCUMBRANCES and PROPOSED
ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
ESMTROW_P_POLY
ESMTROW_P_ARC
dom_ESMTROW_TP
Characters (10)
Description
[Required]
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.
EASEMENTS/ROW
3/8/2010
Attachment 2-16
OR/WA State Data Dictionary
GRANTOR
Geodatabase Name
BLM Structured Name
Notes
Bureau of Land Management
GRANTOR
EASEMENT_ROW_GRANTOR_NAME
Inherited from EXISTING ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
Domain
Data Type
None
Variable characters (30)
Description
[Required]
The name of the entity (person, organization) that is granting the Easement or ROW.
Examples: USFS, BLM, USFWS, BPA, STATE, PRIVATE, DIAMOND RANCH LLC.
GRANTOR_P
Geodatabase Name
BLM Structured Name
Notes
GRANTOR_P
EASEMENT_ROW_PROPOSED_GRANTOR_NAME
Inherited from PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
Domain
Data Type
None
Variable characters (30)
Description
[Required]
The name of the entity (person, organization) that would grant the proposed Easement or ROW.
Examples: USFS, BLM, USFWS, BPA, STATE, PRIVATE, DIAMOND RANCH LLC.
EASEMENTS/ROW
3/8/2010
Attachment 2-17
OR/WA State Data Dictionary
LOCAL_ID
Geodatabase Name
BLM Structured Name
Notes
Bureau of Land Management
LOCAL_ID
EASEMENT_ROW_LOCAL_IDENTIFIER
Inherited from EXISTING ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
Domain
Data Type
None
Variable characters (10)
Description
[Optional]
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.).
RADMETER
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
RADMETER
RADIAL_BUFFER_METERS
Not Inherited
Used in Feature Classes:
ESMTROW_ARC
ESMTROW_P_ARC
None
Decimal (8,2)
Description
[Optional]
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.
EASEMENTS/ROW
3/8/2010
Attachment 2-18
OR/WA State Data Dictionary
RADMETER_L
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
RADMETER
LEFT_RADIAL_BUFFER_METERS
Not Inherited
Used in Feature Classes:
ESMTROW_ARC
ESMTROW_P_ARC
None
Decimal (8,2)
Description
[Required if RADMETER_R has something other than -1]
“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.
RADMETER_R
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
RADMETER
RIGHT_RADIAL_BUFFER_METERS
Not Inherited
Used in Feature Classes:
ESMTROW_ARC
ESMTROW_P_ARC
None
Decimal (8,2)
Description
[Required if RADMETER_L has something other than -1]
“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.
EASEMENTS/ROW
3/8/2010
Attachment 2-19
OR/WA State Data Dictionary
RGT_HOLDER
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
RGT_HOLDER
RIGHT_HOLDER_ORGANIZATION_CODE
Inherited from EXISTING ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
dom_JURISCODE
Variable characters (3)
Description
[Required]
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).
RGT_HOLDER_NM
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
RGT_HOLDER_NM
RIGHT_HOLDER_NAME
Inherited from EXISTING ENCUMBRANCES
Used in Feature Classes:
ESMTROW_POLY
ESMTROW_ARC
dom_JURISNAME
Variable characters (30)
Description
[Optional]
Name of the organization or person that holds the rights granted in the ROW or Easement.
Examples: MOUNT HOOD NF, HART MOUNTAIN NAT ANTELOPE REF, WALLOWA LAKE STATE
PARK, DIAMOND RANCH LLC.
EASEMENTS/ROW
3/8/2010
Attachment 2-20
OR/WA State Data Dictionary
RGT_P_HOLDER_NM
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
RGT_P_HOLDER_NM
RIGHT_HOLDER_PROPOSED_NAME
Inherited from PROPOSED ENCUMBRANCES
Used by feature classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Variable characters (30)
Description
[Optional]
Name of the person or entity applying for a ROW or Easement.
Examples: MOUNT HOOD NF, HART MOUNTAIN NAT ANTELOPE REF, WALLOWA LAKE STATE
PARK, DIAMOND RANCH LLC.
ROAD_LINK
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
ROAD_LINK
ROAD_LINK
Not inherited
Used in Feature Classes:
ESMTROW_ARC
ESMTROW_P_ARC
None
Variable characters (20)
Description
[Optional]
Unique identifier (FRMWK_ID for eastside or ROUTE ID for westside) for each road segment copied from The
Ground Transportation dataset.
EASEMENTS/ROW
3/8/2010
Attachment 2-21
OR/WA State Data Dictionary
STATUS_P
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
STATUS_P
FACILITY_PROPOSED_STATUS_CODE
Inherited from PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
dom_STATUS_P
Variable characters (10)
Description
[Required]
Status of the proposed ROW or Easement.
Examples: Initial, Active, Suspended, Rejected, Relinquished.
VERSION_NAME
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
VERSION_NAME
GEODATABASE_VERSION_TEXT
Only appears in the transactional (edit) version. Public version (which is also the
version used internally for mapping or analysis) does not contain this attribute.
Used in Feature Class:
ESMTROW_ARC
ESMTROW_POLY
ESMTROW_P_ARC
ESMTROW_P_POLY
None
Variable characters (50)
Description
[Required] (automatically generated)
Name of the corporate geodatabase version previously used to edit the record.
InitialLoad = feature has not been edited in ArcSDE.
Format: username.XXX-mmddyy-hhmmss = version name of the last edit (hours might be a single digit; leading
zeros are trimmed for hours only). XXX = theme abbreviation.
EASEMENTS/ROW
3/8/2010
Attachment 2-22
OR/WA State Data Dictionary
WILD_CLEAR
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Bureau of Land Management
WILD_CLEAR
WILDLIFE_CLEARANCE_DATE
Inherited from PROPOSED ENCUMBRANCES
Used in Feature Classes:
ESMTROW_P_POLY
ESMTROW_P_ARC
None
Characters (8)
Description
[Optional]
Date the facility site received wildlife clearance.
YYYYMMDD
EASEMENTS/ROW
3/8/2010
Attachment 2-23
OR/WA State Data Dictionary
Bureau of Land Management
ASSOCIATED FILES OR DATABASES
Data pertaining to individual ROWs or Easements is found in the LR2000 national database. Additional information
may also be found in the Master Title Plats and the official case file record.
LAYER FILES (PUBLICATION VIEWS)
Master corporate feature classes/datasets maintained in the edit database (currently orsoedit) are “published” to the
user database (currently orsovctr) in several ways:
1. Copied completely with no changes (replicated).
2. Copied with no changes except to omit one or more feature classes from a feature dataset.
3. Minor changes made (for example clip, dissolve, union with ownership) in order to make the data
easier to use. These “Publication feature classes” are indicated by “PUB” in their name. They are created through
scripts that can be automatically executed and are easily rebuilt from the master (orsoedit) data whenever necessary.
Layer files point to existing data and are not new data requiring storage and maintenance. They have appropriate
selection and symbolization for correct use and display of the data. They provide the guidance for data published on
the web. Layer files are created by simple documented process and can be deleted and recreated at any time.
A publication feature class will be created for publishing to the web/release to the public that has the attribute
RIGHT_HOLDER_NM removed (for Privacy reasons). All datasets are published, both internally and externally,
with the attribute VERSION_NAME removed (also for Privacy reasons).
EASEMENTS/ROW
3/8/2010
Attachment 2-24
OR/WA State Data Dictionary
Bureau of Land Management
EDITING PROCEDURES
MANAGING OVERLAP
“Overlap” means there are potentially more than one feature in the same feature class that occupies the same space
(“stacked” polygons).
POLY/ARC feature dataset means that there is a polygon feature class with an arc feature class that represents the
perimeter of the polygon and must be kept coincident with the polyline.
In this discussion, a polygon feature may consist of more than one polygon and an arc feature may consist of more
than one arc. They would have multiple records in the spatial table (with identical attributes). Multi-part features
are not allowed. Multi-part features are easily created inadvertently and not always easy to identify. If they are not
consciously and consistently avoided, feature classes will end up with a mixture of single and multi-part features.
Multi-part features can be more difficult to edit, query, and select, along with impacting overall performance .
Overlap is only allowed in the Oregon Data Framework in limited and controlled scenarios. In each case, the
“cause” of the overlap (what attribute changes will “kick off” a new feature which may overlap an existing feature) is
carefully defined and controlled. In other words, in feature classes that permit overlap when there is a change in
spatial extent there is always a new feature created which may overlap an existing feature, but in addition there are
certain attribute(s) that will result in a new feature even if there is no spatial change. The feature classes (and the one
feature dataset) that allow overlap and the attributes that lead to a new, possibly overlapping, feature are described
below.
Overlapping Polygons where polygons are part of a POLY/ARC feature dataset
Topology rules apply only to the POLY/ARC relationship (Polylines in the POLY feature class covered by arcs in the
ARC feature class and vice versa; Arcs must not have dangles, intersect, self-overlap or overlap adjacent arcs).
PLANBDY
Any number of plans or projects might overlap. A new PLANID creates a new
polygon.
Overlapping Polygons where polygons are a stand-alone feature class
No topology rules.
Species Occurrence Group: These are distinct sites defined by species and time. A different species create a new
polygon which may overlap another site in whole or part. A change in time (new visit date) will create a new
polygon if it is desired that the old spatial extent and date is retained (as historic). Additionally, for wildlife, a
different season/type of use (e.g., winter range vs. spring breeding) will create new polygon that may overlap others.
WEEDS
GB_FLORA_SITES
GB_FAUNA_SITES
WILDSITE_POLY
Survey Group: Within each feature class a new survey is created only for a new date. This group might also
include proposed surveys in separate feature classes. (WEED_P_SURV, etc).
WEED_SURV
CULT_SURV
FAUNA_SURV
FLORA_SURV
EASEMENTS/ROW
3/8/2010
Attachment 2-25
OR/WA State Data Dictionary
Bureau of Land Management
Treatment Activity Group: Within each feature class a new treatment area is created only for a new date and
sometimes for a different method if it is not possible to SPLIT the treatment area by method and it is important to
capture more than one method applied to the same area on the same day. This group also includes proposed
treatments in separate feature classes (BURN_P , etc. and these could have additional overlap created by different
alternatives).
BURN, HARV, MECH, REVEG, PROT, BIO, CHEM
Land Status Encumbrances Group: A new polygon is created for a change in casefile number even if it is the same
area.
ESMTROW_POLY
WITHDWL
Overlapping Arcs where arcs are a stand-alone feature class
No topology rules.
ESMTROW_ARC
Overlapping Points:
Not nearly as big of a problem because they have no spatial extent, but still should be checked and duplicates deleted.
Editing and Quality Control Guidelines
Checking for undesired duplicates is critical. Polygons or arcs that are 100% duplicate can be easily found by
searching for identical attributes along with identical Shape_Area and/or Shape_Length. Searching for partially
overlapping arcs or polygons is harder and each case must be inspected to determine if the overlap is desired or not.
Where polygons are created with the buffer tool the correct option must be selected. The default option is “None,”
which means overlap will be retained. Sometimes the overlap should be dissolved and the option changed to “All.”
If the dissolve tool is used on polygons or arcs, the “Create multipart features” should be unchecked.
Snapping Guidelines
Where line segments with different COORD_SRC meet, the most accurate or important (in terms of legal boundary
representation) are kept unaltered and other lines snapped to them. In general, the hierarchy of importance is LLI
(GCD points/lines) first with DLG or SOURCEL next and Digital Elevation Model and map last.
When snapping to the data indicated in COORD_SRC (as opposed to duplicating with copy/paste), be sure there are
exactly the same number of vertices in the target and source theme arcs.
When the DEF_FEATURE is “SUBDIVISION” snap the line segment to GCD points and make sure there are the
same number of vertices in the line as GCD points.
On themes with ACCURACY_FT but no COORD_SRC or DEF_FEATURE, the line with better ACCURACY_FT
is kept unaltered.
EASEMENTS/ROW
3/8/2010
Attachment 2-26
OR/WA State Data Dictionary
Bureau of Land Management
OREGON/WASHINGTON DATA FRAMEWORK OVERVIEW
EASEMENTS/ROW
3/8/2010
Attachment 2-27
OR/WA State Data Dictionary
Bureau of Land Management
ABBREVIATIONS AND ACRONYMS USED IN THIS STANDARD
(does not include abbreviations/acronyms used as codes for particular data attributes)
BLM - Bureau of Land Management
DLG - Digital Line Graphs
DRG - Digital Raster Graphic
FOIA - Freedom of Information Act
GCD - Geographic Coordinate Database
GIS - Geographic Information System
GPS - Global Positioning System
LR2000 – Legacy Rehost 2000 Database
MTP - Master Title Plat
NAD - North American Datum
NARA - National Archives and Records Administration
ODF - Oregon Data Framework
OR/WA - Oregon / Washington
SDE - Spatial Data Engine
EASEMENTS/ROW
3/8/2010
Attachment 2-28
OR/WA State Data Dictionary
Bureau of Land Management
APPENDIX A
DOMAINS (VALID VALUES)
The domains listed below are those that were in effect at the time the data standard was approved and may not be
current. Contact the State Data Administrator for current lists:
OR/WA State Data Administrator
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
Domain Name
Page Number
ACCESS_ESMTROW
29
AUTH_USE
29
CASETP
29
ESMTROW_FTR
32
ESMTROW_TP
33
JURISCODE
33
JURISNAME (Not shown – contact State Data Administrator)
STATUS_P
33
DOMAIN: ACCESS_ESMTROW
CODE
ADMIN
PUBLIC
DESCRIPTION
Access only for BLM administrative purposes
Public access
DOMAIN: AUTH_USE
CODE
Windpower Testing
Windpower Development
Power Transportation
Solar Development
Crossing Access
DESCRIPTION
Testing of an area/site for potential wind power generation
Development of a wind power generation area/site
Movement of power across an area (i.e. transmission lines, pipelines)
Development of an area/site for solar power generation
Crossing the land with a vehicle is authorized
DOMAIN: CASETP
(not all-inclusive, contact State Data Administrator for complete list)
CODE
210006
210007
210017
280003
280004
DESCRIPTION
ACQ-TIMBER ACCESS ROAD
ACQ-PUBLIC LAND ADM ACT
ACQ-ROW RD RCP
ROW-FACILITY TO HIGHWAY
ROW TEMP USE PERMITS
EASEMENTS/ROW
3/8/2010
Attachment 2-29
OR/WA State Data Dictionary
280502
281001
281003
281007
281008
281009
281011
281100
281130
281200
281210
281211
281230
281300
281400
282107
282201
283001
283002
283003
283103
284001
284003
284004
284008
284009
284011
284099
284100
284200
285001
285002
285003
285004
285005
285006
285007
285008
285009
285011
285110
285130
286001
Bureau of Land Management
ROW-FEDERAL BIA
ROW-ROADS
ROW-ROADS, ACQ
ROW-ROADS FEDERAL FAC
ROW-ROADS FED 44LD513
UNAUTH ACTIVITY-ROW-RD
ROW-ROAD RECONVEYED
TRAM & LOG ROAD-PUB LAND
ROW-RD-RCPL PUBLIC LAND
TRAM-LOG RD-O&C,CBRLANDS
ROW-LOG RD PMT O&C,CBWR
ROW-TRAM-LOG O&C RECNV
ROW-LOG RD RWA O&C,CBWR
ROW-COST SHARE RD FLPMA
ROW-COOP AGRMT ROADS
ROW-FS FED AID HWYSEC317
ROW-ROADS UNDER RS 2477
ROW-WIND SITE TEST
ROW-WIND PROJ TEST
ROW-WIND DEV FAC
ROW-SOLAR DEV FAC
ROW-RR,STA GROUND
ROW-RR, FACILITY, ACQ
ROW-RR SPECIAL ACTS
ROW-RR 44LD513
UNAUTH ACTIVITY-ROW-RR
ROW-RR RECONVEYED
TO BE DEFINED
ROW-RR,RD & TRAMWAYS AK
RR & STATIONS OUTSIDE AK
ROW-PWR FACILITIES
ROW-POWER TRAN LINE
ROW-POWER TRAN-FLPMA
ROW-POWER TRANS-IRR PROJ
ROW-POWER TRAN-ACQ
ROW-PWR FACILITY & TRANS
ROW-PWR LINE FED FAC
ROW-PWR LINE 44LD513
UNAUTH ACT-ROW PWR LINE
ROW-PWR LINE RECONVEYED
ROW-RECLAMATION PROJECT
ROW-BOULDER CAN PROJ
ROW-COMM SITE, FLPMA
EASEMENTS/ROW
3/8/2010
Attachment 2-30
OR/WA State Data Dictionary
286003
286005
286007
286008
286009
286011
286100
286200
286202
286203
286205
286207
286208
286209
286211
287001
287003
287007
287008
287009
287011
287100
287101
287111
287200
287300
287400
287500
288001
288004
288005
288009
288011
288100
288101
288102
288103
288104
288105
288106
288111
288150
288151
Bureau of Land Management
ROW-COMM SITE,ACQ
ROW-COMM SITE, 1911
ROW-COMM SITE FED FAC
ROW-COMM SITE 44LD513
UNAUTH ACT-ROW-COMM SITE
ROW-COMM SITE RECONVEYED
ROW-RADIO & TV SITES
ROW-TELEPHONE-TELEGRAPH 43USC959
ROW-TELEPHONE-TELEGRAPH 43USC961
ROW-TEL & TELEG,FLPMA
ROW-TEL & TELEG, ACQ
ROW-TEL & TELEG FED FAC
ROW-TEL & TELEG 44LD513
UNAUTH ACT-ROW-TEL&TELEG
ROW- TELE & TELEG RECNV
ROW-WATER FACILITY
ROW-WATER FAC, ACQ
ROW-WATER FACILITY FED
ROW-WATER FAC44LD513
UNAUTH ACT-ROW-WATER FAC
ROW-WATER FAC RECONVEYED
ROW-IRRIGATION FAC
ROW-IRRIGATION DIST
ROW-IRRIGATION FAC RECNV
ROW-LIVESTOCK WATER FAC
ROW-WATER PLANTS
D/C EXIST PRIOR TO FLPMA
D/C EXERCISE OF RIGHT
ROW-PIPELINE-OTHER
ROW-TRANS SOLID
ROW-PIPELINE, ACQ
UNAUTH USE PIPELINE/FAC
ROW-MIN LSE PURPOS RECNV
ROW-O&G PIPELINES
ROW-O&G FACILITY SITES
UNAUTH ACT-O&G PPLN/FAC
ROW-SALT WTR DISP-MLA
ROW-SALT WTR DISP-FLPMA
UNAUTH ROW-SALT WTR DISP
ROW-O&G TEMP USE PERMITS
ROW-O&G PPLN/FAC RECNV
ROW-AK GAS PIPELINE
AK GAS PIPELINE TUP
EASEMENTS/ROW
3/8/2010
Attachment 2-31
OR/WA State Data Dictionary
288401
289001
289003
289004
289007
289008
289009
289011
289100
289101
289102
289103
289104
289105
289106
289107
289111
289150
289160
289200
Bureau of Land Management
ROW-NPR-A
ROW-OTHER-FLPMA
ROW-MISC-IRR PROJECT
ROW-MISC & SPECIAL
ROW-OTHER FEDERAL FAC
ROW-OTHER FED 44LD513
UNAUTH ACT -ROW-OTHER
ROW-OTHER RECONVEYED
ROW-FOREST LAND
ROW-FS EASEMENT GRANT
ROW-FS CONSTR RDS-TRAILS
ROW-FS 16USC5571C,580D
ROW-FS 16USC528-531
ROW-FS SPEC USE PERMITS
ROW-FS FLPMA EASEMENT
ROW-FS OTHER FED AGENCY
ROW-FS RECONVEYED
ROW-ISSUED BY MIL DEPT
ROW-ISSUED BY AEC
ROW-ACQ LAND-REAL PROP
DOMAIN: ESMTROW_FTR
CODE
ROAD
PIPELINE
TRAIL
PARCEL
FENCE
WINDTOWER
POWERLINE
TELEPHONE
TELE_BURIED
ADMIN_SITE
WATER_GAP
GEOSURVEY
STAGING
EASEMENTS/ROW
DESCRIPTION
ROAD
PIPELINE
TRAIL
PARCEL
FENCE
WINDTOWER
POWERLINE
TELEPHONE
TELEPHONE BURIED
ADMINISTRATIVE SITE
WATER_GAP
GEOSURVEY
STAGING
3/8/2010
Attachment 2-32
OR/WA State Data Dictionary
Bureau of Land Management
DOMAIN: ESMTROW_TP
CODE
ESMT
ROW
CONSR_ESMT
OTHER
DESCRIPTION
EASEMENT
RIGHT-OF-WAY
CONSERVATION EASEMENT
OTHER
DOMAIN: JURISCODE
CODE
BL
BP
BR
CE
CG
DA
DD
FS
FA
FC
FW
GS
GSA
IA
LG
NP
PV
PVI
PVN
PVU
ST
STF
STL
SDT
STP
STW
UN
DESCRIPTION
BUREAU OF LAND MANAGEMENT
BONNEVILLE POWER ADMINISTRATION
BUREAU OF RECLAMATION
CORPS OF ENGINEERS
U.S. COAST GUARD
U.S. DEPT. OF AGRICULTURE (EXCEPT THE FOREST SERVICE)
U.S. DEPT. OF DEFENSE (EXCEPT THE CORPS OF ENGINEERS)
U.S. FOREST SERVICE
FEDERAL AVIATION ADMINISTRATION
FEDERAL ENERGY REGULATORY COMMISSION
U.S. FISH AND WILDLIFE SERVICE
U.S. GEOLOGICAL SURVEY
GENERAL SERVICES ADMINISTRATION
BUREAU OF INDIAN AFFAIRS AND TRIBAL UNITS
LOCAL GOVERNMENT
NATIONAL PARK SERVICE
PRIVATE LANDS
PRIVATE, INDUSTRIAL
PRIVATE, NONINDUSTRIAL
PRIVATE, URBAN
STATE MANAGED LANDS
STATE FORESTS
STATE DIVISION OF LANDS
STATE TRANSPORTATON DEPARTMENT
STATE PARKS
STATE WILDLIFE REFUGES
UNDETERMINED
DOMAIN: STATUS_P
CODE
Initial
Active
Suspended
Rejected
Relinquished
EASEMENTS/ROW
DESCRIPTION
Initial
Active
Suspended
Rejected
Relinquished
3/8/2010
Attachment 2-33
OR/WA 00257
Department of the Interior
Privacy Impact Assessment
Name of Project: Easements and Rights of Way Spatial Data
Bureau: Bureau of Land Management, Oregon/Washington
Project's Unique ID: ESMTROW
A. CONTACT INFORMATION:
1) Who is the person completing this document? Stanley Frazier, ORlWA State Data Administrator, ORIWA Division of Management Services, Branch of Information Resources Management, (503) 808-6009. 2) Who is the system owner? ORlWA Deputy State Director, Division of Resource Planning, Use and Protection, (503) 808-6056 3) Who is the system manager for this system or application? Cathie Jensen, ESMTROW Data Steward, ORlWA Division Resource Planning, Use and Protection, Branch of Lands and Mineral Resources, (503) 808-6310. 4) Who is the IT Security Manager who reviewed this document? Cynthia Yee, ORlWA Division of Management Services, Branch of Information Resources Management, (503) 808-6117. 5) Who is the Bureau/Office Privacy Act Officer who reviewed this document? Sherrie L. Reid, ORlWA Division of Management Services, Branch of Information Resources Management, (503) 808-6677. 6) Who is the Reviewing Official? Lloyd Gilham, Chief Information Officer, ORlWA Division of Management Services, Branch of Information Resources Management, (503) 808-6063. B. SYSTEM APPLICATION/GENERAL INFORMATION:
1)Does this system contain any information about individuals? Yes
a. Is this information identifiable to the individual 1? Yes
b. Is the information about individual members of the public? Yes
c. Is the information about employees? No
Attachment 3 -1
2) What is the purpose of the system/application? To display Easements and
Rights of Way either authorized by the Bureau of Land Management (BLM) or
acquired by the BLM. These are then used in various analytical processes to
support land management decisions. This is a spatial data set that is part of the
ORlWA GIS system and can be combined with a variety of other information
(such as ownership, Sagegrouse habitat, transportation networks, etc.) to answer
or analyze a variety of resource management questions.
3)What legal authority authorizes the purchase or development of this
system/application? Federal Land Policy and Management Act (FLPMA) of
1976. Section 201 directs the Secretary of the Interior to prepare and maintain
on a continuing basis an inventory of all public lands and the resource values.
c. DATA in the SYSTEM:
1) What categories of individuals are covered in the system? Those
individuals and companies that have applied for, or have received, a right of
way on public land. Also includes individuals and companies that have
granted to the BLM a similar right for the agency to use their land (usually an
easement).
2) What are the sources of the information in the system?
a. Is the source of the information from the individual or is it taken from
another source? If not directly from the individual, then what other
source? The information comes from information contained in the
Legacy Rehost 2000 (LR2000) database which tracks case authorizations.
This information was provided by the individual during the Right of Way
or Easement acquisition process.
b. What Federal agencies are providing data for use in the system?
Bureau of Land Management
c. What Tribal, State and local agencies are providing data for use in the
system? None
d. From what other third party sources will data be collected? None
e. What information will be collected from the employee and the public?
The name of the organization or individual that is being granted a Right of
Way to use public land or the name of the organization or individual that
is granting an Easement to the BLM for either administrative or public
access across privately owned land. The serialized case file number is
also recorded which can provide access to the information contained
within LR2000.
Attachment 3 -2
3) Accuracy, Timeliness, and Reliability
a. How will data collected from sources other than DOl records be
verified for accuracy? It will be compared to the data in LR2000 and
case files for accuracy.
b. How will data be checked for completeness? It will be compared to the
data in LR2000 and case files for completeness. At least annually a
comparison will be made of the number of easement and right of way
cases in LR2000 to the number of cases in this spatial data set as a
measure of completeness. It is unlikely that the spatial dataset will ever be
100% complete.
c. Is the data current? What steps or procedures are taken to ensure the
data is current and not out-of-date? Comparisons to LR2000 and case
files will be the primary quality check process. A review of the data
contained in the dataset will be conducted on an annual basis.
d. Are the data elements described in detail and documented? If yes,
what is the name of the document? Yes, Easement/Rights of Way
Spatial Data Standard. This standard will be issued by an Instruction
Memorandum from the Oregon/Washington State Director.
D. ATTRIBUTES OF THE DATA:
1) Is the use of the data both relevant and necessary to the purpose for
which the system is being designed? Yes
2) Will the system derive new data or create previously unavailable data
about an individual through aggregation from the information collected,
and how will this be maintained and filed? No.
3) Will the new data be placed in the individual's record? No, there will be
no new data created.
4) Can the system make determinations about employees/public that would
not be possible without the new data? No
5) How will the new data be verified for relevance and accuracy? No new
data will be created.
6) If the data is being consolidated, what controls are in place to protect the
data from unauthorized access or use? The data is not being consolidated.
Attachment 3 -3
7) If processes are being consolidated, are the proper controls remaining in
place to protect the data and prevent unauthorized access? Explain.
No processes are being consolidated.
8) How will the data be retrieved? Does a personal identifier retrieve the
data? If yes, explain and list the identifiers that will be used to retrieve
information on the individual. It would not be normal practice to retrieve
information by individual name however the dataset is designed in a way that
would make it possible to do so. The attribute RGT~HOLDER contains the
name of the company or person that is granted a right of way while
GRANTOR contains the name of the company or person granting an
easement to the BLM. In addition, the attribute CASEFILE contains the case
number assigned to the particular easement or right of way by the LR2000
database which could be used to find additional information (submitted as part
of the Easement/Right of Way application process).
9) What kinds of reports can be produced on individuals? What will be the
use of these reports? Who will have access to them? Reports showing
what Rights of Way are held by an individual or Easements that have been
granted to BLM by an individual, could be generated. This same information
can also be retrieved from LR2000. However, the ability to capture the data
in a GIS format would allow the number of miles of a right-of-way or
easement controlled by a specific landowner to be calculated when
determining land ownership and rental payments due the United States.
10) What opportunities do individuals have to decline to provide
information (i.e., where providing information is voluntary) or to consent
to particular uses of the information (other than required or authorized
uses), and how individuals can grant consent.) None - in order to apply for
a right of way or to grant an easement the individual would be required to
supply their name.
E. MAINTENANCE AND ADMINISTRATIVE CONTROLS:
1) If the system is operated in more than one site, how will consistent use of
the system and data be maintained in all sites? This is a corporate data set
that is operated out of the centralized GIS database. Controls on who has edit
rights to the data will be enforced by the centralized database. Metadata will
clearly state any restrictions on distribution outside of the BLM.
2) What are the retention periods of data in this system? TEMPORARY.
3) What are the procedures for disposition of the data at the end of the
retention period? How long will the reports produced be kept? Where
are the procedures documented? GRS BLM 20/5 Temporary. Delete when
Attachment 3 -4
no longer needed for administrative, legal, audit, or other operational
purposes.
4) Is the system using technologies in ways that the DOl has not previously
employed (e.g., monitoring software, Smart Cards, Caller-ID)? No
5) How does the use of this technology affect public/employee privacy?
None. The names of the public that are applying for a right-of-way or are
granting an easement to the BLM are already documented in the LR2000
database. Use of this dataset would make it easier to find a name but any
other information about that person would remain in LR2000.
6) Will this system provide the capability to identify, locate, and monitor
individuals? If yes, explain. The data in the spatial layer could be used to
search for an individual by name but it would only identify that the person had
applied for and/or received a right of way to use public land or had granted
similar rights to the BLM over their private land. The data could not be used
to physically identify, locate or monitor individuals.
7) What kinds of information are collected as a function of the monitoring of
individuals? Individuals are not monitored by this dataset.
8) What controls will be used to prevent unauthorized monitoring? No
monitoring is performed.
9) Under which Privacy Act systems of records notice does the system operate? Provide number and name. LLM-32 Land and Minerals Authorization Tracking System. 10) If the system is being modified, will the Privacy Act system of records
notice require amendment or revision? Explain. No, this system works in
conjunction with LR-2000 which is covered under LLM-32.
F. ACCESS TO DATA:
1) Who will have access to the data in the system ? (e.g., contractors, users,
managers, system administrators, developers, tribes, other) BLM users of
the data would access the information through the corporate GIS system. The
data would also be made publicly available via the ORlWA BLM GIS Data
download page and possibly through Geospatial One-Stop (geodata.gov) or
Data.gov.
2) How is access to the data by a user determined? Are criteria, procedures,
controls, and responsibilities regarding access documented? All users are
allowed read access. Only designated and trained editors have access to edit
the data.
Attachment 3 -5
3) Will users have access to all data on the system or will the user's access be
restricted? Explain. Access to all data.
4) What controls are in place to prevent the misuse (e.g., unauthorized
browsing) of data by those having access? (Please list processes and
training materials) No restrictions on browsing the data (read-only). Only
registered and trained editors have the capability to alter data contained in the
dataset.
5) Are contractors involved with the design and development of the system
and will they be involved with the maintenance of the system? If yes,
were Privacy Act contract clauses inserted in their contracts and other
regulatory measures addressed? No contractors have or will be involved in
the development of this data set.
6) Do other systems share data or have access to the data in the system? If
yes, explain. The name of the RGT_HOLDER, GRANTOR and the
CASEFILE number are also contained in the LR2000 database.
7) Who will be responsible for protecting the privacy rights of the public
and employees affected by the interface? The data steward/system
manager.
8) Will other agencies share data or have access to the data in this system
(Federal, State, Local, Other (e.g., Tribal)? Yes, anyone would be able to
download and use the data from our public data download site.
9) How will the data be used by the other agency? It is not known how other
agencies might use this data but it would likely be for the same purposes that
the BLM uses the data (to answer resource management questions) or provide
input to resource management decision making processes.
10) Who is responsible for assuring proper use of the data? The data
steward/system manager.
Attachment 3 -6
The Following Officials Have Approved this Document
1) System Manager
:</Ji/;;O/tJ
_~--,,-,---,-"--:i1'~=--=---...::c-=----(Signature)
t7
I
I
(Date)
Cathie Jensen
Data Steward/System Manager
2) IT Security Manager
_ _ _ _ _ _ _---;/-_ _ _ _ (Signature)
--I------i!:...----­
Cynthia Yee OR/WA IT Security Manager 3) Privacy Act Officer
(Signature)
.2i f!L/10 La
i
J '-"
(Date)
Sherrie L. Reid OR/WA Chief, Records Section (Privacy) n#n
g
Official
(J~,,--.~I'--~----- (Signature) -U(c:t II
(Date)
Lloyd Gilham OR/WA Chief Information Officer Attachment 3 -7