. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Cadastral PLSS Intersected Polygon

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Cadastral PLSS Intersected Polygon

Abstract:
PLSSIntersected: This dataset represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-Attribute section of this metadata describes these components in greater detail.

  1. How should this data set be cited?

    BLM Cadastral Survey, 20140403, BLM OR Cadastral PLSS Intersected Polygon.

  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?

  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?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (1975279)

    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?

    PLSSIntersected
    The atomic level of the PLSS that is similar to the coverage or the smallest pieces used to build the PLSS. Polygons may overlap 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.

    FRSTDIVDUP
    A code indicating if the first division is a duplicated area or identifier (Source: BLM)
                      

    FRSTDIVID
    A unique identifier for the first division that is built by appending the first division elements on the Township identifier. (Source: BLM)
                      

    FRSTDIVLAB
    The label for the first division that is used for cartographic of web display purposes. (Source: BLM)
                      

    FRSTDIVNO
    The number, letter or designator for the first division of the PLSS Township (Source: BLM)
                      

    FRSTDIVTXT
    The first division type as a text field (Source: BLM)
                      

    FRSTDIVTYP
    The type of first division; commonly the section but may be a lot, parcel, tract or other type of division. (Source: BLM)
                      

    GOVLOT
    These are the Government Lot numbers or identifiers (Source: BLM)
                      

    PLSSID
    Concantenation of the principal meridian, township, range, and duplication code that forms a unique id. (Source: BLM)
                      

    PRINMER
    Principal meridian name as a text (Source: BLM)
                      

    PRINMERCD
    Principal meridian code from the BLM PM Code list (Source: BLM)
                      

    QQSEC
    This is the quarter quarter PLSS reference, 1/16th part of a section (Source: BLM)
                      

    QSEC
    Quarter section identifer, a two letter label (NE,SE,SW,SE) (Source: BLM)
                      

    RANGEDIR
    Range direction. The direction of a column of townships from a Public Land Survey System Origin. These are typcially East or West in the west but may be north or south in Ohio (Source: BLM)
                      

    RANGEFRAC
    Range fraction. Range Fractions are created when there are gaps between surveyed Township boundaries or due to excess size in Townships that arose from executing original surveys. (Source: BLM)
                      

    RANGENO
    Range number. The Range Number indicates the number of columns of townships, east or west from a Public Land Survey System Origin. (Source: BLM)
                      

    SECDIVID
    Unique identifier for the second division. (Source: BLM)
                      

    SECDIVLAB
    PLSS Second Division label for cartographic output or web display. (Source: BLM)
                      

    SECDIVNO
    Second division number or aliquot part reference. (Source: BLM)
                      

    SECDIVNOTE
    A note or Code for the second division. Used for additional information (Source: BLM)
                      

    ValueDefinition
    R
    Replaced, (a historical reference for a parcel that has been changed)
    A
    Approximate acres
    Alt Source
    Alternate Source (non-GCDB) data was acquired to represent the PLSS
    C
    Conflict, (data has a problem that needs to be resolved)
    C, Alt Source
    Conflict, Alt Source (the Alternate source dat has a problem that needs resolution)
    D
    Do not add acres, or PLSS Submerged
    E
    Exception
    G
    GeoPolitical Split
    Island
    Unsurveyed Unprotracted Islands 
    N
    Not coded due to complexity
    P
    Survey Acres are different than on the plat
    Remainder
    Reaminder of a government lot 
    S
    Salt water
    Shore line
    Land between the meandered PLSS and the mean high tide line (Ocean)
    U
    Survey within a protraction
    M
    Minus acres
    X
    Exception, or Elongated, or Invaded by resurvey

    SECDIVSUF
    Second division suffix used to uniquely identify duplicates or unnumbered lots (Source: BLM)
                      

    SECDIVTYP
    Code for the type of second division. (Source: BLM)
                      

    STATEABBR
    State abbreviation code two letter postal code (Source: BLM)
                      

    SECDIVTXT
    Second division type text description (Source: BLM)
                      

    STEWARD
    Data steward for the polygon (Source: BLM)
                      

    SURVLAB
    Label that is used for cartographic output or web display. (Source: BLM)
                      

    SURVNO
    Special survey number. (Source: BLM)
                      

    SURVNOTE
    Notes about the polygon feature that are important for using or understanding the feature. From the BLM SurvNotes are A = Approximate Acreage, C = Conflict or Questionable, D = Non-added Acreage (Source: BLM)
                      

    SURVID
    Unique identifier for the survey. (Source: BLM)
                      

    SURVSUF
    Special survey suffix designation that makes the identification of the area unique. (Source: BLM)
                      

    SURVTYPTXT
    The description of the survey type code.  There may be a description of the survey type, or survey status in the case of this feature, without a code. (Source: BLM)
                      

    SRVNAME
    A common or otherwise recognized name for a portion of area of a PLSS Survey, for example the refugee lands in Ohio or in cases where a PLSS Township has a recognized name. (Source: BLM)
                      

    SURVTYP
    Code of the type of special survey. (Source: BLM)
                      

    ValueDefinition
    B
    Minor subdivsion less than 40 acres
    C
    Coal 
    D
    Allotment
    E
    Metes & Bounds
    G
    Land Grant
    H
    Homestead Entry Survey
    I
    Indian Allotment
    J
    Small Tract Act holding claim
    K
    Block & Lot within a townsite
    L
    Government Lot
    M
    Mineral Survey
    N
    Townsite
    O
    Unnumbered lot, (refer to 2ndivsuff for unique identification)
    P
    Parcel
    Q
    Donation Land Claim
    T
    Tract
    U
    Unsurveyed Protracted
    W
    Water
    Y
    Townsite out lot
    Z
    Unsurveyed Unprotracted

    TWNSHPDIR
    Township direction. The direction of a row of Townships from a Public Land Survey System Origin. These are typcially North and South in the West but may be East and West in Ohio (Source: BLM)
                      

    TWNSHPDPCD
    If there are multiple townships in a Public Land Survey System Origin, State and Survey Name, the Township Duplicate Status is used to establish uniqueness. When more than one Public Land Survey System Township has the same Township and Range numbers and directions and fractions, and are in the same State, this attribute is used to distinguish among duplicate values. (Source: BLM)
                      

    SURVDIV
    The name or designation for any division of a PLSS Special Survey such as Lot in a Tract. (Source: BLM)
                      

    TWNSHPFRAC
    Township fraction. Township Fractions are created when there are gaps between surveyed Township boundaries or due to excess size in Townships that arose from executing original surveys. (Source: BLM)
                      

    TWNSHPLAB
    Township label that is used for cartographic output or web display (Source: BLM)
                      

    TWNSHPNO
    Township number. The Township Number indicates the number of rows of townships, north or south from a Public Land Survey System Origin. (Source: BLM)
                      

    SOURCEREF
    The reference to the source document could be a reference to a map or plat or a deed. This could include document type. (Source: BLM)
                      

    SOURCEDATE
    The date of the source document. (Source: BLM)
                      

    RECRDAREATX
    No definition. (Source: BLM)
                      

    RECRDAREANO
    The record or recorded area as a numeric field. (Source: BLM)
                      

    GISACRE
    The area of the feature in acres - computed from the GIS, this is not the record area. (Source: BLM)
                      

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

    Positive real numbers that are automatically generated.

    SHAPE_Area
    Area of feature in internal units squared. (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)

    • BLM Cadastral Survey

  2. Who also contributed to the data set?

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

    Travis Thomas
    Bureau of Land Management
    Land Surveyor
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6177 (voice)
    t2thomas@blm.gov
Back to Top

Why was the data set created?

The CADNSDI or the Cadastral Publication Data Standard is the cadastral data component of the NSDI. This is the publication guideline for cadastral data that is intended to provide a common format and structure and content for cadastral information that can be made available across jurisdictional boundaries, providing a consistent and uniform cadastral data to meet business need that includes connections to the source information from the data stewards. The data stewards determine which data are published and should be contacted for any questions on data content or for additional information. The cadastral publication data is data provided by cadastral data producers in a standard form on a regular basis. Cadastral publication data has two primary components, land parcel data and cadastral reference data. It is important to recognize that the publication data are not the same as the operation and maintenance or production data. The production data is structured to optimize maintenance processes, is integrated with internal agency operations and contains much more detail than the publication data. The publication data is a subset of the more complete production data and is reformatted to meet a national standard so data can be integrated across jurisdictional boundaries and be presented in a consistent and standard form nationally.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    The Oregon GCDB Office will need to be contacted for complete data processing details

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

    503 808-6164 (voice)
    503 808-6164

    Date: unknown (change 2 of 6)
    FGDC Cadastral Subcommittee developed the Cadastral Data Content Standard and submitted it for approval to the FGDC. This was completed in 1998. The most recent version of the FGDC Cadastral Data Content Standard is version 1.4. Federal Geographic Data Committee, 2008, Cadastral Data Content Standard for the National Spatial Data Infrastructure, Version 1.4, Subcommittee on Cadastral Data, Reston, Virginia.

    Date: unknown (change 3 of 6)
    Executive Order 12906 calls for the establishment of the National Spatial Data Infrastructure defined as the technologies, policies, and people necessary to promote sharing of geospatial data throughout all levels of government, the private and non-profit sectors, and the academic community.

    Date: 20031230 (change 4 of 6)
    In 2003 the Cadastral Subcommittee met in Portland Oregon, hosted by the Forest Service, and defined the polices and needs for establishing a robust Cadastral Publication Data Standard for the NSDI.

    Date: 20071230 (change 5 of 6)
    In 2007 after a series of workshops and meetings with key business functions a set of core data was documented. This document was published on the Subcommittee's outreach web site (http://www.nationalcad.org) and it described the data and organizational relationships for the maintenance of the data that is the Cadastral NSDI. This document served as a standard for the Cadastral NSDI content.

    Date: 20081230 (change 6 of 6)
    In 2008 the first draft of the Cadastral Publication Guidelines was published as GIS schema. This document has been revised through the testing efforts from Wildland fire and the western US PLSS data set developed. The final version of the publication guidelines was completed in the Fall of 2009.

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?

  3. How accurate are the heights or depths?

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

    The Subcommittee recognizes that not all data is available in all places, but the data that is available should be provided for publication in the format provided in this guideleines. Exceptions to complete data should be noted by the data steward. The Oregon Data Set contains all of the available GCDB PLSS data.

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

    Data conforming to the Publication Guideline should follow for the format and structure of the standard for published data. This means that the topological relationships of the PLSS and parcels should be followed. Level 1 conformance to the guideline means that the data follows and conforms to the structure and an active data steward is identified and engaged in data creation and maintenance. Level 2 conformance all attributes that are necessary for essential query, extraction, labeling and use are present. Level 3 conformance all attributes as applicable are populated. The Oregon Data Set is at Level 3 of 3 Conformance and fully complies with the national standard

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?

    Downloadable Data

  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: 20140402

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