magnitude-phenometrics
Quantify the intensity and abundance of phenological activity across time and space to analyze synchrony, peak timing, and climate change impacts on species interactions.
Instructions
About the tool: Summarizes the intensity and abundance of phenological activity across multiple individuals, sites, or time periods using aggregated status and intensity data. Shows 'how much' phenological activity is occurring (not just when), providing insights into the magnitude, synchrony, and temporal patterns of biological processes.
When to use: Understanding broad ecological patterns, studying synchrony between interacting species, analyzing peak activity timing, or investigating how environmental changes affect the intensity of biological processes across populations.
Key applications:
Species synchrony analysis: Quantifying how synchronized phenological timing is between interacting species (pollinators and plants, herbivores and host plants, predators and prey)
Peak activity timing: Identifying when maximum biological activity occurs across populations
Climate change impacts: Studying how warming affects the magnitude and timing of phenological events
Biodiversity patterns: Understanding temporal overlap in species activity within ecosystems
Population-level responses: Analyzing how abundant or widespread phenological activity is across landscapes
Conservation planning: Identifying critical timing windows for species management
Scientific context: Based on current research showing that phenological synchrony between species is shifting due to climate change, with implications for ecosystem functioning and species interactions. This tool helps quantify these critical ecological relationships.
Requires: Date range and frequency parameters (daily, weekly, etc.) are essential. Recommended to specify species and phenophases of interest to avoid overwhelming results. Research applications:
'Are migrating birds arriving when their insect food sources are most abundant?'
'How synchronous is flowering across plant species in prairie communities?'
'Has climate change affected the temporal overlap between butterfly emergence and host plant activity?'
Data interpretation: Results show time-series data of phenological abundance/intensity aggregated by specified frequency. Values represent proportion of 'yes' records, animal abundance measures, or intensity metrics across the selected populations.
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. | |
| frequency | Yes | Number of days by which to delineate the period of time. Should be less or equal to number of days between start_date and end_date. | |
| additional_field | No | Additional fields to include in output. |