Currently the loitering table in pipe3 (it is the same in pipe 2.5) includes the
ssvid
associated with each event, but doesn't have
vessel_id
.
Encounters... a related table only has
vessel_id
s for each vessel involved in the events and does not include the
ssvid
s.
It seems like it be helpful from a user perspective if these tables were consistent using using
vessel_id
or
ssvid
.
Loitering table:
world-fishing-827.pipe_ais_v3_alpha_published.loitering
Encounters table:
world-fishing-827.pipe_ais_v3_alpha_published.encounters