GIS Metadata

BLM OR Fire Water Sources Point

Frequently-asked questions:

What does this data set describe?

BLM OR Fire Water Sources Point

FWTR_SRC_POINT: This theme depicts sources of water for fire management purposes that are accessible by engines, water tenders, pumps, or helicopter buckets. Water sources that are identified are judged to be useable during the period of a normal fire season. This theme does not depict water for uses other than fire fighting. For example, potable water is not identified in this theme.

Supplemental information:
BLM (Bureau of Land Management)

  1. How should this data set be cited?

    Bureau of Land Management, 20150331, BLM OR Fire Water Sources Point: BLM/USFS, 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?

    Calendar date: 20150331
    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:

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

    2. What coordinate system is used to represent geographic features?

  7. How does the data set describe geographic features?

    Sources of water that are accessible by fire engines, water tenders, pumps, or helicopter bucket. (Source: BLM)

    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    An indicator of the accuracy of the spatial location of the water source. (Source: BLM)

    1 - Within 10 feet of the actual location. 2 - Within 100 feet of the actual location. 3 - Within 1000 feet of the actual location. 4 - Not accurate within 1000 feet of the actual location.

    The general type of constructed features at the water source (i.e. access ramp, reservoir) (Source: BLM)

    The average depth of the water source (in feet). Depthof 0 (zero) allowed only when SUSTAINABILITY is Nonfunctional (N). Depth can be >0 when SUSTAINABILITY = N. (Source: BLM)

    Year the water source was established or first used for fire suppression activities. Four (4) character year beginning with 19 or 20 (YYYY). (Source: BLM)

    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    PLSS Section Number (Source: BLM)

    Water source that can used by fire engines to fill their water tanks. If the water source can be used by engines, then TYPE_SYM may only be E (Engine) or A (All). (Source: BLM)

    The equipment can use the water source.
    The equipment cannot use the water source.

    Name of water source that can be used for fire fighting purposes. (Source: BLM)

    The owner of the water source. (Source: BLM)

    The quantity of water (gallons) that can be stored at this water source. This is a coded field that represent a capacity range. (Source: BLM)

    A less than 500 gallons B 500 to 999 gallons C 1,000 to 9,999 gallons D 10,000 to 100,000 gallons E Over 100,000 gallons

    Water source that can used by helicopters to fill large water carrying buckets. If water source can be used by Helicopters, then TYP_SYM may only be H (Heli Bucket) or A (All). (Source: BLM)

    The equipment can use the water source.
    The equipment cannot use the water source.

    The quantity of water coming into the water source (in gallons per minute). If INFLOW equals zero, then SUSTAINABILITY must be either Nonfunctional or Initial Attack. (Source: BLM)

    The location of the water source in degrees, minutes, and seconds. Longitude followed by lattitude. This attribute is recalculated and repopulated upon check-in to the the GIS library. (Source: BLM)

    Identifies if maintenance is needed at the water source. (Source: BLM)


    Water from many sources is contaminated with a fungus that kills Port Orford Cedar and cannot be used in areas that are free of the fungus. (Source: BLM)

    The water source is contaminated with the fungus and cannot be used in disease free areas.
    The water source is free of the fungus and can be used in disease free areas.
    It is not known if the water source is contaminated with the fungus.

    Water source that can used by portable water carrying devices. If the water source can be used by portable devices, then TYPE_SYM may only be P (Portable) or A (All). (Source: BLM)

    The equipment can use the water source.
    The equipment cannot use the water source.

    The distance that water must be pumped from the water source to the fire equipment (engines and tenders). (Source: BLM)

    The State Water Right application number, if applicable, for the water source (A-NNNNNNN) where A = R or P and NNNNNNN = a number assigned by the Oregon Dept. of Water Resources. Example: R-1234567 (Source: BLM)

    Material used to line the water source. (Source: BLM)

    Identifies whether the water source is a natural or constructed feature. (Source: BLM)

    Water source is a natural feature.
    Water source is a constructed feature.

    The surface elevation of the water source. This is used primarily to determine whether the source can be utilized by helicopters. (Source: BLM)

    Ability of the fire water source to support fire suppression activities. (Source: BLM)

    Initial Attack Only

    Township and Range location of the fire water source. This attribute is generated from the Landlines theme.
    Must be TXXY-RXXY where X's are numbers and Y is direction North, South, East or West.
    Example: T27S-R09W
     (Source: BLM)

    Water source that can used by tenders (large tanker trucks used to refill smaller trucks with water). If water source can be used by tenders, then TYPE_SYM may only be T (Tender) or A (All). (Source: BLM)

    The equipment can use the water source.
    The equipment cannot use the water source.

    Symbol used in map display to identify the utilization type. Only one code may be entered. If more than one applies (but not all) the user must decide which code they want to display. (Source: BLM)

    H Helicopter Bucket E Engine T Tender P Portable A All

    The date the water source was last visited and its condition assessed. If populated this must be contain 8 characters (YYYYMMDD). Years must begin with 19 or 20, Months must be between 1-12, Days must be between 1-31. (Source: BLM)

    Watersource refers to the descriptive Data Category assigned to a water source such as a lake, river, guzzler etc. (Source: BLM)

    FS Streams. All natural or artificial channels of flowing water. This code therefore includes colloquial names such as river, gully, stream, creek, wash, channel, ditch and canals. SS Lakes. A natural or artificial standing (not flowing) body of water. This code therefore includes lakes, ponds, bays, estuaries, wetlands, and impoundments. UN Unclassified Water body. This code is used to represent water bodies that have not been classified. PS Springs Seeps and wells. An issue of water flowing from the earth onto the land or into a body of surface water. There is no distinction made between man made/enhanced and those which are natural therefore includes guzzler. Also includes standpipes and hydrants or any other point source of water.

    Entity and attribute overview:
    Attributes provide information about the fire water source - when it was established, accuracy of the location, amount of water available, types of fire equipment that can use the water source.

    Entity and attribute detail citation:
    The full detail on the attributes can be found in the Instruction Memorandum (Instruction Memorandum No. OR-2000-046) that issued the data standard.  A link to this memo can be found in the Identification section of this metadata report under ""Cross References"".
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 G. Guenther
    Forest Service
    System Analyst
    P.O. Box 2965
    Portland, OR97208-2965

    503-808-2188 (voice)
    503-808-6163 (FAX)
Back to Top

Why was the data set created?

Fire Management Purposes

Back to Top

How was the data set created?

  1. Where did the data come from?

    GPS (source 1 of 1)

    OR/WA BLM, Global Positioning System: OR BLM, Portland, OR.

    Type of source media: None

  2. What changes have been made?

    The FWTR_SRC layer was added to the BLM corporate district Arcinfo libraries. No data was available with which to populate the libraries. The layer was made transactional so that district editors may populate the layer with data.

    Date: 20070706 (change 2 of 6)
    Extract ArcInfo Library coverages, merged to a single coverage, projected to GCS and imported to ArcSDE Geodatabase.

    Person responsible for change:
    Steve Salas
    U.S. Bureau of Land Management - Oregon/Washington State Office
    GIS Specialist / ArcSDE Administrator
    503-808-6416 (voice)

    Date: 20080822 (change 3 of 6)
    Appended data for BLM's Lakeview district after matching values to the data standard. Summary of data collection: A Summer Temporary Employee was hired for approximately 8 weeks funded by fire/fuels money to conduct a field inventory and verification of Fire water sources. We started with a copy of the fire_water_source.gdb database, then created domains for fields that would benefit from their use. We "GPS enabled" the database with Trimble GPS Analyst extension for ArcGIS 9.2. We broke the inventory effort out into several components for purposes of prioritizing the work. We received a list of existing sources from the Klamath office of ODF, and created a point theme from their legal descriptions. Where these points landed on BLM land near roads we determined to be of high priority to visit and capture attribute data and verify location. The next phase of the work was to perform an intersection of BLM roads and Perennial streams, and perform a "spatial select" on the centroids of perennial water bodies near roads on BLM lands. Points were located, GPS'ed, and attributed in ArcPad. The final phase of the work was to obtain a copy of the Oregon Water Resources Department's water rights geodatabase and find the BLM water rights on BLM land within the resource area. These points were also located, GPS'ed and attributed. In some instances where there was an existing point feature in the database that was well located, ArcPad and the GPS unit were only used for attribution of the point. In other cases the points from the water rights database or ODF's point were not located at the most convenient place to fill an engine or tender and so were relocated using ArcPad. Matt Cornachione performed nearly all of the GPS and GIS work, with some assistance from Mike Limb (Klamath Falls Resource Area GIS Coordinator). All GPS locating, attributing, and recording was performed using ArcPad 7.x on a Trimble GeoXT GPS unit.

    Person responsible for change:
    Mike Limb
    U.S. Bureau of Land Management - Klamath Falls Resource Area
    GIS Coordinator
    541-885-4144 (voice)

    Date: 20081204 (change 4 of 6)
    Appended data for BLM's Roseburg district after matching values to the data standard. Attribute values for field RIGHTS_NUM are known to be incomplete (they lack the prefix letter of either "P" or "R") and will be updated when possible by Roseburg district staff. Summary of data collection provided by Roseburg district: Location information for the water sources was obtained from Tom Lonie. This was in the form of township, range and section and in many cases GPS coordinates. This information was used as a guide in locating the points. In addition to this information, Digital Ortho Quads were used as a background for digitizing water source locations. When they were not visible Tom Lonie, Bob Gilster Judy Hyde and Tom Doss were asked to help locate them based on their field experience. The points were added by Dale Gough using Arcedit. Attributes were then added based on the infomation supplied by the before mentioned people.

    Person responsible for change:
    Gary Passow
    U.S. Bureau of Land Managment, Roseburg District
    Natural Resources Specialist (GIS)
    (541) 464-3294 (voice)

    Date: 20110211 (change 5 of 6)
    Forty five water sources, GPS'ed by DFPA, were added to the layer. In addition, attributes for POC_RESTRICT were updated based on testing for Phyophthora lateralis, completed by the BLM in 2009 and 2010. As per Kevin Carson's guidance (South River SMRS), only water sources with P. lateralis were considered contaminated. If other species of Phytophthora were encountered the water source was considered clean. As well, any water sources previously attributed as contaminated, that were tested and not found to have P. lateralis, were changed to clean.

    Person responsible for change:
    Mike Hubbard
    GIS Specialist
    (541) 464-3387 (voice)

    Date: 20111003 (change 6 of 6)
    Data consists of historic and recently field verified potential water sources for the Medford BLM District. Sources for the sites include AutoCAD data, employee knowledge, and GPS data.

    Person responsible for change:
    Desraye Assali
    U.S. Bureau of Land Management, Medford District Office
    GIS Specialist
    541-471-6511 (voice)

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?

    No data currently exists.

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

    Transaction level: This level of quality control occurs when a district has completed an update to the FWTR_SRC theme and the resulting data layer is provided back for inclusion into the corporate geodatabase. GIS topological checking is limited at check-in time since this is a point theme. This theme has ""required"" fields that must be populated prior to updating the theme in the geodatabase. All text field data must be filled out in upper case. Upon check-in, all attributes are checked to assure that they conform to the data 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 might 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 sources from which they were derived, and both scale and accuracy may vary across the data set. These data might 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, Oregon State Office
    GIS Data Management Specialist
    P.O. Box 2965
    Portland, OR97208

    503-808-6565 (voice)
    503-808-6374 (FAX)
    Hours of Service: 7:30 a.m. to 4:00 p.m.

  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?

Last modified: 20130315
Last reviewed: 20111006

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR97208

(503) 808-6340 (voice)

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

Back to Top