New Task: For ATN data archived at NCEI, provide access to these data via ERDDAP

[MathewBiddle]

Who is requesting this?

@ioos/marine-life

What is being requested?

For ATN satellite trajectory and profile data archived at NCEI, provide access to these data via https://atn.ioos.us/erddap/index.html

What is the requested deadline and why?

No response

What is the current status quo (i.e., what happens if this does not get done)?

Data are not easily accessible through ERDDAP.

What indicates this is done (i.e., how do we know this is complete)?

• [ ] ERDDAP is updated to current version
• [ ] count of datasets accessible via ERDDAP
• [ ] Send a message through IOOS Eyes On The Ocean.

Provide a description or any other important information.

No response

[MathewBiddle]

This ERDDAP will also be indexed by the IOOS Data Catalog as a requirement from DMAC.

• https://data.ioos.us/about
• https://ioos.github.io/catalog/

[MathewBiddle]

@mmckinzie can you have this conversation at the next data meeting?

I've tested loading a template ATN satellite telemetry file in an erddap I manage, just to see how difficult it might be: https://erddap.ioos.us/erddap/tabledap/atn_trajectory_template.html

I can share the datasets.xml configuration with whomever needs it on the ATN side.

[mmckinzie]

We may also want to consider adding animal borne sensor data submitted to the GTS to the IOOS ERDDAP as well as data archived at NCEI. AniBOS data are already getting linked and available via the OMSC ERDDAP.

[MathewBiddle]

@mmckinzie Great thought!

Expanding, and potentially new issue: I wonder if NDBC could harvest ATN data for GTS from an ERDDAP (ATN ERDDAP to be specific), instead of the WAF approach. I know @mwengren has been working on a project migrating the RAs to have NDBC pull from each RA ERDDAP. But, those data types are relatively constrained, so it could be a more significant lift. That way ATN puts data on ATN ERDDAP, NDBC picks up for GTS and IOOS can use for metrics gathering. Plus data are available on ERDDAP! (albeit a subset - I don't think species information / details get added to BUFR messages)

[mmckinzie]

@MathewBiddle it's possible that NDBC could harvest the data from the IOOS ERRDAP but I'm not sure that is the best approach in our case as the DAC is generating the actual BUFR messages from the near r/t data we're harvesting directly from tag manufacturers and serving those to NDBC. NDBC is not creating the messages for us. The data that is being integrated into the OMSC ERRDAP is being harvested directly from the GTS.

And you are correct no species or other life history/morphometric data are included in the BUFR messages. They are flagged as animal borne platforms, i.e., WMO/WIGOS ids are all preference with a '99' and then within the messages themselves the surface station code field is hardcoded to '10' indicating a marine animal and the instrument type for water temp and/or salinity measurements is set to either '995' or '996' indicating instrument attached to a marine mammal or instrument attached to animal other than marine mammal.

[MathewBiddle]

Thank you for clarifying.

Could the NRT data be put on an ERDDAP and NDBC does the BUFR generation? Maybe that's a conversation to be had?

BTW, I was proposing the ATN ERDDAP https://atn.ioos.us/erddap/index.html, not the IOOS ERDDAP https://erddap.ioos.us/erddap/index.html

[lmshowalter3]

In progress, Jira ticket in our system. NCEI to review test files and then will move files to production folder.

[MathewBiddle]

We continue to get more requests for accessing ATN data. The access to data through the portal is lackluster and supporting this ERDDAP endpoint would meet a large user community.

Who is requesting this?

• NASA for a special project
• RWSC offshore wind
• GOOS BioEco Panel

I am bumping up the priority of this task.

[iwensu0313]

ERDDAP, Version 2.25 is now released and deployed. Does that complete the first of the 3 checkboxes in the ticket description? Moved status to TO DO.