Washington Department of Natural Resources Local Unit. These areas are administrative subunits of a Washington Department of Natural Resources District.WA DNR Units Metadata

The NDMPL (Washington State Non-Department of Natural Resources Major Public Lands) data contains ownership parcels for Federal, State (excluding WA DNR), County and City lands within the State of Washington. It also includes Tribal administrative boundaries. The NDMPL data layer is a polygon dataset and does not contain arc attribute information for ownership boundaries. This data is not connected to WA DNR's Cadastre layers (these data include WADNR ownership, Public Land Survey System and other cadastral data). As updates are made to Cadastre layers, they may not be reflected in NDMPL. Click to download This layer was last updated October 2021.

Click to downloadClick for metadataService URL: https://gis.dnr.wa.gov/site2/rest/services/Public_Forest_Practices/WADNR_PUBLIC_FP_Unstable_Slopes/MapServer/3The siteclass data layer was created for use in implementing Forest Practices' Riparian Management Rules. (See WAC 222-30-021 and 222-30-022.)

The siteclass data layer was derived from the DNR soils data layer's site index codes and major tree species codes for western and eastern Washington soils contained in the layer's Soils-Main table and Soils-Pflg (private forest land grade) table. Site index ranges in the Soils_PFLG took precedence over site index ranges in the Soils-Main table where data existed.The siteclass data layer was created for use in implementing new ForestPractices' Riparian Management Rules. (See WAC 222-30-021 and 222-30-022.) The siteclass information was derived from the DNR soils data layer's site indexcodes and major tree species codes for western and eastern Washington soilscontained in the layer's Soils-Main table and Soils-Pflg (private forest landgrade) table. Site index ranges in the Soils_PFLG took precedence over siteindex ranges in the Soils-Main table where data existed.Siteclass codes as derived from the soil survey:For Western Washington, the 50 year site index is used SITECLASS SITE INDEX RANGE I 137+ II 119-136 III 97-118 IV 76-96 V 1-75For Eastern Washington, the 100 year site index is used SITECLASS SITE INDEX RANGE I 120+ II 101-120 III 81-100 IV 61-80 V 1-60In addition to the coding scheme above, the following codes were added forrule compliance: SITECLASS DESCRIPTION 6 (Red Alder) The soils major species code indicated Red Alder 7 (ND/GP) No data), NA, or gravel pit 8 (NC/MFP) Non-commercial or marginal commercial forest land 9 (WAT) Water body(Rule note: If the site index does not exist or indicates red alder,noncommercial, or marginally commercial species, the following apply:If the whole RMZ width is within those categories, use site class V.If those categories occupy only a portion of the RMZ width, then use thesite index for conifer in the adjacent soil polygon.)WADNR SOILS LAYER INFORMATION LAYER: SOILS GEN.SOURCE: State soils mapping program CODE DOCUMENT: State soil surveys CONTACT: NA COVER TYPE: Spatial polygon coverage DATA TYPE: Primary data Information for the SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five year mapping program completed in 1980 for the purpose of forest land taxation. It was funded by the Washington State Department of Revenue in cooperation with the Department of Natural Resources, Soil Conservation Service (SCS), USDA Forest Service and Washington State University. State and private lands which had the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soil survey project, agricultural and non- commercial forest lands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. Approximately 1100 townships wholly or partially contain digitized soils data (2101 townships would provide complete coverage of the state of Washington). SOILS data are currently stored in the Polygon Attribute Table (.PAT) and INFO expansion files. COORDINATE SYSTEM: WA State Plane South Zone (5626) (N. zone converted to S. zone) COORDINATE UNITS: Feet HORIZONTAL DATUM: NAD27 PROJECTION NAME: Lambert Conformal Conic **** MAJOR CODES USED FOR SITECLASS DATA*****PFLG DATA: ITEM: PFLG.MAJ.SPEC TITLE: Potential major tree species for given soil FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 3 3 C 0 0 0 CODE TABLE OR VALUE RANGE: SOIL.MAJ.SPEC.CODE DESCRIPTION: Potentially major tree species for a given soil type. The data carried by this item describes a major commercial tree species that could potentially grow on a specific soil type as identified in the Private Forest Land Grading program (PFLG). Non-tree codes are also included to map non-soil ground cover, e.g. water, gravel pits. ITEM: PFLG.SITE.INDEX TITLE: Mean site index calc.from trees on given soil FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 3 3 I 0 0 0 CODE TABLE OR VALUE RANGE: 0-200 DESCRIPTION: Site index data collected for the Private Forest Land Grading soils program (PFLG). It is a designation of the quality of a forest site based on the height of of the tallest trees (dominant and co-dominant trees) in a stand at an arbitrarily chosen age. Usually the age chosen is 50 or 100 years. For example, if the average height attained by the tallest trees in a fully stocked stand at the age of 50 years is 75 feet, the site index is 75 feet. Westside site conditions are estimated by using an index age of 50 years, while eastside site conditions are estimated by using an index age of 100 years.--------------------------------------------------------------------SOILS-MAIN DATA: CODE TABLE NAME: SOIL.MAJ.SPEC.CODE ----------------------------------------------------------------------------- CODE MAP/REPORT MAP CODE DESCRIPTION LABEL SYMB --------- ------------ ---- -------------------------------------------------- AF ALPINE FIR 0 Subalpine fir DF DOUGLAS FIR 0 Douglas fir GF GRAND FIR 0 Grand fir GP GRAVEL PIT 0 Gravel pit LP LODGEPOLE PN 0 Lodgepole pine MFP MAR FOR PROD 0 Marginal forest productivity NA N/A 0 Not applicable NC NON-COMMERC 0 Non-commercial ND NO DATA 0 No data PP PONDEROSA PN 0 Ponderosa pine RA RED ALDER 0 Red alder WAT WATER 0 Water WH W HEMLOCK 0 Western hemlock WL W LARCH 0 Western larch WP W WHITE PINE 0 Western white pine ITEM: SITE.INDEX.SIDE TITLE: Indicates 100 yr or 50 yr soil site index FORMAT: INPUT OUTPUT DATA DECIMAL ARRAY ARRAY WIDTH WIDTH TYPE PLACES OCCUR. INDEX ------------------------------------------------- 1 1 C 0 0 0 CODE FILE OR VALUE RANGE: SITE.INDEX.SIDE.CODE DESCRIPTION: Code used to indicate whether 100 year or 50 year site index tables are used to calculate the site index of a soil type. Note that some site indexes for "eastside" soils are based on the 50 year index table. SITE.INDEX.SIDE Indicates 100 yr or 50 yr soil site index CODE FILE SITE.INDEX.SIDE.CODE IS NOT USED BY OTHER ITEMS CODE MAP/REPORT MAP CODE DESCRIPTION LABEL SYMB --------- ------------ ---- -------------------------------------------------- E 100 YR SITE 0 Soil site index based on 100 year table W 50 YR SITE 0 Soil site index based on 50 year table------------------------------------------------------------------

Public Land Survey (PLS) Township Subdivision. The primary subdivision of a PLSS Township. It may be a PLSS Section Area, a Donation Land Claim, a PLSS Tract, or a Protracted Block.WA Public Land Survey Sections Metadata

Land that is owned by public entities. Examples of public entity would be State of Washington, Clark County, US Forest Service, cities, Vancouver Housing Authority.See Clark County Metadata

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

This data set depicts federal lands having restrictions on access or activities -- that is, lands mangaed by the National Park Service, Defense Department, or Energy Department -- in western North America. The data set was created by reformatting and merging state- and province-based ownership data layers originally acquired from diverse sources (including state GAP programs, USBLM state offices and other sources). For each original dataset 3 additional fields, "Pub_Pvt", "CA_OWN", and "SOURCE" were added and populated based on the specific ownership information contained in the source data. The original coverages were then merged based on the "CA_OWN" field. Finally, NPS, DOD, and DOE lands were selected out of the ownership layer. All work was completed in AcMap 8.3. This product and all source data are available online from SAGEMAP: http://sagemap.wr.usgs.gov.

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).-

The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations

This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site.

The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many.

CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry.

Symbolizing Spatial Features:
Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records.

Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.General DescriptionThis layer shows only Active Roads on DNR Lands in black. This does not include abandoned, orphaned, decommisioned, or closed roads on DNR lands. Roads not on DNR Lands are of unknown status are shown in grey. Roads not on DNR lands and of unknown status may not be drivable. IncludesThe ROAD feature class stores the spatial location and attributes of the State of Washington, Department of Natural Resources’ (DNR) forest roads and of other DNR, public and selected private roads in the state. Other elements of the transportation network such as ferries, railroads, and trails are not included. ContactWashington State Department of Natural Resources (WA DNR) Engineering DivisionAlexandra WashburnAlexandra.Washburn@dnr.wa.gov Updating EffortsUpdating and editing efforts are primarily focused on roads in DNR managed state lands, adjunct roads or in areas that are covered by a published map that is undergoing an update. The original road lines were entered primarily by digitizing from paper maps, scanning by machine, or derived stereoscopically from black and white photo imagery. They are currently updated and corrected as needed, in most cases using on-line, geo-referenced orthophotography, stereo color imagery, GPS or field survey.Roads on DNR Lands should be edited frequently by division staff.Roads outside of DNR Lands are probably edited much less frequently. The group in mapping that did this, does not do it anymore.AttributesThe ROAD layer includes basic attributes that are linked to the intersection-based road segments. These attributes store information about route id, road name, road number, control, responsibility, status, access, surface, classification, and abandonment.PurposeThis layer is used to help in road infrastructure planning and maintenance, Forest Practices and Road Maintenance and Abandonment Planning (RMAP) compliance reporting, forest management, timber sales planning, and is the basis for the ROAD_ROUTE_FT layer and associated event tables that currently record these maintenance activities and road easements. It is widely used as a layer in cartographic presentations and published maps.

*This dataset is authored by the Washington Department of Natural Resources and is being shared as a direct link by Pend Oreille County. This is a primary reference soils dataset used by our organization for building, planning, and permitting purposes.This data can be used for determining a variety of soils information that was derived from the Private Forest Land Grading system and subsequent soil surveys. See Description and Metadata for more information.For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.Information for SOILS data layer was derived from the Private Forest Land Grading system (PFLG) and subsequent soil surveys. PFLG was a five-year mapping program completed in 1980 for the purpose of forestland taxation. It was funded by the Washington State Department of Revenue. The Department of Natural Resources, Soil Conservation Service (now known as the Natural Resources Conservation Service or NRCS), USDA Forest Service and Washington State University conducted soil mapping cooperatively following national soil survey standards. Private lands having the potential of supporting commercial forests were surveyed along with interspersed small areas of State lands, Indian tribal lands, and federal lands. Because this was a cooperative soil survey project, agricultural and non-commercial forestlands were included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soil map unit delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were later added and are now available through associated lookup tables. SCS (NRCS) soils data on agricultural lands also have been subsequently added to this data layer. The SOILS data layer includes approximately 1,100 townships with wholly or partially digitized soils data. State and private lands which have the potential of supporting commercial forest stands were surveyed. Some Indian tribal and federal lands were surveyed. Because this was a cooperative soils survey project, agricultural and non-commercial forestlands were also included within some survey areas. After the Department of Natural Resources originally developed its geographic information system, digitized soils delineations and a few soil attributes were transferred to the system. Remaining PFLG soil attributes were added at a later time and are now available through associated lookup tables. SCS soils data on agricultural lands also have subsequently been added to this data layer. This layer includes approximately 1, 100 townships with wholly or partially digitized soils data (2,101 townships would provide complete coverage of the state of Washington).- The soils_sv resolves one to many relationships and as such is one of those special "DNR" spatial views ( ie. is implemented similar to a feature class). Column names may not match between SOILS_SV and the originating datasets. Use limitations This Spatial View is available to Washingotn DNR users and those with access to the Washington State Uplands IMS site. The following cautions only apply to one-to-many and many-to-many spatial views! Use these in the metadata only if the SV is one-to-many or many-to-many. CAUTIONS: Area and Length Calculations: Use care when summarizing or totaling area or length calculations from spatial views with one-to-many or many-to-many relationships. One-to-many or many-to-many relationships between tabular and spatial data create multiple features in the same geometry. In other words, if there are two or more records in the table that correspond to the same feature (a single polygon, line or point), the spatial view will contain an identical copy of that feature's geometry for every corresponding record in the table. Area and length calculations should be performed carefully, to ensure they are not being exaggerated by including copies of the same feature's geometry. Symbolizing Spatial Features: Use care when symbolizing data in one-to-many or many-to-many spatial views. If there are multiple attributes tied to the same feature, symbolizing with a solid fill may mask other important features within the spatial view. This can be most commonly seen when symbolizing features based on a field with multiple table records. Labeling Spatial Features: Spatial views with one-to-many or many-to-many relationships may present duplicate labels for those features with multiple table records. This is because there are multiple features in the same geometry, and each one receives a label.Soils Metadata

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata

Use this web map to link to other geospatial datasets available through county and city sites (Not comprehensive). May need to zoom in to see the participating cities. The county boundaries and city points were published by Washington State agencies and downloaded from geo.wa.gov. Locations are approximate, and no warranties are made regarding this data. The canvas basemap has been compiled by Esri and the ArcGIS user community from a variety of best available sources. Want to have your data site listed? Contact the Geospatial Program Office.

Washington Department of Natural Resources Districts. These areas are administrative subunits of a Washington Department of Natural Resources Region.WA DNR Districts MetadataDownload Link

PLS Township. In the Public Land Survey System a Township refers to a unit of land, that is nominally six miles on a side, usually containing 36 sections, some of which are designed to correct for the convergence of meridians or range lines, with boundaries conforming to meridians and parallels within established limits.WA Public Land Survey Townships MetadataClick for downloadService URL: https://fortress.wa.gov/dnr/arcgisext/weba_ext_prod4/rest/services/Cadastre/WADNR_Cadastre_OpenData/MapServer/8

The Point layer covers the State of Washington with a variety of different types of locations. The great majority of Points, point type 1, Corner Point, are located at the corners, or angle points, of Legal Description and Parcel areas. (See the metadata for Legal Description and Parcel.) Corner Points can represent differing types of locations such as surveyed monuments, locations calculated by survey, locations digitized from various maps like US Geological Survey quadrangles, and locations that serve no other purpose than to stabilize the endpoint of a Boundary or angle point of a Legal Description or Parcel. Points are the only features in the upland Cadastre that have attributes regarding the source and accuracy of the data. The known accuracy of the data varies dramatically from place to place. The attributes also indicate whether there is a known physical object to look for on the ground. The second type of Point, Geodetic Control Point, point type 2, is not currently populated. The third type of Point, Significant Coordinated Location, point type 3, can be used to store any type of point location that has cadastral significance. At present, the only Significant Coordinated Points in Cadastre are those points along the Washington Pacific Ocean coast which were used by the US Minerals Management Service to calculate the boundary of the State at one marine league from the coast.WA Public Land Survey Points MetadataClick to download

This dataset describes Tribal Lands in Washington State. Included are areas where the tribes ceded title to their historic areas of use to the U.S. Government through various treaties enacted during the later half of the 19th century. Boundary lines have been digitized from a variety of digital data sources including 1:100,000 streams for boundaries described in treaties as following a stream or river, 1:24k Water Resource Inventory Areas (WRIA), Watershed Administrative Unit (WAU) and Hydrologic Unit Code (HUC) boundaries for boundaries referred to in treaties as 'divide', 'summit' or 'between the waters of', 1:100,000 Major Public Lands (for current reservation areas), 10 meter DEM and 7.5 minute USGS digital Quad maps (to define ridgelines and 'divide' where WRIA, WAU or HUC boundaries don't exist) and NAIP orthophoto imagery (to get a feel for what a questionable boundary area actually looks like today). Ceded Land treaty areas are based on treaty language and US Government decrees dated 1854-1892. Natural geographic barriers such as streams and ridge lines were used where described or eluded to in treaty descriptions. Coordinate based latitude/longitude boundary lines were used in some Central Washington areas where described. References to general compass directions were followed using natural barriers such as watershed boundaries or drainages wherever possible. Some treaty boundary descriptions were found to be inadequate, inaccurate and in some cases misleading in nature in describing what should have been a natural boundary or even a coordinate based solution to a property description. Some of these boundary areas open to interpretation are discussed below in the Supplemental Information based on the language and definite boundaries of other treaty areas. Ceded areas in Oregon and Idaho from the Camp Stevens Treaties have been included in this dataset. The Washington State Department of Ecology makes no warranty for the accuracy of this material and is not libel for its use. Ecology will maintain this data layer for its own use and distribute to all interested parties. Updates, corrections and documentation should be submitted to the contact person. This data may or may not reflect the most current tribal reservation areas. Tribal reservations are updated regularly in the Major Public Lands (MPL) layer maintained by Washington State Department of Natural Resources. This GIS data is draft information and a work in progress and should be used only as a generalized visual guide to 150 year old treaties of limited content.

In 2007, Washington State legislators requested a trails database, but funding to complete that statewide project was not made available at the time.

In 2009, the Federal Government outlined the need for trails database schema in their Data Standards Review Committee, stressing the efficiency in management decisions that a streamlined database can provide.

“The collection, storage and management of trail related data are important components of everyday business activities in many federal and state land-managing agencies, trail organizations and businesses. From a management perspective, trails data must often mesh closely with other types of infrastructure, resource and facility enterprise data.”

In 2014, the Washington State Office of the Chief Information Officer's (OCIO) Geospatial Program Office acquired a Nonhighway and Off-Road Vehicle Activities (NOVA) Program grant through the Washington State Recreation and Conservation Office (RCO) giving the OCIO initial funding to develop a statewide trails database based on Federal Geographic Data Committee standards. Using the same standard for all trails data will allow land managers and recreational users throughout the state to access and use the data regardless of administrative boundary.

"Data standards will make it easier for trail information to be accessed and exchanged and used by more than one individual agency or group…Ease in sharing data increases the capability for enhanced and consistent mapping, inventory, monitoring, conditions assessment, maintenance, costing, budgeting, information retrieval, and summary reporting for internal and external needs.”

Along with streamlining data and facilitating efficiency in management practices across agencies, the database will provide a source of trails information that is open and free to the public.The 2016 State Legislature provided additional funding from the Nonhighway and Off-road Vehicle Activities Account to the Office of the Chief Information Officer to continue work on the database.

Additional details about the project can be found here:

Washington State Trails Map

Please note that this map and its component services have been designed to work together as part of the web application.

A bug has been logged for the 403 error which is generated when trying to download large datasets through the Download menu. As a workaround, the zipped file geodatabase is available here:https://www.arcgis.com/sharing/rest/content/items/d04a50e44fbd4497bb57830b52fe5a2b/dataThe Washington State Land Use coverage was produced from digital county tax parcel layers using Department of Revenue (DOR) two digit land use codes (see; WAC 458-53-030, Stratification of assessment rolls - real property). Land use attribute data has been normalized for all county parcel data to conform to the two digit DOR codes. All county parcel layers are dissolved using the normalized land use code. No county parcel information remains in this data other that what geometry remains from the dissolve process.

These data are part of a larger USGS project to develop an updated geospatial database of mines, mineral deposits and mineral regions in the United States. Mine and prospect-related symbols, such as those used to represent prospect pits, mines, adits, dumps, tailings, etc., hereafter referred to as “mine” symbols or features, are currently being digitized on a state-by-state basis from the 7.5-minute (1:24,000-scale) and the 15-minute (1:48,000 and 1:62,500-scale) archive of the USGS Historical Topographic Maps Collection, or acquired from available databases (California and Nevada, 1:24,000-scale only). Compilation of these features is the first phase in capturing accurate locations and general information about features related to mineral resource exploration and extraction across the U.S. To date, the compilation of 500,000-plus point and polygon mine symbols from approximately 67,000 maps of 22 western states has been completed: Arizona (AZ), Arkansas (AR), California (CA), Colorado (CO), Idaho (ID), Iowa (IA), Kansas (KS), Louisiana (LA), Minnesota (MN), Missouri (MO), Montana (MT), North Dakota (ND), Nebraska (NE), New Mexico (NM), Nevada (NV), Oklahoma (OK), Oregon (OR), South Dakota (SD), Texas (TX), Utah (UT), Washington (WA), and Wyoming (WY). The process renders not only a more complete picture of exploration and mining in the western U.S., but an approximate time line of when these activities occurred. The data may be used for land use planning, assessing abandoned mine lands and mine-related environmental impacts, assessing the value of mineral resources from Federal, State and private lands, and mapping mineralized areas and systems for input into the land management process. The data are presented as three groups of layers based on the scale of the source maps. No reconciliation between the data groups was done.

DOWNLOAD RASTER IMAGERYRS-FRIS Version 5.3 is a remote-sensing based forest inventory for WA DNR State Trust lands.RS-FRIS Version 5.3 is a remote-sensing based forest inventory for WA DNR State Trust lands. Predictions are derived from three-dimensional photogrammetric point cloud data (DAP), field measurements, and statistical models. RS-FRIS 5.3 was constructed using remote sensing data collected in 2021 and 2022, and incorporates depletions for selected completed harvest types through 2025-03-31.