-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create strategy to integrate metadata (BIF-style) into the data product #22
Comments
I think that the basic info, like coordinates, site code, ecosystem, UTC etc. should have high priority and be integrated as soon as possible... |
netCDF?
…On Mon, 22 Aug 2022 at 17:57, Dario Papale ***@***.***> wrote:
I think that the basic info, like coordinates, site code, ecosystem, UTC
etc. should have high priority and be integrated as soon as possible...
—
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTSJCMLDY5M3AXSUKUFXYDV2MXHRANCNFSM5PYDBSBA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Peter Isaac
Ph: +61 3 59685998
Mob: 0429053970
Skype: pisaac.ozflux
Email: ***@***.***
"Vita brevis, ars longa, occasio praeceps, experimentum periculosum,
iudicium difficile" - Hippocrates 400BC
"What's the go o'that?" - James Clerk Maxwell c1835
|
Also, but not only. netCDF are a different product format, we worked on this a lot with Gab and soon will be operational. But we can not (do not want) to remove what is currently everywhere in US and Europe (and FLUXNET2015)... waiting for OZFlux
|
Define how to integrate metadata into ONEFlux data product zip package files for each site (similar to BIF-style file made available for all sites in previous releases).
The text was updated successfully, but these errors were encountered: