pressurepaths.csv
A GeoPressureR pressurepath contains ERA5 variables along the bird trajectory, with one row per pressure measurement of the tag (so at the tag’s sampling interval), using the exact bird location (including flight segments). ERA5 values are taken at the nearest hour. Read more about pressurepaths in the GeoPressureManual
See pressurepaths.type for the supported trajectory types and how they are created.
pressurepath should be used in combination with staps and paths. For stationary rows, join to staps on (tag_id, stap_id). When joining to paths, also match type and j to keep trajectories separate. Decimal stap_id values during flight do not match a stationary-period row in either table.
Only tag_id is defined as a strict foreign key here. stap_id can be decimal during migration segments, so it cannot be enforced as a strict foreign key to staps in all rows.
The definition below does not list ERA5 variables, which can (and should!) be added to the table as additional columns (e.g., 'altitude' or 'surface_pressure'). Read more about these variables in the documentation of pressurepath_create().
Pressurepaths
Source:
pressurepaths-table-schema.json
| Name | Definition | Type |
|---|---|---|
tag_id*
|
Unique identifier of the tag. Foreign key to Example: |
string |
datetime*
|
Date and time of the pressure measurement. Formatted as an ISO 8601 string with timezone designator Example:
|
datetime |
stap_id*
|
Identifier of the stationary-period index for the trajectory. Integer values correspond to Example: |
number |
type*
|
Type of trajectory. Categories
Example: |
string |
lat*
|
Latitude of the trajectory position at this timestamp. Constraints
Example:
|
number |
lon*
|
Longitude of the trajectory position at this timestamp. Constraints
Example:
|
number |
j*
|
Trajectory identifier within each combination of
Example: |
integer |
Table rules
-
Primary key:
tag_id,type,j,datetime— together these identify a row. -
Foreign key:
tag_id→tags.tag_id -
Missing values: an empty cell,
NA. - Columns: optional columns listed above may be omitted. Additional columns are allowed.
-
Required columns: those marked
*must be present and must hold a value in every row.