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.

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/ .

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

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

Government Land Office maps (GLOs) are a result of the effort to survey all United States public lands before settlement. Starting in 1812 land was divided into square six mile blocks called townships, then subdivided into sections and ranges. Each subdivided area was surveyed and given its own map or GLO. During this process surveyors were required to indicate cultural resources such as roads and Indian trails and standardized symbols were used to represent geographic features. These GLOs are now maintained by the Bureau of Land Management as part of the official Land Status and Cadastral Survey records. As land was divided into parcels of individual ownership additional cadastral survey maps were created over time. For this reason there are often multiple GLOs or "cadastral survey maps" for one township / range, generally numbered one through four. For this seamless GLO layer, DAHP focused solely on the more historical GLOs which were usually listed as image number one or two for that specific township / range in the BLM Cadastral Survey records. In some cases no GLOs were available for review. Such areas included National Forest Lands, National Parks, Indian Reservations, and remote wilderness areas.

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.

The Recreation and Conservation Office (RCO) was asked by the state Legislature to provide an inventory of lands in Washington owned by federal, state, and local governments, and by Native American tribes by July 1, 2014 (2013-15 Capital Budget proviso, Section 3174 of Engrossed Substitute Senate Bill 5035).The Public Lands Inventory focuses on natural resource and recreation lands and shows ownership (federal, by agency; state, by agency; local government, by county or city), ownership type (fee simple or assumed fee simple; aquatic, upland, or assumed upland), location, acreage, principal use (developed recreation, habitat and passive recreation, revenue generation, conservation, assumed habitat and passive recreation, other, or unknown), and the date and cost of recent acquisitions (within the past ten years).

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.

Washington State County Boundaries including Department of Natural Resources (DNR) county codes. This data is created from the WA Public Land Survey source data maintained by the DNR.WA County Boundaries Metadata

This map of human habitation was developed, following a modification of Schumacher et al. (2000), by incorporating 2000 U.S Census Data and land ownership. The 2000 U.S. Census Block data and ownership map of the western United States were used to correct the population density for uninhabited public lands. All census blocks in the western United States were merged into one shapefile which was then clipped to contain only those areas found on private or indian reservation lands because human habitation on federal land is negligible. The area (ha) for each corrected polygon was calculated and the 2000 census block data table was joined to the shapefile. In a new field, population density (individuals/ha) corrected for public land in census blocks was calculated . SHAPEGRID in ARC/INFO was used to convert population density values to grid with 90m resolution.

The WA RCO Public Lands Inventory 2019 layer supports the Public Lands Inventory required by the 2017-19 Capital Budget, Chapter 2, Laws of 2018, Section 3083, (SSB 6090), which tasked the Recreation and Conservation Office (RCO) to update the public lands inventory with current information on state agency habitat and recreation land acquisitions and easements and to further develop the inventory to respond to the recommendations of the Joint Legislative Audit and Review Committee for creating a single source of information about land acquisitions. The 2019 update to the Public Lands Inventory must include updated parcel data for state and federal lands and will retain all of the Public Lands Inventory 2014 elements below. Per the 2015 Joint Legislative Audit Review Committee (JLARC) final report on State Recreation and Habitat Lands, it must also: · Provide details about acquisition and funding o Provide details about the properties proposed for acquisition, including location, acreage, and current use. o Estimated acquisition cost and fund source(s). o Include all proposed acquisitions, regardless of fund source(s). o Include all land disposals. · Link proposed or new acquisitions to plans and detailed outcomes o Explain how the acquisition relates to the agency’s plans for an entire management unit (i.e., state park, wildlife area, or natural area) o Clearly identify the detailed outcomes for the property and entire management unit such as specific development plans, service improvements, staffing levels, or habitat restoration needs. o Clearly describe agency progress toward achieving the detailed outcomes and how the acquisition helps achieve those outcomes. · Identify future costs to achieve and maintain detailed outcomes o Estimate future capital, operating, and maintenance costs for the entire management unit, including the costs to achieve the detailed outcomes. o Explain how the proposed acquisition affects those estimated costs. In addition to the requirements outlined above, the Recreation and Conservation Office has set the following requirements for the Public Lands Inventory: · Create an open data service, where state agencies will provide their ownership data and other information described above and include enhanced reporting of forecast and monitoring information and the ability to view/sort data as needed. o Expand reporting capabilities to allow end users to generate and print their own ownership reports by geographic boundaries and data ranges. The WA RCO Public Lands Inventory 2014 layer supports the 2013-15 Capital Budget, Chapter 19, Laws of 2013, Section 3174, (ESSB 5035) tasked the Recreation and Conservation Office (RCO) to provide a centralized inventory of lands in Washington owned by federal, state and local governments, and by Native American tribes. This work is to be undertaken in collaboration with the Joint Legislative Audit and Review Committee (JLARC). The proviso stipulates that the inventory must: · Be in a web-accessible format, including a Geographic Information System (GIS)-based interactive map that allows users to find out information about specific aspects of land ownership. The data must be standardized to allow summary information to be accessible. · Include the following information: o Ownership (federal; state, by state agency; local government; and tribal).o Ownership type (fee simple or easements).o Location.o Acreage.o Principal use of these lands (intended use at the time of acquisition and current use) including, but not limited to, developed recreation land, habitat and passive recreation land, and revenue-generation uses.o Acquisition costs if acquired by state agencies over the last ten years, including acquisition funding sources.

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

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

Planned Land Use from the 2021 Comprehensive Plan Amendment Act of 2021. This data set is an update to the 2006 original version, which was digitized from the Generalized Land Use Map of the District of Columbia Comprehensive Plan. It shows which areas of the city are planned for various uses. These uses include residential and commercial uses at various densities, public land, institutional, federal, and industrial uses. Although planned uses and current uses may be similar, this is not a data set describing current land use. This is a generalized product, and cannot be used to identity specific uses for all specific locations in the District of Columbia.

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.

The Colockum elk herd inhabits a mix of public and private lands northeast of Ellensburg between Blewett Pass of the Cascade Range and west of the Columbia River (fig. 35). The population ranges between 4,000 and 5,000 animals and is partially migratory, with individuals displaying a mix of resident (63 percent of analyzed individuals) and migratory (34 percent of analyzed individuals) behaviors. During winter, many elk inhabit grassland, sagebrush, antelope bitterbrush, and ponderosa pine habitats in the Whiskey Dick, Quilomene, and Colockum Wildlife Areas and the eastern reaches of the Naneum State Forest. As spring green up of vegetation nears, migratory elk travel northwest toward summer ranges in the Wenatchee Mountains, north of Ellensburg. Resident elk inhabit the same areas as wintering migratory elk. Agricultural producers in the eastern Kittitas Valley often experience conflicts with elk consuming hay in fields. Additional concerns for the herd include semipermeable barriers along Interstate 90 and U.S. Highway 97 and disturbance from human recreation on the winter range. These mapping layers show the location of the Migration routes for elk (Cervus canadensis) in the Colockum population in Washington. They were developed from 89 migration sequences collected from a sample size of 35 animals comprising GPS locations collected every 3 hours.

The Washington State Zoning Atlas (“WAZA” or “Atlas”) is a centralized database of spatial zoning data, hosted by the Department of Commerce. It provides simplified and accessible zoning information for Washington’s 39 counties and 281 cities (320 jurisdictions total) to the public. The interactive map and downloadable database illustrate key features and regulatory characteristics of zoning codes across jurisdictions. Data attributes for each zone include generalized land use categories, allowed uses, and development standards (e.g., building heights, densities, parking requirements). The Atlas makes it easier to compare zoning codes between jurisdictions and identify regional and statewide trends in regulation, which will strengthen local planning for housing, transportation, environmental impacts, climate response, and economic growth.The Washington State Zoning Atlas was developed by a team including MAKERS architecture and urban design LLP, the University of Washington, Western Washington University, BHC Consultants, and the Washington State Department of Commerce. Funding was allocated for this project in the Engrossed Substitute Senate Bill 5187.

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

Washington Department of Natural Resources Local Unit. These areas are administrative subunits of a Washington Department of Natural Resources District.WA DNR Units 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.