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/9160 (OR955/OR957) P
February 11, 2011
EMS TRANSMISSION 02/15/2011
Instruction Memorandum No. OR-2011-023
Expires: 9/30/2012
To:
DMs, DSDs, Staff, and Branch Chiefs
From:
State Director, Oregon/Washington
Subject:
Ocean Spatial Data Standard
Program Area: Geographic Sciences.
Purpose: This instruction memorandum (IM) reissues the established spatial data standard for
Ocean (see attachment) previously under the OR IM-2008-051 dated March 5, 2008. Only
minor editing and formatting changes were made.
Policy/Action: This data standard is to be followed for all Ocean geospatial data. The data
should be reviewed by all field offices, and any needed corrections and/or additions that are
needed should be made through established editing procedures.
Timeframe: This data standard is effective immediately.
Budget Impact: None.
Background: All offices have a need for accurate and up-to-date spatial data for Oceans. In
order for that to happen, the data needs to be standardized so it can be made available in the
corporate edit environment. This data standard should be used in conjunction with the data
standard for Resource Area Boundaries as Oceans form the westernmost land edge of
Oregon/Washington.
Manual/Handbook Sections Affected: None.
Coordination: The State Data Steward reviewed the data standard and found no need for
changes.
2
Contact: If you have any questions, please contact Corey Plank, State Data Steward, at
503-808-6145; Pamela Keller, Geographical Information System 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 IM and satisfy any bargaining
obligations before implementation. Your servicing Human Resources Office or Labor Relations
Specialist can provide you with assistance in this matter.
Signed by
Michael S. Mottice
Associate State Director
Attachment
Ocean Spatial Data Standard (20 pp)
Distribution
OC530 (Chatfield)
WO500
Authenticated by
Rita Wallberg
Records Section
State Data Dictionary
Bureau of Land Management
February 01, 2011
Ocean
02/01/2011
Attachment 1- 1
State Data Dictionary
Bureau of Land Management
TABLE OF CONTENTS
SECTION
PAGE
NUMBER
General Information
Responsibilities
FOIA Category
Records Retention Schedule
Security/Access/Sensitivity
Data Set Description
Use
Sponsor/Affected Parties
Data Category/Architecture Link
Data Organization/Structure
Relationship to the Department of the Interior
Enterprise Architecture – Data Resource Model
OCEAN Data Organization Graphic
Data Management Protocols
Accuracy Requirements
Collection and Input Protocols
Maintenance Protocols
Update Transactions
Update Frequency
Statewide Monitoring
OCEAN Geodatabase Schema
Projection and Spatial Extent
Spatial Entity Characteristics
Attribute Characteristics and Definitions
Associated Files or Databases
Layer Files (Publication Views)
Edit Guide
Oregon Data Framework Overview
Abbreviations and Acronyms Used
Ocean
02/01/2011
3
3
3
3
3
4
4
4
4
4
5
6
7
7
7
7
7
7
7
8
9
9
10
13
13
14
15
16
Attachment 1- 2
State Data Dictionary
Bureau of Land Management
GENERAL INFORMATION
Data Set Name
Data Set Abbreviation
Ocean
OCEAN
RESPONSIBILITIES
State Data Steward - The State Data Steward (Corey Plank) 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, Geographical 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 (Pam Keller) 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 (Stan Frazier) 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 (Sherrie Reid) 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 (FOIA) category.
FOIA CATEGORY
Public
RECORDS RETENTION SCHEDULE
BLM GRS 20/52c. PERMANENT. Cutoff end of the fiscal year (EOFY) in which the layer/data is created or significantly altered by the BLM. Transfer copy of data to National Archives and Records Administration (NARA)
at the EOFY.
SECURITY/ACCESS/SENSITIVITY
The Ocean 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.
Ocean
02/01/2011
Attachment 1- 3
State Data Dictionary
Bureau of Land Management
DATA SET OVERVIEW
DESCRIPTION
The OCEAN data standard contains requirements for the GIS representation of the Pacific Ocean, its coastline with
OR/WA (land/ocean interface) and near-shore islands. The polygon representing the ocean is squared off at an
arbitrary distance in the ocean. At some time in the future the coastline and islands may be included in a broader
hydrography theme or themes. In particular, the National Hydrography Data and the Watershed Boundaries
datasets have shoreline components. As those datasets mature they should become the source for the coastline data.
The OCEAN data set may not be needed when that occurs and will be archived if that is the case.
USAGE
The OCEAN feature classes are used for display on maps and for GIS analysis. A known use for the coastline arcs
will be to create a “land only” Resource Area Boundary (described in a separate data standard) for the westernmost
districts of OR/WA BLM. This boundary may be used in a wide range of applications including Resource
Management Plans. In addition, the ocean islands or a selection of them may be used for analysis and planning.
Some have BLM surface jurisdiction and many provide special wildlife habitat. Coastline arcs may also be used to
delineate Hydrologic Unit (watershed) boundaries (HU).
SPONSOR/AFFECTED PARTIES
The sponsor for this data set is the Deputy State Director, Management Services. Since the coastline and islands
fall into the broader hydrography data group, affected parties include the United States Fish and Wildlife Service,
US Geological Survey, and US Forest Service, as well as State agencies for OR/WA with responsibilities for water
resources. It is expected that OR/WA BLM will coordinate with these agencies and use the accepted interagency
standards where they exist.
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 ODF showing the
overall organization and entity inheritance. The Resource Area Boundary (RAB) entities are highlighted. It should
be noted that, in general, datasets falling in Resources category do not require a polygon/line pair (where the line
provides boundary segment definitions which are critical for datasets in the Boundaries category. For additional
information and a link to the entire ODF, contact:
OR/WA State Data Administrator
Stan Frazier
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
Ocean
02/01/2011
Attachment 1- 4
State Data Dictionary
Bureau of Land Management
OCEAN DATA ORGANIZATION / STRUCTURE
For OCEAN, the categories/groups that the data set is part of are:
BLM OCEAN POLYGONS:
Oregon Data Framework
Resources
Water
Ocean
OCEAN_POLY
BLM OCEAN LINE:
Oregon Data Framework
Resources
Water
Ocean
OCEAN_ARC
RELATIONSHIP TO THE DEPT. 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: Natural and Cultural Resource
Information Class: Water Resource
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
Ocean
02/01/2011
Attachment 1- 5
State Data Dictionary
Ocean
Bureau of Land Management
02/01/2011
Attachment 1- 6
State Data Dictionary
Bureau of Land Management
DATA MANAGEMENT PROTOCOLS
Accuracy Requirements: The coastline arcs represent the mean high tide of the ocean. At a minimum, this data is
to meet national map accuracy requirements at 1:24,000 scale (the accuracy of the paper source). Island minimum
size is approximately 60 feet along the shortest axis.
Collection and Input Protocols: The best GIS data from all available sources was combined to create an initial
shoreline dataset. The definition used for coastline includes jetties with a closure line from endpoint to endpoint.
The coastline will be coincident with hydrologic unit boundaries from the National Hydrologic Dataset once those
are rectified. Future updates will take place as feature representations are refined to higher accuracy.
Maintenance Protocols: Once the theme has been created, it is the responsibility of the State Data Steward to
ensure that the theme remains current. It is the responsibility of District Data Stewards and GIS Coordinators to
keep the State Data Steward apprised of improvements to the GIS source data and to assist with updates. Proposed
changes will be provided to the State Data Steward who will coordinate with the appropriate interagency data
steward(s) for approval of the change. Changes may also originate from outside of OR/WA BLM and it is the
responsibility of the State Data Steward to oversee these changes. Finally, it is the responsibility of the State Data
Steward to notify District Data Stewards and GIS Coordinators when there is an update.
Update Transactions: The unit of processing for updating the OCEAN theme is the State. Editors at the State
Office will initiate transactions by "checking-out" the OCEAN theme features. They will then add, delete or
modify the features prior to "check-in".
Update Frequency: Updates to OCEAN should be very infrequent because there is no on-going data collection effort related to coastline or island perimeters. Changes are discouraged because of the need for interagency approval and the
significant impact on planning boundaries. It is also the responsibility of the Data Steward to ensure that any database external to the Corporate GIS remains
current. There are no known databases associated with OCEAN, but if the coastline was used in a planning area
boundary and the coastline arcs are modified, a plan amendment may be required to document a change in acres.
Statewide Monitoring: The State Data Steward in conjunction with the Lead GIS Specialist and District Data
Stewards are responsible for reviewing the OCEAN theme across the state at least once per year. An interagency
review is preferred. Coincidence of OCEAN arcs with dependent themes (see Spatial Entity Characteristics
section) is also checked.
Ocean
02/01/2011
Attachment 1- 7
State Data Dictionary
Bureau of Land Management
OCEAN 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
OCEAN DATASET
OCEAN_POLY (Ocean Polygons)
Attribute Name
Data Type
ISLAND_NAME
String
VERSION_NAME String
OCEAN_ARC (Ocean Lines)
Attribute Name
Data Type
COORD_SRC
String
SOURCE_LYR
String
ACCURACY_FT Short Integer
ORGANIZATION String
VERSION_NAME String
Length
50
50
Default Value
Req?
InitialLoad
Yes*
Length
7
15
Default Value
Req?
Yes
Yes
InitialLoad
Yes*
15
50
Domain
Domain
dom_COORD_SRC
dom_ORGANIZATION
*Values automatically generated
Ocean
02/01/2011
Attachment 1- 8
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) is the coastline for OR/WA extending into British Columbia and California and an arbitrary distance
well past the 3 mile coastal waters boundary. See the metadata for this data set for more precise description of the
extent.
SPATIAL ENTITY CHARACTERISTCS
OCEAN POLYGON (OCEAN_POLY)
Description: Instance of Resources Water Ocean group.
Geometry: Polygons that form a continuous “wall-to-wall” cover with no gaps or overlaps.
Topology: Yes. OCEAN_POLY lines are coincident with OCEAN_ARC lines and together make the feature
dataset, OCEAN.
Integration Requirements: Polygon features are used with Resource Area and District boundaries to create
publication layers.
OCEAN LINE (OCEAN_ARC)
Description: Instance of Resources Water Ocean group.
Geometry: Simple, non-overlapping lines that are split between endpoints as needed.
Topology: Yes. OCEAN_POLY lines are coincident with OCEAN_ARC lines and together make the feature
dataset, OCEAN.
Integration Requirements: Arcs must remain coincident with other GIS themes as indicated by COORD_SRC (for
example with HU when COORD_SRC is SOURCEL and SOURCE_LYR is HU) and with Boundary group themes that have arc segments defined by ocean coastline or islands.
Ocean
02/01/2011
Attachment 1- 9
State Data Dictionary
Bureau of Land Management
ATTRIBUTE CHARACTERISTICS AND DEFINTIONS
ACCURACY_FT
Geodatabase Name
BLM Structured Name
Comment
ACCURACY_FT
Accuracy_Feet_Measure
Inherited from Entity POLITICAL ADMIN SMA LINE
Used in Feature Classes:
Domain
Data Type
Length
Precision
<None>
Short integer
Description
[Optional]
How close, in feet, the spatial GIS depiction is to the actual location on the ground. There are several factors to
consider in GIS error: scale and accuracy of map-based sources, accuracy of Global Positioning System (GPS)
equipment, and the skill level of the data manipulators. A value of „0‟ indicates no entry was made. This is the
correct value when the COORD_SRC is another GIS theme (Digital Line Graphs (DLG), Geographic Coordinate
Database (GCD), Digital Elevation Model (DEM)) because the accuracy is determined by that theme. If
COORD_SRC is MAP or GPS, however, 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.
_____________________________________________________________________________________________
COORD_SRC
Geodatabase Name
BLM Structured Name
Comment
COORD_SRC
Coordinate_Source_Code
Inherited from Entity POLITICAL ADMIN SMA LINE
Used in Feature Classes:
Domain
Data Type
Length
Precision
dom_COORD_SRC
Characters (3)
3
Description
[Required]
The actual source of the GIS coordinates for the line segments.
Examples: CFF, DEM, DLG, GCD, MAP, SOURCEL
_____________________________________________________________________________________________
Ocean
02/01/2011
Attachment 1- 10
State Data Dictionary
ISLAND_NAME
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Length
Precision
Bureau of Land Management
ISLAND_NAME
Island_Name
Not Inherited
Used in Feature Classes:
OCEAN_POLY
<None>
Variable characters (50)
50
Description
[Optional]
The official name of the island as listed in the U.S. Geographic Names Information System or the British Columbia
GNIS. If the island is not named, fill with <null> and if the polygon represents the ocean fill with “Pacific Ocean”.
Examples: “Bowen Island”, “Tunnel Island”
_____________________________________________________________________________________________
ORGANIZATION
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Length
Precision
ORGANIZATION
Organization_Code
Not Inherited
Used in Feature Classes:
OCEAN_ARC
dom_ORGANIZATION
Variable characters (15)
15
Description
[Optional]
The name of the organization that supplied the spatial feature.
Examples: ST_WA_DNR (State of Washington Dept. of Natural Resources); NOAA (National Oceanic and Atmospheric Administration); BLM_OR_OSO (Oregon State Office BLM).
_____________________________________________________________________________________________
Ocean
02/01/2011
Attachment 1- 11
State Data Dictionary
SOURCE_LYR
Geodatabase Name
BLM Structured Name
Notes
Domain
Data Type
Length
Precision
Bureau of Land Management
SOURCE_LYR
Source_Layer_Name
Not Inherited
Used in Feature Classes:
OCEAN_ARC
<None>
Variable characters (15)
15
Description
[Required - if applicable]
The name of the feature class from which features are duplicated. Required if COORD_ SRC is SOURCEL. Otherwise field is blank.
_____________________________________________________________________________________________
VERSION_NAME
Geodatabase Name
BLM Structured Name
Comment
VERSION_NAME
Geodatabase_Version_Text
Inherited from Entity Oregon Data Model.
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 Classes:
Domain
Data Type
Length
Precision
<None>
Variable characters (50)
50
Description
[Required]
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 last edit (hours might be a single digit; leading zeros are trimmed for hours only). XXX=theme abbreviation.
Ocean
02/01/2011
Attachment 1- 12
State Data Dictionary
Bureau of Land Management
ASSOCIATED FILES OR DATABASES
None
LAYER FILES (PUBLICATION VIEWS)
Layer files will be created through scripts that can be automatically executed. Layer files do not require storage and
maintenance of additional data and can be deleted and recreated at any time.
The ocean polygons can be intersected with District and RAB to create those portions occurring on land only.
Please see the data standard for RAB for details on the layer files and publication feature classes that OCEAN is a
component.
Ocean
02/01/2011
Attachment 1- 13
State Data Dictionary
Bureau of Land Management
EDITING PROCEDURES (TO BE ADDED LATER)
Cluster Tolerance
Topology Rules
Allowed Exceptions
Reference Themes and Tables
Editing Symbology
Editing Workflow
Snapping Guidelines
Ranks
Tolerances
"Do's and Don'ts"
QC Checklist
Ocean
02/01/2011
Attachment 1- 14
State Data Dictionary
Bureau of Land Management
OREGON DATA FRAMEWORK OVERVIEW (OCEAN HIGHLIGHTED)
Ocean
02/01/2011
Attachment 1- 15
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
DEM
DLG
DOB
FOIA
GCD
GIS
HU
IDP
NAD
NARA
ODF
OR/WA
RA
RMP
SDE
SMA
USFS
USGS
Ocean
Bureau of Land Management
Digital Elevation Model
Digital Line Graphs
BLM District Office Boundary
Freedom of Information Act
Geographic Coordinate Database
Geographic Information System
Hydrologic Unit
Interdisciplinary
North American Datum
National Archives and Records Administration
Oregon Data Framework
Oregon /Washington
Resource Area
Resource Management Plan
Spatial Data Engine
Special Management Areas
United States Forest Service
United States Geological Survey
02/01/2011
Attachment 1- 16
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
Stan Frazier
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
DOMAIN: COORD_SRC (choices relevant to OCEAN are highlighted)
CODE
CFF
DESCRIPTION
Lines duplicated or buffered from Cartographic Feature Files (USFS)
DEM
Digital Elevation Model (30 m or better accuracy) used for creation of contours
DIS
DLG
Lines generated to connect discontinuous features
-Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs
DOQ
DRG
GCD
GPS
Screen digitized linework over Digital Orthoquad backdrop
Screen digitized linework over Digital Raster Graphic backdrop
Lines snapped to Geographic Coordinate Database Points
Lines obtained from a Global Positioning System device
IMG
Linework derived from interpretation of satellite or other non-photographic imagery
MAP
SOURCEL
Digitized linework from hardcopy map
Source Layer from BLM GIS.
SRV
TIGER
TRS
UNK
Survey methods were used to create the linework (e.g. COGO)
Tiger Data
Coordinates only given as a legal description (township, range, section)
Unknown coordinate source
WOD
WODDB Photogrammetric
Ocean
02/01/2011
Attachment 1- 17
State Data Dictionary
Bureau of Land Management
DOMAIN: ORGANIZATION
CODE
DESCRIPTION
BLM_ID_ISO
BLM_OR_BNS
BLM_OR_BNS_ADR
BLM_OR_BNS_THR
BLM_OR_CBY
BLM_OR_CBY_MRW
BLM_OR_CBY_UMR
BLM_OR_EUG
BLM_OR_EUG_SIU
BLM_OR_EUG_UPW
BLM_OR_LAK
BLM_OR_LAK_KLF
BLM_OR_LAK_LAK
BLM_OR_MED
BLM_OR_MED_ASH
BLM_OR_MED_BTF
BLM_OR_MED_GLD
BLM_OR_MED_GTP
BLM_OR_OSO
BLM_OR_PRI
BLM_OR_PRI_CNO
BLM_OR_PRI_DCH
BLM_OR_RSB
BLM_OR_RSB_SOR
BLM_OR_RSB_SWR
BLM_OR_SLM
BLM_OR_SLM_CAS
BLM_OR_SLM_MPK
BLM_OR_SLM_TLM
BLM_OR_SPO
BLM_OR_SPO_BRD
BLM_OR_SPO_WEN
BLM_OR_VAL
BLM_OR_VAL_BKR
BLM_OR_VAL_JOR
BLM_OR_VAL_NML
BLM_ST
Idaho State Office, BLM
Burns District, BLM
Andrews Resource Area, BLM
Three Rivers Resource Area, BLM
Coos Bay District, BLM
Myrtlewood Resource Area, BLM
Umpqua Resource Area, BLM
Eugene District, BLM
Siuslaw Resource Area, BLM
Upper Willamette Resource Area, BLM
Lakeview District, BLM
Klamath Falls Resource Area, BLM
Lakeview Resource Area, BLM
Medford District, BLM
Ashland Resource Area, BLM
Butte Falls Resource Area, BLM
Glendale Resource Area, BLM
Grants Pass Resource Area, BLM
Oregon State Office, BLM
Prineville District, BLM
Central Oregon Resource Area, BLM
Deschutes Resource Area, BLM
Roseburg District, BLM
South River Resource Area, BLM
Swiftwater Resource Area, BLM
Salem District, BLM
Cascades Resource Area, BLM
Mary&#39;s Peak Resource Area, BLM
Tillamook Resource Area, BLM
Spokane District, BLM
Border Resource Area, BLM
Wenatchee Resource Area, BLM
Vale District, BLM
Baker Resource Area, BLM
Jordan Resource Area, BLM
Malheur Resource Area, BLM
National Science and Technology Center, BLM
Ocean
02/01/2011
Attachment 1- 18
State Data Dictionary
BLM_WO
BOC
BOR
CI_OR
CI_OR_ONT
CT_OR
CT_WA
FS_GSC
FS_PNW_COL
FS_PNW_CRG
FS_PNW_DES
FS_PNW_FRM
FS_PNW_GPN
FS_PNW_ICB
FS_PNW_MAL
FS_PNW_MBS
FS_PNW_MTH
FS_PNW_MTH_ZZAG
FS_PNW_OCH
FS_PNW_OKA
FS_PNW_OLY
FS_PNW_RO
FS_PNW_ROG
FS_PNW_RSC
FS_PNW_SIS
FS_PNW_SIU
FS_PNW_UMA
FS_PNW_UMP
FS_PNW_WAW
FS_PNW_WEN
FS_PNW_WIL
FS_PNW_WIN
FS_PSW_KLA
FS_PSW_MOD
FWS
GS
GS_EROS
GS_GNIS
GS_WAT
IBC
MMS
Ocean
Bureau of Land Management
Washington Office, BLM
Bureau of the Census
Bureau of Reclamation
City Government, OR
City of Ontario, OR
County Government, OR
County Government, WA
Forest Service-Geometronics Service Center
Colville National Forest
Columbia River Gorge National Scenic Area, FS
Deschutes National Forest
Fremont National Forest
Gifford Pinchot National Forest
Interior Columbia Basin Ecosystem Management Project, FS
Malheur National Forest
Mt. Baker-Snoqualmie National Forest
Mt. Hood National Forest
Zig Zag Ranger District, FS
Ochoco National Forest
Okanogan National Forest
Olympic National Forest
Pacific Northwest Regional Office, FS
Rogue River National Forest
Pacific Northwest Research Station, FS
Siskiyou National Forest
Siuslaw National Forest
Umatilla National Forest
Umpqua National Forest
Wallowa-Whitman National Forest
Wenatchee National Forest
Willamette National Forest
Winema National Forest
Klamath National Forest
Modoc National Forest
U.S. Fish and Wildlife Service
U.S. Geologic Survey
EROS Data Center, U.S. Geologic Survey
GNIS, U.S. Geologic Survey
Water Resources, U.S. Geologic Survey
International Boundary Commission
Minerals Management Service
02/01/2011
Attachment 1- 19
State Data Dictionary
NAT
NGS
NOAA
NPS
NRCS
OT_REO
OT_UNKNOWN
PV_EOSAT
PV_ESRI
PV_TITAN
PV_TNC
PV_WEYERHAEUSER
ST_ID_WAT
ST_OR_DOGAMI
ST_OR_ODF
ST_OR_ODFW
ST_OR_ODOT
ST_OR_ODSL
ST_OR_OGIS
ST_OR_OSHPO
ST_OR_OSL
ST_OR_OSU_CLIM
ST_OR_OSU_FOR
ST_OR_OSU_GAP
ST_OR_OSU_NHP
ST_UT_USU_LEMA
ST_WA_DNR
ST_WA_DOT
ST_WA_WDF
ST_WA_WRC
USA
Ocean
Bureau of Land Management
The National Atlas
National Geodetic Survey
National Oceanic and Atmospheric Administration
National Park Service
Natural Resources Conservation Service
Regional Ecosystem Office
Unknown Source
Space Imaging
Environmental Systems Research Institute
Titan Geospatial Inc.
The Nature Conservancy
Weyerhaeuser Corporation
Department of Water Resources, State of Idaho
Department of Mineral Industries, State of Oregon
Department of Forestry, State of Oregon
Department of Fish and Wildlife, State of Oregon
Department of Transportation, State of Oregon
Department of State Lands, State of Oregon
GIS Service Center, State of Oregon
Historic Preservation Office, State of Oregon
Oregon State Legislature, State of Oregon
Oregon Climate Service, Oregon State University
College of Forestry, Oregon State University
Oregon GAP Analysis Program, Oregon State University
Oregon Natural Heritage Program, Oregon State University
Landscape Ecology, Management, and Analysis Lab, Utah State Univ
Department of Natural Resources, State of Washington
Department of Transportation, State of Washington
Department of Fisheries, State of Washington
Washington State Redistricting Committee, State of Washington
U.S. Government
02/01/2011
Attachment 1- 20