North-Facing Meteorological Met Station with air temp, incoming shortwave radiation, soil moisture, rain gage and barometric pressure
GGL_NF_Met is a 2.5 m multi parameter meterological tripod representing North facing aspects of Gordon Gulch.
See related for GGL_SF_Met (Gordon Gulch Lower South Facing Met Station)
Sensor ID and descriptions-
GGL_Met_NF, Communication, Campbell Scientific CR 1000 s/n 38503 Pakbus address of CR1000=13, replaced 20170317 wiring panel serial# 36616
Vaisala Barometer PTB110 s/n D0850005, current as of 3/17/17 M0310142
Li Cor 200x Pyranometer s/n PY58515. replaced on Range: 500-1100hPa, Output 0-2.5 Vdc, Supply 10-30 Vdc, Model PTB110 1B0CA, serial NO 00840011
REBS Q-7.1 Net Radiometer s/n Q10011 pos. calibration factor 8.94, negative calibration factor 11.04, replaced with Kipp and Zonen NR-Lite2 serial # 160923 sensitivity 12.9, height above ground: 180cm.
Campbell Scientific T-107 Soil Temperature Probe s/n CZOT_017, replace w HMP60L T AND RH SERIAL # M3141043, Campbell Scientific T-107 Temperature Probe s/n CZOT013 depth 22 cm., RMYoung 03101 L wind speed s/n CZOwind01, Campbell Scientific CS616 s/n CZOvw017, Texas Electronics TR 525M tipping bucket, replaced on 20170317 w TR-525M serial #45894-208. , Campbell Scientific RF401a spread spectrum radio serial # 2658, 10w solartech panel., Sun gaurd solar charge controller
Meteorological, Met, Air Temperature, Soil temperature, Shortwave Radiation, Net Radiation, Barometric Pressure, North Facing, Climate
XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.
Citation for This Dataset
Citation for This Webpage
Suzanne Anderson; Dillon Ragar (2019). "CZO Dataset: Gordon Gulch: Lower - Air Temperature, Meteorology (2012-2019) - North-Facing Meteorological Tower (GGL_NF_Met)." Retrieved 18 Apr 2019, from http://criticalzone.org/national/data/dataset/2888/
Data Use Policy
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 http://www.datacite.org/whycitedata). 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
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 http://www.datacite.org/whycitedata.
To fully zoom into a small area, you may need to visit the "Map" button and uncheck "Terrain" view.