This PR attempts to reduce the number of extra gaps being generated by tagging messages during the thinning phase
with is_possible_gap_end. Only tagged messages that have this set to true can generate a gap event.
[!CAUTION]
This has not been tested. Do not merge without testing!
smart_thin_records.py: Convert VesselLocationRecords to VisitLocationRecords on input. These have the added field is_possible_gap_end, which is initially set to False. When emitting points due to a gap, set is_possible_gap_end to True for the gap end.
port_visits_pipeline.py: load messages as VisitLocationRecord rather the VesselLocationRecord to accommodate is_possible_gap_end field.
create_in_out_events.py: Only generate gap events if the end point has is_possible_gap_end set.
This PR attempts to reduce the number of extra gaps being generated by tagging messages during the thinning phase with
is_possible_gap_end. Only tagged messages that have this set to true can generate a gap event.Changes
message_schema.py: addis_possible_gap_endcolumn. Remove unuseddestinationcolumn.smart_thin_records.py: Convert VesselLocationRecords to VisitLocationRecords on input. These have the added fieldis_possible_gap_end, which is initially set to False. When emitting points due to a gap, setis_possible_gap_endto True for the gap end.port_visits_pipeline.py: load messages as VisitLocationRecord rather the VesselLocationRecord to accommodateis_possible_gap_endfield.create_in_out_events.py: Only generate gap events if the end point hasis_possible_gap_endset.