. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR WA Cadastral PLSS Standardized Data PLSS Point

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR WA Cadastral PLSS Standardized Data PLSS Point

Abstract:
PLSSPOINT: PLSS Point data created by the Bureau of Land Management for the states of Oregon and Washington. This feature class is part of the Cadastral National Spatial Data Infrastructure (NSDI) CADNSDI publication data set for rectangular and non-rectangular Public Land Survey System (PLSS) data set. The metadata description in the Cadastral Reference System Feature Data Set more fully describes the entire data set (http://www.nationalcad.org/). These are the corners of the PLSS. This feature class contains summary information about the coordinate location and reliability of corner coordinate information. alternate names or aliases for corners are also inlcuded in this feature class.

  1. How should this data set be cited?

    BLM Cadastral Survey - <ST>, 20141026, BLM OR WA Cadastral PLSS Standardized Data PLSS Point.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.731900
    East: -116.463690
    North: 48.644464
    South: 41.992082

  3. What does it look like?

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

    Calendar date: 20141026
    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:
      Public Land Survey System (PLSS) locations

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Entity point (1807576)

    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?

    PLSSPoint
    These points represent the corners of the PLSS. This feature class contains summary information about the coordinate location and reliability of corner coordinate information. alternate names or aliases for corners are also inlcuded in this feature class. (Source: BLM)

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    COORDMETH
    The method of observation or measurement for the coordinate value. This typically indicates a technology such as GPS, digitized, line of sight (Source: BLM)
                      

    COORDSYS
    The coordinate system for the coordinate value, this may be different than the GIS coordinate system if the reported x,y values are different than the GIS coordinate system. (Source: BLM)
                      

    ELEV
    This is an average elevation for the entire PLSS Township (Source: BLM)
                      

    ERRORX
    The error in the X direction, typically computed from a least squares analysis (Source: BLM)
                      

    ERRORY
    The error in the Y direction,  typically computed from a least squares analysis (Source: BLM)
                      

    ERRORZ
    The error in the Z direction,  typically computed from a least squares analysis (Source: BLM)
                      

    HDATUM
    The horizontal datum for the coordinate value, this is the datum the reported coordinate value is reported in and may be different than the GIS horizontal datum (Source: BLM)
                      

    RELYTXT
    RELYNUMB
    LOCAL1
    The first alias for the corner point, most commonly occurs on PLSS Township boundaries where a point has an identifier in more than one township or when a rectangular and non-rectangular survey share a common corner.  If this is blank there is not a known alias. (Source: BLM)
                      

    LOCAL2
    The second alias for the corner point, most commonly occurs on PLSS Township boundaries where a point has an identifier in more than one township or when a rectangular and non-rectangular survey share a common corner.  If this is blank there is not a known alias (Source: BLM)
                      

    LOCAL3
    The third alias for the corner point, most commonly occurs on PLSS Township boundaries where a point has an identifier in more than one township or when a rectangular and non-rectangular survey share a common corner.  If this is blank there is not a known alias. (Source: BLM)
                      

    LOCAL4
    The fourth alias for the corner point, most commonly occurs on PLSS Township boundaries where a point has an identifier in more than one township or when a rectangular and non-rectangular survey share a common corner.  If this is blank there is not a known alias. (Source: BLM)
                      

    PLSSID
    Concatenation of the state, principal meridian, township, range, and duplicate code that forms a unique id for the PLSS Township (Source: BLM)
                      

    POINTID
    Unique point identifier for the corner  (Source: BLM)
                      

    POINTLAB
    PLSS Point label for cartographic output or web display. (Source: BLM)
                      

    REVISEDDATE
    The last revision date for the coordinate value for the PLSS Corner (Source: BLM)
                      

    STEWARD1
    The primary data steward for the plss point.  The alias for this field will be updated in the version 2 schema (Source: BLM)
                      

    STEWARD2
    The second data steward for the PLSS point. A second steward may be a person who has responsibility along an adjoining boundary. (Source: BLM)
                      

    VDATUM
    The vertical datum for an observed Z or height (Source: BLM)
                      

    XCOORD
    X, longitude or east coordinate value for the corner. (Source: BLM)
                      

    YCOORD
    Y, latitude or north coordinate value for the corner (Source: BLM)
                      

    SURVEYYEAR
    ZCOORD
    Z, Height, Observed Elevation for the corner (Source: BLM)
                      

    GLOBALID
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)

    • BLM Cadastral Survey - <ST>

  2. Who also contributed to the data set?

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

    Bureau of Land Management, Oregon State Office
    GCDB Manager
    P.O. Box 2965
    Portland, OR 97208
    US

    503-808-6164 (voice)
    503-808-6190 (FAX)
Back to Top

Why was the data set created?

This data provides the essential observed coordinate information for plss corners. This is not the complete data set for corners. These are the most current coordinates and a summary of information about the accuracy and quality of the coordinate values. Contact the identified data steward for more information.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 20120101 (change 1 of 2)
    For points with a BLM Cadastral as the data steward this feature class is built geographic coordinate database (GCDB) point files. All PLSS Points are at the nodes of line intersections and have a unique identifier as well as any applicable alias that represents the point identifier in adjoining townships or adjoining features. For points with county or state data stewards the PLSS corners are imported from geodatabase files provided by the data steward.

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

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

    Date: 20130607 (change 2 of 2)
    BLM Oregon GCDB Manager 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:
    BLM, Oregon State Office
    Land Surveyor
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6164 (voice)
    (503) 808-6190 (FAX)

Back to Top

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

  1. How well have the observations been checked?

    The BLM GCDB personnel using software tools such as dataprep and native GS tools in ArcGIS checked the data for attribute accuracy by verifying it against land records databases such as legal land description (LLD) and Case Status databases. There may be instances where information in survey records and LLD and Case do not agree or places where records are missing. If there are questions about the attribution of a polygon contact the identified data steward.

  2. How accurate are the geographic locations?

    Accuracy of the individual points contained in the PLSSPoint Feature Class that were determined using GMM software the resulting accuracy is reported with the point in the feature class. An overall statement of reliability may be provided for points that are derived from the least accurate component of the error ellipse(largest value). Accuracy of the individual points that were determined using PCCS software a carries positional reliability factor for the average of the misclosures in the data set and the maximum misclosure in the data set.

  3. How accurate are the heights or depths?

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

    This feature class represents all available geographic coordinate database (GCDB) at the time of publication. Every attempt was made to complete the rectangular Public Land Survey System(PLSS) to at least the First Division (section) level and to capture the outside boundary of non-rectangular PLSS features. Gaps or holes in the data that are know areas of conflict are presented in the ConflictedAreas feature class. If there are other gaps it is where data has not been automated, was not available from the data steward or was not of sufficient quality to be included.

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

    This feature class data set is topologically structured with nodes being constructed from the PLSS Points and hence points being coincident with nodes at all intersections.

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:
This data is for GIS and mapping purposes and is not intended to support or replace land survey data or the information provided by land survey. 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 for 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 information may be updated without notification.

Distributor 1 of 1

  1. Who distributes the data set?

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

    503-808-6565 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov

  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: 20130322
Last reviewed: 20130611

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

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

Back to Top