State Data Standards
OR/WA Bureau of Land Management
HAZARDOUS SITE or TRESPASS
SPATIAL DATA STANDARD
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 1
State Data Standards
OR/WA Bureau of Land Management
TABLE OF CONTENTS
SECTION
1
1.1
1.2
1.3
1.4
1.5
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3
3.1
3.2
3.3
3.4
4
4.1
5
6
7
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
TITLE
General Information
Roles and Responsibilities
FOIA Category
Records Retention Schedule
Security/Access/Sensitivity
Keywords
Data Set Overview
Description
Usage
Sponsor/Affected Parties
Relationship to Other Datasets, Databases or Files
Data Category/Architecture Link
Relationship to the Department of the Interior Enterprise Architecture –
Data Resource Model
Hazardous Site or Trespass Data Organization/Structure
Data Management Protocols
Accuracy Requirements
Collection, Input, and Maintenance Protocols
Update Frequency and Archival Protocols
Statewide Monitoring
Hazardous Site or Trespass Schema (Simplified)
HAZ_TRES_POLY Feature Class
Projection and Spatial Extent
Spatial Entity Characteristics
Attribute Characteristics and Definitions
ACCURACY_FT
AMSCM_LINK
AMSCM_GEOMETRY
BLM_ORG_CD
CASEFILE
CLASSIFIER
CLOSE_DT
COMMENTS
COORD_SRC
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
PAGE
4
4
5
5
5
5
6
6
6
6
6
7
7
8
9
9
9
9
9
10
10
11
11
12
12
12
12
13
13
14
14
14
15
Page 2
State Data Standards
OR/WA Bureau of Land Management
7.10
7.11
7.12
7.13
7.14
7.15
7.16
7.17
7.18
7.19
7.20
7.21
7.22
7.23
7.24
8
9
9.1
9.2
10
ENV_PHYS
FILEPATH
FTR_TYPE
GIS_ACRES
HAZ_TRES_MAT
HAZ_TRES_TYPE
IMARS_LINK
JURIS_CD
LENGTH_FT
PROT_DEVICE
REPORT_DT
SITE_NAME
SITE_STAT
TRES_TYPE
VERSION_NAME
Layer Files (Publication Views)
Editing Procedures
Managing Overlap
Editing Quality Control
Oregon/Washington Data Framework Overview
15
15
16
16
17
17
17
18
18
18
19
19
19
20
20
21
21
21
22
23
11
Abbreviations and Acronyms Used in this Standard
24
Appendix A
Domains (Valid Values)
25
A.1
dom_BLM_ORG_CD
25
A.2
dom_COORD_SRC
26
A.3
dom_ENV_PHYS
26
A.4
dom_FTR_TYPE
26
A.5
dom_HAZ_TRES_MAT
27
A.6
dom_HAZ_TRES_TYPE
27
A.7
dom_JURIS_CD
28
A.8
dom_PROT_DEVICE
28
A.9
dom_SITE_STAT
29
A.10
dom_TRES_TYPE
29
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 3
State Data Standards
OR/WA Bureau of Land Management
1. GENERAL INFORMATION
Dataset (Theme) Name: Hazardous Sites or Trespass
Dataset (Feature Class): HAZ_TRES_POLY
1.1 ROLES AND RESPONSIBILITIES
Roles
State Data Stewards
Lead GIS Specialist
State Data
Administrator
State Records
Administrator
Responsibilities
The State Data Stewards, John Barber, at 503-808-6538, for hazardous sites
and Janet Cheek, at 503-808-6040, for realty trespass, are responsible for
approving data standards and business rules, developing Quality
Assurance/Quality Control procedures, identifying potential privacy issues,
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
national data stewards. The State Data Steward also reviews geospatial
metadata for completeness and quality.
The Lead GIS Specialist, Ryan Kelley, at 503-808-6495,works with data
stewards to convert business needs into GIS applications and derive data
requirements and participates in the development of data standards. The
lead GIS specialist coordinates with system administrators and GIS
coordinators to manage the GIS databases. The lead GIS specialist works
with data editors to make sure data is being input into the enterprise Spatial
Database Engine (SDE) database consistently and in accordance with the
established data standard. The lead GIS specialist provides technical
assistance and advice on GIS analysis, query and display of the dataset.
The Acting State Data Administrator, Georgia Bosse, at 503-808-6120,
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
State Data Administrator is responsible for making data standards and
metadata accessible to all users. The State Data Administrator also
coordinates with data stewards and GIS coordinators to respond to national
spatial data requests.
The acting State Records Administrator, Janice Johnson, at 503-808-6430,
assists the State Data Steward to identify any privacy issues related to
spatial data. The State Records Administrator also provides direction and
guidance on data release and fees. The State Records Administrator also
ensures that data has been classified under the proper records retention
schedule and determines appropriate Freedom of Information Act category.
Table 1 Role and Responsibilities
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 4
State Data Standards
OR/WA Bureau of Land Management
1.2 FOIA CATEGORY
Non-Public
1.3 RECORDS RETENTION SCHEDULE
General Records Schedule (GRS) BLM 20/52 (Electronic Records/Geographic Information Systems).
TEMPORARY. Delete when no longer needed for administrative, legal, audit, or other operational
purposes (subject to any records freeze or holds that may be in place).
1.4 SECURITY/ACCESS/SENSITIVITY
The Trespass theme does 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 dataset is sensitive and there may be restrictions on access to this data either from within the BLM
or external to the BLM. This dataset falls under the standard Records Access Category 1B- Public
Review Data, data that must be reviewed for potential protected information prior to release.
There are no privacy information issues or concerns associated with these data themes.
1.5 KEYWORDS
Keywords that can be used to locate this dataset include (thesaurus):
(BLM Thesaurus)
Lands
Minerals
Human Dimension
Oregon
Washington
(International Organization for Standardization (ISO) Thesaurus)
Environment and Conservation (environment), 007
Structure (structure), 017
(Additional keywords)
Hazardous
HAZMAT
Trespass
Unauthorized use
Dangerous area
Abandoned mine lands
AML
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 5
State Data Standards
OR/WA Bureau of Land Management
2. DATASET OVERVIEW
2.1 DESCRIPTION
The Hazardous Site or Trespass (HAZ_TRES_POLY) dataset represents spatial location and basic
information about hazardous or potentially hazardous sites. Hazards might be physical or
environmental. The sites might be prior authorized development such as abandoned mine lands. Or the
sites might represent trespass defined as unauthorized use, occupancy or development other than casual
use, upon public lands without a prior land use authorization or a right granted by statute or law, that
causes physical damage to public lands, property located thereon or resources or loss of revenue to the
United States.
Attributes include information about the type of site and material as well as status of action on the site
and dates.
The Comprehensive Environmental Response Compensation and Liability Act (CERCLA) of 1980 and
the National Contingency Plan (NCP) in Title 40 of the Code of Federal Regulations (CFR), part 300,
mandates why and how we clean up hazardous material releases. Executive Order 12580 delegated
authorities and responsibilities for responding to hazardous substance releases to DOI under CERCLA.
2.2 USAGE
This dataset is used to display hazardous areas or trespass sites on maps for field verification and
briefings. The spatial features can be combined with other spatial datasets to assess impact to resources
and for reporting purposes. There are reporting requirements to regulatory agencies such as the U.S.
Environmental Protection Agency and Oregon Department of Environmental Quality as well as BLM
“Environmental Disposal Liabilities” reports to the US Department of the Interior.
2.3 SPONSOR/AFFECTED PARTIES
The sponsor for this data set is the Deputy State Director, Resource Planning, Use & Protection. A site
is sometimes located on non-BLM land or under some other jurisdiction and may require some
coordination, otherwise it is not necessary to share or match these data with other agency datasets.
2.4 RELATIONSHIP TO OTHER DATASETS, DATABASES or FILES
This dataset may be related to the Structures dataset (described under a different data standard) to the
extent that a feature in the Structures dataset may also be found in this dataset if it is considered a
hazardous or trespass site. Structures installed as protective or warning devices (e.g. fence or sign) are
noted here in attribute PROT_DEVICE, but the feature itself is found in the Structures dataset. Likewise
if the trespass is a Right-Of-Way (ROW) infraction, there will be a relationship to the ROW feature on
the Easements and Rights-Of-Way dataset and to the road or trail on the Ground Transportation dataset
(both described under a different data standard).
This dataset contains the spatial location for entities contained in the national Abandoned Mine-Site
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 6
State Data Standards
OR/WA Bureau of Land Management
Cleanup Module (AMSCM) and for realty trespass cases and includes linking fields for these two
databases (AMSCM_LINK and CASEFILE). The spatial features will be uploaded to AMSCM when
requested to populate a national dataset. Attributes will be kept synchronized with the two national
databases, AMSCM and the realty Legacy Rehost (LR2000) database.
2.5 DATA CATEGORY/ARCHITECTURE LINK
This data theme is a portion of the Oregon Data Framework (ODF). The ODF utilizes the concept of
inheritance to define specific instances of data. All OR/WA resource-related data are divided 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 subcategories may be further broken into more specific groups until the basic dataset cannot be further subdivided. 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 ODF Overview (figure 2)
for a simplified schematic of the entire ODF showing the overall organization and entity inheritance.
The Hazardous Sites_Trespass entities are highlighted. For additional information about the ODF,
contact:
OR/WA State Data Administrator
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
503-808-6009
In the ODF, HAZ_TRES_POLY is considered a boundary and categorized as follows:
ODF
Boundaries
Land Status, Existing
HAZ_TRES_POLY
2.6 RELATIONSHIP TO THE DEPARTMENT OF THE INTERIOR ENTERPRISE
ARCHITECTURE - DATA RESOURCE MODEL
The Department of the Interior (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, the Data Subject Area and Information Class are:
• Data Subject Area: Geospatial
• Information Class: Location
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 7
State Data Standards
OR/WA Bureau of Land Management
2.7 HAZARDOUS SITE or TRESPASS DATA ORGANIZATION / STRUCTURE
Figure 1 Data Organization Structure
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 8
State Data Standards
OR/WA Bureau of Land Management
3. DATA MANAGEMENT PROTOCOLS
3.1 ACCURACY REQUIREMENTS
This dataset requires the highest possible accuracy in order to accurately locate and map the extent of
unauthorized uses or hazardous sites. Locational accuracy is within 40 feet unless the site status is
“Pending”, “Invalid” or “Not Found”. Required attributes have an accuracy of at least 95 percent.
3.2 COLLECTION, INPUT, AND MAINTENANCE PROTOCOLS
Initial coordinates for a hazardous sites or trespass area might come from a variety of sources including:
GPS coordinates, paper site maps, public supplied coordinates and legal descriptions.
The initial coordinates might be for a single point, a line or a polygon. The attribute REPORT_DT is
filled in with the initial report date. If the initial coordinates are point or line, a polygon is created using
the supplied width or radius or using a default buffer of 1 meter. Once a polygon is created, whether
provided initially or from a default buffer, the feature is overlaid on aerial imagery to refine the
boundary, if the feature is visible. The imagery must be as current as possible, correctly groundrectified and projected, and with a minimum half-meter resolution. The initial polygon receives a site
status (SITE_STAT) of “Pending” until a site visit and/or other verification can be made. The
coordinate source and accuracy of the final polygon representation, not the initial source and accuracy,
is put into COORD_SRC and ACCURACY_FT.
The attribute FTR_TYPE is the official AMSCM feature type and should be entered or verified by the
local minerals or hazardous materials (HAZMAT) specialist. Similarly, the attribute TRES_TYPE is the
official realty trespass type and should be entered or verified by the local realty specialist.
If a site is referred to law enforcement, SITE_STAT is changed to “Referred”. When a realty trespass
case is closed, the spatial entity can be retained, if desired, with SITE_STAT = “Closed” and the
CLOSE_DT filled in. There are also choices for “Cleanup Initiated” and “Cleanup Completed” for a
site and for the initial signing or fencing of a new site.
There will be relatively few spatial features on HAZ_TRES_POLY and they may be scattered, highly
dispersed, solitary features or clusters of small features. There may be a HAZMAT site within an
abandoned mine land site or a realty trespass that is also a HAZMAT site or all three in one small area.
It is preferred that a separate (sometimes very small) polygon is created for each type of site, even if
they overlap in whole or part. Sometimes, however, it is truly a single site (for example a trespass dump
site that contains hazardous materials) and the attributes are provided for labeling a single site polygon
appropriately.
3.3 UPDATE FREQUENCY AND ARCHIVAL PROTOCOLS
Data is updated on an on-going basis. It is archived annually at the end of the fiscal year.
It is the responsibility of district specialists (minerals, HAZMAT, realty, GIS) to ensure that the spatial
features and attributes in HAZ_TRES_POLY are correct and agree with any external database.
3.4 STATEWIDE MONITORING
The State Data Steward, assisted by the Lead GIS Specialist, is responsible for checking consistency
across Districts and for checking the layer files (publication views) for appropriate filtering.
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 9
State Data Standards
OR/WA Bureau of Land Management
4. HAZ_TRES_POLY 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. Current domains are found on
the internal OR/WA SharePoint data management page. Some of the domains used in this data
standard are also available at the following public web site:
http://www.blm.gov/or/datamanagement/index.php
For domains not listed at that site contact:
OR/WA State Data Administrator
Bureau of Land Management
P.O. Box 2965
Portland, OR 97208
503-808-6009
4.1 HAZ_TRES_POLY Feature Class (Hazardous Site or Trespass Polygons)
Attribute Name
SITE_NAME
SITE_STAT
BLM_ORG_CD
JURIS_CD
REPORT_DT
CLASSIFIER
HAZ_TRES_TYPE
FTR_TYPE
ENV_PHYS
AMSCM_LINK
AMSCM_GEOMETRY
TRES_TYPE
CASEFILE
HAZ_TRES_MAT
PROT_DEVICE
IMARS_LINK
CLOSE_DT
ACCURACY_FT
COORD_SRC
Data
String
String
String
String
String
String
String
String
String
Integer
String
String
String
String
String
String
String
Integer
String
Length Default
40
20
5
OR000
3
8
20
4
30
10
Long
5
30
15
30
20
10
8
Short
7
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Required?
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Domain
No
Yes
No
No
No
No
No
No
Yes
(Point or Poly)
dom_TRES_TYPE
dom_SITE_STAT
dom_BLM_ORG_CD
dom_JURIS_CD
dom_HAZ_TRES_TYPE
dom_FTR_TYPE
dom_ENV_PHYS
dom_HAZ_TRES_MAT
dom_PROT_DEVICE
dom_COORD_SRC
Page 10
State Data Standards
COMMENTS
String
FILEPATH
String
LENGTH_FT
Double
GIS_ACRES
Double
VERSION_NAME*
String
* Values automatically generated
OR/WA Bureau of Land Management
100
150
16,4
16,6
50
InitialLoad
No
No
No
Yes*
Yes*
5. PROJECTION AND SPATIAL EXTENT
All feature classes and feature datasets are in Geographic, North American Datum (NAD) 83. Units are
decimal degrees. Spatial extent (area of coverage) includes all lands managed by the BLM OR/WA,
bordered on the North by Latitude 49.5, on the South by Latitude 41.5, on the East by Longitude -116
and on the West by Longitude -125.
6. SPATIAL ENTITY CHARACTERISTICS
HAZ_TRES_POLY
Description: Instance of ODF Boundaries, Existing Land Status sub-category.
Geometry: Polygon only. Sites are scattered and relatively small. There might be many polygons in a
small area and they can overlap in whole or part.
Topology: No topology enforced.
Integration Requirements: Features with COORD_SRC of CADNSDI or GCD should be snapped to
PLSSPoint. Features with COORD_SRC of SOURCEL should be copied or snapped accordingly.
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 11
State Data Standards
OR/WA Bureau of Land Management
7. ATTRIBUTE CHARACTERISTICS AND DEFINITION (In alphabetical order)
7.1 ACCURACY_FT
Geodatabase Name
ACCURACY_FT
BLM Structured Name
Accuracy_Feet_Measure
Inheritance
Inherited from Entity ODF
Feature Class Use
HAZ_TRES_POLY
How close, in feet, the spatial GIS depiction is in relation 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 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 Graph, Cadastral National Spatial Data
Infrastructure and Digital Elevation Model) because the accuracy is
determined by that theme. However, if COORD_SRC is MAP (digitized
from a paper map) or GPS, 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 the accuracy is unknown and no reliable estimate can be made.
Optional
No domain. Examples: 3 (for high accuracy GPS), 40 (best possible for
USGS 24K topo map), 200
Short Integer
Definition
Required/Optional
Domain (Valid Values)
Data Type
7.2 AMSCM_LINK
Geodatabase Name
AMSCM_LINK
BLM Structured Name
AMSCM_Database_Foreign_Key
Inheritance
Inherited from HAZ_TRES_POLY
Feature Class Use
HAZ_TRES_POLY
Definition
Linking field to AMSCM database
Required/Optional
Optional
Domain (Valid Values)
No domain. Examples:
Data Type
Long Integer
7.3 AMSCM_GEOMETRY
Geodatabase Name
AMSCM_GEOMETRY
BLM Structured Name
AMSCM_SPATIAL_GEOMETRY_TYPE
Inheritance
Inherited from Entity HAZ_TRES_POLY
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 12
State Data Standards
Feature Class Use
OR/WA Bureau of Land Management
Required/Optional
HAZ_TRES_POLY
Used for conversion to the spatial geometry representation in the national
AMSCM dataset. If “Point”, only the centroid of the HAZ_TRES_POLY
is uploaded to the national dataset.
Optional
Domain (Valid Values)
None, but only valid values are “Point” or “Poly”
Data Type
Variable Characters (5)
Definition
7.4 BLM_ORG_CD
Geodatabase Name
BLM_ORG_CD
BLM Structured Name Administrative_Unit_Organization_Code
Inheritance
Inherited from Entity ODF
Feature Class Use
HAZ_TRES_POLY
A combination of the BLM administrative state and field office which has
administrative responsibility for the spatial entity. This includes which
office covers the entity for planning purposes and which office is the lead
for GIS edits. Another agency or individual may have the physical
management responsibility for the on-the-ground entity. This field applies
particularly when a spatial entity crosses resource area or district boundaries
and the administrative responsibility is assigned to one or the other rather
than splitting the spatial unit. Similarly, OR/WA BLM may have
administrative responsibility over some area that is physically located in
Nevada, Idaho, and California and vice versa. When appropriate, the office
can be identified only to the district or state level rather than to the resource
area level.
Required
Definition
Required/Optional
Domain (Valid
Values)
dom_BLM_ORG_CD Domain is a subset of the BLM national domain for
organization codes. Only positions three through seven of the national code
are used (leading LL and trailing zeros are dropped).
Data Type
Variable Characters (5)
7.5 CASEFILE
Geodatabase Name
CASEFILE
BLM Structured Name
Casefile_Number
Inheritance
Inherited from Existing Land Status
Feature Class Use
HAZ_TRES_POLY
Definition
Case number assigned by the LR2000 database (serial number full) when
an action has begun (either by BLM action or due to receipt of an
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 13
State Data Standards
Required/Optional
Domain (Valid Values)
Data Type
OR/WA Bureau of Land Management
application). Include suffix (a unique identifier of cases resulting from the
division of an original case into multiple, separate, and unique cases).
For features with no BLM action, enter “NON_BLM.” This number must
match exactly with the serial numbers in LR2000 including any spacing in
the number (see the examples below).
Optional
No domain. Examples: OROR 65814, OROR 6818PT, OROR
61083FD, OROR 6173P1, ORORE 00014635
Variable Characters (15)
7.6 CLASSIFIER
Geodatabase Name
CLASSIFIER
BLM Structured Name
Classifier_Name
Inheritance
Inherited from Oregon Data Framework
Feature Class Use
HAZ_TRES_POLY
Required/Optional
Name (mixed case, first and last) of the subject matter specialist most
knowledgeable about the site. The contact person.
Optional
Domain (Valid Values)
No domain. Examples: Mary Smith, John Doe
Data Type
Variable Characters (20)
Definition
7.7 CLOSE_DT
Geodatabase Name
CLOSE_DT
BLM Structured Name
Case_Closed_Date
Inheritance
Inherited from Existing Land Status
Feature Class Use
HAZ_TRES_POLY
Required/Optional
Full date the case was officially closed in standard 8 character format,
YYYYMMDD. From the Case File or Project Lead if no Case File.
Optional
Domain (Valid Values)
No domain. Examples: 20100315, 20131205
Data Type
Variable Characters (8)
Definition
7.8 COMMENTS
Geodatabase Name
COMMENTS
BLM Structured Name
Comments_Text
Inheritance
Inherited from Oregon Data Framework
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 14
State Data Standards
OR/WA Bureau of Land Management
Feature Class Use
HAZ_TRES_POLY
Definition
Free text with additional important information about the site.
Required/Optional
Optional
Domain (Valid Values)
No domain. Examples:
Data Type
Variable Characters (100)
7.9 COORD_SRC
Geodatabase Name
COORD_SRC
BLM Structured Name
Coordinate_Source_Code
Inheritance
Inherited from Entity Boundaries
Feature Class Use
Required/Optional
HAZ_TRES_POLY
The actual source of the GIS coordinates for the polylines. If the line is
copied from another theme, and already has COORD_SRC, it should be
reviewed and may need to be changed for use in this dataset.
Required
Domain (Valid Values)
dom_COORD_SRC
Data Type
Variable Characters (7)
Definition
7.10 ENV_PHYS
Geodatabase Name
ENV_PHYS
BLM Structured Name
Environmental_Or_Physical_Site_Type_Code
Inheritance
Inherited from Entity HAZ_TRES_POLY
Feature Class Use
Required/Optional
HAZ_TRES_POLY
Indicates whether the site contains physical or environmental hazards or
both.
Required
Domain (Valid Values)
dom_ENV_PHYS
Data Type
Variable Characters (10)
Definition
7.11 FILEPATH
Geodatabase Name
FILEPATH
BLM Structured Name
Filename_Path_Text
Inheritance
Inherited from Entity Boundaries
Feature Class Use
HAZ_TRES_POLY
Definition
Computer storage location for a photo file (e.g., jpg), Word document,
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 15
State Data Standards
Required/Optional
OR/WA Bureau of Land Management
spreadsheet or other associated document. The value in this field serves as a
hyperlink to that location and the file it opens. Could also be a directory or
dataset that opens for further browsing (where multiple files are being
referenced).
Optional
Domain (Valid Values)
No Domain. Example:
G:\bns\DistrictMonitoring\Upland\Andrews_Allotments\Alvord_Peak_6038
\Pace_180\6038_001\6038-001.xls \EM_6.4.docx
Data Type
Variable Characters (15)
7.12 FTR_TYPE
Geodatabase Name
FTR_TYPE
BLM Structured Name
Abandoned_Mine_or_Hazardous_Site_Feature_Type_Code
Inheritance
Inherited from Entity HAZ_TRES_POLY
Feature Class Use
Required/Optional
HAZ_TRES_POLY
Type of feature related to an abandoned mine and/or hazardous materials
site. Choices match those from the AMSCM database feature types.
Required
Domain (Valid Values)
dom_FTR_TYPE
Data Type
Variable Characters (30)
Definition
7.13 GIS_ACRES
Geodatabase Name
GIS_ACRES
BLM Structured Name
GIS_Acres_Measure
Inheritance
Inherited from entity Oregon Data Framework
Feature Class Use
HAZ_TRES_POLY
GIS_ACRES is calculated when the submitted polygon is approved for
incorporation into the dataset. The standard spatial reference of
Geographic (NAD 1983) cannot be used for calculating acres so the
features are projected to one of three projections as determined by the
BLM_ORG_CD of the record. These three projections all utilize linear
units of meters, so the ESRI Geodatabase-controlled field SHAPE.AREA
can be used to convert to acres with the factor based on the U.S. Survey
Foot:
GIS_ACRES = SHAPE.AREA * 0.0002471044
Definition
District indicated by
BLM_ORG_CD:
Prineville
Coos Bay, Eugene, Lakeview,
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
ESRI Projection used:
NAD 1983 USFS R6 Albers
NAD 1983 UTM Zone 10N
Page 16
State Data Standards
OR/WA Bureau of Land Management
Required/Optional
Medford, Roseburg, Salem
Burns, Spokane, Vale
Required (automatically generated)
Domain (Valid Values)
No domain
Data Type
Decimal (16,6)
NAD 1983 UTM Zone 11N
7.14 HAZ_TRES_MAT
Geodatabase Name
HAZ_TRES_MAT
BLM Structured Name
Hazardous_Or_Trespass_Site_Material_Code
Inheritance
Inherited from Entity HAZ_TRES_POLY
Feature Class Use
Required/Optional
HAZ_TRES_POLY
The actual hazardous material at the site. Provides additional detail to the
general type found in required attributes FTR_TYPE and/or TRES_TYPE.
Not applicable (NA) for physical (HAZ_TRES_TYPE = ‘PHYS’) sites.
Optional
Domain (Valid Values)
dom_HAZ_TRES_MAT
Data Type
Variable Characters (30)
Definition
7.15 HAZ_TRES_TYPE
Geodatabase Name
HAZ_TRES_TYPE
BLM Structured Name
Hazardous_Or_Trespass_Site_Type_Code
Inheritance
Inherited from Entity HAZ_TRES_POLY
Feature Class Use
Required/Optional
HAZ_TRES_POLY
The general type of site: Abandoned Mine Land (AML), Hazard
Management or Resource Restoration (HMRR), or realty Trespass.
Required
Domain (Valid Values)
dom_HAZ_TRES_TYPE
Data Type
Variable Characters (4)
Definition
7.16 IMARS_LINK
Geodatabase Name
IMARS_LINK
BLM Structured Name
IMARS_Database_Foreign_Key
Inheritance
Inherited from HAZ_TRES_POLY
Feature Class Use
HAZ_TRES_POLY
Definition
Linking field to Incident Management, Analysis, and Reporting Systems
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 17
State Data Standards
OR/WA Bureau of Land Management
Required/Optional
(IMARS) database. Law enforcement database with information about
illegal activities. IMARS not viewable except by law enforcement officers.
Standardized field format: first 2 characters are a code for type of incident,
e.g. “LM” for “Land Management”, next 2 digits are the year and the
remaining 6 comprise a sequential number, left-filled with zeroes.
Optional
Domain (Valid Values)
No domain. Examples: LM14000001
Data Type
Character (10)
7.17 JURIS_CD
Geodatabase Name
JURIS_CD
BLM Structured Name
Site_Jurisdiction_Code
Inheritance
Inherited from entity Existing Land Status
Feature Class Use
Required/Optional
HAZ_TRES_POLY
Broad governmental or private organization with administrative
responsibility for the site.
Required
Domain (Valid Values)
dom_JURIS_CD
Data Type
Variable Characters (5)
Definition
7.18 LENGTH_FT
Geodatabase Name
LENGTH_FT
BLM Structured Name
Feature_Length_Feet_Measure
Inheritance
Inherited from entity Existing Land Status
Feature Class Use
Required/Optional
HAZ_TRES_POLY
Manually entered length of a linear trespass feature as measured in the
field. Provided for convenience since sites are represented as polygons.
Optional
Domain (Valid Values)
No Domain. Examples: 100.5, 2444
Data Type
Double (16,4)
Definition
7.19 PROT_DEVICE
Geodatabase Name
PROT_DEVICE
BLM Structured Name
Protection_Device_Code
Inheritance
Inherited from entity HAZ_TRES_POLY
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 18
State Data Standards
Feature Class Use
OR/WA Bureau of Land Management
Required/Optional
HAZ_TRES_POLY
Type of protective structure or device installed on a hazardous site. To
protect humans or animals. Actual feature found on the Structures dataset.
Optional
Domain (Valid Values)
dom_PROT_DEVICE
Data Type
Variable Characters (20)
Definition
7.20 REPORT_DT
Geodatabase Name
REPORT_DT
BLM Structured Name
Site_Discovery_Reporting_Date
Inheritance
Inherited from entity HAZ_TRES_POLY
Feature Class Use
Required/Optional
HAZ_TRES_POLY
Date the site was initially reported in standard 8 character format:
YYYYMMDD, YYYYMM if only month and year known, YYYY if
only the year is known, or “UNKNOWN”.
Optional
Domain (Valid Values)
No Domain. Examples: 20130622, 201411
Data Type
Variable Characters (8)
Definition
7.21 SITE_NAME
Geodatabase Name
SITE_NAME
BLM Structured Name
Site_Name_Text
Inheritance
Inherited from entity HAZ_TRES_POLY
Feature Class Use
HAZ_TRES_POLY
Definition
Identifying name for a site. Generally assigned by the local office.
Required/Optional
Required
Domain (Valid Values)
No Domain. Examples: “Smith Fence”, “Glass Buttes Mercury Mine
1”, “Side Canyon Trash Dump”
Data Type
Variable Characters (40)
7.22 SITE_STAT
Geodatabase Name
SITE_STAT
BLM Structured Name
Site_Status_Code
Inheritance
Inherited from entity HAZ_TRES_POLY
Feature Class Use
HAZ_TRES_POLY
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 19
State Data Standards
OR/WA Bureau of Land Management
Required/Optional
Verification, mitigation or cleanup status of a hazardous or trespass site.
Important for filtering out sites that shouldn’t be displayed (see Section 8,
Publication Views).
Required
Domain (Valid Values)
dom_SITE_STAT
Data Type
Variable Characters (20)
Definition
7.23 TRES_TYPE
Geodatabase Name
TRES_TYPE
BLM Structured Name
Trespass_Type_Code
Inheritance
Inherited from entity HAZ_TRES_POLY
Feature Class Use
HAZ_TRES_POLY
Definition
Official trespass type and number code from realty program.
Required/Optional
Required
Domain (Valid Values)
dom_TRES_TYPE
Data Type
Variable Characters (30)
7.24 VERSION_NAME
Geodatabase Name
VERSION_NAME
BLM Structured Name
Geodatabase_Version_Text
Inheritance
Inherited from Entity Oregon Data Framework
Feature Class Use
All feature classes
Name of the corporate geodatabase version previously used to edit the
record.
InitialLoad = feature has not been edited in ArcSDE.
Definition
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.
Required/Optional
Example: sfrazier.FIRE_POLY-121210-111034
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.
Required (automatically generated)
Domain (Valid Values)
No domain
Data Type
Variable Characters (50)
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 20
State Data Standards
OR/WA Bureau of Land Management
8. 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:
A. Copied completely with no changes (replicated).
B. Copied with no changes except to omit one or more feature classes from a feature dataset.
C. Minor changes made (e.g., clip, dissolve, union with ownership) in order to make the data
easier to use. Feature classes that have been changed 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 are not new data requiring storage and maintenance, but point to existing data. 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 processes, and
can be deleted and recreated at any time.
The HAZ_TRES_POLY dataset uses the attribute SITE_STAT to filter out certain types of sites. In
BLM internal layer files, a SITE_STAT of ‘Pending’ will have a unique symbology to flag it as not yet
verified. Similarly, unique symbology will be used for SITE_STAT of ‘Invalid’ or ‘Not Found’, if they
are included in publication. Entities with SITE_STAT of ‘Referred’ (indicating potentially sensitive
data) will not be included in layer files.
The HAZ_TRES_POLY dataset will not be published to the web.
9. EDITING PROCEDURES
9.1 Managing Overlap
“Overlap” means there are potentially more than one feature in the same feature class that occupies the
same space (“stacked” polygons). Depending on the query, acres will be double-counted.
In this discussion, an entity may consist of more than one polygon. It 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 ODF in limited and controlled scenarios. In each case, the “cause” of the
overlap (the attribute changes that “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 for 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.
In the case of HAZ_TRES_POLY a new polygon that potentially overlaps an existing one is created if
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 21
State Data Standards
OR/WA Bureau of Land Management
the type of site or material is different.
9.2 Editing Quality Control
1.
Duplicate features. Checking for undesired duplicates is critical. Polygons or arcs that are
100% duplicate are 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.
2. Gap and overlap slivers. These can be hard to find if there are no topology rules. A temporary
map topology can be created to find overlap slivers. Gap slivers can be found by constructing
polygons from all arcs and checking polygons with very small area.
3. Buffer and dissolve considerations. 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.” Lines resulting
from buffer have vertices too close together, especially around the end curves. They should be
generalized to thin the vertices. If the dissolve tool is used on polygons or arcs, the “Create
multipart features” should be unchecked.
4. GPS considerations. GPS linework may be messy and should always be checked and cleaned up
as necessary. Often vertices need to be thinned (generalize) especially at line ends. Multi-part
polygons are sometimes inadvertently created when GPS files with vertices too close together, or
crossing lines, or spikes are brought into ArcGIS. Tiny, unwanted polygons are created but are
“hidden” because they are in a multi-part.
5. Be careful when merging lines. Multi-part lines will be created if there are tiny unintentional
(unknown) gaps and it can be difficult to find these unless the multi-parts are exploded.
6. Null geometry. Check any features that have 0 or very small Shape_Area or Shape_Length. If a
feature has 0 geometry and you can’t zoom to it, it is probably an inadvertently created “Null”
feature and should be deleted. Very small features may also be unintended, resulting from messy
linework.
7. Check tolerances. In general, set Cluster Tolerance as small as possible. This is 0.000000009
Degree (0.000007 degree is approximately 1 meter).
8. Snapping considerations. 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 PLSS (CadNSDI points/lines)
first, with DLG or SOURCEL next, then DEM, 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 PLSS points, and make sure there are the same
number of vertices in the line as PLSS points.
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 22
State Data Standards
OR/WA Bureau of Land Management
10. OREGON/WASHINGTON DATA FRAMEWORK OVERVIEW
Figure 2 Oregon Data Framework Overview
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 23
State Data Standards
OR/WA Bureau of Land Management
11. ABBREVIATIONS AND ACRONYMS USED
(does not include abbreviations/acronyms used as codes for particular data attributes or domain values)
Abbreviations
AML
AMSCM
BLM
CadNSDI
DEM
DLG
FOIA
GIS
GPS
HAZMAT
HMRR
IMARS
LR2000
ODF
OR/WA
PLSS
USGS
Descriptions
Abandoned Mine Lands
Abandoned Mine – Site Cleanup Module
Bureau of Land Management, U.S. Department of the Interior
Cadastral National Spatial Data Infrastructure
Digital Elevation Model (a USGS data structure)
Digital Line Graph (a USGS vector data format)
Freedom Of Information Act
Geographic Information System
Global Positioning System
Hazardous Materials
Hazard Management and Resource Restoration
Incident Management, Analysis, and Reporting System
Legacy Rehost 2000 (Lands & Minerals) database
Oregon Data Framework
Oregon/Washington
Public Land Survey System
United States Geological Survey, U.S. Department of the Interior
Table 2 Abbreviations/Acronyms Used
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 24
State Data Standards
OR/WA 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
503-808-6009
A.1 dom_BLM_ORG_CD (http://www.blm.gov/or/datamanagement/index.php)
OR000
OR000 − Oregon/Washington BLM
ORB00
ORB00 − Burns District Office
ORB05
ORB05 − Three Rivers Field Office
ORB06
ORB06 − Andrews Field Office
ORC00
ORC00 − Coos Bay District Office
ORC03
ORC03 − Umpqua Field Office
ORC04
ORC04 − Myrtlewood Field Office
ORE00
ORE00 − Eugene District Office
ORE05
ORE05 − Siuslaw Field Office
ORE06
ORE06 − Upper Willamette Field Office
ORL00
ORL00 − Lakeview District Office
ORL04
ORL04 − Klamath Falls Field Office
ORL05
ORL05 − Lakeview Field Office
ORM00
ORM00 − Medford District Office
ORM05
ORM05 − Butte Falls Field Office
ORM06
ORM06 − Ashland Field Office
ORM07
ORM07 − Grants Pass Field Office
ORP00
ORP00 − Prineville District Office
ORP04
ORP04 − Central Oregon Field Office
ORP06
ORP06 − Deschutes Field Office
ORR00
ORR00 − Roseburg District Office
ORR04
ORR04 − Swiftwater Field Office
ORR05
ORR05 − South River Field Office
ORS00
ORS00 − Salem District Office
ORS04
ORS04 − Cascades Field Office
ORS05
ORS05 – Mary’s Peak Field Office
ORS06
ORS06 − Tillamook Field Office
ORV00
ORV00 − Vale District Office
ORV04
ORV04 − Malheur Field Office
ORV05
ORV05 − Baker Field Office
ORV06
ORV06 − Jordan Field Office
ORW00
ORW00 − Spokane District Office
ORW02
ORW02 − Wenatchee Field Office
ORW03
ORW03 − Border Field Office
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 25
State Data Standards
OR/WA Bureau of Land Management
A.2 dom_COORD_SRC
CADNSDI
CADNSDI – Lines from or snapped to the CADNSDI dataset
CFF
CFF – Lines duplicated or buffered from Cartographic Feature Files
DEM
DEM − Digital Elevation Model (30m or better accuracy) used for creation of
contours
DLG
DLG − Lines duplicated or buffered from (24K scale accuracy) USGS Digital
Line Graphs Typical Accuracies (40 feet)
DIS
DIS – Lines generated to connect discontinuous features
DLG
DLG – Lines duplicated or buffered from USGS Digital Line Graphs
DOQ
DOQ – Screen digitized linework over Digital Orthoquad backdrop
DRG
DRG − Screen digitized linework over Digital Raster Graphic (USGS) backdrop
GCD
GCD − Lines snapped to Geographic Coordinate Database Points
GPS
GPS − Lines obtained from a Global Positioning System device
IMG
IMG – Linework derived from interpretation of non-photographic imagery
MAP
MAP − Digitized line work from hardcopy map
MTP
MTP − Lines duplicated from Digital Master Title Plat
SOURCEL
SOURCEL − Source layer from BLM GIS
SRV
SRV − Survey methods were used to create the linework
TIGER
TIGER – Tiger data
TRS
TRS – Coordinates only given as a legal description (township, range, section)
UNK
UNK − Unknown coordinate source
WOD
WOD – WODDB (Western Oregon Digital Database) Photogrammetric
A.3 dom_ENV_PHYS
ENV
PHYS
ENV/PHYS
UNK
ENV – Environmental hazard site
PHYS – Physical hazard site
ENV/PHYS – Both Environmental and Physical hazards
UNK – Unknown
A.4 dom_FTR_TYPE
Adit Caved
Adit Open
Shaft Caved
Shaft Open
Mine Highwalls
Hazardous Waste Dump
Solid Waste Dump
Landfill
Mine Processing Mill
Industrial Facility
Orphaned Well
Pipeline Leak
Mining Prospect Pit
Repository
Adit Caved – Decline, Tunnel
Adit Open – Decline, Tunnel
Shaft Caved - Incline, Stope
Shaft Open – Incline, Stope
Mine Highwalls – or Pits
Hazardous Waste Dump – with or without solid waste
Solid Waste Dump Landfill Mine Processing Mill Industrial Facility Orphaned Well Pipeline Leak – or spill
Mining Prospect Pit Repository -
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 26
State Data Standards
Evap or Waste Pond
Spill-NonPipeline
Tailings
Tank-Above Ground
Tank-Below Ground
Shooting Sports Area
Wire Burn
Heap Leach
Ordnance
Old Building
Other
Unknown
OR/WA Bureau of Land Management
Evap or Waste Pond – Reserve Pits, Produced Water Pond
Spill-NonPipeline Tailings Tank - Above Ground Tank-Below Ground Shooting Sports Area Wire Burn Heap Leach Ordnance – or dynamite
Old Building – Hanta Virus
Other Unknown -
A.5 dom_HAZ_TRES_MAT
Gas
Diesel
Propane
Chemical
Water-Unknown
Water-Contaminated
Domestic Trash
Appliances
Vehicles or Tires
Construction Materials Chemical Trash
Marijuana
Animal-Contaminated
Gravel
Cultivated Plants
Agricultural Stockpiles
Livestock Use
Water Development
Utility Development
Residences
Mining Equipment
Signs
Locked Gate
Road
Gas - Petroleum
Diesel - Petroleum
Propane - Petroleum
Chemical Water-Unknown
Water-Contaminated Domestic Trash Appliances Vehicles or Tires Construction Materials Chemical Trash Marijuana Animal-Contaminated – Hanta Virus threat
Gravel – or sand or rock
Cultivated Plants – other than marijuana
Agricultural Stockpiles – equipment or product
Livestock Use – fences, hay storage, troughs
Water Development – pipelines, dugouts, dams, ditches
Utility Development – installation of lines
Residences – permanent or temporary
Mining Equipment Signs Locked Gate Road – or trail construction or realignment
A.6 dom_HAZ_TRES_TYPE
AML
HMRR
TRES
UNK
AML – Abandoned Mine Land
HMRR – Hazard Management and Resource Restoration
TRES – Realty Trespass
UNK – Unknown
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 27
State Data Standards
OR/WA Bureau of Land Management
A.7 dom_JURIS_CD
BL
BL-Bureau of Land Management
BP
BP-Bonneville Power Administration
BR
BR-Bureau of Reclamation
CE
CE-Corps of Engineers
CG
CG-U.S. Coast Guard
DA
DA-U.S. Dept. of Agriculture (except the Forest Service)
DD
DD-U.S. Dept. of Defense (Except the Corps of Engineers)
FA
FA-Federal Aviation Administration
FC
FC-Federal Energy Regulatory Commission
FS
FS-U.S. Forest Service
FW
FW-U.S. Fish and Wildlife Service
GS
GS-U.S. Geological Survey
GSA
GSA-General Services Administration
IA
IA-Bureau of Indian Affairs and Tribal Units
LG
LG-Local Government
NP
NP-National Park Service
PV
PV-Private Lands
PVI
PVI-Private, Industrial
PVN
PVN-Private, Non-Industrial
PVU
PVU-Private, Urban
SDT
SDT-State Transportation Department
ST
ST-State Managed Lands
STF
STF-State Forests
STL
STL-State Division of Lands
STP
STP-State Parks
STW
STW-State Wildlife Refuges
UN
UN-Undetermined
A.8 dom_PROT_DEVICE
Sign
Fence
Sign/Fence
Barricade
Bat Cuppola
Bat Grate
Bulkhead
Bulkhead/Plug
Cable Net
Gate
PUF
Unknown
Sign – Warning sign installed
Fence – Area fenced off
Sign/Fence – Warning signs and fences
Barricade Bat Cuppola Bat Grate – or gate
Bulkhead Bulkhead/Plug Cable Net Gate – to prevent human passage
PUF – Polyurethane Foam
Unknown -
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 28
State Data Standards
OR/WA Bureau of Land Management
A.9 dom_SITE_STAT
Pending
Invalid
Not Found
Referred
Needs Analysis
Action Planned
Action in Progress
Action Completed
Monitor and Maintain
Closed
Unknown
Pending – Site has not been field verified and/or spatially corrected.
Invalid – Site is not hazardous nor a trespass
Not found Referred – to legal or administrative action
Needs Analysis Action Planned Action in Progress Action Completed Monitor and Maintain Closed – Case is closed, final closeout
Unknown -
A.10 dom_TRES_TYPE
1-Agriculture
2-Occupancy
3-Right-Of-Way
4-Enclosures
5-Water
6-Filming
7-Commercial Vending
8-Apiary
9-Road Use
10-Fire
11-Grazing
12-Minerals
13-Timber
14-Special Forest Products
15-Turpentine
16-Recreation
17-Archaeological
18-Hazardous Materials
19-Other
Unknown
Not Applicable
1-Agriculture 2-Occupancy 3-Right-Of-Way - encroachment
4-Enclosures 5-Water 6-Filming –
7-Commercial Vending 8-Apiary – bee hives
9-Road Use 10-Fire 11-Grazing 12-Minerals 13-Timber 14-Special Forest Products – and Range
15-Turpentine 16-Recreation 17-Archaeological 18-Hazardous Materials 19-Other
Unknown
Not Applicable – not a trespass site
Hazardous Site or Trespass Spatial Data Standard
June 15, 2014
Page 29