. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Oregon Washington State Boundary Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Oregon Washington State Boundary Line

Abstract:
state_arc: This theme shows line representation of jurisdictional and cartographic state perimeters for Oregon and Washington.

Supplemental information:
BLM (Bureau of Land Management), CFF (Cartographic Feature File), DLG (Digital Line Graph), DNR (Washington Department of Natural Resources), DRG (Digital Raster Graphic), FIPS (Federal Information Processing Standard), GCD (Geographic Coordinate Database layer), GCDB (Geographic Coordinate Data Base), HYD (WODDB Hydrologic Features layer), LLI (Landlines layer), USFS (U.S. Forest Service), USGS (U.S. Geological Survey), WODDB (Western Oregon Digital Data Base). The POCA layer is an integrated set of geographic- referencing data covering the state of Washington. It is derived from land surveys, DNR orthophotos, USGS 7.5' quadrangles, and DNR tract books. This dataset is held in Librarian and can be exported in various extents, including individual states.

  1. How should this data set be cited?

    Bureau of Land Management, 20130130, BLM OR Oregon Washington State Boundary Line: OR BLM, Portland, OR.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -125
    East: -116
    North: 49.5
    South: 41.5

  3. What does it look like?

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

    Beginning date: 19990101
    Beginning time: unknown
    Ending date: 20010101
    Ending time: unknown
    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 Washington

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

    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 2e-008. Longitudes are given to the nearest 2e-008. 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?

    State Lines
    Outlines the states of Oregon and Washington. (Source: OR/WA BLM)

    type
    Distinction between a jurisdictional (statute) line and cartographic (geographic feature) line. That is, a distinction between the extent of a county's legal authority and the reach of a county's terra firma (solid ground). (Source: BLM)
                      

    ValueDefinition
    1
    Jurisdiction. OR: The County jurisdictional boundary where it is coincidental with a State or hydrologic boundary is defined as a combination of the surveyed boundaries between Oregon, California, Nevada, and Idaho; the State Seaward Boundary; the line in the Columbia River determined by the Oregon-Washington Columbia River Boundary Compact; and the middle of the main channel of the Snake River. WA: The County jurisdictional boundary where it is coincidental with a State or hydrologic boundary is defined as a combination of the surveyed boundaries of Washington, Oregon, and Idaho; the surveyed International Boundary between the United States and Canada; the middle of the main channel of the Snake River to the mouth of the Clearwater River; the agreed-upon boundary between the United States and Canada in the waters between Vancouver Island and the mainland of Washington; and the State Seaward Boundary.
    2
    Cartographic: western boundary will cut across bays and estuaries, etc., from bank to bank. OR: The County cartographic boundary where it is coincidental with a State or hydrologic boundary is defined as a combination of the surveyed boundaries between Oregon, California, Nevada, and Idaho; and the shoreline of the Pacific Ocean, Columbia and Snake Rivers, including the surveyed islands within the State jurisdictional boundary. WA: The County cartographic boundary where it is coincidental with a State or hydrologic boundary is defined as a combination of the surveyed boundaries between Washington, Oregon, and Idaho; the surveyed International Boundary between the United States and Canada; and the shorelines of the Pacific Ocean, Puget Sound, Straits of Juan de Fuca, and of those islands in the waters between Vancouver Island and the mainland of Washington south of the International Boundary between the U.S. And Canada.
    3
    Line segment is both jurisdictional and cartographic.
    0
    Unknown

    objectid
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    feature
    Type of land feature (Source: BLM)
                      

    ValueDefinition
    0
    Water
    1
    Islands in rivers
    2
    Islands in the ocean
    3
    Mainland

    reliability
    Reliability of the source of the line. Describes the accuracy of the line's position. (Source: BLM)
                      

    ValueDefinition
    1
    1 foot or less
    2
    3 feet or less
    3
    10 feet or less
    4
    40 feet or less (supports USGS and USFS data with a cutoff at the National Map Accuracy Standard for 7.5 minute maps)
    5
    100 feet or less
    6
    200 feet or less (supports USGS data when PLSS lines are depicted by dashed lines)
    7
    over 200 feet (supports USGS data when PLSS lines are not depicted)
    8
    Over 300 feet

    source
    The source used to locate the line. (Source: BLM)
                      

    ValueDefinition
    BLM
    BLM-generated lines
    CFF
    USFS Cartographic Feature File
    DLG
    USGS Digital Line Graph
    DRG
    USGS Digital Raster Graphic
    GCDB
    BLM Geographic Coordinate Data Base
    IBC
    MMS

    shape
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    SHAPE_Length
    Length of feature in internal units. (Source: Esri)
                      

    Positive real numbers that are automatically generated.

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

  2. Who also contributed to the data set?

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

    Corey Plank
    Bureau of Land Management
    Lead Cartographer
    P.O. Box 2965
    Portland, OR 97201
    US

    (503) 808-6427 (voice)
    cplank@blm.gov
Back to Top

Why was the data set created?

Resource management planning and mapping.

Back to Top

How was the data set created?

  1. Where did the data come from?

    USFS BD_CFF (source 1 of 6)

    OR BLM, Boundaries, CFF (Polygon, Line, Node): OR BLM, Portland, OR.

    Type of source media: None
    Source contribution:
    Lines

    BLM LLI (source 2 of 6)

    OR/WA BLM, 19960901, Landlines (Polygon, Node, Line): OR BLM, Portland, OR.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Lines and attributes

    MMS (source 3 of 6)

    DOI Mineral Management Service MMS, unknown, Mineral Management Service Maps: MMS, Reston, VA.

    Type of source media: None
    Source contribution:
    Lines

    USGS BD (source 4 of 6)

    USGS, 19981221, Boundaries, DLG Oregon (Polygon, Line, Node): OR BLM, Portland, OR.

    Type of source media: None
    Source contribution:
    Lines

    BLM HYD (source 5 of 6)

    BLM OR/WA, 19870101, Hydrologic Features (Lines).

    Type of source media: onLine
    Source scale denominator: 4800
    Source contribution:
    Lines

    BLM GCD (source 6 of 6)

    OR/WA BLM, 19890101, Geographic Coordinate Database Oregon (Point and Line): OR BLM, Portland, OR.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Lines

  2. What changes have been made?

    Date: 20010801 (change 1 of 2)
    BLM contractor used the cited sources (see source information) to extract the desired line work and create the new coverage. This was accomplished in ARCEDIT using the SELECT & PUT commands. The coverage was then cleaned, built for topology and projected to Lambert Conformal Conic. All line work was ultimately snapped to GCDB points where available.

    Person responsible for change:
    Don Hsiao
    Bureau of Land Management, Oregon State Office
    GIS Specialist
    503-808-6534 (voice)
    dhsiao@or.blm.gov

    Date: 20050101 (change 2 of 2)
    Original coverage version of the state boundary dataset was loaded into the Oregon Washington Corporate SDE instance as two separate feature classes (Line & Polygon). This SDE data is now considered the master version.

    Person responsible for change:
    Bryant Mecklem
    Bureau of Land Management, Oregon State Office
    GIS Specialist/SDE Administrator
    50.808.6506 (voice)
    bmecklem@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?

  2. How accurate are the geographic locations?

    Line accuracy is stored in the line attribute RELIABILITY, where codes are assigned based on the line source. See Entity and Attribute Information section for the breakdown used.

  3. How accurate are the heights or depths?

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

    This theme covers all public and private lands in Oregon and Washington.

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

    This theme was built for polygon 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: 20051118
Last reviewed: 20140211

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