Open AndreaSanchezTapia opened 3 weeks ago
The tinyest change to avoid a long explanation is renaming selfReportedInfo$id
to selfReportedInfo$vesselId
in the results. No change to parameters or API calls, only readme and vignette results processing.
Hi. Hope you don't mind me jumping in, but I had a thought about argument naming! I notice in the latest version of gfwr
, get_raster()
has had some changes, one of which is that the user specified region
should be an sf
object (great enhancement, thanks!). Given this change, wouldn't it make sense to use region_source = "user_polygon"
, or something similar, rather than "user_json"
?
id
inget_vessel_info()
andvessels
in other functionsid
orvesselId
in the API results (selRepoortedInfo$id
,combinedSourcesInfo$VesselID
but there are other fields namedid
in the returning datasets that are not vessel IDs likeregistryInfo$id
Possible discussion with the API team as well to avoid solving downstream.