Summarise Prepared Tracks into Per-Trip Cell-Day Effort

Reduces prepared fishing points to the table aggregate_pds_effort() keeps as its source of truth: one row per trip, cell, year, gear, country and calendar day.

Usage

build_trip_effort(df)

Arguments

df

Prepared fishing points, as returned by prepare_tracks_for_effort(), carrying gear and country.

Value

A tibble with columns trip, h3_index, year, gear, country, date, cell_hours and cell_pings.

Details

This is the smallest summary the H3 grid can still be derived from in full. Keeping trip means unique_trips can be counted rather than added up, and keeping date means active days can be counted rather than unioned from a list-column; keeping both means a trip's contribution can be removed when PDS revises it, which a grid of running totals cannot support. It is about one row per trip and cell visited on a day – a few hundred thousand rows against five million pings – so a rebuild reads it in seconds instead of re-downloading every predicted track.

See also

derive_effort_grid(), aggregate_pds_effort()