Dataset Listing

Oracle Ridge - Meteorology (2010-2019)

Meteorological Data from the Oracle Ridge Site

Variables:  Precipitation, Barometric pressure, Temperature, Relative humidity, Dew point temperature, Battery voltage

Standard Variables:  Barometric pressure|Battery voltage|Temperature, dew point|Precipitation|Relative humidity

Date Range:  (2010-10-18 to 2019-05-17)

Dataset Creators/Authors:  Peter Troch; Nate Abramson

Contact:  Peter Troch, Department of Hydrology and Water Resources, University of Arizona, 1133 E James E. Rogers Way Tucson, AZ 85721,

Field Area:   Oracle Ridge (Mid-Elevation)

Keywords & XML
  • Description

    Standard meteorological data are being collected at the Oracle Ridge site (mid elevation) using a Onset HOBO U30 weather station. Air temperature, relative humidity, pressure and rainfall intensity are continuously monitored at 10 minute intervals.

    Data are provisional and may be subject to revision. Data for 2011 and later were collected and managed by Nate Abramson, Research Specialist, University of Arizona, Pressure sensor malfunctioned on 12/29/2010. Data logger malfunction on 3/29/2011. New logger HOBO Micro Station H21-002 installed and pressure sensor replaced on 4/29/2011. Bear broke RH and Temperature probe on 5/20/2011. New RH and Temperature probe installed on 7/18/2011. Dew point temperature computed starting on 8/25/2011. Most of data are missing between 6/4/2012 and 8/20/2012 because of a bear attack on the weather station. No data recorded from 8/21/2014 to 12/16/2014 because of logger failed. No data recorded from 2/1/2015 to 3/13/2015 because of logger failed.
  • Keywords

    Meteorology, Precipitation, Barometric pressure, Temperature, Relative humidity, Dew point temperature, Santa Catalina Mountains, Arizona.

    XML Metadata

    XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.

  • Citation for This Dataset

    The following acknowledgment should accompany any publication or citation of these data - Logistical support and/or data were provided by the NSF-supported Jemez River Basin and Santa Catalina Mountains Critical Zone Observatory EAR-0724958.

    Citation for This Webpage

    Peter Troch; Nate Abramson (2019). "CZO Dataset: Oracle Ridge - Meteorology (2010-2019)." Retrieved 13 Dec 2019, from

  • Acknowledgements


    National Science Foundation EAR-0724958
    National Science Foundation EAR-1331408


Sites - Methods

(nas/)   Data Level 0

Oracle Ridge - Meteorological Data 2010

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2011

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2012

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2013

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2014

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2015

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2016

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2017

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2018

(.csv)   Data Level 0,  Metadata

Oracle Ridge - Meteorological Data 2019

(.csv)   Data Level 0,  Metadata

Data Use Policy
Data Sharing Policy
Research Groups/Foci
  • Data Use Policy

    DRAFT v.0.4.0

    1. Use our data freely. All CZO Data Products* except those labelled Private** are released to the public and may be freely copied, distributed, edited, remixed, and built upon under the condition that you give acknowledgement as described below. Non-CZO data products — like those produced by USGS or NOAA — have their own use policies, which should be followed.

    2. Give proper citation and acknowledgement. Publications, models and data products that make use of these datasets must include proper citation and acknowledgement. Most importantly, provide a citation in a similar way as a journal article (i.e. author, title, year of publication, name of CZO “publisher”, edition or version, and URL or DOI access information. See Also include at least a brief acknowledgement such as: “Data were provided by the NSF-supported Southern Sierra Critical Zone Observatory” (replace with the appropriate observatory name).

    3. Let us know how you will use the data. The dataset creators would appreciate hearing of any plans to use the dataset. Consider consultation or collaboration with dataset creators.

    *CZO Data Products.  Defined as a data collected with any monetary or logistical support from a CZO.

    **Private. Most private data will be released to the public within 1-2 years, with some exceptionally challenging datasets up to 4 years. To inquire about potential earlier use, please contact us.

  • Data Sharing Policy

    DRAFT v.0.2.5

    All CZO investigators and collaborators who receive material or logistical support from a CZO agree to:

    1. Share data privately within 1 year. CZO investigators and collaborators agree to provide CZO Data Products* — including data files and metadata for raw, quality controlled and/or derived data — to CZO data managers within one year of collection of samples, in situ or experimental data. By default, data values will be held in a Private CZO Repository**, but metadata will be made public and will provide full attribution to the Dataset Creators†.

    2. Release data to public within 2 years. CZO Dataset Creators will be encouraged after one year to release data for public access. Dataset Creators may chose to publish or release data sooner.

    3. Request, in writing, data privacy up to 4 years. CZO PIs will review short written applications to extend data privacy beyond 2 years and up to 4 years from time of collection. Extensions beyond 3 years should not be the norm, and will be granted only for compelling cases.

    4. Consult with creators of private CZO datasets prior to use. In order to enable the collaborative vision of the CZO program, data in private CZO repositories will be available to other investigators and collaborators within that CZO. Releasing or publishing any derivative of such private data without explicit consent from the dataset creators will be considered a serious scientific ethics violation.

    * CZO Data Products. Defined as data collected with any monetary or logistical support from a CZO. Logistical support includes the use of any CZO sensors, sampling infrastructure, equipment, vehicles, or labor from a supported investigator, student or staff person. CZO Data Products can acknowledge multiple additional sources of support.

    ** Private CZO Repository. Defined as a password-protected directory on each CZO’s data server. Files will be accessible by all investigators and collaborators within the given CZO and logins will be maintained by that local CZO’s data managers. Although data values will not be accessible by the public or ingested into any central data system (i.e. CUAHSI HIS), metadata will be fully discoverable by the public. This provides the dual benefit of giving attribution and credit to dataset creators and the CZO in general, while maintaining protection of intellectual property while publications are pending.

    † Dataset Creators. Defined as the people who are responsible for designing, collecting, analyzing and providing quality assurance for a dataset. The creators of a dataset are analogous to the authors of a publication, and datasets should be cited in an analogous manner following the emerging international guidelines described at

  • Research Groups/Foci

CZO Field Areas


CZO Authors

Explore Further

data |

Explore Further