Issue 71 in ioostech: IOOS SOS test naming issues

[ioos...@googlecode.com]

Status: New
Owner: sh...@axiomalaska.com
Labels: Type-Defect Priority-Medium

New issue 71 by sh...@axiomalaska.com: IOOS SOS test naming issues
http://code.google.com/p/ioostech/issues/detail?id=71

Many of the GetObservation tests:

https://code.google.com/p/ioostech/wiki/ListofTestsIOOSSOS#3.3.2_IOOS-specific_Tests

are
named "IOOS-SOS.GetCapabilities-ResponseContainsValidOperationsMetadataProperty.x".
These tests are GetObservation tests (not GetCapabilities), and aren't
testing operations metadata properties. Can these names be fixed?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ioos...@googlecode.com]

Comment #1 on issue 71 by abir...@gmail.com: IOOS SOS test naming issues
http://code.google.com/p/ioostech/issues/detail?id=71

Yes, of course they can be fixed. The reason for them looking like that is
pretty simple: I wanted to speed up a delivery of that list of tests, and
individual test names seemed not very important at the moment. I will give
it a shot now...

[ioos...@googlecode.com]

Comment #2 on issue 71 by abir...@gmail.com: IOOS SOS test naming issues
http://code.google.com/p/ioostech/issues/detail?id=71

Fixed the names on GitHub at
https://github.com/abirger/Docs/blob/master/List%20of%20tests%20for%20IOOS%20SOS%201.0.md .

[ioos...@googlecode.com]

Updates:
Status: Fixed

Comment #4 on issue 71 by sh...@axiomalaska.com: IOOS SOS test naming issues
http://code.google.com/p/ioostech/issues/detail?id=71

(No comment was entered for this change.)

[ioos...@googlecode.com]

Comment #3 on issue 71 by sh...@axiomalaska.com: IOOS SOS test naming issues
http://code.google.com/p/ioostech/issues/detail?id=71

GitHub test list has moved to:

https://github.com/abirger/docs/blob/master/content/testing.md

At first glance, looks great. Thanks for revising. Closing this issue.

[Dan Ramage]

I am working on implementing a PyCSW server and was wondering if anyone
had any python tools that would make it less painful to go from the
THREDDS metadata to one of the formats PyCSW supports for importing. I saw
a thread in the PyCSW issues page about this, but I didn't see a
conclusion to it.


Dan

[Kyle Wilcox]

Dan - 

The ncISO portion of THREDDS can output ISO 19115-2 metadata files.  Have you tried to use these in pycsw?  If they work, you could use: https://github.com/kwilcox/thredds_crawler to download the ISO files you want to ingest into pycsw.  A direct connector in pycsw would also be a good idea...

--
--
You received this message because you are subscribed to the Google
Groups "ioostech_dev" group.
To post to this group, send email to iooste...@googlegroups.com
To unsubscribe from this group, send email to
ioostech_dev...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/ioostech_dev?hl=en

---
You received this message because you are subscribed to the Google Groups "ioostech_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ioostech_dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dan Ramage]

I saw there was the command line java piece, so I am trying that and it works. Let me back up, my definition of works is I see an entry in the database after I created the xml metadata file then pointed pycsw to ingest it. I am not sure if all the fields are populated in a useful manner yet as I am learning what the schema for pycsw is at the same time.

Dan

[Derrick Snowden - NOAA Federal]

Dan,

Ask John Maurer (jma...@hawai.edu) directly.  I don't think he's on this list but I know he's done exactly what you're asking.  I think Eric Bridger has also done it.  Alternatively you could post the same questions  to ioos...@googlegroups.com and they'd both see it.  Eric is on this list as well so maybe he'll reply.

Derrick

Derrick Snowden
System Architect and Acting Chief, Operations and Communications Division
US IOOS
1100 Wayne Ave, Suite 1225
Silver Spring, MD 20912
+1 301 427 2464 (o), +1 301 427 2073 (f)

Find us on Facebook

[Eric Bridger]

Dan,

Wasn't sure you were referring to Java ncISO in your original post.

NERACOOS runs this nightly against 2 of our TDS catalogs and produces a WAF.

http://www.neracoos.org/WAF/

The ISO files are at:

http://www.neracoos.org/WAF/UMaine/iso/

http://www.neracoos.org/WAF/BIO/iso/

AFAIK the ncISO crawler produces valid ISO files via the ncISO TDS plugin and the NGDC Geoportal ingests it successfully.

I posted a simple python 2.7 script we use to run this via cron.

https://github.com/neracoos-open/neracoos_catalog/tree/master/src/MetadataWAF

It has a rename option since we are running ncSOS which requires a ncml extension to overcoming a TDS aggregation cache issue, but that is optional.

The TDS catalog url's are:

http://www.neracoos.org/thredds/UMO_SOS_historical_realtime_agg.html

and

http://www.neracoos.org/thredds/catalog/WW3/catalog.html

Hope this helps.

Eric