When using VirtualShip with locally stored data (i.e. virtualship run --from-data) the requirements for the .nc files are strict and inflexible. It is probably easier, more maintainable and more widely applicable to instead require that any data generally is SGRID compliant. So that any data that works with Parcels v4 also works with VirtualShip v1.
Simultaneously, it would be good to add support for ingesting local files which are not split across the time dimension. Currently, each timestep must be a separate .nc file which is probably annoying to some users and probably not necessary.
EDIT: or perhaps, rather, ensure the data is metadata rich enough to be ingested by a Parcels convert function (e.g. copernicusmarine_to_sgrid) under the VirtualShip hood. Full SGRID compliance might be too much to ask.
When using VirtualShip with locally stored data (i.e.
virtualship run --from-data) the requirements for the .nc files are strict and inflexible. It is probably easier, more maintainable and more widely applicable to instead require that any data generally is SGRID compliant. So that any data that works with Parcels v4 also works with VirtualShip v1.Simultaneously, it would be good to add support for ingesting local files which are not split across the time dimension. Currently, each timestep must be a separate .nc file which is probably annoying to some users and probably not necessary.
EDIT: or perhaps, rather, ensure the data is metadata rich enough to be ingested by a Parcels convert function (e.g.
copernicusmarine_to_sgrid) under the VirtualShip hood. Full SGRID compliance might be too much to ask.