Data Package Metadata   View Summary

Anole treefall gap transects (Bisley and El Verde-H10 Gaps)

General Information
Data Package:
Local Identifier:knb-lter-luq.2.308829
Title:Anole treefall gap transects (Bisley and El Verde-H10 Gaps)
Alternate Identifier:DOI PLACE HOLDER
Abstract:

Transects were established through large recent treefall gaps to determine the relative abundance of different anole species at different distances from the center of the gap.

Publication Date:2010-03-22
Language:English

Time Period
Begin:
1989-02-18
End:
1989-02-24

People and Organizations
Contact:Reagan, Douglas  [  email ]
Creator:Reagan, Douglas 
Associate:Melendez-Colom, Eda (University of Puerto Rico, Rio Piedras Campus, data manager)
Associate:Garcia, Miguel 

Data Entities
Data Table Name:
El Verde and Bisley Treefall Gap Transect Data
Description:
El Verde and Bisley Treefall Gap Transect Data
Detailed Metadata

Data Entities


Data Table

Data:https://pasta-s.lternet.edu/package/data/eml/knb-lter-luq/2/308829/bb38f3a7c3051537cf0eb25fda8502a7
Name:El Verde and Bisley Treefall Gap Transect Data
Description:El Verde and Bisley Treefall Gap Transect Data
Number of Records:35
Number of Columns:15

Time Period
Begin:
1989-02-22
End:
1989-02-24

Table Structure
Object Name:AnolisGAPTRANS.csv
Size:4845
Text Format:
Number of Header Lines:1
Number of Foot Lines:0
Record Delimiter:\r\n
Orientation:column
Simple Delimited:
Field Delimiter:,

Table Column Descriptions
 STUDYFILENAMELOCATIONTIMEDATETRANSECTSEASONTRANSECT_DISTANCE_(M)SPECIESSEX/AGEHEIGHTDISTANCE_FROM_CENTERLINEPERCH_SUBSTRATEPERCH_DIAMETERCOMMENTS
Column Name:Site of study  
Point of observation  
Plot location  
Time of observation  
Date  
Transect name  
Season of observation  
Transect distance  
Species name  
Sex or Age  
Perch Height  
Distance from central line  
Perch substrate  
Perch diameter  
Additional information  
Definition:Code assigned to the study area in relation to the tree species studiedFile name indicating where the observation was performed or forest level: Bisley or El VerdeStudy area including direction followed when observing along a transect of tower: Smithonian or H10 gap transecTime of observation (hh:mm:ss AA)Date of observation (mm/dd/yy)Transect name indicating its length or including direction followed when observing along a transect of tower, Starting at canopy end of 60m, starting at top end.Range of months in the year when observation was performedDistance in meters along each ground level transect in metersScientific name of species observedSex of adults or age stage of individualHeight above ground level in metersDistance from central axis of vertical transect to the lizardUnderlying line where lizard was observedDiameter of a pole or rod, usually horizontal, serving as a roost for the lizardComments; prey length in mm; miscellaneous observations, including color of enamel used; Maximum length of the prey item in mm
Storage Type:string  
string  
string  
string  
date  
string  
string  
  string  
string  
        string  
Measurement Type:nominalnominalnominalnominaldateTimenominalnominalrationominalnominalratioratioratiorationominal
Measurement Values Domain:
Allowed Values and Definitions
Enumerated Domain 
Code Definition
CodeGap
Definitionlarge recent treefall gaps
Source
DefinitionFile name indicating where the observation was performed or forest level: Bisley or El Verde
DefinitionStudy area including direction followed when observing along a transect of tower: Smithonian or H10 gap transec
DefinitionTime of observation (hh:mm:ss AA)
FormatDD/MM/YYYY
Precision
DefinitionTransect name indicating its length or including direction followed when observing along a transect of tower, Starting at canopy end of 60m, starting at top end.
Allowed Values and Definitions
Enumerated Domain 
Code Definition
Codedry
DefinitionJanuary to July
Source
Code Definition
Codewet
DefinitionJuly to December
Source
Unitmeter
Typereal
DefinitionScientific name of species observed
Allowed Values and Definitions
Enumerated Domain 
Code Definition
Code?
Definitionsex undetermined
Source
Code Definition
CodeF
Definitionfemale
Source
Code Definition
CodeF?
Definitionprobably a female
Source
Code Definition
CodeM
Definitionmale
Source
Code Definition
CodeM?
Definitionprobably a male
Source
Code Definition
Codeadult
Definitionindividual in adult stage
Source
Code Definition
Codehatch
Definitionhatching ( few days old, juvenile)
Source
Code Definition
Codejuvenile / sub-adult
Definition= individual in a juvenile to sub-adult stage
Source
Code Definition
Codesub-adult
Definitionindividual in a sub-adult stage
Source
Code Definition
Codesub-adult?
Definitionprobably a sub-adult, juvenile
Source
Code Definition
Codemale
Definitiona juvenile male individual
Source
Code Definition
Codejuvenile / female
Definition= a juvenile female individual
Source
Code Definition
Codejuvenile / male?
Definitionjuvenile and probably a male
Source
Code Definition
Codejuvenile / female?
Definitionjuvenile and probably a female
Source
Unitmeter
Precision0.1
Typereal
Unitmeter
Typereal
Unitcentimeter
Typereal
Unitcentimeter
Precision0.1
Typereal
DefinitionComments; prey length in mm; miscellaneous observations, including color of enamel used; Maximum length of the prey item in mm
Missing Value Code:                              
Accuracy Report:                              
Accuracy Assessment:                              
Coverage:                              
Methods:                              

Data Package Usage Rights

Data Policies

LTER Network Data Access Policy, Data Access Requirements, and General Data Use Agreement
approved by the LTER Coordinating Committee April 6, 2005

Long Term Ecological Research Network Data Access Policy

The LTER data policy includes three specific sections designed to express shared network policies regarding the release of LTER data products, user registration for accessing data, and the licensing agreements specifying the conditions for data use.

LTER Network Data Release Policy

Data and information derived from publicly funded research in the U.S. LTER Network, totally or partially from LTER funds from NSF, Institutional Cost-Share, or Partner Agency or Institution where a formal memorandum of understanding with LTER has been established, are made available online with as few restrictions as possible, on a nondiscriminatory basis. LTER Network scientists should make every effort to release data in a timely fashion and with attention to accurate and complete metadata.

Data[current-user:created]

There are two data types:

Type I – data are to be released to the general public according to the terms of the general data use agreement (see Section 3 below) within 2 years from collection and no later than the publication of the main findings from the dataset and,

Type II - data are to be released to restricted audiences according to terms specified by the owners of the data. Type II data are considered to be exceptional and should be rare in occurrence. The justification for exceptions must be well documented and approved by the lead PI and Site Data Manager. Some examples of Type II data restrictions may include: locations of rare or endangered species, data that are covered under prior licensing or copyright (e.g., SPOT satellite data), or covered by the Human Subjects Act. Researchers that make use of Type II Data may be subject to additional restrictions to protect any applicable commercial or confidentiality interests.

While the spirit of this document is to promote maximum availability for ecological data in either Type I or II status, there are criteria by which priority for data release may be determined. Primary observations collected for core research activities directly supported by LTER research must receive the highest priority for data release. Data collected by other sources to which LTER supported research has added value is also a high priority Other types of data including non-LTER data that was acquired for LTER research, student thesis data, schoolyard LTER data, or legacy data that already suffer from inadequate documentation or format obsolescence may be ranked a lower priority by a site with justifications provided in their data management policy. Finally, some data may be determined of lowest priority for archiving on the grounds that they are interim data that led to final products that carry the scientific value. These might include data files created during stages within an analytic workflow, raw or replicate data values that were subsequently aggregated or processed for release, or individual outputs from stochastic models.

Metadata

Metadata documenting archived/online data sets of all types listed above will be made available when, or before, the dataset itself is released according to the terms above.
All metadata will be publicly available regardless of any restrictions on access to the data.
All metadata will follow LTER recommended standards and will minimally contain adequate information on proper citation, access, contact information, and discovery. Complete information including methods, structure, semantics, and quality control/assurance is expected for most datasets and is strongly encouraged.
LTER Network Data Access Requirements

The access to all LTER data is subject to requirements set forth by this policy document to enable data providers to track usage, evaluate its impact in the community, and confirm users' acceptance of the terms of acceptable use. These requirements are standardized across the LTER Network to provide contractual exchange of data between Site Data Providers, Network Data Providers, and Data Users that can be encoded into electronic form and exchanged between computers. This will allow direct access to data via a common portal once these requirements have been fulfilled. The following information may be required directly or by proxy prior to the transference of any data object:

Registration

1. Name

2. Affiliation

3. Email Address

4. Full Contact Information

Acceptance of the General Public Use Agreement or Restricted Data Use Agreement, as applicable.
A Statement of Intended Use that is compliant with the above agreements. Such statements may be made submitted explicitly or made implicitly via the data access portal interface.

General Data Use Agreement

LUQ  data and metadata is released under public domain:  CC BY – Attribution.

Conditions of Use

The consumer of these data (“Data User” herein) has an ethical obligation to cite it appropriately in any publication that results from its use. The Data User should realize that these data may be actively used by others for ongoing research and that coordination may be necessary to prevent duplicate publication. The Data User is urged to contact the authors of these data if any questions about methodology or results occur. Where appropriate, the Data User is encouraged to consider collaboration or coauthorship with the authors. The Data User should realize that misinterpretation of data may occur if used out of context of the original study. While substantial efforts are made to ensure the accuracy of data and associated documentation, complete accuracy of data sets cannot be guaranteed. All data are made available “as is.” The Data User should be aware, however, that data are updated periodically and it is the responsibility of the Data User to check for new versions of the data. The data authors and the repository where these data were obtained shall not be liable for damages resulting from any use or misinterpretation of the data. Thank you.
Disclaimer

While substantial efforts are made to ensure the accuracy of data and documentation contained in this Data Set, complete accuracy of data and metadata cannot be guaranteed. All data and metadata are made available "as is". The Data User holds all parties involved in the production or distribution of the Data Set harmless for damages resulting from its use or interpretation.[current-user:name]

Keywords

By Thesaurus:
Core Areaspopulations
LTER Controlled Vocabularyorganisms, animals, vertebrates, reptiles, lizards

Methods and Protocols

These methods, instrumentation and/or protocols apply to all data in this dataset:

Methods and protocols used in the collection of this data package
Description:

A single 60m transect was established through two large treefall gaps. Each transect was centered on the center of the treefall gap and extended 30m from the center into the surrounding forest. The species, sex/age, distance along the transect line (m), height above ground level, perch diameter, substrate, and distance from centerline of the transect were recorded.

People and Organizations

Creators:
Individual: Douglas Reagan
Address:
350 Gordon Drive,
Castle Rock, CO 80104 US
Phone:
(303) 688-0754 (voice)
Email Address:
douglas_reagan@urscorp.com
Contacts:
Individual: Douglas Reagan
Address:
350 Gordon Drive,
Castle Rock, CO 80104 US
Phone:
(303) 688-0754 (voice)
Email Address:
douglas_reagan@urscorp.com
Associated Parties:
Individual: Eda Melendez-Colom
Organization:University of Puerto Rico, Rio Piedras Campus
Address:
University of Puerto Rico at Rio Piedras, Ponce de Leon Ave.,
San Juan, PR 00931 US
Phone:
(787) 764-0000 (voice)
Email Address:
edacorreo@yahoo.com
Role:data manager
Individual: Miguel Garcia
Address:
US
Email Address:
notavailable@lternet.edu
Role:associated researcher

Temporal, Geographic and Taxonomic Coverage

Temporal, Geographic and/or Taxonomic information that applies to all data in this dataset:

Time Period
Begin:
1989-02-18
End:
1989-02-24
Sampling Site: 
Description:Puerto Rico 988 El Yunque National Forest, Luquillo, 00773, Puerto Rico ‎ 550 m NE
Site Coordinates:
Longitude (degree): -65.7453Latitude (degree): 18.3164
Altitude (meter):924
Sampling Site: 
Description:Puerto Rico 988 El Yunque National Forest, Luquillo, 00773, Puerto Rico ‎ 515 m N
Site Coordinates:
Longitude (degree): -65.7432Latitude (degree): 18.3156
Altitude (meter):356

Temporal, Geographic and/or Taxonomic information that applies to Data Table: El Verde and Bisley Treefall Gap Transect Data


Time Period
Begin:
1989-02-22
End:
1989-02-24

Project

Other Metadata

EDI is a collaboration between the University of New Mexico and the University of Wisconsin – Madison, Center for Limnology:

UNM logo UW-M logo