20260511
10040700
1.0
FALSE
TEMP_SAMPLE_PUB_PT
002
Geographic
GCS_North_American_1983
Angular Unit: Degree (0.017453)
<GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433],AUTHORITY["EPSG",4269]]</WKT><XOrigin>-400</XOrigin><YOrigin>-400</YOrigin><XYScale>999999999.99999988</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>8.983152841195215e-09</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><LeftLongitude>-180</LeftLongitude><WKID>4269</WKID><LatestWKID>4269</LatestWKID></GeographicCoordinateSystem>
20260514
09202000
20260514
09202000
150000000
5000
dataset
external
5a5e623f2f1754e1ac1730244bffa682caeb0e82
Scott Kiefer
Bureau of Land Management (BLM), Oregon State Office
GS0301 - Geographic Information System Specialist
P.O. Box 2965
Portland
OR
97208
US
skiefer@blm.gov
Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GIS Specialist
Role: Unknown
Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GIS Specialist
Role: Unknown
True
Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GS0301 - Geographic Information System Specialist
Role: Unknown
20260504
ArcGIS Metadata
1.0
Eric Hiebenthal
Bureau of Land Management
GIS Data Management Specialist
503-808-6565
503-808-6419
P.O Box 2965
Portland
OR
97208
US
ehiebent@blm.gov
contact instructions
Contact distributor.
2018-03-27
Data are only available through the Oregon/Washington State office of the Bureau of Land Management.
Arc GIS
Feature Class
Winzip
Winzip
Arc GIS, Winzip
https://gbp-blm-egis.hub.arcgis.com/pages/oregon
File Geodatabase Feature Class
BLM-STATE
Oregon
Washington
BLM-THEME
Hydrology
NONE
Hydrography
Streams
Water Temperature
U.S. Department of the Interior, Bureau of Land Management (BLM)
BLM OR Water Quality and Quantity Stream Temperature Publication Point
2026-05-14
Bureau of Land Management
Portland, Oregon
vector digital data
WTR_TEMP_PUB_PT: Stream temperatures are the result of a variety of energy transfer processes, including solar radiation, evaporation, conduction, and advection. Stream temperatures reflect seasonal changes in net radiation and daily changes in air temperatures. Patterns of energy input are also modified by flow velocity, flow depth, bottom substrate, and spring and groundwater inflow. The temperature tables defined in this data standard store the raw temperature measurements recorded by a continuous reading device (WTR_TEMP_RAW_TBL) and the attributes that are summarized from the raw data (WTR_TEMP_TBL).
The Water Quality dataset represents spatial location and basic information about stream sampling activities.
Bureau of Land Management (BLM), Oregon State Office
Michael Brown
OR/WA Bureau of Land Management
GS0401 - Natural Resource Specialist
(503) 808-6662
P.O. Box 2965
Portland
OR
97208
US
mebrown@blm.gov
environment
Hydrography
Hydrology
inlandWaters
Oregon
Streams
Washington
Water Temperature
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.
None, these data are considered public domain.
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.
ESRI Arc Catalog 10.4
-125
-116
41.5
49.5
publication date
2026-05-14
BLM (Bureau of Land Management) A published revision of the Department Manual’s Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm)
-125
-116
49
42
Non classified
None
Last metadata review date: 20260126
Non classified
None
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.
None, these data are considered public domain.
Unknown
Unknown
Unknown
Unknown
Point data was derived from the BLM SAMPLE_PT data and the values of WTR_TEMP_RAW_TBL were merged with the point data using a Relate table.
2018-03-25
Dana Baker-Alum
BLM
Senior GIS Applications Developer
(503) 808-6320
P.O. Box 2965
Portland
OR
97208
US
dbakerallum@blm.gov
Attributes AUDIT_RCVR_WET_WIDTH_FT, AUDIT_RCVR_SENS_DEP_FT, AUDIT_RCVR_TOT_DEP_FT, AUDIT_MID_WET_WIDTH_FT, AUDIT_MID_SENS_DEP_FT, AUDIT_MID_TOT_DEP_FT, AUDIT_DPLY_WET_WIDTH_FT, AUDIT_DPLY_SENS_DEP_FT, AUDIT_DPLY_TOT_DEP_FT, LOGGER_SERIAL_NO, LOGGER_EQUIP, BKF_WIDTH_FT, and DRAINAGE_AREA_AC.
2020-08-10
Dana Baker-Allum
BLM
Geospatial Data Designer
(503) 808-6340
P.O. Box 2965
Portland
OR
97208
US
dbakerallum@blm.gov
0
EPSG
6.5(3.0.1)
WTR_TEMP_PUB_PT
Feature Class
0
Stream temperatures
BLM
OBJECTID
OBJECTID
OID
8
0
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
SAMPLE_ID
Sample ID
Unique identifier for each sample point for the sampling indicated in SAMPLE_TYPE. Serves as the link to an external table (if any) with detailed measurement information by date (a one-to-many relationship). Districts are encouraged to develop standard naming schemes.
BLM
String
60
0
0
Examples: 5531-009, YA_1.5, WLD_RD_7, LUBI-01
SAMPLE_GRP
Sample Group
A sample grouping identifier, if needed.
BLM
String
50
0
0
Examples: A, Rattlesnake, North, South
SAMPLE_TYPE
Sample Type
The purpose for taking the sample at this location.
BLM
String
30
0
0
ACEC
ACEC - RNA monitoring
BLM
AIM Lentic
AIM Lentic - Assessment, Inventory, & Monitoring Lentic
BLM
AIM Lotic
AIM Lotic- Assessment, Inventory, & Monitoring Lotic
BLM
AIM Upland
AIM Upland - Assessment, Inventory, & Monitoring Upland
BLM
Aspen
Aspen - Stand monitoring
BLM
BMP
BMP - Best Management Practice
BLM
Contract
Contract - Monitoring of a contract or permit
BLM
Erosion
Erosion - Monitoring
BLM
Fire Effects
Fire Effects - Monitoring
BLM
Fish
Fish
BLM
Greenline
Greenline - Riparian measurement
BLM
HAF
HAF - Habitat Assessment Framework Monitoring
BLM
HMA
HMA - Wildhorse use or count
BLM
Juniper
Juniper - Measurement
BLM
MIM
MIM - Multiple Indicator Monitoring
BLM
Mineral Potential
Mineral Potential - Test wells or drill sites
BLM
Photo
Photo - Photo Sample Point
BLM
Range Trend
Range Trend - Monitoring
BLM
Range Utilization
Range Utilization - Measurement
BLM
Recreation Use
Recreation Use - Monitoring
BLM
Riparian
Riparian - Monitoring
BLM
Riparian Utilization
Riparian Utilization
BLM
Road/Trail
Road/Trail - Documentation
BLM
Sensitive Birds
Sensitive Birds - Monitoring
BLM
Sensitive Plants
Sensitive Plants - Monitoring
BLM
Shade
Shade - Measurement
BLM
Soil
Soil - Description
BLM
Soil Crust
Soil Crust - Monitoring
BLM
Stand Exam
Stand Exam
BLM
Stand Exam-EcoSurvey
Stand Exam-EcoSurvey
BLM
Stream Location
Stream Location
BLM
Study Plot
Study Plot - Research
BLM
Treatment
Treatment - Effectiveness or implementation monitoring
BLM
Vegetation
Vegetation - Plant Community
BLM
Water Contaminants
Water Contaminants - Measurement
BLM
Water Temperature
Water Temperature - Measurement
BLM
Water (Multiple)
Water (Multiple)
BLM
Wilderness Use
Wilderness Use - Monitoring
BLM
Wildlife Utilization
Wildlife Utilization - Measurement
BLM
Other
Other
BLM
Unknown
Unknown
BLM
SAMPLE_METH
Sample Method
The method or standard protocol used to conduct the sampling activity at this point. The method is dependent on the SAMPLE_TYPE.
BLM
0
String
30
0
AIM Lentic BLM TR 1735 X 2021
AIM Lentic BLM TR 1735 X 2021 - Field Protocol for Lentic Riparian and Wetland Systems (Draft)
BLM
AIM Lotic BLM TR 1735 2 2016
AIM Lotic BLM TR 1735 2 2016 - Field Protocol for Wadeable Lotic Systems
BLM
AIM Lotic BLM TR 1735 2 2017
AIM Lotic BLM TR 1735 2 2017 - Field Protocol for Wadeable Lotic Systems
BLM
AIM Lotic BLM TR 1735 2 2021
AIM Lotic BLM TR 1735 2 2021 - Field Protocol for Wadeable Lotic Systems
BLM
AIM Upland Method
AIM Upland Method - Monitoring Manual for Grassland, Shrubland, and Savanna Ecosystems 2nd Ed. Herrick et. al.
BLM
BAF Variable Radius Plot
BAF Variable Radius Plot - For timber stand exams
BLM
Belt Transect
Belt Transect - For vegetation
BLM
Circle Plot
Circle Plot - For vegetation
BLM
Cole Browse
Cole Browse
BLM
Counter
Counter - Traffic counter
BLM
ESI Veg Plot
ESI Veg Plot - Ecological Site Inventory
BLM
FIRE_MON
FIRE_MON - For fuels treatments
BLM
Fixed Area Plot
Fixed Area Plot - For timber stand exams
BLM
Fixed Radius Plot
Fixed Radius Plot - For timber stand exams
BLM
Fred Hall 2002
Fred Hall 2002 - Photo method
BLM
Hanna Multisensor Probe
Hanna Multisensor Probe
BLM
Herbaceous Utilization
Herbaceous Utilization
BLM
HOBO Temp Probe
HOBO Temp Probe
BLM
Line Point-Intercept
Line Point-Intercept
BLM
Line Transect
Line Transect - For vegetation or surface
BLM
MIM Rip. BLM TR 1737 23 2011
MIM Rip. BLM TR 1737 23 2011 - Multiple Indicator Monitoring of Stream Channels and Streamside Vegetation
BLM
Nested Frequency
Nested Frequency - For vegetation
BLM
NRCS 232
NRCS 232 - Soil description
BLM
Ocular Count
Ocular Count - Visual estimate
BLM
Ocular Cover
Ocular Cover - Vegetation cover estimate
BLM
Pace 180
Pace 180 - For vegetation
BLM
Photo
Photo
BLM
Thermometer
Thermometer
BLM
Trapping
Trapping
BLM
Utilization Cage
Utilization Cage
BLM
Winward 2000
Winward 2000 - Greenline method
BLM
Woody Utilization
Woody Utilization
BLM
Other
Other
BLM
Unknown
Unknown
BLM
LASTVISIT_DT
Last Visited Date
The last date that a sample was taken or measured at this point.
BLM
Date
0
0
0
ESTABLISH_DT
Established Date
The date the monitoring or sampling point was established in the field.
BLM
Date
0
0
0
DIRECTION
Direction
Direction of the sampling activity, if applicable. For example, the direction the camera is pointed or of a transect line. Expressed as one- or two-character compass cardinal direction points (eight choices, starting at N).
BLM
String
3
0
0
N
N - North
BLM
NW
NW - Northwest
BLM
W
W - West
BLM
SW
SW - Southwest
BLM
S
S - South
BLM
SE
SE - Southeast
BLM
E
E - East
BLM
NE
NE - Northeast
BLM
LENGTH_FT
Length (ft)
Length of the sampling activity, if applicable. The sample point is taken as the starting point. Combined with DIRECTION, a line can be created if needed.
BLM
Integer
4
0
0
Examples: 10, 25, 200
ELEVATION_FT
Elevation (ft)
The height of the ground above mean sea level. Measured in feet.
BLM
Integer
4
0
0
RATING1
Rating 1
For monitoring and sampling activities that have only one or two ratings or measurements and a related table or database is not needed. This attribute holds the last recorded rating or measurement only. RATING1, 2, and 3 all refer to the same measurement date. The RATING2 is only used if there is a second measure besides what is recorded in RATING1 and RATING3 is only used if there is a third measure besides what is in RATING1 and 2. Acceptable values depend on SAMPLE_TYPE and SAMPLE_METH and are established by the program. They might be qualitative such as “Good” or “Stable” or a number.
BLM
String
20
0
0
RATING2
Rating 2
For monitoring and sampling activities that have only one or two ratings or measurements and a related table or database is not needed. This attribute holds the last recorded rating or measurement only. RATING1, 2, and 3 all refer to the same measurement date. The RATING2 is only used if there is a second measure besides what is recorded in RATING1 and RATING3 is only used if there is a third measure besides what is in RATING1 and 2. Acceptable values depend on SAMPLE_TYPE and SAMPLE_METH and are established by the program. They might be qualitative such as “Good” or “Stable” or a number.
BLM
String
20
0
0
RATING3
Rating 3
For monitoring and sampling activities that have only one or two ratings or measurements and a related table or database is not needed. This attribute holds the last recorded rating or measurement only. RATING1, 2, and 3 all refer to the same measurement date. The RATING2 is only used if there is a second measure besides what is recorded in RATING1 and RATING3 is only used if there is a third measure besides what is in RATING1 and 2. Acceptable values depend on SAMPLE_TYPE and SAMPLE_METH and are established by the program. They might be qualitative such as “Good” or “Stable” or a number.
BLM
0
String
20
0
OTHERNAME
Other Name
It is not uncommon for the same monitoring or sampling point to have more than one name because of changes in staff and databases. Knowing the other names is sometimes critical to determining if the sample location is indeed the same or different than another named location. One or more historical names can be placed in this field.
BLM
String
100
0
0
TRT_PROJ_NM
Treatment Project Name
The name of the associated treatment or project that is being monitored, measured, or otherwise sampled.
BLM
String
50
0
0
COORD_SRC
Coordinate Source
The actual source of the GIS coordinates for the points.
BLM
String
7
0
0
CADNSDI
CADNSDI - Lines from or snapped to the CADNSDI dataset
BLM
CFF
CFF - Lines duplicated or buffered from Cartographic Feature Files (USFS)
BLM
DEM
DEM - Digital Elevation Model (30m or better accuracy) used for creation of contours
BLM
DGPS
DGPS - Feature obtained from a Global Positioning System device with Real Time Correction (SBAS)
BLM
DIS
DIS - Lines generated to connect discontinuous features
BLM
DLG
DLG - Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs
BLM
DOQ
DOQ - Screen digitized linework over digital orthophotography backdrop (DOQ, NAIP, OSIP, or others)
BLM
DRG
DRG - Screen digitized linework over Digital Raster Graphic backdrop
BLM
GCD
GCD - Lines snapped to Geographic Coordinate Database Points
BLM
GPS
GPS - Lines obtained from a Global Positioning System device
BLM
IMG
IMG - Linework derived from interpretation of satellite or other non-photographic imagery
BLM
LiDAR
LiDAR - LiDAR points, lines, or polygons generated through interpretation or analysis.
BLM
MAP
MAP - Digitized coordinates from hardcopy map or onto a map backdrop
BLM
MTP
MTP - Lines duplicated from Digital Master Title Plat
BLM
SOURCEL
SOURCEL - Coordinates duplicated from a BLM GIS source layer.
BLM
SOURCEX
SOURCEX - Source Layer from non-BLM GIS
BLM
SRV
SRV - Survey methods were used to create the linework (e.g., COGO)
BLM
TIGER
TIGER - Tiger Data
BLM
TRS
TRS - Coordinates only given as a legal description (township, range, section)
BLM
UNK
UNK - Unknown coordinate source
BLM
WOD
WOD - WODDB Photogrammetric
BLM
ACCURACY_FT
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 Graphs (DLG), Geographic Coordinate Database (GCD), and Digital Elevation Model (DEM)) 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.
BLM
Integer
4
0
0
CURRENT_CD
Current
Whether the sample point is currently in use or historic. Date/age does not determine this but whether the entity is now removed, obsolete, replaced, or erased in some sense.
BLM
String
1
0
0
C
C - Entity is still present on the ground
BLM
H
H - Entity is obsolete, obliterated or removed
BLM
N
N - Not applicable, entity still proposed
BLM
START_DT
Start Date
The starting date of the data collection period.
BLM
Date
8
1
0
Example: 5/1/2017
END_DT
End Date
The ending date of the data collection period. Date is entered as MM/DD/YYYY.
BLM
Date
8
1
0
Example: 8/15/2017
STUDY_DAYS_NUM
# Days in Study
The number of full (24 hour) days of temperature recordings.
BLM
SmallInteger
2
0
0
Examples: 112, 100
RAW_DATA_YN
Raw Data?
A Yes/No flag field to indicate if there is related raw temperature measurement data.
BLM
String
1
0
0
Y
Yes
BLM
N
No
BLM
U
Unknown
BLM
MAX_7DAM_TEMP_F
Max 7DAM Temp F
The 7-day average of the daily maximum stream temperature (7DAM) is "the 7-day moving average of the daily maximum temperatures." (Body, Mathew and Debra Sturdevant, p. 2) To calculate the rolling 7DAM, average the daily maximum temperature for that day plus the three previous days and three following days. The Max 7DAM is the highest 7DAM value for the data collection period.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
MAX_7DAM_MED_DT
7-Day Max Median Date
The date when the 7-day maximum temperature occurs. If the 7-day maximum temperature occurs on multiple days during the data collection period, enter the date occurring latest in the year. Date is entered as MM/DD/YYYY.
BLM
Date
8
1
0
Examples: 7/10/2007, 9/25/2010
MAX_7DAM_DELTA_F
7-Day Max Delta Temp F
The total fluctuation on the day of the seven day maximum temperature. For the maximum seven day average max, subtract the lowest temperature from the highest temperature (between 12:01am and 11:59pm local time). Values are recorded in degrees Fahrenheit and rounded to two decimal places.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
MAX_7DAMIN_TEMP_SUM_F
Max 7DAMIN Temp Sum F
The maximum 7DAMin is the highest value of the rolling daily minimum stream temperature for the Summer (May 21 to Sept 21). Values are recorded in degrees Fahrenheit and rounded to two decimal places..
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
MAX_7DAMIN_TEMP_SUM_DT
Max 7DAMIN Temp Sum Date
The maximum 7DAMin is the highest value of the rolling daily minimum stream temperature for the Summer (May 21 to Sept 21). This field records the date this occurs.
BLM
Date
8
1
0
Examples: 7/10/2007, 9/25/2010
MAX_FLUCT_SUM_F
Max Daily Summer Fluct F
The largest diurnal temperature fluctuation during the Summer (June 21 – Sept 21). Values are recorded in degrees Fahrenheit and rounded to two decimal places.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
MAX_FLUCT_SUM_DT
Max Fluct. Summer Date
The date of the maximum daily Summer fluctuation. Values are entered as MM/DD/YYYY.
BLM
Date
8
1
0
Examples: 7/23/2017, 8/4/2013
MAX_FLUCT_WIN_F
Max Daily Winter Fluct F
The largest diurnal temperature fluctuation during the Winter (Nov 1 – Apr 30). Values are recorded in degrees Fahrenheit and rounded to two decimal places.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
MAX_FLUCT_WIN_DT
Max Fluct. Winter Date
The date of the maximum daily Winter fluctuation. Values are entered as MM/DD/YYYY.
BLM
Date
8
1
0
Examples: 12/5/2012, 3/7/2007
DAY_GTSTD
No. of Days > Standard
Enter the number of days the temperature reading was above the State’s standard for that stream for the data collection period.
BLM
SmallInteger
2
0
0
MAX_7D_GTSTD
No. 7-Day Max > Standard
The number of 7-day max rolling values that are greater than the standard for the stream. Comparing values year to year is useful for monitoring trend.
BLM
SmallInteger
2
0
0
Examples: 5, 33
QC_PASSED_YN
QC Passed?
A yes/no field to indicate if the record met quality control requirements. Quality control requirements can vary.
BLM
String
2
0
0
Y
Yes
BLM
N
No
BLM
NA
No Assessment
BLM
U
Unknown
BLM
AUDIT_DPLY_DT
Audit Deploy Date
The date that the deployment audit was performed. This should be the same day the temperature logging equipment was inserted into the stream or water feature. If one of the Audit Deploy fields is filled out, ALL the fields must be filled out.
BLM
Date
8
1
0
Examples: 5/1/2000, 10/15/1999
AUDIT_DPLY_TIME
Audit Deploy Time
The time of day (in military measurements) that the deployment audit was performed. If one of the Audit Deploy fields is filled out, ALL the fields must be filled out.
BLM
String
4
0
0
Examples: 0512, 1455
AUDIT_DPLY_TEMP_F
Audit Deploy Temp F
The temperature measured by the sampling instrument at the time of the deployment audit. Values are recorded in degrees Fahrenheit and rounded to two decimal places. This value is used to compare against values recorded by the temperature logging equipment. If one of the Audit Deploy fields is filled out, ALL the fields must be filled out.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
AUDIT_DPLY_LOG_TEMP_F
Audit Deploy Logger Temp F
The temperature measured by the temperature logging equipment at the time of the deployment audit. Values are recorded in degrees Fahrenheit and rounded to two decimal places. If one of the Audit Deploy fields is filled out, ALL the fields must be filled out.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
AUDIT_MID_DT
Audit Mid-Season Date
The date that the mid-season audit was performed. If one of the Audit Midseason fields is filled out, ALL the fields must be filled out.
BLM
Date
8
1
0
Examples: 5/1/2000, 10/15/1999
AUDIT_MID_TIME
Audit Mid-Season Time
The time of day (in military measurements) that the mid-season audit was performed. If one of the Audit Midseason fields is filled out, ALL the fields must be filled out.
BLM
String
4
0
0
Examples: 0512, 1455
AUDIT_MID_TEMP_F
Audit Mid-Season Temp F
The temperature measured by the sampling instrument at the time of the mid-season audit. Values are recorded in degrees Fahrenheit and rounded to two decimal places. This value is used to compare against values recorded by the temperature logging equipment. If one of the Audit Midseason fields is filled out, ALL the fields must be filled out.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
AUDIT_MID_LOG_TEMP_F
Audit Mid-Season Logger Temp F
The temperature measured by the temperature logging equipment at the time of the mid-season audit. Values are recorded in degrees Fahrenheit and rounded to two decimal places. If one of the Audit Midseason fields is filled out, ALL the fields must be filled out.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
AUDIT_RCVR_DT
Audit Recovery Date
The date that the recovery audit was performed. This should be the same day the temperature logging equipment was removed from the stream or water feature. If one of the Audit Recovery fields is filled out, ALL the fields must be filled out.
BLM
Date
8
1
0
Examples: 5/1/2000, 10/15/1999
AUDIT_RCVR_TIME
Audit Recovery Time
The time of day (in military measurements) that the recovery audit was performed. If one of the Audit Recovery fields is filled out, ALL the fields must be filled out.
BLM
String
4
0
0
Examples: 0512, 1455
AUDIT_RCVR_TEMP_F
Audit Recovery Temp F
The temperature measured by the sampling instrument at the time of the recovery audit. Values are recorded in degrees Fahrenheit and rounded to two decimal places. This value is used to compare against values recorded by the temperature logging equipment. If one of the Audit Recovery fields is filled out, ALL the fields must be filled out.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
AUDIT_RCVR_LOG_TEMP_F
Audit Recovery Logger Temp F
The temperature measured by the temperature logging equipment at the time of the recovery audit. Values are recorded in degrees Fahrenheit and rounded to two decimal places. If one of the Audit Recovery fields is filled out, ALL the fields must be filled out.
BLM
Double
8
0
0
Temperature Range Domain (Fahrenheit). Range domain where the allowable values are -1 to 115.
GLOBALID_T
GLOBALID Temp
An alpha-numeric code that serves as the universal and unique identifier for each feature within the feature class or table of a geodatabase. Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data.
BLM
GUID
38
0
0
Example: {4747B796-44B4-4628-B069-2D496422E59F}
GLOBALID_SP
GLOBALID Sample Pt
An alpha-numeric code that serves as the universal and unique identifier for each feature within the feature class or table of a geodatabase. Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data.
BLM
GUID
38
0
0
Example: {4747B796-44B4-4628-B069-2D496422E59F}
SAMPLE_GUID
Sample GUID
Unique identifier for the Sample Points feature class. Used to relate Temperature or Cross-Section records to the SAMPLE_PT feature class.
BLM
GUID
38
0
0
Example value: “{E37EF156-4C20-4A78-A9BE-9EB4E6F00544}”
GLOBALID
GlobalID
An alpha-numeric code that serves as the universal and unique identifier for each feature within the feature class or table of a geodatabase. Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data.
Esri
GlobalID
38
0
0
Example: {4747B796-44B4-4628-B069-2D496422E59F}
SHAPE
SHAPE
Geometry
0
0
0
Feature geometry.
Esri
Coordinates defining the features.
Complete documentation and Attribute info4rmation may be found in the Water Quality and Quantity Spatial Data Standard located here:
https://www.blm.gov/about/data/oregon-data-management