Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Major change - bug fix
get_vessel_info()
. For some advancedqueries using
where
, the function was returning only a subset of the vessels.This issue is now solved and the number of results should be equal to the number
of vessels returned by Vessel Viewer on our map. (solves Implement pagination in
get_vessel_info()
#176)Breaking changes
Some fields in the response were renamed across outputs (addressing issue improve nomenclature consistency #146):
get_vessel_info()
: in$registryInfo
we renamedid
toregistryId
get_event()
: we renamedid
toeventId
andtype
toeventType
New features
get_vessel_info()
: We added anindex
column to indicate whichvesselIds
are grouped together and belong to the same vessel. This should help associate
information from the returned datasets and guide the user when requesting events
for a single vessel or a group of vessels.
get_event()
: We unnested the column-list"vessel"
to give more visibility tothe vessels each event corresponds to.
Minor changes
get_event()
section in the README to improve the workflow andsend groups of
vesselIds
corresponding to one or multiple vessels.