. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Fire History Point

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Fire History Point

Abstract:
FIRE_POINT: This dataset represents points of origins of BLM fires that occur naturally (e.g., lightning) or by humans accidentally (e.g., escaped campfire) or maliciously across Oregon and Washington. The dataset includes some, but not all, historic fires (fires declared 'out' in calendar years prior to the current year). There is no lower size limit for fires to be included. In addition, many non-BLM Federal and State agencies fire origins are present.

Supplemental information:
There is no lower size limit for fires to be included, although BLM does require capture of a final perimeter on fires 10 acres or larger in Type 1 (BLM land protected by BLM) and Type 2 (BLM land protected by another Federal agency under a cooperative agreement or contract; including mutual aid agreements) scenarios. Single tree ignitions and extremely small fires are generally omitted from FIRE_POLY and found only on FIRE_POINT. In addition, while FIRE_POINT contains fire origin points for most of the fires whose perimeters are included on FIRE_POLY, there are perimeters without a corresponding point; particularly for historic fires. It should be noted in the standard that the national standards (both BLM and Interagency) are being considered for revision and this standard should be considered interim until those updates occur.

  1. How should this data set be cited?

    Bureau of Land Management, 20130823, BLM OR Fire History Point.

  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?

    Calendar date: 20130425
    Currentness reference:
    publication date

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

  6. How does the data set represent geographic features?

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

      It contains the following vector data types (SDTS terminology):
      • Entity point (11990)

    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?

    FIRE_POINT
    Points of origin for wildfires (Source: BLM)

    OBJECTID
    Internal feature number. (Source: Esri)
                      

    Sequential unique whole numbers that are automatically generated.

    UNIT_ID
    The unit identifier for the agency that has primary protection responsibility at the point of origin at the time of the incident.  The administrative unit at the fire's point of origin. Domain values to lengthy to list. See Data Standard for complete list. (Source: NWCG)
                      

    SHAPE
    Feature geometry. (Source: Esri)
                      

    Coordinates defining the features.

    FIRE_NUM
    Official fire incident number assigned at dispatching office.  Obtained from Wildcad application. A four to six digit number assigned to a fire by the reporting unit that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.   (Source: NWCG)
                      

    FIRE_CODE
    Cost accounting tracking number assigned by the FireCode application.  For the BLM, pre-Fiscal Year 2004 (prior to the FireCode system), this is the fire number assigned to the incident by the reporting office. (Source: NWCG)
                      

    FIRE_NAME
    The name assigned to an incident; assigned by responsible land management unit. (Source: NWCG)
                      

    COMPLEX_NAME
    Name of complex.  Applicable only if fire was incorporated into a complex at any point before declared contained.  A complex is two or more incidents located in the same general area which are assigned to a single incident commander or unified command.  Incidents are an occurrence, either human-caused or natural phenomenon, that requires action or support by emergency service personnel to prevent or minimize loss of life or damage to property and/or natural resources. (Source: NWCG)
                      

    FIRE_YEAR
    The year in which the fire occurred.  In YYYY format. (Source: NWCG)
                      

    INC_ID
    A unique identifier generated for each wildland fire. Concatenation of fire year, FIRE_UNIT_ID, and FIRE_NUM yyyy-SSUUUU-xxxxxx yyyy = calendar year SSUUUU = FIRE_UNIT_ID xxxxxx = local incident identifier (FIRE_NUM)  (Source: NWCG)
                      

    WFMI_ID
    The Unique Identifier (FireID) assigned to each fire in the Wildland Fire Management Information system (DOI fires only). (Source: WFMI (Wildland Fire Management Information))
                      

    LOCAL_NUM
    Local identifying number (code) for a fire.  Legacy number or number used prior to assignment of official FIRE_NUM. (Source: NWCG)
                      

    FIRE_DSCRV_DATE
    The date the fire was confirmed to exist or was reported as discovered.  In YYYYMMDD format.  UNKNOWN is an allowable entry. (Source: NWCG)
                      

    BLM_ORG_CD
    A combination of the BLM administrative state and field office which has administrative responsibility for the spatial entity.  This includes which office covers the entity for planning purposes and which office is the lead for GIS edits.  Another agency or individual may have the physical management responsibility for the on-the-ground entity.  This field applies particularly when a spatial entity crosses resource area or district boundaries and the administrative responsibility is assigned to one or the other rather than splitting the spatial unit.  Similarly, OR/WA BLM may have administrative responsibility over some area that is physically located in Nevada, Idaho, and California and vice versa.  When appropriate, the office can be identified only to the district or even the state level rather than to the resource area level. (Source: BLM)
                      

    ValueDefinition
    OR000
    Oregon/Washington BLM
    ORB00
    Burns District Office
    ORB05
    Three Rivers Field Office
    ORB06
    Andrews Field Office
    ORC00
    Coos Bay District Office
    ORC03
    Umpqua Field Office
    ORC04
    Myrtlewood Field Office
    ORE00
    Eugene District Office
    ORE05
    Siuslaw Field Office
    ORE06
    Upper Willamette Field Office
    ORL00
    Lakeview District Office
    ORL04
    Klamath Falls Field Office
    ORL05
    Lakeview Field Office
    ORM00
    Medford District Office
    ORM05
    Butte Falls Field Office
    ORM06
    Ashland Field Office
    ORM07
    Grants Pass Field Office
    OR08
    Glendale Field Office
    ORP00
    Prineville District Office
    ORP04
    Central Oregon Field Office
    ORP06
    Deschutes Field Office
    ORR00
    Roseburg District Office
    ORR04
    Swiftwater Field Office
    ORR05
    South River Field Office
    ORS00
    Salem District Office
    ORS04
    Cascades Field Office
    ORS05
    Marys Peak Field Office
    ORS06
    Tillamook Field Office
    ORV00
    Vale District Office
    ORV04
    Malheur Field Office
    ORV05
    Baker Field Office
    ORV06
    Jordan Field Office
    ORW00
    Spokane District Office
    ORW02
    Wenatchee Field Office
    ORW03
    Border Field Office

    CONTROL_DT
    The date the wildfire is surrounded by fireline or natural features such that its burning potential is reduced to a point that it no longer threatens further spread or resource damage under foreseeable conditions.  UNKNOWN is an allowable entry.   In YYYYMMDD format. (Source: NWCG)
                      

    DISC_TIME
    Time the fire was discovered expressed as Universal Time Co-Ordinated time.  Also referred to as Zulu time.  For example, 11:01 a.m. Pacific Standard time is 1901 Zulu.  See http://navysite.de/what/zulu.htm for more information and a conversion table. (Source: BLM)
                      

    OUT_DATE
    The date when all observable combustion has ceased or there is no risk that the fire will become active again and require additional control or management actions.  UNKNOWN is an allowable entry. (Source: NWCG)
                      

    CAUSE_CAT
    The general circumstance which caused a fire or set the stage for its occurrence (Human vs Natural). (Source: BLM)
                      

    ValueDefinition
    Unknown
    Cause of the fire is not known
    Human
    Fire was caused by humans
    Natural
    Fire was naturally caused (e.g., lightning)

    CAUSE_DET
    More detailed description of the cause of a fire than what is provided in CAUSE_CAT. (Source: BLM)
                      

    CLASSIFIER
    Name (mixed case, first and last) of the person or agency who provided the fire perimeter or point coordinates.  For FIRE_POINT, this may be the name of the national database point coordinates were downloaded from. (Source: BLM)
                      

    COORD_SRC
    The actual source of the GIS coordinates for the points.  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
    CADNSDI
    Lines from or snapped to the CADNSDI dataset
    CFF
    Lines duplicated or buffered from Cartographic Feature Files
    DEM
    Digital Elevation Model (30m or better accuracy) used for creation of contours
    DLG
    Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs Typical Accuracies (40 feet)
    DIS
    Lines generated to connect discontinuous features
    DOQ
    Screen digitized linework over Digital Orthoquad backdrop
    DRG
    Screen digitized linework over Digital Raster Graphic (USGS) backdrop
    GCD
    Lines snapped to Geographic Coordinate Database Points
    GPS
    Lines obtained from a Global Positioning System device
    IMG
    Linework derived from interpretation of non-photographic imagery
    MAP
    Digitized line work 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
    TIGER
    Tiger data
    TRS
    Coordinates only given as a legal description (township, range,section)
    UNK
    Unknown coordinate source
    WODDB
    WODDB (Western Oregon Digital Database) Photogrammetric

    COORD_DATE
    Date the coordinates, whose source is listed in COORD_SRC, were collected. In YYYYMMDD format. (Source: BLM)
                      

    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 (Digital Line Graph, Cadastral National Spatial Data Infrastructure and 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)
                      

    TOT_ACRES_RPTD
    Official final reported burned acres.  May differ from GIS_ACRES total. (Source: NWCG)
                      

    COMMENTS
    Free text for comments about the fire point (Source: BLM)
                      

    VERSION_NAME
    Name of the corporate geodatabase version previously used to edit the record. (Source: BLM)
                      

    GLOBALID
    Automatically generated ID number (Source: ESRI)
                      

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?

    Dale Guenther
    US Forest Service
    System Analyst
    333 Southwest First Avenue
    Portland, OR 97204
    US

    (503) 808-2188 (voice)
    dguenther@fs.fed.us
Back to Top

Why was the data set created?

This dataset is used to display historic wildfire points of origin on maps. The number and spatial extent of fire across the landscape is important information for natural resource management and planning activities. Fire points will be combined with a wide variety of other GIS datasets including habitat and special management areas for effects and impact analyses.

Back to Top

How was the data set created?

  1. Where did the data come from?

    Unknown (source 1 of 1)

    Data Resource Management/Fire & Aviation, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture, 20071228, S_R06.FireHistoryPt.

    Type of source media: onLine
    Source scale denominator: 24000
    Source contribution:
    Geospatial data obtained from Forest local Geographic Information System data library. Some forests maintain fire data, for years before 1970, when Kansas City Fire Occurrence Database was established.

  2. What changes have been made?

    The following information was taken from individual forests metadata, only where metadata was attached to data, when it was submitted to DST. GIFFORD PINCHOT NATIONAL FOREST; Fire History points for 2006 were summarized from Fire Reports into FIRESTAT 2006 for GIS.xls by Dispatch (Amy Davis). Location information was in degrees, minutes, seconds or Township, Range, Section (fractions) descriptions. Amy used a conversion tool on her PC to convert to decimal degrees and entered the latitude/longitudes into the .xls file. Irene Ward formatted a copy of the .xls (fires06.xls) using Excel and MS Access to add and define the standard data fields, populated Agency, Data_Source, Cause (a numeric field from the initial Cause text field), Size_Class from Reported_Acres field, and formatted Fire_Day and Fire_Month with leading zeros, and Fire_Name using the PROPER function to have first letter of a word in upper case, the rest in lower case (and checked for the other syntax requirement for fire names). The resulting event table (Fires06) was brought into ArcMap, for Display X,Y. Had first added SDE feature class S_R06.FireManagement/S_R06.FireHistoryPt in ArcMap, so could use it's spatial reference when exporting the point events. Exported to a personal geodatabase for loading into a template personal geodatabase created per draft Fire History Edit Guide, March 27, 2007 from the R6 DRM Data Standardization Team (Colleen Williams). MOUNT HOOD NATIONAL FOREST; Jaimie Bradbury acquired 3 point shapefiles by year (2004, 2005, 2006) in UTM10 NAD27 from Jim Wrightson, Fire, Mt. Hood NF HQ, as queried and generated from the National Fire Occurrence Database, NIFMID. Jaimie projected shapefiles to Albers NAD83 and imported each year into separate point feature class with existing attribute fields in working personal geodatabase. Created new point feature class in final personal geodatabase, imported National GIS Data Dictionary defined fields from standardized forehis_pt coverage. Loaded separate year point feature classes from working personal geodatabase into single point feature class in final personal geodatabase, mapping fields available to match National GIS Data Dictionary fields. In ArcMap, joined working personal geodatabase tables for each fire occurrence year to the fire history point feature class in the final personal geodatabase, calculated value for NIFMID_LNK by concatenating fields as described in National GIS Data Dictionary. NIFMID number was not provided with original data. Calculated FIRE_DAY, FIRE_MONTH, and FIRE_YEAR values by parsing DISC_DATE field using VBScript function DatePart (interval, date_field). Added two missing points by creating event layer from longitude, latitude x,y coordinates in decimal degrees supplied by Jim Wrightson. Saved as shapefile with original shapefiles. Projected to Albers NAD83, saved with other projected shapefiles, imported into working personal geodatabase, and loaded into point feature class in final personal geodatabase. Fire history corporate dataset update was submitted to Data Standardization Team (Colleen Williams) 3/30/2007. UMPQUA NATIONAL FOREST; Points were imported from a spreadsheet using decimal degrees, converted to a shapefile, and then a coverage. Spreadsheet retrieved from fire database. MALHEUR NATIONAL FOREST; The points layer was developed through the FAMWEB, KC Fast, fire, fire reports. Choose the "Corporate GIS for Administrative Unit format". The file that is produced contains all of the mandatory data fields required by the corporate data standard. A username and password is required to use this site. In most cases the Fire Management Officer or Dispatcher on the Forest unit will have access to the web site and know how t run the query. Once the file has been downloaded to a PC, run the fire-hispt_con.aml. The aml is designed to process data that has been downloaded from the databasea dn will create an output "GIS" coverage. Data from the south end of the forest (within the BIFZ fire planning unit) up to date through 2004. Data from the north end is only complete through 2002. Process Steps and Process Description: 20050210 - Rick Momsen, Data Standardization Team contractor through Titan Corp.; standardized coverage to agree with the GIS Core Data Dictionary. 20050523 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; copied to double precision. 20050715 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; Updated with fire points from BLM Burns District (Stacy Fenton). Layer created from various sources: Burns BLM, Malheur NF, Snow Mountain District, NIFMID/KCFAST national database. Since almost all of Malheur's points from before 2002 were hand-drawn ("HD"), I decided to use the BLM layer which had a more accurate location. To make it easier I also used the BLM 2002 NIFMID locations. I added the FS attributes to the BLM layer and calculated the values in from BLM. Where the locations overlapped, I deleted the FS point. On the NIFMID points I manually calculated the values from the FS coverage onto the BLM point. Snow Mountain fire points before 1993 were added from the Snow Mountain library fire_pcha and fire_pt layers: from 1985-92 from pcha as that was more accurate; before 1985 from fire_pt. The final steps were to clip the BLM layer to the Malheur watershed extent, remove the BLM attributes, and merge the BLM layer into the firehis_pt coverage. 20060327 - Dave Stockdale, GIS/Data Services Analyst on the Malheur National Forest; Reprojected to Region 6 Albers NAD83 projection. 20070323 - Teri Corning-Sevey, GIS/Data Services Specialist on the Malheur National Forest; Updated with 2006 fire season points. UMATILLA NATIONAL FOREST; Completeness Report: All fires less than ten acres and start locations for larger fires are shown in this coverage to the effect that fire locations where given to the Umatilla GIS for input. The coverage is completed each year for each year to follow. Process Steps and Process Description: 20040429 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Pathfinder office gps files, other venders gps files, ascii text files of lat and long coordinates from kcfast, heads up digitizing using DRGS. Year update process is to pull new locations from KCFAST database. You need to have a WIMS username and password. Go to http://famweb.nwcg.gov/ and select KCFAST, Fire, Fire Reports. Put in administrative unit (0614), begin year and end year. Then select corporate GIS for Administration unit. The report will go to a FTP site and retrieve from there. Take text file report and add column headings by inserting a new text line at start of file. Project file using ArcCatalog assuming a geographic projection with a NAD83 Datum from North America. Then reproject to local projection. Match PAT table and append to existing coverage. 20041222 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Added in 2004 year fire start locations. All locations were derived from the data in the KCFast database. All locations were derived from the Latitude and Longitude stored in the database for the 2004 fires. All Lat and Long were assumed to be in NAD83 Geographic and then reprojected to the local projection. 20050627 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Dropped redundant items that are also in the PCHA database. Corrected the locations of some points where the Lat and Long values were incorrectly entered. 20060301 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Reprojected to Region 6 Albers NAD83 projection. 20070309 - Andrew Lacey, Forest GIS Coordinator on the Umatilla National Forest; Added calendar year 2005 and 2006 fires from Information in the NIFMID and or KCFast interface. Points were reprojected from a NAD83 Geographic Projection into the local projection. COLVILLE NATIONAL FOREST; Process Steps and Process Description: 19990112 - Dave Larson on the Colville National Forest; Colville NF - FOC Oracle database on DG converted to Info and added to FOC.pat. 20010307 - Janice Berube on the Colville National Forest; Added fire occurrence points for 1999 and 2000 - Colville NF. 20040121 - Janice Berube on the Colville National Forest; Fire starts added for 2002 and 2003 (with Nancy Cassel) - Colville NF. 20050121 - Rick Momsen, Data Standardization Team contractor through Titan Corp.; standardized coverage to agree with the GIS Core Data Dictionary. Metadata updated. 20050128 - Cindy Potestio on the Colville National Forest; Fire starts for 2004 (Colville NF) added (with Jimmy Corvino), missing information added for fires back to 1994, metadata updated. 20060119 - Janice Berube, GIS/Data Services Specialist on the Colville National Forest; Fire starts for 2005 (Colville NF) added (with Nancy Cassel). Matched attribute fields to a R6 data standardization copy by Colleen Williams requested by Dale Guenther for the National Data Warehouse on 07/29/05. Removed SO- from local_number. Deleted USF0608 points outside of Colville NF administrative boundary. Changed Agency field for BIA points. Newport District added 2002/2003 BIA points. These points have missing attributes which will be completed at a later date. 20060320 - Cindy Potestio, GIS/Data Services Analyst on the Colville National Forest; Reprojected to Region 6 Albers NAD83 projection.

    Data sources used in this process:
    • Each individual National Forest submitted data files to DST, for the Initial Standardization Phase and the First Major Update Cycle. Where metadata was present in forest covers, the Process Step and Process Description was summarized here, for each forest having metadata.

    Date: 20071228 (change 2 of 3)
    Initial Standardization Phase was completed in 2005 and the First Major Update Cycle for 2006 data was completed in 2007. During the Initial Standardization Phase and the First Major Update Cycle, all Fire History data was submitted to Region 6 Data Resource Management (DRM) Data Standardization Team (DST), by each Forest's GIS Fire Data Manager, from Region 6, in ArcInfo coverage export file format or as shapefiles. During the update process the same file formats were received with the addition of personal geodatabases. Data files were received via e-mail or downloaded from the FTP server, ftp2.fs.fed.us. Data was re-formatted, standardized, and loaded into the Enterprise Fire History Region 6 feature dataset S_R06.FireManagement in SDE.

    Person responsible for change:
    Colleen Williams
    Data Standardization Team, Data Resource Management, Pacific Northwest Region, Forest Service, U.S. Department of Agriculture
    Database Standardization Specialist
    Wallowa-Whitman National Forest
    Baker City, OR 97814
    US

    541-523-1253 (voice)
    cmwilliams@fs.fed.us

    Date: 20130501 (change 3 of 3)
    1. Created Fire_History geodatabase with feature classes, attributes, and domains according to the Fire History data standard. 2. Populated FIRE_POINT feature class with fire origin point locations submitted by Districts, and adjusted attributes as needed. Attribute completeness varied greatly across the submissions. 4. Identified and removed true duplicates.

    Person responsible for change:
    Barbara W. Haney
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208

    503-808-2741 (voice)
    bhaney@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?

  3. How accurate are the heights or depths?

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

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

    FIRE ORIGIN POINTS (FIRE_POINT) Description: Instance of Fire group. Geometry: Simple, not multi-part points. Topology: No topology enforced. Integration Requirements: Each FIRE_POLY perimeter may have zero or one FIRE_POINT and the point must fall within the polygon.

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: 20130503
Last reviewed: 20130823

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