<?xml version="1.0" encoding="UTF-8"?>
<metadata xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xdt="http://www.w3.org/2005/xpath-datatypes">
<idinfo>
<citation>
<citeinfo>
<origin>OR/WA BLM</origin>
<pubdate>20060306</pubdate>
<title>Geographic Coordinate Database Oregon (Line)</title>
<geoform>map</geoform>
<pubinfo>
<pubplace>Portland, OR</pubplace>
<publish>OR BLM</publish>
</pubinfo>
</citeinfo>
</citation>
<descript>
<abstract>This layer contains the lines generated from the GCDB.  These form the basis for township and range, section lines, and federally owned land parcels.</abstract>
<purpose>Resource management planning</purpose>
<supplinf>LR2000 (Legacy Rehost 2000), BLM (Bureau of Land Management), ADS (Automated Digitizing System), MOSS (Map Overlay Statistical System), GCDB (Geographic Coordinate Data Base), PCCS (Public Land Survey System Cartographic Coordinate System), WODDB (Western Oregon Digital Data Base), WGCD (WODDB Geographic Coordinate Database layer in Lakeview District), USGS (United States Geological Survey), GCD (Geographic Coordinate Database layer), LLI (Landlines layer)</supplinf>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>1989</begdate>
<begtime>unknown</begtime>
<enddate>Present</enddate>
<endtime>unknown</endtime>
</rngdates>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>In work</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc>-124.625</westbc>
<eastbc>-116.375</eastbc>
<northbc>49.4</northbc>
<southbc>41.625</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Base Data</themekey>
<themekey>geographic coordinate database</themekey>
<themekey>township</themekey>
<themekey>section</themekey>
<themekey>GCD</themekey>
<themekey>Framework</themekey>
</theme>
<theme>
<themekt>ISO 19115</themekt>
<themekey>location</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Oregon</placekey>
<placekey>Washington</placekey>
</place>
</keywords>
<accconst>Discretionary, contains no sensitive information - generally considered releasable.</accconst>
<useconst>The geographic coordinates and their associated products have NO legal significance.  They should be used for record keeping, mapping, graphics, and planning purposes only.</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Tim Keck</cntper>
<cntorg>Bureau of Land Management, OR/WA State Office</cntorg>
</cntperp>
<cntpos>Land Surveyor</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>P. O. Box 2965</address>
<city>Portland</city>
<state>OR</state>
<postal>97208-2965</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(503)808-6164</cntvoice>
<cntfax>(503)808-6190</cntfax>
<cntemail>tim_keck@or.blm.gov</cntemail>
</cntinfo>
</ptcontac>
<native>Arc/Info; AIX/UNIX</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>
The point-id was checked to assure that it conforms to requirements.  This includes checking to be sure that each point in a township has a point-id value, each point-id is unique within a township, the point-id values contain six digits, and the point-ids generally follow the 100100 to 700700 numbering system.

When a district editor has completed an edit and is ready to put the coverage back into the library the coverage is compared against the library format coverage using software built specifically for this purpose.  The software also checks the ptreliability and point-id attributes to make sure that they are populated and not left blank.
</attraccr>
</attracc>
<logic>
For original WODDB data still present in Western Oregon, ten percent of the topology was point checked to make sure point-ids matched the point.  Western Oregon does not contain line data unless the District BLM editors added lines during a transactional update.

For Eastern Oregon, a series of AMLs were used to check the topology of the data.  These AMLs failed if they found two or more lines intersecting without creating a node.  The AMLs&apos; main function was to edgetie each GCD township with adjacent townships.  A polygon perimeter was created from the data, and this was compared against the polygon perimeters of adjacent townships to locate sliver polygons where townships did not edgetie.  All data within a township GCD coverage was compared to the polygon perimeter coverage to make sure the interior data snapped to the boundary properly.  All nodes of each township boundary were compared to nodes of adjacent township boundaries to make sure they snapped to each other.
</logic>
<complete>This layer covers BLM lands in Oregon and portions of Washington.</complete>
<posacc>
<horizpa>
<horizpar>A wide range of positional accuracy is reflected.  The accuracy field ptreliability within the GCD point attribute table contains feature level horizontal positional accuracy information stratified into 14 categories.</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>BLM OR/WA State Office</origin>
<pubdate>1989</pubdate>
<title>Geographic Coordinate Digital Database</title>
<onlink>http://web.or.blm.gov/gis/resources/dataset.asp?cid=36</onlink>
</citeinfo>
</srccite>
<srctime>
<timeinfo>
<rngdates>
<begdate>1989</begdate>
<begtime>unknown</begtime>
<enddate>Present</enddate>
<endtime>unknown</endtime>
</rngdates>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>OR\WA BLM GCD</srccitea>
<srccontr>Points, lines, and attributes</srccontr>
</srcinfo>
<procstep>
<procdesc>An ASCII file was created on PRIME from input data by BLM personnel.</procdesc>
<procdate>1988</procdate>
<proctime>000000</proctime>
</procstep>
<procstep>
<procdesc>(Westside data only) BLM contractors converted the ASCII data to ADS, and then converted it to MOSS.</procdesc>
<procdate>1988</procdate>
</procstep>
<procstep>
<procdesc>(Westside data only) GCD was converted from MOSS to ArcInfo and inserted into the libraries as a point theme.</procdesc>
<procdate>1995</procdate>
</procstep>
<procstep>
<procdesc>(Eastside data only) BLM contractors translated the ASCII data to ArcInfo, edgematched the data, and inserted GCD into the libraries as a point and line theme.</procdesc>
<procdate>1996</procdate>
</procstep>
<procstep>
<procdesc>The WODDB-created GCD layer present in the Lakeview library was renamed to WGCD.  This was done in order to allow the insertion of the GCDB-created GCD layer, which had slightly different attributes, better reliability, and was built for lines and points rather than just points.</procdesc>
<procdate>19960605</procdate>
</procstep>
<procstep>
<procdesc>The Coos Bay library was missing all GCD data for the township S26W09.  The ASCII file for this township was translated to ArcInfo and the new GCD township was inserted into the library.</procdesc>
<procdate>19961030</procdate>
</procstep>
<procstep>
<procdesc>The Salem library GCD layer did not contain the point-id attribute. This layer was dropped and re-inserted so the point-id would be included in the layer and the layer would match the other WODDB library GCD layers.</procdesc>
<procdate>19961118</procdate>
</procstep>
<procstep>
<procdesc>During the creation of the LLI layer, a problem was identified with the GCD layer in which there were two excess points present in township S35W14 in the Coos Bay library.  Upon inspection by the data steward, it was decided that these two points should be deleted.</procdesc>
<procdate>19961220</procdate>
</procstep>
<procstep>
<procdesc>The Roseburg library was missing all GCD data for township S29.5W07.  The ASCII file for this township was translated to ArcInfo, and the new GCD township was inserted into the library.</procdesc>
<procdate>19961230</procdate>
</procstep>
<procstep>
<procdesc>Three townships (S27W08, S27.5W08, S28W08) that fall in the Coos Bay and Roseburg libraries were re-inserted because their point-ids were labeled incorrectly.  The ASCII files were translated to ArcInfo and inserted into the Coos Bay and Roseburg libraries.</procdesc>
<procdate>19970105</procdate>
</procstep>
<procstep>
<procdesc>(Westside data only) The GCD layer was built for line topology in addition to point topology.  The attributes twn_name, x_r, and afmt were dropped from the point attribute file, while the attributes twnrng, ptsource, ptdate, ptreliability, and corner-id were added to the point attribute file, and the attributes were populated according to the data found in the ASCII files.</procdesc>
<procdate>19970113</procdate>
</procstep>
<procstep>
<procdesc>
The GCD layer was released to BLM GIS editors for transactional updates in order to maintain the layer with current data and to populate areas with no data.  The unit of update is the 7.5-minute quadrangle.  Updating the spatial component of GCD that reflects federal status will be performed by the District Cadastral Survey staff for the westside, and the State Office GCDB for the eastside, unless the necessary points and lines already exist in the GCD theme.  Upon checkin of the edited quadrangle for inclusion into the GIS corporate library, all attributes are checked to assure that they conform to the data standard.

This will be an ongoing process.  The process date reflects the first date that access was granted in any ArcInfo library.
</procdesc>
<procdate>19970327</procdate>
</procstep>
<procstep>
<procdesc>ASCII files created from survey records were translated to ArcInfo coverages.  A quality control was conducted on these coverages to identify duplicate values, blank values, incorrect format, or invalid range in the point-id.  The coverages were checked for invalid intersections, where two or more lines meet without creating a node.  The township-based coverages were compared to adjacent township coverages to be sure that adjacent townships are edgetied, to be sure that all line data snaps to points, and to be sure that all nodes snap to nodes in adjacent townships.  If there was a problem with any of these issues the problem was identified and depicted in a screen print and sent to the State Office GCDB for edit.  The original survey data was checked, the ASCII files edited if necessary, and the translation and Q.C. process repeated.  When all the data passed Q.C. it was merged together and inserted into the GIS corporate libraries.</procdesc>
<procdate>20010320</procdate>
</procstep>
</lineage>
<cloud>Unknown</cloud>
</dataqual>
<spdoinfo>
<indspref>Public Land Survey Corners</indspref>
<direct>Point</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>String</sdtstype>
<ptvctcnt>2871018</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>0.000000</latres>
<longres>0.000000</longres>
<geogunit>Decimal degrees</geogunit>
</geograph>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378206</semiaxis>
<denflat>294.9786982</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys></altsys>
</vertdef>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>Geographic Coordinate Database Lines</enttypl>
<enttypd>This entity has no attributes.</enttypd>
</enttyp>
<attr>
<attrlabl>objectid</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntperp>
<cntper>Eric Hiebenthal</cntper>
<cntorg>Bureau of Land Management/Northrop Grumman</cntorg>
</cntperp>
<cntpos>Data Administration Supervisor</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>P.O. Box 2965</address>
<city>Portland</city>
<state>OR</state>
<postal>97208</postal>
<country>USA</country>
</cntaddr>
<cntvoice>503-808-6565</cntvoice>
<cntfax>503-808-6374</cntfax>
<cntemail>ehiebent@blm.gov</cntemail>
<hours>7:30 a.m. to 4:00 p.m.</hours>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>No 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.</distliab>
<stdorder>
<fees>Contact distributor.</fees>
<ordering>Data are only available through the Oregon/Washington State office of the Bureau of Land Management.</ordering>
</stdorder>
</distinfo>
<metainfo>
<metd>19970408</metd>
<metrd>20020424</metrd>
<metfrd>20030424</metfrd>
<metc>
<cntinfo>
<cntperp>
<cntper>Stanley Frazier</cntper>
<cntorg>Bureau of Land Management, Oregon State Office</cntorg>
</cntperp>
<cntpos>State Data Administrator</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>P.O. Box 2965</address>
<city>Portland</city>
<state>OR</state>
<postal>97208</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(503)808-6009</cntvoice>
<cntfax>(503)808-6419</cntfax>
<cntemail>Stan_Frazier@or.blm.gov</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
</metainfo>
</metadata>

