Bureau of Land Management - Oregon State Office20091026BLM OR WA Legal Description arcvector digital dataFilename: Legal_Description_arc.
This theme portrays information related to the Public Land Survey System (PLSS) in the states of Washington and Oregon.Land use planning, watershed analysis, project planning.BLM (Bureau of Land Management)20061001Presentpublication dateAs needed-124.860832-116.46302649.00243241.992081NoneBase Datalandlinesownershipjurisdictionpublic land survey system (PLSS)subsurface mineral estateLLIFrameworkGCDBBLM-StateOregonWashingtonISO 19115planningCadastreBLM-ThemeLand Use PlanningDiscretionary, contains no sensitive information - generally considered releasable.None; however, users are reminded that the official records for federal land ownership and jurisdiction are maintained at the Oregon State Office of the Bureau of Land Management. The Master Title Plats provide a reference to these records. 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 discrepancies in the ownership theme to the BLM office from which it was obtained.Tim KeckOR/WA BLM - Oregon State OfficeLand Surveyor, 957.3 GCDB Sectionmailing addressP. O. Box 2965PortlandOR97208-2965USA(503)firstname.lastname@example.orgMicrosoft Windows 2000 Version 5.2 (Build 3790) Service Pack 1; ESRI ArcCatalog 184.108.40.2062Attributes were compared with the source material for accuracy. Discrepancies were cross-checked with other sources to determine and confirm the correct attribute. Lines are coded to indicate the source of the attribute.The Legal_Description was built for polygon, arc, and node topology.This theme covers the states of Oregon and Washington.Horizontal positional accuracy varies from point to point. With relation to GCD based data, Positional accuracy is expressed as a code, and is found in the attribute label 'ptreliability' contained in the GCD layer. This attribute refers to the point reliability/accuracy of the nodes upon which LLI is built as well as that of the GCD points. Other Source data derived from other Federal, State, and county sources as a rule did not address positional accuracy. Positional accuracy was determined from metadata statements if available.OR/WA BLM1995Geographic Coordinate DatabasePortland, OROR BLM1200GCDB flat files1995publication dateGCDBLines, points, and attributes; supplied for the State of Oregon by the BLM Oregon State Office.OR/WA BLMWestern Oregon Digital Data BaseUnknownGovernment Land Records, and USGS QuadsWODDBWestern Oregon Digital Data Base Lines, points, and attributes; supplied for the State of Oregon by the BLM Oregon State Office.Cc_gps pointsClallam County, Washingtonhttp://www.clallam.net/directory/departments.htmlonlineplss_coverageClallam County, Washingtonhttp://www.clallam.net/directory/departments.htmlonlineDouglas County, WashingtonDCParcels9_8_06http://www.douglascountywa.net/departments/tls/gis/default.asponlineFranklin County, WashingtonFranklinCountyTwpIdhttp://gis.co.franklin.wa.us/onlineFranklin County, WashingtonFranklinCountyhttp://gis.co.franklin.wa.us/onlineGrays Harbor County, WashingtonGHC_PLSonlineKlickitat County, WashingtonKlickitathttp://klickitatcounty.org/onlineLewis County, WashingtonLewisCohttp://maps.lewiscountywa.gov/maps/maplib_index.htmlonlinePierce County, Washingtoncadastre_thenrit7505517http://www.co.pierce.wa.us/pc/interactive.htmonlineSnohomish County, WashingtonSnohomishhttp://www1.co.snohomish.wa.us/Departments/Information_Services/onlineThurston County, Washingtoncontrolpointshttp://www.geodata.org/online.htmonlineWhatcom CountyWhatcomhttp://www.whatcomcounty.us/pds/planning/gis/gisdata.jsponlineYakima County, WashingtonYakamaCog83Data 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. Priorities were determined for acceptance. Data with positional accuracy statements were first choice (GCDB data). Data with accuracy statements in the metadata were second, and data without accuracy statements was the third priority for acceptance. The data was then combined with and edge matched to previously accepted data and adjusted to conform to the topology rules.GCDBWODBBTim KeckOR/WA BLM - Oregon State OfficeLand Surveyor, 957.3 GCDB Sectionmailing addressP. O. Box 2965PortlandOR97208-2965USA503email@example.comSteve SalasBureau of Land Management, Oregon State OfficeGIS Specialistmailing addressP.O. Box 2965PortlandOR97208USA503 firstname.lastname@example.orgWashington state data extracted from equivalent WA_LLI theme (WA_GCDBLines_arc). Any overlaps with existing Oregon data in LEGAL_DESCRIPTION_ARC were resolved by deleting features from LEGAL_DESCRIPTION_ARC. Field VERSION_NAME of the Washington data was filled with the value "InitialLoad". Values in Washington fields were translated to corresponding LEGAL_DESCRIPTION_ARC fields using crosswalk table approved by data steward Tim Keck. Washington data loaded into LEGAL_DESCRIPTION_ARC. Edge-match of data along the Oregon and Washington border was completed by Erin Frostad using GCDB points.20091023CA BLMGeographic Coordinate Databasehttp://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.Tim KeckOR/WA BLM - Oregon State OfficeLand Surveyor, 957.3 GCDB Sectionmailing addressP. O. Box 2965PortlandOR97208-2965USA503email@example.comData was assembled using information from the California 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. Priorities were determined for acceptance. Data with positional accuracy statements were first choice (GCDB data). Data with accuracy statements in the metadata were second, and data without accuracy statements was the third priority for acceptance. The data was then combined with and edge matched to previously accepted data and adjusted to conform to the topology rules.201006OregonVectorString1954200.0000000010.000000001Decimal degreesNorth American Datum of 1983Geodetic Reference System 806378137.000000298.257222
LEGAL_DESCRIPTION_arcLines derived from the creation of parcel data for ownership, surface & subsurface rightsOR/WA BLMltypeThe relationship of the arcs to the PLSS, managing agency rights, surface rights or subsurface rightsOR/WA BLMThe line type can be defined using any or all of seven codes. They are: S= Section, T= Township, J= property status, N= Juris name, L= federal status, R= Rights other than mineral, and M= Mineral rightscartolinesThe visibility of a lineOR/WA BLM0invisibleBLM1VisibleBLMshapeFeature geometry.ESRICoordinates defining the features.shape_LengthLength of feature in internal units.ESRIPositive real numbers that are automatically generated.OBJECTIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.def_featureThe physical or legal feature that defines the boundary according to the legal boundary descriptionOR/WA BLMFor the most part, Arcs in this feature class represent the PLSS. When dealing with metes & bound descriptions, physical features or man-made features may be defining featurescoord_sourceThe actual source of the GIS coordinates for the line segmentsOR/WA BLMcoord_source_orgName of the Agency that supplied the dataOR/WA BLMsource_vintageThe date the data was addedOR/WA BLMsource_layerWhere the existing geometry came fromOR/WA BLMThe majority of the geometry came from the GIS layer, GCD, however other layers have been and can be used to obtain geometry. This identifies where the geometry originated.GLOBALIDGlobally unique identifiersedit_orgThe Entity that edited the dataOR/WA BLMedit_dateThe date of the editOR/WA BLM1) Geographic Coordinate Data Base, Data Collection Attribute Definitions, Version 2.0, Bureau of Land Management, February 14, 1991; 2) GCDB ArcInfo Coverage Format, Version 10Sep99; 3) OR/WA State Data Dictionary.Eric HiebenthalBureau of Land Management, Oregon State OfficeMailing addressP.O. Box 2965PortlandOR97208USA503-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 Data20091023Stanley FrazierBureau of Land Management, Oregon State OfficeState Data Administratormailing addressP.O. Box 2965PortlandOR97208USA(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