. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Grazing Allotments and Pastures Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Grazing Allotments and Pastures Line

Abstract:
GRA_ARC: Linework describing livestock grazing allotment and pasture boundaries. For a complete description of this data contact the BLM Oregon Data Steward for a copy of "Grazing Allotments and Pastures Data Standard"

Supplemental information:
BLM -Bureau of Land Management Animal Unit - Considered to be one mature cow of approximately 1,000 pounds, either dry, or with a calf up to 6 months of age or equivalent based on a standardized amount of forage consumed. AUM (Animal Unit Month) - The amount of dry forage required by one animal unit for one month based on a forage allowance of 26 pounds per day. RAS (Rangeland Administration System) - The system used by BLM for billing for grazing on public land. The system contains allotments, pastures, permittees, grazing fees and other pertinent information related to public land grazing. Fenced Federal Range - Generally a small amount of public land fenced with a large amount of private land. Seed Ripe - In terms of plant phenology, it is that point from where seed becomes hard to the beginning of seed dispersal. Custodial - An area where the grazing system is not defined and resource values on public land are protected.

  1. How should this data set be cited?

    OR/WA BLM, 20140403, BLM OR Grazing Allotments and Pastures Line: OR, Portland.

    Other citation details:
    Geodatabase is known as GRA in internal BLM systems.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.077907
    East: -116.774507
    North: 49.000110
    South: 41.893851

  3. What does it look like?

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

    Calendar date: 20140403
    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 (29164)

    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.98315284119521e-009. Longitudes are given to the nearest 8.98315284119521e-009. 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?

    OSODBA.gra_arc
    Area of land designated and managed for livestock grazing. The polygons are attributed by a pasture number and naming system that is consistent with the Rangeland Administration System (RAS). All land, regardless of ownership or whether it is used for livestock grazing, may be covered with a polygon. (Source: 43CFR4100.05 and BLM Manual H-4110-1.22D)

    objectid
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    shape
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    DEF_FEATURE
    The physical or legal feature that defines the boundary according to the legal boundary description.  In general, the lowest level defining feature, but it depends on how the boundary segment is actually defined.  For example, SUBDIVISION rather than COUNTY unless the boundary segment is specifically defined as following the COUNTY boundary.  If the line is copied from another theme, and already has DEF_FEATURE, it should be reviewed and may need to be changed for use in this dataset.  Allotments and Pastures may be legally described by Township/Range and sections.  It is important to know the legal description.  However, it is not sufficient just to know the legal description because pastures are in fact defined by the physical features that keep livestock in or out.  Legal Land Lines are used only if there is no physically confining feature and the pasture needs to be closed.  If fences are not yet digitally captured it may be necessary to use ownership and section lines or roads or streams as legally described, but these should be replaced when the fence is captured.  If it is known that a particular pasture boundary segment is a fence, then the GRA_ARC attribute DEF_FEATURE should be set to "FENCE" even if the line temporarily used to depict it is a parcel line.  The GRA lines depicting pasture boundaries usually represent or are related to fences, rims, water, roads, subdivisions (sections or ownership) which may be found on other themes.  It is important to know as precisely as possible what defines a pasture boundary.  If the boundary is described as a stream then the question needs to be asked, "Which side of the stream?" because that determines which pasture includes the water.  Often a pasture boundary will follow the middle of a stream or road in which case the appropriate segment from the GIS transportation or hydrography theme is copied.  If the boundary is defined as one side or the other, then the transportation or hydrography segment can be buffered, and the appropriate buffer line used or an offset line can be digitized.  In summary, the following hierarchy is used for creating GRA lines and attributing DEF_FEATURE:  1.  FENCE, always use fencelines first, if possible 2.  RIM, LAKE, STREAM_LBANK, STREAM_RBANK, STREAM 3.  ROAD, ROAD_OFFSET 4.  SUBDIVISION 5.  POINT-TO-POINT 6.  UNKNOWN (Source: BLM)
                      

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

    COORD_SRC
    The actual source of the GIS coordinates for the line segments.  If the line is copied from another theme and already has COORD_SRC, it should be reviewed and may need to be changed for use in this dataset. (Source: BLM)
                      

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

    ACCURACY_FT
    How close, in feet, the spatial GIS depiction is to the actual location on the ground.  There are several factors to consider in GIS error:  scale and accuracy of map-based sources, accuracy of GPS equipment, and the skill level of the data manipulators.  A value of "0" indicates no entry was made.  This is the correct value when the COORD_SRC is another GIS theme (DLG, Geographic Coordinate Database (GCD), Digital Elevation Model) because the accuracy is determined by that theme.  However, if COORD_SRC is MAP (digitized from a paper map) or GPS, a value of "0" indicates a missing value that should be filled in either with a non-zero number or "-1." A value of "-1" indicates that the accuracy is unknown and no reliable estimate can be made. (Source: BLM)
                      

    GlobalID
    SHAPE.LEN
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)

    • OR/WA BLM

  2. Who also contributed to the data set?

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

    Robert Hopper
    Bureau of Land Management
    Rangeland Management Specialist
    2965 P.O. Box
    Portland, OR 97208
    US

    (503) 808-6118 (voice)
    (503) 808-6334 (FAX)
    rhopper@blm.gov
Back to Top

Why was the data set created?

Land use planning, allotment management plans, and analysis.

Back to Top

How was the data set created?

  1. Where did the data come from?

    GABS (source 1 of 11)

    BLM District range staff, unknown, Grazing Authorization and Billing System.

    Type of source media: None
    Source contribution:
    Attribute data.

    DRG (source 2 of 11)

    U.S. Geological Survey or another mapping agency in cooperation with USGS., 1:24,000-scale Digital Raster Graphics files: USGS, Reston, Virginia.

    Type of source media: None
    Source scale denominator: 24000
    Source contribution:
    Backdrop for screen digitizing lines for allotments and pastures.

    DLG (source 3 of 11)

    U.S. Geological Survey or another mapping agency in cooperation with USGS., 1:24,000-scale Digital Line Graphs: USGS, Reston, Virginia.

    Type of source media: None
    Source scale denominator: 24000
    Source contribution:
    Lines for allotments and pastures.

    GCDB (source 4 of 11)

    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:
    Polygon corners and lines.

    RAS (source 5 of 11)

    BLM District range staff, unknown, Rangeland Administration System.

    Type of source media: None
    Source contribution:
    Attribute data.

    Grazing Allotment Boundaries Forest Service Oregon (source 6 of 11)

    U.S. Forest Service, Grazing Allotment Boundaries Forest Service Oregon.

    Type of source media: None
    Source scale denominator: 24000
    Source contribution:
    Digital fencelines for adjacent allotments; FS allotment numbers.

    BLM-GRA (source 7 of 11)

    BLM District range staff, 20050101, BLM District records.

    Type of source media: hardcopyPaper
    Source scale denominator: 24000
    Source contribution:
    Polygons for allotments and pastures.

    DOQ (source 8 of 11)

    U.S. Geological Survey or another mapping agency in cooperation with USGS., 1:24,000-scale Digital Orthophoto Quadrangles: USGS, Reston, Virginia.

    Type of source media: hardcopyPhoto
    Source scale denominator: 24000
    Source contribution:
    Backdrop for screen digitizing lines for allotments and pastures.

    LLI (source 9 of 11)

    BLM OR/WA State Office, 19960901, Landlines: OR BLM, Portland, OR.

    Type of source media: None
    Source contribution:
    Lines for allotments and pastures.

    GPS (source 10 of 11)

    BLM District range staff, unknown, Global Positioning System data.

    Type of source media: None
    Source contribution:
    Lines for allotments and pastures.

    FS_CFF (source 11 of 11)

    U.S. Forest Service, Cartographic Feature Files: Cartographic Feature Files, U.S. Forest Service, .

    Type of source media: None
    Source scale denominator: 24000
    Source contribution:
    Digital fencelines

  2. What changes have been made?

    Date: unknown (change 1 of 5)
    Line feature class was exported from polygon

    Person responsible for change:
    Barbara Welsh-Haney
    Bureau of Land Management, Oregon State Office
    GS0301 - GIS Specialist (GIS DATA MGMT)
    PO Box 2965
    Portland, OR 97208
    US

    (503) 808-6313 (voice)
    bhaney@blm.gov

    Date: 20101227 (change 2 of 5)
    Deleted two parcels from AllotNum 00756 in the GRA per Angela Links instructions. These two parcels were transfered to Douglas County PUD and are no longer under BLM management.

    Person responsible for change:
    Alan Monek
    Bureau of Land Management, Wenatchee Field Office
    GIS Specialist
    915 Walla Walla
    Wenatchee, WA 98801
    US

    (509) 665-2142 (voice)
    (509) 665-2121 (FAX)
    amonek@blm.gov

    Date: 20111001 (change 3 of 5)
    Renamed fields GRADEFFEATURE to DEF_FEATURE, GRACOORDSOURCE to COORD_SRC , and GRAACCURACYFT to ACCURACY_FT which are the standard field names for feature-level metadata.

    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: 20111203 (change 4 of 5)
    New Allotment boundaries entered for McCormack, Coffelt (N/S) Klootchman, Scott, and Spring Creek Related to land exchange 12/2011

    Person responsible for change:
    Greg Daniels
    Bureau of Land Management
    GIS-Coordinator
    3050 NE 3rd Street
    Prineville, OR 97754
    US

    541-416-6768 (voice)
    gdaniels@blm.gov

    Date: 20130315 (change 5 of 5)
    Updates to Domain DEF_FEATURE and COOR_SRC.

    Person responsible for change:
    Roger Mills
    Bureau of Land Management
    GIS Spec.
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6340 (voice)
    r2mills@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?

    Some attribute data is contained within the Rangeland Administration System database. Accuracy of those attributes is assured through the annual billing process.

  2. How accurate are the geographic locations?

    Unknown

  3. How accurate are the heights or depths?

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

    Data is currently available for the Burns, Medford, Lakeview, Spokane, Coos Bay, Vale, and Prineville BLM Districts.

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

    Grazing allotments consist of unique polygons. Pastures are fully contained within one allotment.

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: 20130308
Last reviewed: 20130315

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