Hi,
I'm currently running a relatively recent trunk build (version 2.5, r5946) and was wondering if anyone has had any experience harvesting metadata from a THREDDS WCS?
From what I can tell I can only harvest a single dataset from thredds at a time (by pointing the harvester at 'http://servername/thredds/wcs/dataset/foo.nc’) and I was wondering if anyone knew of a way to nicely harvest metadata from *all* WCS datasets for a given Thredds instance?
Thanks
Josh Vote
On 7/5/10 1:27 AM, Josh.Vote@anonymised.com wrote:
Hi,
I'm currently running a relatively recent trunk build (version 2.5, r5946) and was wondering if anyone has had any experience harvesting metadata from a THREDDS WCS?
> From what I can tell I can only harvest a single dataset from thredds at a time (by pointing the harvester at 'http://servername/thredds/wcs/dataset/foo.nc’) and I was wondering if anyone knew of a way to nicely harvest metadata from *all* WCS datasets for a given Thredds instance?
This is a surprising approach. With the other OGC WS, one harvests the GetCapabilities URL and the layers or data sets are pulled in. If this is not configured in the harvester, it should be, as all WCS must support capabilities.
Doug.
Thanks
Josh Vote
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
--
Douglas D. Nebert
Senior Advisor for Geospatial Technology, System-of-Systems Architect
FGDC Secretariat T:703 648 4151 F:703 648-5755 C:703 459-5860
On 06/07/2010 11:13 PM, ddnebert@anonymised.com wrote:
This is a surprising approach. With the other OGC WS, one harvests the
GetCapabilities URL and the layers or data sets are pulled in. If this
is not configured in the harvester, it should be, as all WCS must
support capabilities.
That's more or less what I'm doing now and it 'works' in a limited fashion.
The problem is that I need to create a harvester entry for each and every dataset I wish to harvest in a given THREDDS instance. I'm really hoping I'm overlooking something obvious because what I'd like to see is a single THREDDS URL I can use with the Geonetwork harvester (ie GetCapabilities) that will allow me to harvest ALL datasets.
I'm probably going a little beyond the scope of this mailing list so I may go bug the THREDDS community with this instead 
Josh
-----Original Message-----
From: Douglas Nebert [mailto:ddnebert@anonymised.com]
Sent: Tuesday, 6 July 2010 10:43 PM
To: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] Harvesting THREDDS WCS
On 7/5/10 1:27 AM, Josh.Vote@anonymised.com wrote:
Hi,
I'm currently running a relatively recent trunk build (version 2.5, r5946) and was wondering if anyone has had any experience harvesting metadata from a THREDDS WCS?
> From what I can tell I can only harvest a single dataset from thredds at a time (by pointing the harvester at 'http://servername/thredds/wcs/dataset/foo.nc’) and I was wondering if anyone knew of a way to nicely harvest metadata from *all* WCS datasets for a given Thredds instance?
This is a surprising approach. With the other OGC WS, one harvests the
GetCapabilities URL and the layers or data sets are pulled in. If this
is not configured in the harvester, it should be, as all WCS must
support capabilities.
Doug.
Thanks
Josh Vote
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
--
Douglas D. Nebert
Senior Advisor for Geospatial Technology, System-of-Systems Architect
FGDC Secretariat T:703 648 4151 F:703 648-5755 C:703 459-5860
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Hi Josh,
A THREDDS catalog harvester was added to geonetwork in 2.5 by
Simon Pigot (csiro).
This harvester takes a THREDDS xml catalog url as a parameter and crawls
through the catalog creating iso19119/19139 metadata for each service
defined in the catalog and optionally iso19115/19139 metadata for each
dataset defined in the catalog. It sounds like something generally
along the lines of what you are looking for but may not meet your exact
needs re WCS services. As it is relatively new, it can probably benefit
from some constructive feedback from the community on its
usefulness and/or suggestions on areas for improvement.
I haven't used the harvester for harvesting WCS (or WMS) services here
myself yet but will probably be looking at it shortly as our need to
harvest this kind of metadata increases.
Regards,
--
Craig Jones
eMII Infrastructure Programmer
IMOS e-Marine Information Infrastructure Facility (eMII)
Ph: +61 3 6226 8567
On Tue, 2010-07-20 at 15:55 +0800, Josh.Vote@anonymised.com wrote:
On 06/07/2010 11:13 PM, ddnebert@anonymised.com wrote:
> This is a surprising approach. With the other OGC WS, one harvests the
> GetCapabilities URL and the layers or data sets are pulled in. If this
> is not configured in the harvester, it should be, as all WCS must
> support capabilities.That's more or less what I'm doing now and it 'works' in a limited fashion.
The problem is that I need to create a harvester entry for each and every dataset I wish to harvest in a given THREDDS instance. I'm really hoping I'm overlooking something obvious because what I'd like to see is a single THREDDS URL I can use with the Geonetwork harvester (ie GetCapabilities) that will allow me to harvest ALL datasets.
I'm probably going a little beyond the scope of this mailing list so I may go bug the THREDDS community with this instead
Josh
-----Original Message-----
From: Douglas Nebert [mailto:ddnebert@anonymised.com]
Sent: Tuesday, 6 July 2010 10:43 PM
To: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] Harvesting THREDDS WCSOn 7/5/10 1:27 AM, Josh.Vote@anonymised.com wrote:
> Hi,
>
> I'm currently running a relatively recent trunk build (version 2.5, r5946) and was wondering if anyone has had any experience harvesting metadata from a THREDDS WCS?
>
> > From what I can tell I can only harvest a single dataset from thredds at a time (by pointing the harvester at 'http://servername/thredds/wcs/dataset/foo.nc’) and I was wondering if anyone knew of a way to nicely harvest metadata from *all* WCS datasets for a given Thredds instance?
>
>
This is a surprising approach. With the other OGC WS, one harvests the
GetCapabilities URL and the layers or data sets are pulled in. If this
is not configured in the harvester, it should be, as all WCS must
support capabilities.Doug.
> Thanks
>
> Josh Vote
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
>
>