Skip to content
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

Command line ncISO code? #7

Open
ethanrd opened this issue Jan 28, 2015 · 29 comments
Open

Command line ncISO code? #7

ethanrd opened this issue Jan 28, 2015 · 29 comments

Comments

@ethanrd
Copy link
Member

ethanrd commented Jan 28, 2015

@shane-axiom - There is a connection but I'm not sure how extensive it is. Mainly, I believe, the connection is limited to the XSLT transformation files that are shared between the command-line version and this plugin for THREDDS Data Server (TDS). But I will defer to Dave (@geoneubie) as my understanding of the connection isn't particularly detailed.

@shane-axiom wrote (originally issue 4 on ethanrd/threddsIso):

This may not apply, but is there any connection between this repo and the
command line version of ncISO? The line between ncISO and threddsISO
seems to be a little hazy. TDS documentation and configuration usually
references the embedded ncISO plugin, but according to this NGDC page
and this repository name ncISO is actually a jar meant for command line
execution against a remote TDS instance, and threddsISO is the name of
the TDS embedded plugin.

In any case, the CLI ncISO version on NGDC's page is broken, and I haven't
had luck getting on their mailing list. Any traction/illumination here? A brief
README might make the relation of this repo to ncISIO apparent.

@rsignell-usgs
Copy link
Contributor

rsignell-usgs commented May 27, 2016

Kevin O'Brien (github handle?) has a bit of funding to upgrade the stand-alone nciso, and he and I spoke with @lesserwhirls at the CF-2.0 meeting about merging the command line capabilities into the same jar that is used in THREDDS.

I think this would be a great benefit, as Unidata could upgrade the netcdf-java logic and Kevin O'Brien could work on ensuring that we have command line capabilities that match those of the THREDDS nciso service.

@geoneubie , are you okay with this?

@lesserwhirls , please comment if I got this wrong...

@rsignell-usgs
Copy link
Contributor

Bringing in @lukecampbell here as he is working on ISO metadata harvesting issues as well.

@geoneubie
Copy link
Contributor

Kevin and Roland reached out prior to the submission, they have received a copy of CLI ncISO from 2011, glad someone can take this on!

@srstsavage
Copy link
Contributor

👍 Promising news. Thanks!

@rsignell-usgs
Copy link
Contributor

@kevin-obrien, when will this work commence?

@kevin-obrien
Copy link
Collaborator

Roland and I will sit down next week and try to get a scope on the problem, and where to fit it into the priorities and I will have a better answer then. Will update this thread.....

@rsignell-usgs
Copy link
Contributor

@kevin-obrien , any updates?

@rsignell-usgs
Copy link
Contributor

@lukecampbell, you can try pinging here

@rsignell-usgs
Copy link
Contributor

@kevin-obrien , any updates on the stand-alone ncISO code?

@kevin-obrien
Copy link
Collaborator

@rsignell-usgs - we still need to get the ACDD v1.3 mappings to ISO 19115 squared away. Was hoping this could happen at winter ESIP meeting...

@lesserwhirls
Copy link
Collaborator

Who will be at the ESIP summer meeting this year? Any interest in trying to have a hackathon to bring the ncIso command line and TDS plugin together? Even thought I won't be there, I'd be more than happy to participate remotely.

@kwilcox
Copy link

kwilcox commented Apr 5, 2017

I won't be there but can also participate remotely!

@geoneubie
Copy link
Contributor

geoneubie commented Apr 6, 2017 via email

@rsignell-usgs
Copy link
Contributor

Since we all know each other, couldn't we do this with a 2 hour web meeting, like, say next week? ;-)

@lesserwhirls
Copy link
Collaborator

Very true, although I would not want to do it before the Users Committee meeting (things are a bit crazy around here at this point). I've been wanting to get involved with ESIP, so I thought this might be a good way to kick start that, but I am not opposed to having an all-remote hackathon. I'd be more than happy to set something up at a liquids and foods establishment here in Boulder for the locals to gather in one spot for a remote hackathon, if there was interest 🍺

@kevin-obrien
Copy link
Collaborator

Perhaps @noaaroland can chime in. I believe that we are still waiting for a blessing of the proposed ISO mappings to ACDD v1.3 from the ESIP documentation gods that be...

@rsignell-usgs
Copy link
Contributor

@BobSimons
Copy link

BobSimons commented Apr 6, 2017 via email

@amilan17
Copy link

amilan17 commented Apr 6, 2017 via email

@BobSimons
Copy link

BobSimons commented Apr 6, 2017 via email

@kevin-obrien
Copy link
Collaborator

@noaaroland worked with Philip Jones and they put together a spreadsheet of proposed mappings from ACDD 1.3 to ISO. Message was sent Feb 9. I can forward it to you, Anna..

@BobSimons
Copy link

BobSimons commented Apr 6, 2017 via email

@amilan17
Copy link

amilan17 commented Apr 6, 2017 via email

@noaaroland
Copy link

The ACDD to ISO mapping as proposed was done by Phillip Jones at NCEI as part of his work on NOAA OneStop. I just highlighted his spread sheet with pretty colors to indicate the attributes that were added when moving from 1.2 to 1.3.

NOAA in its wisdom will not allow me to share the Google doc as a link to people outside of NOAA, but the link is here.

I downloaded and attached the spreadsheet as well, but would prefer to keep edits in the Google doc.
Proposed Mapping of ACDD 1.3 to ISO.xlsx

@amilan17
Copy link

amilan17 commented Apr 12, 2017 via email

@rsignell-usgs
Copy link
Contributor

@noaaroland , if you move that document to the google drive associated with your personal google account, you can share with anyone (NOAA, USGS, anyone!). I do that all the time because USGS has the same stupid policy with the USGS google accounts.

@kevin-obrien
Copy link
Collaborator

Hi Anna -

Thanks for looking at and annotating the spreadsheet that Roland provided.
For the things that need consensus and discussion - where and how should that happen? I assume this is an ESIP documentation cluster activity?

thanks..

@dpsnowden
Copy link

Just wondering on the status of this thread. Have the mappings in the spreadsheet been "approved" by whoever needs to do this? Have they been implemented in ERDDAP (@BobSimons) or ncISO (@kevin-obrien)?

I'm also still a little unclear on the relationship between what used be the standalone nciso.jar application and the threddsiso.jar app that is bundled with THREDDS.

We are struggling with providing good attribution back to (operators/publishers/funders/data analysts) etc on our national aggregation products like the IOOS Catalog and Environmental Data Server and having a reliable source of information on the crosswalks would really help us out.

@kevin-obrien
Copy link
Collaborator

kevin-obrien commented Jul 21, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests