Long-term rainfall and discharge data from the Luquillo Experimental Forest (LEF) were analysed to develop relationships between rainfall, stream-runoff, and elevation. These relationships were then used with a Geographic Information System (GIS) to determine spatially-averaged, mean annual hydrologic budgets for watersheds and forest types within the study area. Model estimates indicate that a total of 3864 mm/yy (444 hm3) of rainfall falls on the forest in an average year. The Tabonuco, Colorado, Palm and Dwarf Forest types receive an estimated annual rainfall of 3537, 4191, 4167, and 4849 mm/yy, respectively. Of the average annual rainfall input, 65% (2526 mm/yr) is converted to runoff and the remainding 35% (1338 mm.yr) is lost from the system by evapotranspiration and other abstractions. In comparison to other tropical forests, the LEF as a whole has more evapotranspiration than many tropical montane forests but less evapotranspiration than many lowland tropical forests.
Hydrology, Water Chemistry
XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.
Citation for This Dataset
Scatena, F.N., IITF, Heartsil-Scalley, IITF. Bisley Weekly Bulk Rain Chemistry. 2008. https://www.sas.upenn.edu/lczodata/?q=content/bisley-weekly-bulk-rain-chemistry
Citation for This Webpage
Scatena, F.N.; IITF; Heartsil-Scalley (2007). "CZO Dataset: Bisley - Overland Water Chemistry, Nutrient Fluxes, Throughfall Chemistry, Rainfall Chemistry (1988-2007) - Including weekly bulk rain chemistry." Retrieved 20 Mar 2019, from http://criticalzone.org/luquillo/data/dataset/2627/
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.