Bureau of Land Management, Oregon State Office20091026vector digital datahttp://www.blm.gov/or/gis/http://www.blm.gov/or/gis/data-details.php?data=ds000013http://www.blm.gov/or/gis/files/regional/land_lines.zipFilename: PLSS_Township_poly. This theme portrays information related to the Public Land Survey System of lands in the states of Oregon and Washington.Land use planning, watershed analysis, project planning.Bureau of Land Management (BLM)200910Presentpublication dateCompleteAs needed-124.860832-116.46302649.00243241.992081NoneBase Datalandlinesownershipjurisdictionpublic land survey systemsubsurface mineral estateLLIFrameworkGCDBPLSSBLM-StateOregonSoutheast WashingtonWashingtonISO 19115planningCadastreBLM-ThemeLand Use ManagementDiscretionary, contains no sensitive information - generally considered releasable.None; however, users are reminded that the official records for land ownership and jurisdiction are maintained on the Master Title Plats at the Oregon State Office of the Bureau of Land Management. The federal surface and minerals management status in the ownership theme are to be used as general planning and management tools only. The ownership theme is based on the best available information at the time of file update. The official Public Land Tenure Records maintained by the Bureau of Land Management and other responsible Federal agencies should always be checked for current status on specific tracts of land. Please report errors in the ownership theme to the BLM office from which it was obtained.Tim KeckBureau of Land Management, OR/WA State OfficeLand Surveyor, 957.3 GCDB Sectionmailing address

P. O. Box 2965

PortlandOR97208-2965USA(503)808-6164tkeck@or.blm.govMicrosoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.1.0.722Attributes were compared with the source material for accuracy. Discrepancies were cross checked with other sources to determine and confirm the correct attribute.The PLSS_Township was built for polygon, arc, and node topology.This theme covers the states of Oregon and Washington.Source Data derived from the BLM addresses positional accuracy by referring to the error elipses from the Geographic coordinate data base (GCDB). Other Source data derived from other Federal, State, and county sources as a rule did not address positional accuracy. Accuracy was then determined from metadata statements if available.OR/WA BLMUnknownPortland, OROR BLM12000GCDB flat files1985unknownunknownunknownpublication dateGCDBPolygons, lines, and attributes; supplied for the state of Oregon.OR/WA BLMUnknownUnKnownGovernment Land Records, and USGS QuadsWODDBWestern Oregon Digital Data Base Lines, points, and attributes; supplied for the State of Oregon by the BLM Oregon State OfficeClallam County, Washingtonhttp://www.clallam.net/directory/departments.htmlonlineClallam County, Washingtonhttp://www.clallam.net/directory/departments.htmlonlineDouglas County, Washingtonhttp://www.douglascountywa.net/departments/tls/gis/default.asponlineFranklin County, Washingtonhttp://gis.co.franklin.wa.us/onlineFranklin County, Washingtonhttp://gis.co.franklin.wa.us/onlineGrays Harbor County, WashingtononlineKlickitat County, Washingtonhttp://klickitatcounty.org/onlineLewis County, Washingtonhttp://maps.lewiscountywa.gov/maps/maplib_index.htmlonlinePierce County, Washingtonhttp://www.co.pierce.wa.us/pc/interactive.htmonlineSnohomish County, Washingtonhttp://www1.co.snohomish.wa.us/Departments/Information_Services/onlineThurston County, Washingtonhttp://www.geodata.org/online.htmonlineWhatcom Countyhttp://www.whatcomcounty.us/pds/planning/gis/gisdata.jsponlineYakima County, WashingtonData was assembled using information from the Oregon State Office and from various federal, state, and county agencies. When data from multiple sources covered the same area, the data was then assessed for best quality content and accuracy. Priorties were determined for acceptance. Data with positional accuracy statements were first choice (GCDB data). Data with accuracy statements in the meta data were second, and data without accuracy statements was the third priority for acceptance. The data assembled using the data from the OR_PLSSSection _poly and was dissolved on the T_R field to display the final Polygon. The data was then combined with and edgematched to previously accepted data and adjusted to conform to the topology rules. The data was then combined and edgematched to conform to the topology rules.GCDBWODDBNot completeTim KeckBureau of Land Management, OR/WA State OfficeLand Surveyor, 957.3 GCDB Sectionmailing address

P. O. Box 2965

PortlandOR97208-2965USA(503) 808-6164Tim_Keck@or.blm.govSteve SalasBureau of Land Management, Oregon State OfficeGIS Specialistmailing address

P.O. Box 2965

PortlandOR97208USA503 808-6416ssalas@blm.govWashington state data extracted from equivalent WA_LLI theme (WA_PLSSTownship_poly). Any overlaps with existing Oregon data in PLSS_TOWNSHIP_POLY were resolved by deleting features from PLSS_TOWNSHIP_POLY. Field VERSION_NAME of the Washington data was filled with the value "InitialLoad". Washington data loaded into PLSS_TOWNSHIP_POLY with field EDITDATE directed into field EDIT_DATE. Edge-match of data along the Oregon and Washington border was completed by Erin Frostad using GCDB points.20091023CA BLMhttp://www.blm.gov/ca/st/en/prog/cadastral/gcdbpage.html12000GCDB flat filesGCDBLines, points, and attributes; supplied for the State of California and Nevada by the BLM California State Office.VectorG-polygon851180.0000000010.000000001Decimal degreesNorth American Datum of 1983Geodetic Reference System 806378137.000000298.257222 PLSSTownship_polyThe extents of a townshipOR/WA BLMsourceThe source of the data where the data came from.OR/WA BLMOBJECTIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.edit_dateThe date the edit was madeOR/WA BLMshape_LengthLength of feature in internal units.ESRIPositive real numbers that are automatically generated.ShapeFeature geometry.ESRICoordinates defining the features.GLOBALIDGlobally Unique IdentifierESRITwpIDA coded value that identifies the State, Meridian, Township, and Range of a polygonOR/WA BLMtwpid is a 15 character representation. Example: OR = State, 33 = Meridian, 0370N = Township, 0170E = RangeT_RThe common Township and Range identifierOR/WA BLMExample: t_r = T37N-R17Eshape_AreaArea of feature in internal units squared.ESRIPositive real numbers that are automatically generated.Eric HiebenthalBureau of Land Management, Oregon State OfficeMailing address

P.O. Box 2965

PortlandOR97208USA503-808-6565503-808-6419GIS Data Management Specialistehiebent@blm.govNo warranty is made by the Bureau of Land Management as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data.Downloadable Data20091026Stanley FrazierBureau of Land Management, Oregon State OfficeState Data Administratormailing address

P.O. Box 2965

PortlandOR97208USA(503)808-6009 (direct) (503)808-6004 (front desk)(503)808-6419Stan_Frazier@or.blm.govFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeNoneNoneNot Classified201006302013063020090810file://\\blm\dfs\or\egis\gisdata\corp\BLMReplication\stage\corp\land_lines.gdbLocal Area Network