site-phenometrics
Determine the typical start and end dates of phenological activity for each species at a monitoring site by aggregating individual observations.
Instructions
About the tool: Aggregates individual phenological data to provide average start and end dates of phenological activity for each species at each monitoring site. Represents the 'typical' timing for a species at a location by averaging across all individuals of that species at the site.
When to use: Creating phenological calendars, analyzing site-specific timing patterns, comparing phenology across locations, understanding regional growing seasons, or studying how local climate affects species timing.
Key applications:
Phenological calendars: Creating seasonal timing guides for specific locations
Growing season analysis: Quantifying length of active growing periods for sites/regions
Climate relationship studies: Investigating how phenological timing relates to temperature, precipitation, and seasonal patterns
Site comparisons: Comparing phenological timing across elevation gradients, latitude gradients, or different habitat types
Regional management: Planning for activities like controlled burns, invasive species management, or ecotourism
Agricultural applications: Understanding wild plant timing to inform crop management decisions
Scientific context: Site phenometrics average out individual variation to reveal location-specific phenological signatures. Essential for understanding how climate drivers affect species timing at landscape scales.
Research applications:
'When do oak leaves typically emerge at Yellowstone vs. Great Smoky Mountains?'
'How long is the typical growing season for maple species in Minnesota?'
'When should we expect peak wildflower blooms in different Colorado elevation zones?'
Data interpretation: Each record represents one species at one site for the specified time period. Start/end dates are averages across individuals. Sites represent uniform habitat areas ≤15 acres. Values of -9999 represent missing/null data.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| start_date | Yes | Start date in YYYY-MM-DD format. Must be used with end_date. | |
| end_date | Yes | End date in YYYY-MM-DD format. Must be used with start_date. | |
| bottom_left_x1 | No | X coordinate of the bottom left corner for bounding box filtering. | |
| bottom_left_y1 | No | Y coordinate of the bottom left corner for bounding box filtering. | |
| upper_right_x2 | No | X coordinate of the upper right corner for bounding box filtering. | |
| upper_right_y2 | No | Y coordinate of the upper right corner for bounding box filtering. | |
| species_id | No | Unique species identifier. | |
| station_id | No | Unique identifier associated with an observer’s location. | |
| species_type | No | Species type(s) the organism belongs to. Must match values from getAnimalTypes and getPlantTypes. | |
| network | No | Name of the network(s)/group(s) where the organism is observed. Must match values from getPartnerNetworks. | |
| state | No | State where the observation occurred. Uses two-character postal abbreviation. | |
| phenophase_category | No | Phenophase category. Must match values from getPhenophase. | |
| phenophase_id | No | Unique identifier of the phenophase. | |
| functional_type | No | Functional types of the species. Must match values from getSpeciesFunctionalTypes. | |
| climate_data | No | Flag to indicate whether all climate data fields should be returned. Accepts 0 or 1. Almost always beneficial to see climate data in relation to phenometric data. | |
| individual_ids | No | List of unique identifiers of the individuals for which the observations are made. | |
| additional_field | No | Additional fields to include in output. |