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

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.

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.

description: The Public Land spatial data sets (shapefile) contains Public Land Survey section polygons that had mining claims recorded in the U.S. Bureau of Land Management's LR2000 database as of December 31, 2010 (from a March 1, 2011 data extraction) for the period from 1976 to 2010 in Arizona, Arkansas, California, Colorado, Florida, Idaho, Montana, Nebraska, New Mexico, Nevada, North Dakota, Oregon, South Dakota, Utah, Washington, and Wyoming. Alaska was not updated in version 4.; abstract: The Public Land spatial data sets (shapefile) contains Public Land Survey section polygons that had mining claims recorded in the U.S. Bureau of Land Management's LR2000 database as of December 31, 2010 (from a March 1, 2011 data extraction) for the period from 1976 to 2010 in Arizona, Arkansas, California, Colorado, Florida, Idaho, Montana, Nebraska, New Mexico, Nevada, North Dakota, Oregon, South Dakota, Utah, Washington, and Wyoming. Alaska was not updated in version 4.