search

ices-eg / wg_WGACOUSTICGOV

Working Group on Acoustic Trawl Data Portal Governance
http://ices.dk/community/groups/Pages/WGacousticgov.aspx
5 stars 1 forks source link

ICES acoustic data format - Echoview export question? #56

Open HjalteParner opened 8 months ago

HjalteParner commented 8 months ago

ICES DC got the following question from Echoview on behalf of a user request.

"My name is Chelsey, I’m a member of the Echoview science team based in the UK.

I recently had a conversation with some of our customers about the CSV file format for the ICES acoustic database. Currently, when users export data to this format ‘by region classes by cells’ in Echoview, the resulting CSV file will contain one row per region class (e.g., SaCategory) per cell. This is the case even when the cell is empty. The customers would prefer that the CSV file contains only one row per empty cell.

This is a change that we can implement. However, I’m not sure whether this request is specific to those customers’ preferences, or whether it is generally preferred that files uploaded to the ICES database contain only one row per empty cell. Could you please provide some insight on this matter?"

Can you please help with this question from your and possible also from StoX/EchoR point of view?

jmjech commented 5 months ago

Will this apply to only an export to ICES database format, or to all region by cell exports?

SvenGastauer commented 5 months ago

This is more a strategic quesiton for Echoview than a question for WGACOUSTICGOV. The customer base of Echoview is much larger than the ICES DB/StoX/EchoR user group. We can imagine a number of scenarios where either or export would be useful. The only suggestion we can provide is to implement this as an export option to satify an as large as possible user group and number of user cases. The desired output format will depend on the user's further analysis and routines.

BrionyH commented 5 months ago

Hi @jmjech - Chelsey's question is specific to the ICES database export only (it will not impact/change any other exports).

@SvenGastauer, adding an option into the software will work well for us, as long as doing so doesn't result in downstream issues for your group. As the ICES export is so heavily designed for this group, our top priority is to ensure that any changes to this export don't result in unintentional problems here. It sounds like that won't be the case, which is great!

jmjech commented 5 months ago

@BrionyH - That's what I thought, but thanks for clarifying.

elorsepp commented 2 months ago

@HjalteParner will contact Briony to clarify the status.