. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Status Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Status Line

Abstract:
STATUS_ARC: This theme portrays the source information for the boundaries of the parcel polygons in OWNERSHIP_POLY and SUBSURFCASE_RIGHTS_POLY.

Supplemental information:
BLM (Bureau of Land Management)

  1. How should this data set be cited?

    Bureau of Land Management - Oregon State Office, 20141118, BLM OR Status Line.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.785528
    East: -116.463565
    North: 49.002430
    South: 41.624852

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar date: 20141118
    Currentness reference:
    publication date

  5. What is the general form of this data set?

    Geospatial data presentation form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      Indirect spatial reference:
      Oregon

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • String (661912)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 8.9831529999999996e-007. Longitudes are given to the nearest 8.9831529999999996e-007. Latitude and longitude values are specified in Decimal Degrees.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    STATUS_ARC
    Lines derived from the creation of parcel data for ownership, surface & subsurface rights (Source: OR/WA BLM)

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    DEF_FEATURE
    The physical or legal feature that defines the boundary according to the legal boundary description. (Source: BLM)
                      

    ValueDefinition
    CLOSURE
    CLOSURE-Closure extension.  Used to close small gaps.
    COAST_3MILE
    COAST_3MILE-Separating coastal water from territorial sea at 3-mile
    COUNTY
    COUNTY-County boundary
    ELEVATION
    ELEVATION-Line of common elevation
    FENCE
    FENCE-Fence line
    FOREST_SERVICE_ADMIN
    FOREST_SERVICE_ADMIN-Forest Service administrative boundaries
    GRAZING_BOUNDARY
    GRAZING_BOUNDARY-Pasture or other administrative grazing boundary that is not fenced and does not follow a subdivision or some					other legal boundary.
    HU
    HU-Hydrologic unit divide
    JETTY
    JETTY-Jetty
    JURISDICTION
    JURISDICTION-Surface jurisdiction boundary
    LAVA
    LAVA-Edge of lava flow
    LEVEE
    LEVEE-Dike or levee
    MARSH
    MARSH-Edge of Marsh, wetland, swamp, or bog boundary
    MINERAL_DISTURBANCE
    MINERAL_DISTURBANCE-Edge of quarry, mine, gravel stockpile or other mineral surface disturbance area
    NLCS_BOUNDARY
    NLCS_BOUNDARY-Wilderness, Wild and Scenic River, Historic District or other NLCS designation boundary.
    OTHER
    OTHER - Known boundary not represented by other domain options.
    PARKING_AREA
    PARKING_AREA-Motorized vehicle parking area.
    POINT-TO-POINT
    POINT-TO-POINT-Boundary defined by a straight line segment between two points
    POWERLINE
    POWERLINE-Power transmission line or buffer offset
    RIDGE
    RIDGE-Ridge
    RIGHT-OF-WAY
    RIGHT-OF-WAY-A legal right of way forms boundary
    RIM
    RIM-Line generally follows a natural topographic barrier
    ROAD
    ROAD-Routes managed for use by low or high-clearance (4WD) vehicles, but not ATVs
    ROAD_OFFSET
    ROAD_OFFSET-Boundary is offset from a road (not a consistent buffer)
    SHORELINE
    SHORELINE-Lake, pond, reservoir, bay or ocean shoreline or meander line
    STREAM_LBANK
    STREAM_LBANK-Downstream left stream bank
    STREAM_RBANK
    STREAM_RBANK-Downstream right stream bank
    SUBDIVISION
    SUBDIVISION-Public Land Survey System derived aliquot (1/2s, 1/4s) parts and lots
    TRAIL
    TRAIL-Routes managed for human-powered, stock or off-highway vehicle forms of travel
    UNKNOWN
    UNKNOWN-Defining feature is unknown
    VEGETATION
    VEGETATION-Seeding boundary or other relatively permanent vegetation change
    WATERCOURSE
    WATERCOURSE-Stream, river, ditch, canal or drainage centerline
    WATERCOURSE_OFFSET
    "WATERCOURSE_OFFSET - Boundary is offset from a watercourse (not a consistent buffer)"

    COORD_SOURCE
    The actual source of the GIS coordinates for the polylines.   (Source: BLM)
                      

    ValueDefinition
    CFF
    CFF-Lines duplicated or buffered from Cartographic Feature Files (USFS)
    DEM
    DEM-Digital Elevation Model (30 m or better accuracy) used for creation of contours
    DIS
    DIS-Lines generated to connect discontinuous features
    DLG
    DLG-Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs
    DOQ
    DOQ-Screen digitized linework over Digital Orthoquad backdrop
    DRG
    DRG-Screen digitized linework over Digital Raster Graphic backdrop
    GCD
    GCD-Lines snapped to Geographic Coordinate Database Points
    GPS
    GPS-Lines obtained from a Global Positioning System device
    IMG
    IMG-Linework derived from interpretation of satellite or other non-photographic imagery
    MAP
    MAP-Digitized linework from hardcopy map
    SOURCEL
    SOURCEL-Source Layer from BLM GIS.
    SRV
    SRV-Survey methods were used to create the linework (e.g. COGO)
    TIGER
    TIGER-Tiger Data
    TRS
    TRS-Coordinates only given as a legal description (township, range, section)
    UNK
    UNK-Unknown coordinate source
    WOD
    WOD-WODDB Photogrametric

    COORD_SOURCE_ORG
    Name of the Agency that supplied the data (Source: BLM)
                      

    SOURCE_VINTAGE
    The date the data was added (Source: BLM)
                      

    SOURCE_LAYER
    Where the existing geometry came from. The majority of the geometry came from the GIS layer, GCD, however other layers have been and can be used to obtain geometry.  (Source: BLM)
                      

    GLOBALID
    Globally unique identifiers (Source: ESRI)
                      

    EDIT_ORG
    The Entity that edited the data (Source: BLM)
                      

    EDIT_DATE
    The date of the edit (Source: BLM)
                      

    SHAPE.LEN
    Entity and attribute detail citation:
    1) 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.
Back to Top

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

    • Bureau of Land Management - Oregon State Office

  2. Who also contributed to the data set?

  3. To whom should users address questions about the data?

    Frank Lahm
    Bureau of Land Management
    Cartographer
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6428 (voice)
    flahm@blm.gov
Back to Top

Why was the data set created?

Land use planning, watershed analysis, project planning.

Back to Top

How was the data set created?

  1. Where did the data come from?

    GCDB (source 1 of 16)

    CA BLM, Geographic Coordinate Database.

    Type of source media: CD-ROM
    Source scale denominator: 12000
    Source contribution:
    Lines, points, and attributes; supplied for the State of California and Nevada by the BLM California State Office.

    GHC_PLS (source 2 of 16)

    Grays Harbor County, Washington, GHC_PLS.

    Type of source media: onLine

    controlpoints (source 3 of 16)

    Thurston County, Washington, controlpoints.

    Type of source media: onLine

    Snohomish (source 4 of 16)

    Snohomish County, Washington, Snohomish.

    Type of source media: onLine

    cadastre_thenrit7505517 (source 5 of 16)

    Pierce County, Washington, cadastre_thenrit7505517.

    Type of source media: onLine

    Klickitat (source 6 of 16)

    Klickitat County, Washington, Klickitat.

    Type of source media: onLine

    FranklinCountyTwpId (source 7 of 16)

    Franklin County, Washington, FranklinCountyTwpId.

    Type of source media: onLine

    Whatcom (source 8 of 16)

    Whatcom County, Whatcom.

    Type of source media: onLine

    LewisCo (source 9 of 16)

    Lewis County, Washington, LewisCo.

    Type of source media: onLine

    FranklinCounty (source 10 of 16)

    Franklin County, Washington, FranklinCounty.

    Type of source media: onLine

    YakamaCog83 (source 11 of 16)

    Yakima County, Washington, YakamaCog83.

    Type of source media: None

    DCParcels9_8_06 (source 12 of 16)

    Douglas County, Washington, DCParcels9_8_06.

    Type of source media: onLine

    plss_coverage (source 13 of 16)

    Clallam County, Washington, plss_coverage.

    Type of source media: onLine

    Cc_gps points (source 14 of 16)

    Clallam County, Washington, Cc_gps points.

    Type of source media: onLine

    WODDB (source 15 of 16)

    OR/WA BLM, Western Oregon Digital Data Base.

    Type of source media: None
    Source scale denominator: 0
    Source contribution:
    Western Oregon Digital Data Base Lines, points, and attributes; supplied for the State of Oregon by the BLM Oregon State Office.

    GCDB (source 16 of 16)

    OR/WA BLM, 19950101, Geographic Coordinate Database: OR BLM, Portland, OR.

    Type of source media: CD-ROM
    Source scale denominator: 1200
    Source contribution:
    Lines, points, and attributes; supplied for the State of Oregon by the BLM Oregon State Office.

  2. What changes have been made?

    Date: not complete (change 1 of 5)
    Data 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.

    Person responsible for change:
    Tim Keck
    OR/WA BLM - Oregon State Office
    Land Surveyor, 957.3 GCDB Section
    P. O. Box 2965
    Portland, OR 97208-2965
    US

    503-808-6164 (voice)
    tkeck@or.blm.gov

    Data sources used in this process:
    • GCDB
    • WODBB

    Date: 20091023 (change 2 of 5)
    Washington 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.

    Person responsible for change:
    Steve Salas
    Bureau of Land Management, Oregon State Office
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    503 808-6416 (voice)
    ssalas@blm.gov

    Date: 20100601 (change 3 of 5)
    Data 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.

    Person responsible for change:
    Tim Keck
    OR/WA BLM - Oregon State Office
    Land Surveyor, 957.3 GCDB Section
    P. O. Box 2965
    Portland, OR 97208-2965
    US

    503-808-6164 (voice)
    tkeck@or.blm.gov

    Date: 20130606 (change 4 of 5)
    Tim Keck, State Data Steward for Survey data and Surface and Public Ownership data reviewed the spatial and attribute data and found that the data continues to meet the needs of the Bureau of Land Management.

    Person responsible for change:
    Tim Keck
    Bureau of Land Management
    Land Surveyor
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6164 (voice)
    tkeck@blm.gov

    Date: 20141027 (change 5 of 5)
    Changed dataseta name from LEGAL_DESCRIPTION_ARC to STATUS_ARC.

    Person responsible for change:
    Steve Salas
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6416 (voice)
    ssalas@blm.gov

Back to Top

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

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

  2. How accurate are the geographic locations?

    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.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    This theme covers the states of Oregon and Washington.

  5. How consistent are the relationships among the observations, including topology?

    The Legal_Description was built for polygon, arc, and node topology.

Back to Top

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access constraints: PUBLIC DATA: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and may contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived, and both scale and accuracy may vary across the data set. These data may not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Management Specialist
    P.O Box 2965
    Portland, OR 97208
    US

    503-808-6340 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov
    Contact Instructions:
    contact instructions

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.

  4. How can I download or order the data?

    • Cost to order the data: Contact distributor.


    • Special instructions:

      Data are only available through the Oregon/Washington State office of the Bureau of Land Management.

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20110830
Last reviewed: 20141028

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR 97208
US

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
r2mills@blm.gov
Hours of Service: 8:00-4:00
Contact Instructions:
None

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata(FGDC-STD-001-1998)

Back to Top