Color: [115, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
FCode: Coded Values:
[85000: Water Supply or Treatment Facility]
, [85001: Potable Water Facility]
, [85002: Public Water Supply Intake]
, ...7 more...
FCode: Coded Values:
[85000: Water Supply or Treatment Facility]
, [85001: Potable Water Facility]
, [85002: Public Water Supply Intake]
, ...7 more...
FCode: Coded Values:
[85000: Water Supply or Treatment Facility]
, [85001: Potable Water Facility]
, [85002: Public Water Supply Intake]
, ...7 more...
FCode: Coded Values:
[85000: Water Supply or Treatment Facility]
, [85001: Potable Water Facility]
, [85002: Public Water Supply Intake]
, ...7 more...
Color: [47, 140, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
FCode: Coded Values:
[83000: Government or Military Facility]
, [83002: Bureau of Land Managment Facility]
, [83004: US Capitol]
, ...22 more...
ID: 790
Name: Building General
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Coded Values:
[79000: Building General]
, [79002: Mobile Home Park]
, [79004: Multi-Family Dwelling]
, ...2 more...
ID: 880
Name: Information and Communication
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Coded Values:
[88000: Information or Communication Facility]
, [88002: Communication Tower]
, [88004: Data Center]
, ...6 more...
ID: 810
Name: Transportation Facilities
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Inherited
ID: 850
Name: Water Supply and Treatment
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Coded Values:
[85000: Water Supply or Treatment Facility]
, [85001: Potable Water Facility]
, [85002: Public Water Supply Intake]
, ...7 more...
FCode: Coded Values:
[83000: Government or Military Facility]
, [83002: Bureau of Land Managment Facility]
, [83004: US Capitol]
, ...22 more...
ID: 790
Name: Building General
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Coded Values:
[79000: Building General]
, [79002: Mobile Home Park]
, [79004: Multi-Family Dwelling]
, ...2 more...
ID: 880
Name: Information and Communication
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Coded Values:
[88000: Information or Communication Facility]
, [88002: Communication Tower]
, [88004: Data Center]
, ...6 more...
ID: 810
Name: Transportation Facilities
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Inherited
ID: 850
Name: Water Supply and Treatment
Domains:
Data_Security: Inherited
Distribution_Policy: Inherited
FCode: Coded Values:
[85000: Water Supply or Treatment Facility]
, [85001: Potable Water Facility]
, [85002: Public Water Supply Intake]
, ...7 more...
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [168, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [169, 0, 230, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [169, 0, 230, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [137, 90, 68, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [137, 90, 68, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: Maritime limits for the United States are measured from the U.S. baseline, recognized as the low-water line along the coast as marked on NOAA's nautical charts in accordance with the articles of the Law of the Sea. The baseline and related maritime limits are reviewed and approved by the interagency U.S. Baseline Committee. The primary purpose of this dataset is to update the official depiction of these maritime limits and boundaries on NOAA's nautical charts. The Office of Coast Survey depicts on its nautical charts the territorial sea (12 nautical miles), contiguous zone (24nm), and exclusive economic zone (200nm, plus maritime boundaries with adjacent/opposite countries). U.S. maritime limits are ambulatory and subject to revision based on accretion or erosion of the charted low water line. To ensure you are up-to-date and for more information about U.S. Maritime Limits and Boundaries, see http://www.nauticalcharts.noaa.gov/csdl/mbound.htm.For the full FGDC metadata record, see http://www.ncddc.noaa.gov/approved_recs/nos_de/ocs/ocs/ocs/MB_ParentDataset.html.Coordinates for the US/Canada international boundary, on land and through the Great Lakes, are managed by the International Boundary Commission. These boundaries are included with this dataset for continuity.
Copyright Text: National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Coast Survey (OCS)
Description: Maritime limits for the United States are measured from the U.S. baseline, recognized as the low-water line along the coast as marked on NOAA's nautical charts in accordance with the articles of the Law of the Sea. The baseline and related maritime limits are reviewed and approved by the interagency U.S. Baseline Committee. The primary purpose of this dataset is to update the official depiction of these maritime limits and boundaries on NOAA's nautical charts. The Office of Coast Survey depicts on its nautical charts the territorial sea (12 nautical miles), contiguous zone (24nm), and exclusive economic zone (200nm, plus maritime boundaries with adjacent/opposite countries). U.S. maritime limits are ambulatory and subject to revision based on accretion or erosion of the charted low water line. To ensure you are up-to-date and for more information about U.S. Maritime Limits and Boundaries, see http://www.nauticalcharts.noaa.gov/csdl/mbound.htm.For the full FGDC metadata record, see http://www.ncddc.noaa.gov/approved_recs/nos_de/ocs/ocs/ocs/MB_ParentDataset.html.Coordinates for the US/Canada international boundary, on land and through the Great Lakes, are managed by the International Boundary Commission. These boundaries are included with this dataset for continuity.
Copyright Text: National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Coast Survey (OCS)
Description: Maritime limits for the United States are measured from the U.S. baseline, recognized as the low-water line along the coast as marked on NOAA's nautical charts in accordance with the articles of the Law of the Sea. The baseline and related maritime limits are reviewed and approved by the interagency U.S. Baseline Committee. The primary purpose of this dataset is to update the official depiction of these maritime limits and boundaries on NOAA's nautical charts. The Office of Coast Survey depicts on its nautical charts the territorial sea (12 nautical miles), contiguous zone (24nm), and exclusive economic zone (200nm, plus maritime boundaries with adjacent/opposite countries). U.S. maritime limits are ambulatory and subject to revision based on accretion or erosion of the charted low water line. To ensure you are up-to-date and for more information about U.S. Maritime Limits and Boundaries, see http://www.nauticalcharts.noaa.gov/csdl/mbound.htm.For the full FGDC metadata record, see http://www.ncddc.noaa.gov/approved_recs/nos_de/ocs/ocs/ocs/MB_ParentDataset.html.Coordinates for the US/Canada international boundary, on land and through the Great Lakes, are managed by the International Boundary Commission. These boundaries are included with this dataset for continuity.
Copyright Text: National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Coast Survey (OCS)
Description: Maritime limits for the United States are measured from the U.S. baseline, recognized as the low-water line along the coast as marked on NOAA's nautical charts in accordance with the articles of the Law of the Sea. The baseline and related maritime limits are reviewed and approved by the interagency U.S. Baseline Committee. The primary purpose of this dataset is to update the official depiction of these maritime limits and boundaries on NOAA's nautical charts. The Office of Coast Survey depicts on its nautical charts the territorial sea (12 nautical miles), contiguous zone (24nm), and exclusive economic zone (200nm, plus maritime boundaries with adjacent/opposite countries). U.S. maritime limits are ambulatory and subject to revision based on accretion or erosion of the charted low water line. To ensure you are up-to-date and for more information about U.S. Maritime Limits and Boundaries, see http://www.nauticalcharts.noaa.gov/csdl/mbound.htm.For the full FGDC metadata record, see http://www.ncddc.noaa.gov/approved_recs/nos_de/ocs/ocs/ocs/MB_ParentDataset.html.Coordinates for the US/Canada international boundary, on land and through the Great Lakes, are managed by the International Boundary Commission. These boundaries are included with this dataset for continuity.
Copyright Text: National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Coast Survey (OCS)
Description: The Airports database is a geographic point database of aircraft landing facilities in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the landing facility, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product.
Copyright Text: The Federal Aviation Administration (FAA) develops and maintains the textual data from which this geospatial layer was derived.
Description: The Airports database is a geographic point database of aircraft landing facilities in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the landing facility, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product.
Copyright Text: The Federal Aviation Administration (FAA) develops and maintains the textual data from which this geospatial layer was derived.
Description: The Airports database is a geographic point database of aircraft landing facilities in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the landing facility, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product.
Copyright Text: The Federal Aviation Administration (FAA) develops and maintains the textual data from which this geospatial layer was derived.
Color: [168, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [76, 115, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [179, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [115, 38, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [169, 0, 230, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [112, 168, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: This layer includes Oregon Department of Environmental Quality (DEQ) and Oregon Health Authority (OHA) Drinking Water Program Source Water Assessment drinking water source area results for community (C), non-transient non-community (NTNC), transient non-community (TNC), and some state-regulated (SP) public water systems (PWS) for groundwater public water systems that were active in June 1999 (when Oregon's Source Water Assessment Plan was approved by EPA). Data is updated and modified as needed.
Copyright Text: Most original groundwater well, infiltration gallery, and spring drinking water source areas were established by the Oregon Health Authority ((OHA); formerly OR Dept. of Human Service), Drinking Water Program-Springfield Office under the direction of the Drinking Water Protection Groundwater Coordinator. Data includes "community", "nontransient noncommunity", and "transient noncommunity" public water supply sources. Limited "state-regulated" sources are also included. The combined GIS spatial data file of all wells, infiltration galleries, and springs was developed by Oregon Dept. of Environmental Quality/Water Quality Division/Drinking Water Protection.
Description: This map includes Oregon Department of Environmental Quality (DEQ) and Oregon Health Authority’ (OHA) Drinking Water Program Source Water Assessment results for community and non-transient non-community public water systems (PWS) for surface water systems that were active in June 1999 (when Oregon's Source Water Assessment Plan was approved by EPA). Subsequently, post-1999 systems have been added including some non-community systems.
Copyright Text: All original surface water source area files and combined GIS spatial data files were developed or established by the Oregon Department of Environmental Quality, Water Quality Division/Drinking Water Protection Program.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [112, 168, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.(ei
Copyright Text: ORBIC Stewardship Geodatabase. December 2013. Modified from: US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
Own_Name
(
type: esriFieldTypeString, alias: Owner Name, length: 70
, Coded Values:
[0100: Tennessee Valley Authority (TVA)]
, [0110: Bureau of Land Management (BLM)]
, [0115: Bureau of Ocean Energy Management, Regulation and Enforcement (DOI)]
, ...54 more...
)
Loc_Own
(
type: esriFieldTypeString, alias: Local Owner, length: 100
)
Status
(
type: esriFieldTypeString, alias: Status, length: 70
, Coded Values:
[Designated: Designated - Legally or administratively decreed]
, [Proposed: Proposed - local government level approval]
, [Other: Other - Site is recognized in a manner not otherwise classified]
, ...1 more...
)
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.(ei
Copyright Text: ORBIC Stewardship Geodatabase. December 2013. Modified from: US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
Own_Name
(
type: esriFieldTypeString, alias: Owner Name, length: 70
, Coded Values:
[0100: Tennessee Valley Authority (TVA)]
, [0110: Bureau of Land Management (BLM)]
, [0115: Bureau of Ocean Energy Management, Regulation and Enforcement (DOI)]
, ...54 more...
)
Loc_Own
(
type: esriFieldTypeString, alias: Local Owner, length: 100
)
Status
(
type: esriFieldTypeString, alias: Status, length: 70
, Coded Values:
[Designated: Designated - Legally or administratively decreed]
, [Proposed: Proposed - local government level approval]
, [Other: Other - Site is recognized in a manner not otherwise classified]
, ...1 more...
)
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.(ei
Copyright Text: ORBIC Stewardship Geodatabase. December 2013. Modified from: US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
Own_Name
(
type: esriFieldTypeString, alias: Owner Name, length: 70
, Coded Values:
[0100: Tennessee Valley Authority (TVA)]
, [0110: Bureau of Land Management (BLM)]
, [0115: Bureau of Ocean Energy Management, Regulation and Enforcement (DOI)]
, ...54 more...
)
Loc_Own
(
type: esriFieldTypeString, alias: Local Owner, length: 100
)
Status
(
type: esriFieldTypeString, alias: Status, length: 70
, Coded Values:
[Designated: Designated - Legally or administratively decreed]
, [Proposed: Proposed - local government level approval]
, [Other: Other - Site is recognized in a manner not otherwise classified]
, ...1 more...
)
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.(ei
Copyright Text: ORBIC Stewardship Geodatabase. December 2013. Modified from: US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
Own_Name
(
type: esriFieldTypeString, alias: Owner Name, length: 70
, Coded Values:
[0100: Tennessee Valley Authority (TVA)]
, [0110: Bureau of Land Management (BLM)]
, [0115: Bureau of Ocean Energy Management, Regulation and Enforcement (DOI)]
, ...54 more...
)
Loc_Own
(
type: esriFieldTypeString, alias: Local Owner, length: 100
)
Status
(
type: esriFieldTypeString, alias: Status, length: 70
, Coded Values:
[Designated: Designated - Legally or administratively decreed]
, [Proposed: Proposed - local government level approval]
, [Other: Other - Site is recognized in a manner not otherwise classified]
, ...1 more...
)
Description: ownership_poly_dissolve: This theme portrays information related to surface jurisdiction of lands located in the states of Oregon and Washington.
Description: This data layer depicts lands and waters administered by the U.S. Fish and Wildlife Service (USFWS) in North America, U.S. Trust Territories and Possessions. It may also include inholdings that are not administered by USFWS. The primary source for this information is the USFWS Realty program.
Copyright Text: U.S. Fish and Wildlife Service, National Willdlife Refuge System, Division of Realty, Cadastral Data Working Group
Description: An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area.
Description: dob_land_poly: This theme shows the polygon representation of Bureau of Land Management Districts for Oregon and Washington up to the coastline and including the off-shore islands within the district boundaries.
Description: This geographic feature data is a product of the 76th Oregon Legislative Session Redistricting process. These are the approved Senate districts. Every 10 years the Legislature is tasked with reassigning census units to new districts to balance the population. There are two House districts nested in one Senate district. Each Senate district is numbered by sequential House districts (Senate 1 consists of House 1 & 2).These boundaries are subject court challenge until August 1, 2011. Verify district accuracy by checking with the Oregon Secretary of State's Office or Oregon Department of Administrative Services- Geospatial Enterprise Office before conducting any legally binding analysis.
Copyright Text: Wayne Coffey, GIS Coordinator for Oregon Redistricting, Legislative Administration Committee Services.
http://www.leg.state.or.us/
Description: This geographic feature data is a product of the 76th Oregon Legislative Session Redistricting process. These are the approved House districts. Every 10 years the Legislature is tasked with reassigning census units to new districts to balance the population. There are two House districts nested in one Senate district. Each Senate district is numbered by sequentialHouse districts (Senate 1 consists of House 1 & 2).These boundaries are subject court challenge until August 1, 2011. Verify district accuracyby checking with the Oregon Secretary of State's Office or Oregon Department of Administrative Services- Geospatial Enterprise Office before conducting any legally binding analysis.
Copyright Text: Wayne Coffey, GIS Coordinator for Redistricting, Oregon Legislative Administration Committee Services.
http://www.leg.state.or.us/
Description: This geographic feature data is a product of the 76th Oregon Legislative Session Redistricting process. These are the approved Congressional districts. Every 10 years the Legislature is tasked with reassigning census units to new districts to balance the population. These boundaries are subject court challenge. Verify district accuracy by checking with the Oregon Secretary of State's Office or Oregon Department of Administrative Services- Geospatial Enterprise Office before conducting any legally binding analysis.
Copyright Text: Wayne Coffey, GIS Coordinator for Oregon Redistricting, Legislative Administration Committee Services.
http://www.leg.state.or.us/
Description: These polygons were built using the RING polygon generation setting in Network Analyst. Each polygon represents the area covered by a 5 minute marginal travel time limit to the facility (e.g., a ring with between 0 and 5 minutes to a particular hospital is the total area within 5 minutes of a hospital, following the road network; a 25-30 minute ring coveres the area between 25 and 30 minutes; etc.).Rings are generated out to 60 minute of travel time to a particular facility.Rings for different facilities are allowed to overlap each other.Specific analysis settings for polygons are as follows:Cost/Impedance: 5 Minute increments, up to 60 minutes from the facilityDirection: Inbound, towards facilityRestrictions applied:Avoid Pedestrian ZonesAvoid WalkwaysDriving a Passenger Car--YesObey Oneway StreetsThrough Traffic ProhibitedUse Street Heirarchy--NO!!!Street Network Used: 2013 - StreetMap™ North America, Publication Date 06-01-2013. Distributed by ArcGIS Development Team (909-793-2853), in conjunction with TomTom North America.
Copyright Text: Michael Greenwald--Oregon Health Authority, Office of Health Analytics
Tel: 503-945-6759
e-mail: michael.greenwald@dhsoha.state.or.us
Description: Linework for boom strategies used in Oregon's Department of Environmental Quality Geographic Response Plans (GRPs). GIS data contains booming strategies for the Oregon Coast, Descutes River, and the Columbia River (includes both Oregon and Washington sides of the river). Data corrected based on georectified images of existing GRP data.
Copyright Text: Developed by the the Oregon Department of Environmental Quality; edits made by University of Washington student group.
Description: Linework for boom strategies used in Oregon's Department of Environmental Quality Geographic Response Plans (GRPs). GIS data contains booming strategies for the Oregon Coast, Descutes River, and the Columbia River (includes both Oregon and Washington sides of the river). Data corrected based on georectified images of existing GRP data.
Copyright Text: Developed by the the Oregon Department of Environmental Quality; edits made by University of Washington student group.
Description: Boom strategy locations and attribute data used in Oregon's Department of Environmental Quality Geographic Response Plans (GRPs). GIS data contains booming strategies for the Oregon Coast, Descutes River, and the Columbia River (includes both Oregon and Washington sides of the river). Data corrected based on georectified images of existing GRP data.
Copyright Text: Developed by the Oregon Department of Environmental Quality; edits made by University of Washington student group.
Description: Boom strategy locations and attribute data used in Oregon's Department of Environmental Quality Geographic Response Plans (GRPs). GIS data contains booming strategies for the Oregon Coast, Descutes River, and the Columbia River (includes both Oregon and Washington sides of the river). Data corrected based on georectified images of existing GRP data.
Copyright Text: Developed by the Oregon Department of Environmental Quality; edits made by University of Washington student group.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. The third publication of the OFPBDS dataset (Version 3) complies with version 1.1 of the data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. Linear referencing attributes for the Pacific Northwest Hydrography have been retained in this version of the publication datasets, however they are no longer part of the data standard and will be removed from the next dataset publication version. Version 3 of the OFPBDS dataset contains over 30,000 barrier features from seventeen separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2011, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed (e.g. dam removals and culvert replacements) will be published simultaneously with version 3 of the OFPBDS dataset. The OFPBDS database does not represent a comprehensive record of fish passage barriers in Oregon. Attributes (including key attributes such as fish passage status) are often incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset comprehensive, current and accurate. Fish passage status is a key attribute. Many barrier features - including all ODOT barriers - have an unknown passage status. For other features, the passage status may have changed since documented. Note that this metadata file is best viewed in ArcCatalog with the FGDC Classic Stylesheet. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife, Oregon Department of Transportation, Oregon Department of Water Resources, Oregon Department of Forestry, Oregon Watershed Enhancement Board, US Bureau of Land Management, US Forest Service, Nez Perce Tribe, Benton SWCD, Washington County and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. The third publication of the OFPBDS dataset (Version 3) complies with version 1.1 of the data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. Linear referencing attributes for the Pacific Northwest Hydrography have been retained in this version of the publication datasets, however they are no longer part of the data standard and will be removed from the next dataset publication version. Version 3 of the OFPBDS dataset contains over 30,000 barrier features from seventeen separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2011, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed (e.g. dam removals and culvert replacements) will be published simultaneously with version 3 of the OFPBDS dataset. The OFPBDS database does not represent a comprehensive record of fish passage barriers in Oregon. Attributes (including key attributes such as fish passage status) are often incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset comprehensive, current and accurate. Fish passage status is a key attribute. Many barrier features - including all ODOT barriers - have an unknown passage status. For other features, the passage status may have changed since documented. Note that this metadata file is best viewed in ArcCatalog with the FGDC Classic Stylesheet. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife, Oregon Department of Transportation, Oregon Department of Water Resources, Oregon Department of Forestry, Oregon Watershed Enhancement Board, US Bureau of Land Management, US Forest Service, Nez Perce Tribe, Benton SWCD, Washington County and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. The third publication of the OFPBDS dataset (Version 3) complies with version 1.1 of the data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. Linear referencing attributes for the Pacific Northwest Hydrography have been retained in this version of the publication datasets, however they are no longer part of the data standard and will be removed from the next dataset publication version. Version 3 of the OFPBDS dataset contains over 30,000 barrier features from seventeen separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2011, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed (e.g. dam removals and culvert replacements) will be published simultaneously with version 3 of the OFPBDS dataset. The OFPBDS database does not represent a comprehensive record of fish passage barriers in Oregon. Attributes (including key attributes such as fish passage status) are often incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset comprehensive, current and accurate. Fish passage status is a key attribute. Many barrier features - including all ODOT barriers - have an unknown passage status. For other features, the passage status may have changed since documented. Note that this metadata file is best viewed in ArcCatalog with the FGDC Classic Stylesheet. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife, Oregon Department of Transportation, Oregon Department of Water Resources, Oregon Department of Forestry, Oregon Watershed Enhancement Board, US Bureau of Land Management, US Forest Service, Nez Perce Tribe, Benton SWCD, Washington County and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Description: This product is for informational purposes only; the plats were drawn in GIS based on the legal descriptions of each plat. These drawings are NOT SURVEY QUALITY. They are drawn to best ability at the time. Use with caution.
Description: This product is for informational purposes only; the plats were drawn in GIS based on the legal descriptions of each plat. These drawings are NOT SURVEY QUALITY. They are drawn to best ability at the time. Use with caution.
Description: This dataset was developed for coarse spatial understanding of clam beds used by recreational users. The target audience is recreational users, resource managers, and estuarine scientists. It is currenly most often used by recreational users looking for clamming areas.We developed this spatial dataset using a combination of data from clamming creel projects, local agency knowledge, and prior reports. Polygons are not rigirously derived from standardized datasets.
POLY_CLASS
(
type: esriFieldTypeString, alias: Class of polygon feature, length: 50
, Coded Values:
[Complex: Complex of colonies and/or subcolonies]
, [Group: Group of individual rocks or sites]
, [Area: Extent of breeding area at single rock or site]
)
Description: This layer is a composite of several years of aerial kelp surveys off Oregon. A coastwide survey was conducted in 1990, reef-specific surveys at 5 south coast reefs (Blanco, Orford, Redfish, Humbug and Rogue reefs) were conducted for 4 years from 1996 – 1999, and a regional survey was conducted from Cape Arago south to the California border in 2010. Three distinct survey designs were implemented for acquiring kelp bed imagery over two decades of kelp surveys. The target species was bull kelp, Nereocystis luetkeana. In 1990, the kelp survey was contracted to Ecoscan Resources Data. Kelp beds were photographed with black and white near infrared slide film. Interpretation methods included the application of a 50 meter radius to account for plant growth, and plants within 100 meters of each other (within 100 meters of the 50 meter radius) were included in a kelp polygon. ODFW designed the kelp surveys for 5 south coast reefs from 1996-1999. Specifications were established that ensured continuity between years.Bergman Photographic, Inc was contracted to acquire the imagery. Kelp beds were photographed using infrared photographic print film. Kelp beds were delineated without the addition of a 50 meter radius around kelp beds as was done with the 1990 data. In Oregon, the giant kelp, Macrocystis sp. is found only at Cape Arago. Both the 1990 and 2010 surveys covered Cape Arago, however only the 1990 survey delineation canopy for the giant kelp. In 2010, digital multispectral imagery of kelp canopy in southern Oregon was acquired and gridded at 1m resolution. The geographic coverage of the aerial survey is from Cape Arago (located near Coos Bay) to the Oregon-California border. Purpose The purpose of this survey was to update ODFW's kelp biomass surveys of the mid 1990's .This layer shows the spatial extent of kelp canopy in Oregon based on 5 years of kelp surveys.
Copyright Text: Oregon Dept. of Fish and Wildlife, Marine Resources Program
Description: This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands Project Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.
Color: [112, 68, 137, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. The third publication of the OFPBDS dataset (Version 3) complies with version 1.1 of the data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. Linear referencing attributes for the Pacific Northwest Hydrography have been retained in this version of the publication datasets, however they are no longer part of the data standard and will be removed from the next dataset publication version. Version 3 of the OFPBDS dataset contains over 30,000 barrier features from seventeen separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2011, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed (e.g. dam removals and culvert replacements) will be published simultaneously with version 3 of the OFPBDS dataset. The OFPBDS database does not represent a comprehensive record of fish passage barriers in Oregon. Attributes (including key attributes such as fish passage status) are often incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset comprehensive, current and accurate. Fish passage status is a key attribute. Many barrier features - including all ODOT barriers - have an unknown passage status. For other features, the passage status may have changed since documented. Note that this metadata file is best viewed in ArcCatalog with the FGDC Classic Stylesheet. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife, Oregon Department of Transportation, Oregon Department of Water Resources, Oregon Department of Forestry, Oregon Watershed Enhancement Board, US Bureau of Land Management, US Forest Service, Nez Perce Tribe, Benton SWCD, Washington County and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Description: The Oregon Fish Passage Barrier Data Standard (OFPBDS) dataset contains barriers to fish passage in Oregon watercourses. Barriers include the following types of natural or artificial structures: bridges, cascades, culverts, dams, debris jams, fords, natural falls, tide gates, and weirs. The OFPBDS dataset does not include structures which are not associated with in-stream features (such as dikes, levees or berms). Barriers are structures which do, or potentially may, impede fish movement and migration. Barriers can be known to cause complete or partial blockage to fish passage, or they can be completely passable, or they may have an unknown passage status. The third publication of the OFPBDS dataset (Version 3) complies with version 1.1 of the data standard. New optional attributes have been added to describe fish passage barrier feature modifications, to describe supplementary information (via a comments field) and also to linear reference the barrier features to the National Hydrography Dataset. Linear referencing attributes for the Pacific Northwest Hydrography have been retained in this version of the publication datasets, however they are no longer part of the data standard and will be removed from the next dataset publication version. Version 3 of the OFPBDS dataset contains over 30,000 barrier features from seventeen separate sources including: Oregon Department of Fish and Wildlife (ODFW), Oregon Department of Transportation (ODOT), Oregon Department of Water Resources (OWRD), Oregon Department of Forestry (ODF), Oregon Watershed Enhancement Board (OWEB), US Bureau of Land Management (BLM), US Forest Service, Nez Perce Tribe, Benton SWCD, Washington county and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins. The Data Steward obtained fish passage barrier data from multiple data originators between 2008 and 2011, collaborated with them to develop inclusion / exclusion criteria and dataset specific crosswalks for converting data from its original data structure to the structure of the OFPBDS. The data were then converted into the OFPBDS format and analyzed for duplication with existing OFPBDS barrier features. Where duplicates were identified, depending upon the scenario, one feature was either chosen over the other or in some cases attributes from different sources are combined. Source information is retained for each feature. The data were then loaded into the OFPBDS database. Barrier features were linear referenced (Framework Hydro only which is outside of the standard) and the corresponding optional attribute elements were populated. The data conversion, duplication reconciliation and linear referencing protocols are documented in the Oregon Fish Passage Barrier Data Management Plan. A separate dataset containing fish passage barrier features that have been completely removed (e.g. dam removals and culvert replacements) will be published simultaneously with version 3 of the OFPBDS dataset. The OFPBDS database does not represent a comprehensive record of fish passage barriers in Oregon. Attributes (including key attributes such as fish passage status) are often incomplete. Consistency in attribution also varies among data originators. Field verification of barrier features and their attributes will be an important component to making this dataset comprehensive, current and accurate. Fish passage status is a key attribute. Many barrier features - including all ODOT barriers - have an unknown passage status. For other features, the passage status may have changed since documented. Note that this metadata file is best viewed in ArcCatalog with the FGDC Classic Stylesheet. Documentation for the OFPBDS can be found online at http://www.oregon.gov/DAS/EISPD/GEO/docs/bioscience/OregonFishPassageBarrierDataStandardv1dot1.pdf.
Copyright Text: Barrier features originate primarily from the following agencies: Oregon Department of Fish and Wildlife, Oregon Department of Transportation, Oregon Department of Water Resources, Oregon Department of Forestry, Oregon Watershed Enhancement Board, US Bureau of Land Management, US Forest Service, Nez Perce Tribe, Benton SWCD, Washington County and watershed councils representing the Rogue, Umpqua, Siuslaw, Santiam, Calapooia, Clackamas and Scapoose basins.
Color: [112, 68, 137, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: Oregon Fish Habitat Distribution.These data describe areas of suitable habitat believed to be used currently or historically by wild, natural, and/or hatchery fish populations. The term "currently" is defined as within the past five reproductive cycles. Historical habitat includes suitable habitat that fish no longer access and will not access in the foreseeable future without human intervention. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually. These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Historical habitat distribution data are now within the scope of the standard and are identified via the habitat use (fhdUseType) attribute. Historical habitats are only identified outside of currently accessible habitat and are not comprehensive.Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are now mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2014.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach, David L. Bradford. Numerous fisheries biologists from ODFW as well as other natural resource agencies and tribes have contributed toward the development of these data. Data originator names are attributed at the feature level.
Description: Oregon Fish Habitat Distribution.These data describe areas of suitable habitat believed to be used currently or historically by wild, natural, and/or hatchery fish populations. The term "currently" is defined as within the past five reproductive cycles. Historical habitat includes suitable habitat that fish no longer access and will not access in the foreseeable future without human intervention. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually. These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Historical habitat distribution data are now within the scope of the standard and are identified via the habitat use (fhdUseType) attribute. Historical habitats are only identified outside of currently accessible habitat and are not comprehensive.Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are now mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2013.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach, David L. Bradford. Numerous fisheries biologists from ODFW as well as other natural resource agencies and tribes have contributed toward the development of these data. Data originator names are attributed at the feature level.
Description: Oregon Fish Habitat Distribution.These data describe areas of suitable habitat believed to be used currently or historically by wild, natural, and/or hatchery fish populations. The term "currently" is defined as within the past five reproductive cycles. Historical habitat includes suitable habitat that fish no longer access and will not access in the foreseeable future without human intervention. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually. These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Historical habitat distribution data are now within the scope of the standard and are identified via the habitat use (fhdUseType) attribute. Historical habitats are only identified outside of currently accessible habitat and are not comprehensive.Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are now mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2012.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach, David L. Bradford. Numerous fisheries biologists from ODFW as well as other natural resource agencies and tribes have contributed toward the development of these data.
Description: Oregon Fish Habitat Distribution.These data describe areas of suitable habitat believed to be used currently or historically by wild, natural, and/or hatchery fish populations. The term "currently" is defined as within the past five reproductive cycles. Historical habitat includes suitable habitat that fish no longer access and will not access in the foreseeable future without human intervention. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually. These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Historical habitat distribution data are now within the scope of the standard and are identified via the habitat use (fhdUseType) attribute. Historical habitats are only identified outside of currently accessible habitat and are not comprehensive.Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are now mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2014.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach, David L. Bradford. Numerous fisheries biologists from ODFW as well as other natural resource agencies and tribes have contributed toward the development of these data. Data originator names are attributed at the feature level.
Description: The Pacific lamprey has inhabited the rivers, streams and coastal waters of the west for 350 million years (BPA, 2005). These data describe areas of suitable habitat currently and historically used by Pacific lamprey populations. Pacific lamprey, Lampetra tridentata, (more recently identified as Entosphenus tridentatus), are native to the Pacific coast from Baja California to the Bering Sea. They are anadromous, migrating from their natal stream to the ocean and back, but unlike salmon, Pacific lamprey spend well over half of their total life cycle in freshwater. The Pacific lamprey was listed as an Oregon State sensitive species in 1993 and in 1996 was protected through restriction of harvest (ODFW 2006). These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf The term "currently" is defined as within the past five reproductive cycles. This information is based on sampling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually.Habitat distribution data are mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1990 to 2011.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach
Description: These data describe areas of suitable habitat believed to be used currently and historically by redband trout populations. Columbia River redband trout, Oncorhynchus mykiss gairdneri, a subspecies of rainbow trout, Oncorhynchus mykiss, is native to the Fraser and Columbia River drainages, east of the Cascade Mountains to barrier falls on the Pend Oreille, Spokane, Snake and Kootenai rivers (Allendorf et al. 1980; Behnke 1992). Northern Great Basin redband trout, Oncorhynchus mykiss newberrii, are found in the closed basins of south-central Oregon as well as the Upper Klamath Lake basin. While Upper Klamath Lake now drains to the ocean, redband trout in the basin had ancestors that came from interior connections to the Great Basin and not from connections to the ocean (Behnke 1992).Redband trout, for the purposes of habitat distribution mapping, are generally defined as stream-resident O. mykiss gairdneri; migration is confined within their natal stream or watershed while steelhead, or the anadromous life form of O.mykiss gairdneri, migrate from their natal stream to the ocean and back. It is recognized, that while redband and steelhead habitat distribution datasets are published separately, overlapping areas represent the same subspecies.The term "currently" is defined as within the past five reproductive cycles. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually.These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2011.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach
Description: Oregon Fish Habitat Distribution.These data describe areas of suitable habitat believed to be used currently or historically by wild, natural, and/or hatchery fish populations. The term "currently" is defined as within the past five reproductive cycles. Historical habitat includes suitable habitat that fish no longer access and will not access in the foreseeable future without human intervention. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually. These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Historical habitat distribution data are now within the scope of the standard and are identified via the habitat use (fhdUseType) attribute. Historical habitats are only identified outside of currently accessible habitat and are not comprehensive.Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are now mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2014.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach, David L. Bradford. Numerous fisheries biologists from ODFW as well as other natural resource agencies and tribes have contributed toward the development of these data. Data originator names are attributed at the feature level.
Description: Oregon Fish Habitat Distribution.These data describe areas of suitable habitat believed to be used currently or historically by wild, natural, and/or hatchery fish populations. The term "currently" is defined as within the past five reproductive cycles. Historical habitat includes suitable habitat that fish no longer access and will not access in the foreseeable future without human intervention. This information is based on sampling, the best professional opinion of Oregon Dept. of Fish and Wildlife or other natural resources agency staff biologists or modeling (see the fhdBasis field). Due to natural variations in run size, water conditions, or other environmental factors, some habitats identified may not be used annually. These data now comply with the Oregon Fish Habitat Distribution Data Standard that was adopted by the Oregon Geographic Information Council in February 2011. The Standard document can be found at: http://gis.oregon.gov/DAS/EISPD/GEO/standards/docs/OregonFishHabitatDistributionDataStandardv2.pdf Historical habitat distribution data are now within the scope of the standard and are identified via the habitat use (fhdUseType) attribute. Historical habitats are only identified outside of currently accessible habitat and are not comprehensive.Key features of the Oregon Fish Habitat Distribution Data include: species, run, life history, habitat use, origin, production, the basis for each record, originator name, originator entity and reference. Habitat distribution data are now mapped at a 1:24,000 scale statewide and are based on the Pacific Northwest Framework Hydrography dataset. The data are made available as GIS files in both shapefile and ESRI geodatabase format. The data were developed over an extensive time period ranging from 1996 to 2014.
Copyright Text: Oregon Department of Fish and Wildlife, Jon K. Bowers, Ruth Schellbach, David L. Bradford. Numerous fisheries biologists from ODFW as well as other natural resource agencies and tribes have contributed toward the development of these data. Data originator names are attributed at the feature level.
Color: [38, 115, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: The MPA Inventory is a comprehensive catalog that provides detailed information for existing marine protected areas in the United States. The inventory provides geospatial boundary information (in polygon format) and classification attributes that seek to define the conservation objectives, protection level, governance and related management criteria for all sites in the database. The comprehensive inventory of federal, state and territorial MPA sites provides governments and stakeholders with access to information to make better decisions about the current and future use of place-based conservation. The information also will be used to inform the development of the national system of marine protected areas as required by Executive Order 13158.
Copyright Text: NOAA Marine Protected Areas Center in joint effort with the US Department of the Interior
Color: [115, 76, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands Project Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.
Description: These data identify (in general) the areas where critical habitat for the Taylor's Checkerspot Butterfly (Euphydryas editha taylori) occur. Maps published in the Federal Register in 2013.
Description: This layer contains critical habitat polygons designated by the USFWS for the Northern Spotted Owl (Strix occidentalis caurina) in November 2012.
Copyright Text: Natural Resource Geospatial Geodata Systems Development GIS / Information Services and U.S. Fish and Wildlife Service
Description: A precise geographical area within which placement of dredged material occurs. This feature class is a compilation of geographic data digitized from various sources.
Copyright Text: U.S. Army Corps of Engineers, Portland District
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Light Font Style: normal Font Weight: normal Font Decoration: none
Description: The Oregon Active Fault Element and Template is a feature class and database of active faults compilied by the Oregon Department of Geology and Mineral Industries (DOGAMI) for inclusion in the State Geothermal Project. The Oregon Active Fault Element and Template is a compilation of Oregon's active faults in the form of a personal geodatabase, which stores tabular data in a Microsoft Access .mdb file, and an associated line feature class for spatial/geometric data. Active faults can serve as important pathways for geothermal energy/fluids and used to investigate areas which may have geothermal potential. Each active fault in the dataset is entered as a record (row) with fields (columns) containing information such as fault age, length, name, geologic unit, movement data including rate of movement, general description, and other data about the fault feature.These data are a compilation of 3,114 records from two primary fault databases; one from U.S. Geological Survey Quaternary Fault Database and the other from DOGAMI's Oregon Geologic Data Compilation (v5).
Copyright Text: DOGAMI used grant funding awarded as a sub-proposal for this work. The award was issued by the Arizona Geological Survey (AZGS) through the U.S. Department of Energy (US DoE) Geothermal Technologies Program. US DoE awarded funding to AZGS for the American Recovery and Reinvestment Act, Public Law 111-5, US DoE Number: DE-FOA-0000109, Topic Area 3: Geothermal Data Development, Collection, and Maintenance. The Content Model for Active Faults was developed by AZGS to submit/report data to the State Geothermal Project of the American Association of State Geological Surveys' (AASG) for inclusion in the National Geothermal Data System (NGDS). DOGAMI compilied this dataset from its Oregon Geologic Data Compilation and the U.S. Geological Survey's Quaternary Fault Database; see Citation Section.
Description: This map uses the methods of HAZUS-MH MR4 to create a new landslide suceptibility map for Oregon. HAZUS assigns susceptibility classes based on the combination of three geologic material classes and six slope classes. The geologic material classes were dervied from teh Oregn Geologic Data Compilation (OGDC v5) the Sttewide Landsldie Information Layer for Oregon (SLIDO-2), and several other published geologic maps. Slope data was derived from a mosaic of all Oregon Lidar Consortium lidar topography available at teh time and the USGS 30 m DEM. The methods and data used t make this map are described in detail in : Madin, I.P., and Burns, W.J., 2013, Ground motion, ground deformation, tsunami inundation, coseismic subsidence, and damage potential maps for the 2012 Oregon Resilience Plan for Cascadia Subduction Zone Earthquakes; Oregon Department of Geology and Mineral Industries Open-File Report O-13-06.
Copyright Text: Ian P. Madin, William J. Burns, Oregon Department of Geology and Mineral Industries
Description: This map uses the methods of HAZUS-MH MR4 (FEMA 2011 in references) to create new liquefaction suceptibility data for Oregon. HAZUS assigns susceptibility classes based on geology. For this map, the geology was primarily taken from OGDC 5 (Ma and others, 2009, in refernces) and SLIDO 2 (Burns and others, 2011 in references) with some coming from published liquefaction studies. The methods and data used to make this map are described in detail in : Madin, I.P., and Burns, W.J., 2013, Ground motion, ground deformation, tsunami inundation, coseismic subsidence, and damage potential maps for the 2012 Oregon Resilience Plan for Cascadia Subduction Zone Earthquakes; Oregon Department of Geology and Mineral Industries Open-File Report O-13-06.
Copyright Text: Ian P. Madin, William J. Burns, Oregon Department of Geology and Mineral Industries
Description: This map uses the methods of HAZUS-MH MR4 (FEMA 2011 in references) to create new liquefaction suceptibility data for Oregon. HAZUS assigns susceptibility classes based on geology. For this map, the geology was primarily taken from OGDC 5 (Ma and others, 2009, in refernces) and SLIDO 2 (Burns and others, 2011 in references) with some coming from published liquefaction studies. The methods and data used to make this map are described in detail in : Madin, I.P., and Burns, W.J., 2013, Ground motion, ground deformation, tsunami inundation, coseismic subsidence, and damage potential maps for the 2012 Oregon Resilience Plan for Cascadia Subduction Zone Earthquakes; Oregon Department of Geology and Mineral Industries Open-File Report O-13-06.
Copyright Text: Ian P. Madin, William J. Burns, Oregon Department of Geology and Mineral Industries
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The polygons in this shapefile represent the various tsunami evacuation brochure boundaries/extents for the respective communities along the Oregon coast. The brochures that can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org
Copyright Text: OR Dept. of Geology & Mineral Industries - Taylore Wille
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The polygons in this shapefile represent the various tsunami evacuation brochure boundaries/extents for the respective communities along the Oregon coast. The brochures that can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org
Copyright Text: OR Dept. of Geology & Mineral Industries - Taylore Wille
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The polygons in this shapefile represent the TIM's boundaries/extents for the Oregon coast. This feature class can also be used to identify which tsunami project area and grid model contains the original tsunami data for the tsunami scenarios shown on the respective TIM.
Copyright Text: OR Dept. of Geology & Mineral Industries - Taylore Wille, Kaleena Hughes, Sean Pickner
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The polygons in this shapefile represent the TIM's boundaries/extents for the Oregon coast. This feature class can also be used to identify which tsunami project area and grid model contains the original tsunami data for the tsunami scenarios shown on the respective TIM.
Copyright Text: OR Dept. of Geology & Mineral Industries - Taylore Wille, Kaleena Hughes, Sean Pickner
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The assembly area locations depicted in this shapefile are those shown on the tsunami evacuation brochures which can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org These locations were chosen by local government representatives following a thorough review of the tsunami inundation for their respective community. The goal was to find locations on high ground outside of the XXL tsunami scenario where visitors and residents could assemble temporarily following a Cascadia Subduction Zone (CSZ) earthquake. Assembly areas are not evacuation centers. Evacuation centers are established after a disaster when proper officials have determined the location is a structurally safe and can provide necessary amenities for short- or long- term assembly.Assembly areas do not necessarily have amenities like electricity or potable water and can be an outside gathering place with limited or no shelter. These locations are designated for life safety purposes only.
Copyright Text: Varies per community. Generally, the County emergency manager, fire chief, police chief, sheriff's office deputy, city/county planner, and CERT leader, or their designated officials, were present at evacuation brochure meetings where these assembly area locations were determined. Other representatives included: state and federal park/wildlife, local school district, city/county public works, GIS coordinators, and port representatives.
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The assembly area locations depicted in this shapefile are those shown on the tsunami evacuation brochures which can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org These locations were chosen by local government representatives following a thorough review of the tsunami inundation for their respective community. The goal was to find locations on high ground outside of the XXL tsunami scenario where visitors and residents could assemble temporarily following a Cascadia Subduction Zone (CSZ) earthquake. Assembly areas are not evacuation centers. Evacuation centers are established after a disaster when proper officials have determined the location is a structurally safe and can provide necessary amenities for short- or long- term assembly.Assembly areas do not necessarily have amenities like electricity or potable water and can be an outside gathering place with limited or no shelter. These locations are designated for life safety purposes only.
Copyright Text: Varies per community. Generally, the County emergency manager, fire chief, police chief, sheriff's office deputy, city/county planner, and CERT leader, or their designated officials, were present at evacuation brochure meetings where these assembly area locations were determined. Other representatives included: state and federal park/wildlife, local school district, city/county public works, GIS coordinators, and port representatives.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The critical facility locations depicted in this shapefile are those shown on the tsunami evacuation brochures and on the TIM's which can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org, The features represented are: public school, hospital, airport, fire station, police station, city hall, bridge, sheriff office, and tsunami siren.
Copyright Text: OR Dept. of Geology and Mineral Industries: Taylore Wille, Kaleena Hughes, and Sean Pickner
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The critical facility locations depicted in this shapefile are those shown on the tsunami evacuation brochures and on the TIM's which can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org, The features represented are: public school, hospital, airport, fire station, police station, city hall, bridge, sheriff office, and tsunami siren.
Copyright Text: OR Dept. of Geology and Mineral Industries: Taylore Wille, Kaleena Hughes, and Sean Pickner
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. The evacuation zones are the local and distant tsunami scenarios shown on the tsunami evacuation brochures which can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org The local tsunami evacuation zone is equal to the XXL tsunami scenario. The distant tsunami evacuation zone is equal to the AKMax tsunami scenario. These are the worst case scenarios for a local and distant earthquake/tsunami event. These polygons represent the evacuation zones for the entire Oregon coast.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile is a supplemental file to the primary tsunami inundation scenarios released with this publication. It contains polygon features representing high ground on the tsunami evacuation brochures which can be found on the Oregon Tsunami Clearinghouse web site: www.oregontsunami.org This shapefile was created for cartographic purposes only.
Copyright Text: Oregon Department of Geology and Mineral Industries - Taylore Wille
Description: This shapefile represents the AK64 tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile represents the AKMax tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile represents the Small (SM1) tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile represents the Medium (M1) tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile represents the Large (L1) tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile represents the Extra-Large (XL1) tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Description: This shapefile represents the Extra-Extra-Large (XXL1) tsunami inundation scenario for the Oregon coast. See the accompanying text report for more information.
Copyright Text: George R. Priest (1), Robert C. Witter (2), Y. Joseph Zhang (3), Kelin Wang (4), Chris Goldfinger (5), Laura L. Stimely (1), John English (6), Sean G. Pickner (7), Kaleena L.B. Hughes (7), Taylore E. Wille (7), and Rachel L. Smith (7)
1) Oregon Department of Geology and Mineral Industries, Coastal Field Office, 313 SW 2nd Street, Suite D, Newport, Oregon 97365
2) U.S. Geological Survey, Alaska Science Center, 4210 University Dr., Anchorage, Alaska, 99508
3) Virginia Institute of Marine Science, Center for Coastal Resources Management, 1375 Greate Road, P.O. Box 1346, Gloucester Point, VA 23062
4) Geological Survey of Canada, Pacific Geoscience Centre, Room 4714m, 9860 West Saanich Road, Sidney, British Columbia, Canada V8L 4B2
5) College of Earth, Ocean and Atmospheric Sciences, Oregon State University, Ocean Admin. Bldg. 104, Corvallis, Oregon 97331
6) City of Hillsboro, Information Services, Civic Center 150 E. Main Street, Hillsboro, Oregon, 97123
7) Oregon Department of Geology and Mineral Industries, 800 NE Oregon Street, #28, Suite 965, Portland, OR 97232
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [230, 0, 169, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Description: PLSSFirstDivision: This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.
Description: PLSSFirstDivision: This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 16 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 16 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 16 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [194, 158, 215, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 14 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [78, 78, 78, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 22 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [78, 78, 78, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 22 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [130, 130, 130, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementAboveAlong Label Expression: [Name] Use Coded Values: true Symbol:
Color: [47, 140, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementAboveAlong Label Expression: [Name] Use Coded Values: true Symbol:
Color: [47, 140, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementAboveAlong Label Expression: [Name] Use Coded Values: true Symbol:
Color: [47, 140, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
Color: [130, 130, 130, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
FCode: Coded Values:
[53700: Area of Complex Channels]
ID: 398
Name: Lock Chamber
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[39800: Lock Chamber]
ID: 454
Name: Special Use Zone
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45400: Special Use Zone]
, [45402: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Abandoned]
, [45401: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Operational]
, ...2 more...
ID: 455
Name: Spillway
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45500: Spillway]
ID: 362
Name: Flume
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[36200: Flume]
ID: 343
Name: DamWeir
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[34300: Dam/Weir]
, [34305: Dam/Weir: Construction Material = Earthen]
, [34306: Dam/Weir: Construction Material = Nonearthen]
ID: 485
Name: Water IntakeOutflow
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[48500: Water Intake/Outflow]
ID: 307
Name: Area to be Submerged
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[30700: Area to be Submerged]
FCode: Coded Values:
[53700: Area of Complex Channels]
ID: 398
Name: Lock Chamber
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[39800: Lock Chamber]
ID: 454
Name: Special Use Zone
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45400: Special Use Zone]
, [45402: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Abandoned]
, [45401: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Operational]
, ...2 more...
ID: 455
Name: Spillway
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45500: Spillway]
ID: 362
Name: Flume
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[36200: Flume]
ID: 343
Name: DamWeir
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[34300: Dam/Weir]
, [34305: Dam/Weir: Construction Material = Earthen]
, [34306: Dam/Weir: Construction Material = Nonearthen]
ID: 485
Name: Water IntakeOutflow
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[48500: Water Intake/Outflow]
ID: 307
Name: Area to be Submerged
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[30700: Area to be Submerged]
FCode: Coded Values:
[53700: Area of Complex Channels]
ID: 398
Name: Lock Chamber
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[39800: Lock Chamber]
ID: 454
Name: Special Use Zone
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45400: Special Use Zone]
, [45402: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Abandoned]
, [45401: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Operational]
, ...2 more...
ID: 455
Name: Spillway
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45500: Spillway]
ID: 362
Name: Flume
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[36200: Flume]
ID: 343
Name: DamWeir
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[34300: Dam/Weir]
, [34305: Dam/Weir: Construction Material = Earthen]
, [34306: Dam/Weir: Construction Material = Nonearthen]
ID: 485
Name: Water IntakeOutflow
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[48500: Water Intake/Outflow]
ID: 307
Name: Area to be Submerged
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[30700: Area to be Submerged]
Color: [137, 90, 68, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Calibri Font Style: normal Font Weight: normal Font Decoration: none
FCode: Coded Values:
[53700: Area of Complex Channels]
ID: 398
Name: Lock Chamber
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[39800: Lock Chamber]
ID: 454
Name: Special Use Zone
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45400: Special Use Zone]
, [45402: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Abandoned]
, [45401: Special Use Zone: Special Use Zone Type = Dump Site; Operational Status = Operational]
, ...2 more...
ID: 455
Name: Spillway
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[45500: Spillway]
ID: 362
Name: Flume
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[36200: Flume]
ID: 343
Name: DamWeir
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[34300: Dam/Weir]
, [34305: Dam/Weir: Construction Material = Earthen]
, [34306: Dam/Weir: Construction Material = Nonearthen]
ID: 485
Name: Water IntakeOutflow
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[48500: Water Intake/Outflow]
ID: 307
Name: Area to be Submerged
Domains:
Resolution: Inherited
Elevation: Inherited
FCode: Coded Values:
[30700: Area to be Submerged]
Description: Maritime limits for the United States are measured from the U.S. baseline, recognized as the low-water line along the coast as marked on NOAA's nautical charts in accordance with the articles of the Law of the Sea. The baseline and related maritime limits are reviewed and approved by the interagency U.S. Baseline Committee. The primary purpose of this dataset is to update the official depiction of these maritime limits and boundaries on NOAA's nautical charts. The Office of Coast Survey depicts on its nautical charts the territorial sea (12 nautical miles), contiguous zone (24nm), and exclusive economic zone (200nm, plus maritime boundaries with adjacent/opposite countries). U.S. maritime limits are ambulatory and subject to revision based on accretion or erosion of the charted low water line. To ensure you are up-to-date and for more information about U.S. Maritime Limits and Boundaries, see http://www.nauticalcharts.noaa.gov/csdl/mbound.htm.For the full FGDC metadata record, see http://www.ncddc.noaa.gov/approved_recs/nos_de/ocs/ocs/ocs/MB_ParentDataset.html.Coordinates for the US/Canada international boundary, on land and through the Great Lakes, are managed by the International Boundary Commission. These boundaries are included with this dataset for continuity.
Copyright Text: National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Coast Survey (OCS)
Description: Maritime limits for the United States are measured from the U.S. baseline, recognized as the low-water line along the coast as marked on NOAA's nautical charts in accordance with the articles of the Law of the Sea. The baseline and related maritime limits are reviewed and approved by the interagency U.S. Baseline Committee. The primary purpose of this dataset is to update the official depiction of these maritime limits and boundaries on NOAA's nautical charts. The Office of Coast Survey depicts on its nautical charts the territorial sea (12 nautical miles), contiguous zone (24nm), and exclusive economic zone (200nm, plus maritime boundaries with adjacent/opposite countries). U.S. maritime limits are ambulatory and subject to revision based on accretion or erosion of the charted low water line. To ensure you are up-to-date and for more information about U.S. Maritime Limits and Boundaries, see http://www.nauticalcharts.noaa.gov/csdl/mbound.htm.For the full FGDC metadata record, see http://www.ncddc.noaa.gov/approved_recs/nos_de/ocs/ocs/ocs/MB_ParentDataset.html.Coordinates for the US/Canada international boundary, on land and through the Great Lakes, are managed by the International Boundary Commission. These boundaries are included with this dataset for continuity.
Copyright Text: National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), Office of Coast Survey (OCS)
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Min. Scale: 50000.0 Max. Scale: 24001.0 Label Placement: esriServerLinePlacementCenterAlong Label Expression: [GNIS_Name] Use Coded Values: true Symbol:
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementCenterAlong Label Expression: [GNIS_Name] Use Coded Values: true Symbol:
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerLinePlacementCenterAlong Label Expression: [GNIS_Name] Use Coded Values: true Symbol:
Color: [102, 119, 205, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Color: [205, 170, 102, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [205, 170, 102, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [205, 170, 102, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: baseline Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Color: [166, 141, 99, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 18 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none