[GeoNetwork-users] WFS auto-harvested layers registered as WMS OGC:WMS-1.0.0-http-get-feature

Dear List,

The following WFS was registered (auto-harvesting) with GN 2.4.1: http://gsv-ws.dpi.vic.gov.au/EarthResourceML/1.1/wfs
Setup details:
Debian Lenny
Java 1.6
Tomcat 6
MySQL

The gmd:distributionInfo is as expected

<gmd:transferOptions>
   <gmd:MD_DigitalTransferOptions>
     <gmd:onLine>
       <gmd:CI_OnlineResource>
         <gmd:linkage>
           <gmd:URL>http://gsv-ws.dpi.vic.gov.au/EarthResourceML/1.1/wfs?&lt;/gmd:URL&gt;
         </gmd:linkage>
         <gmd:protocol>
           <gco:CharacterString>OGC:WFS-1.1.0-http-get-feature</gco:CharacterString>
         </gmd:protocol>
         <gmd:name>
           <gco:CharacterString>er:Mine</gco:CharacterString>
         </gmd:name>
         <gmd:description>
           <gco:CharacterString>EarthResourceML Mines</gco:CharacterString>
         </gmd:description>
       </gmd:CI_OnlineResource>
     </gmd:onLine>
   </gmd:MD_DigitalTransferOptions>
</gmd:transferOptions>

I created another GN 2.4.2 instance on different machine.
Setup details:
Debian Lenny
Java 1.6
Tomcat 5.5
MySQL

The above service was registered on the machine in exactly the same way:
auto-harvesting
OGC Web services (ie. WMS, WFS, WCS, WPS)
OGC Web Feature Service (WFS) Version 1.1.0 - preferred
Selected 'Create metadata for layer elements using GetCapabilities information.
Groups: All
Category for service: Datasets
Category for datasets: Datasets

However, the gmd:distributionInfo looks different now:

The output of GetRecords query:
<gmd:transferOptions>
   <gmd:MD_DigitalTransferOptions>
     <gmd:onLine>
       <gmd:CI_OnlineResource>
         <gmd:linkage>
           <gmd:URL />
         </gmd:linkage>
         <gmd:protocol>
           <gco:CharacterString>OGC:WMS-1.0.0-http-get-feature</gco:CharacterString>
         </gmd:protocol>
         <gmd:name>
           <gco:CharacterString>er:Mine</gco:CharacterString>
         </gmd:name>
         <gmd:description>
           <gco:CharacterString>EarthResourceML Mines</gco:CharacterString>
         </gmd:description>
       </gmd:CI_OnlineResource>
     </gmd:onLine>
   </gmd:MD_DigitalTransferOptions>
</gmd:transferOptions>

Please note:
* the protocol is: OGC:WMS-1.0.0-http-get-feature
* The url is missing: <gmd:URL />

My initial though was that there is something wrong with GN 2.4.2, but 2.4.1 gives me the same result.

There is another service that exhibits similar problem: http://auscope-services.arrc.csiro.au/geodesy/wfs

This service provides three layers:
http://auscope-services.arrc.csiro.au/geodesy/wfs?service=WFS&version=1.1.0&request=GetCapabilities
ngcp:GnssStation
geodesy:stations
geodesy:station_observations

When the service was registered with the new instance of GN 2.4.2 the ngcp:GnssStation layer was missing.

I had a look at the output of GetCapabilities query; The only difference b/w those three services was projection:
urn:x-ogc:def:crs:EPSG:4283 in case of ngcp:GnssStation
urn:x-ogc:def:crs:EPSG:4326 for the other two layers.

As the service is under our control, I changed the projection in GeoServer for the ngcp:GnssStation layer to 4326 and the new GN was able to register the layer. When I changed the projection back to 4283 and run harvesting, it dissapeard.

I am wondering what is wrong with the new installation?
Can someone please shed a light on this?

Thanks
Jarek

Hello Jarek,

2010/3/29 <Jarek.Sanders@anonymised.com>:

Dear List,

The following WFS was registered (auto-harvesting) with GN 2.4.1: http://gsv-ws.dpi.vic.gov.au/EarthResourceML/1.1/wfs
Setup details:
Debian Lenny
Java 1.6
Tomcat 6
MySQL

The gmd:distributionInfo is as expected

<gmd:transferOptions>
<gmd:MD_DigitalTransferOptions>
<gmd:onLine>
<gmd:CI_OnlineResource>
<gmd:linkage>
<gmd:URL>http://gsv-ws.dpi.vic.gov.au/EarthResourceML/1.1/wfs?&lt;/gmd:URL&gt;
</gmd:linkage>
<gmd:protocol>
<gco:CharacterString>OGC:WFS-1.1.0-http-get-feature</gco:CharacterString>
</gmd:protocol>
<gmd:name>
<gco:CharacterString>er:Mine</gco:CharacterString>
</gmd:name>
<gmd:description>
<gco:CharacterString>EarthResourceML Mines</gco:CharacterString>
</gmd:description>
</gmd:CI_OnlineResource>
</gmd:onLine>
</gmd:MD_DigitalTransferOptions>
</gmd:transferOptions>

I created another GN 2.4.2 instance on different machine.
Setup details:
Debian Lenny
Java 1.6
Tomcat 5.5
MySQL

The above service was registered on the machine in exactly the same way:
auto-harvesting
OGC Web services (ie. WMS, WFS, WCS, WPS)
OGC Web Feature Service (WFS) Version 1.1.0 - preferred
Selected 'Create metadata for layer elements using GetCapabilities information.
Groups: All
Category for service: Datasets
Category for datasets: Datasets

However, the gmd:distributionInfo looks different now:

The output of GetRecords query:
<gmd:transferOptions>
<gmd:MD_DigitalTransferOptions>
<gmd:onLine>
<gmd:CI_OnlineResource>
<gmd:linkage>
<gmd:URL />
</gmd:linkage>
<gmd:protocol>
<gco:CharacterString>OGC:WMS-1.0.0-http-get-feature</gco:CharacterString>
</gmd:protocol>
<gmd:name>
<gco:CharacterString>er:Mine</gco:CharacterString>
</gmd:name>
<gmd:description>
<gco:CharacterString>EarthResourceML Mines</gco:CharacterString>
</gmd:description>
</gmd:CI_OnlineResource>
</gmd:onLine>
</gmd:MD_DigitalTransferOptions>
</gmd:transferOptions>

Please note:
* the protocol is: OGC:WMS-1.0.0-http-get-feature

Fixed in trunk. FYI, we're not using the protocol value for WFS
getFeature operation in GeoNetwork.

* The url is missing: <gmd:URL />

Using WFS 1.1.0 is working ok for me.

There is another service that exhibits similar problem: http://auscope-services.arrc.csiro.au/geodesy/wfs

This service provides three layers:
http://auscope-services.arrc.csiro.au/geodesy/wfs?service=WFS&version=1.1.0&request=GetCapabilities
ngcp:GnssStation
geodesy:stations
geodesy:station_observations

When the service was registered with the new instance of GN 2.4.2 the ngcp:GnssStation layer was missing.

I had a look at the output of GetCapabilities query; The only difference b/w those three services was projection:
urn:x-ogc:def:crs:EPSG:4283 in case of ngcp:GnssStation
urn:x-ogc:def:crs:EPSG:4326 for the other two layers.

I can't reproduce the issue, I get the 3 layers. I think the main
issue with that WFS is that layers have no title, abstract nor
keywords, so harvesting that service will produce not so useful
metadata records.

Cheers.

Francois

As the service is under our control, I changed the projection in GeoServer for the ngcp:GnssStation layer to 4326 and the new GN was able to register the layer. When I changed the projection back to 4283 and run harvesting, it dissapeard.

I am wondering what is wrong with the new installation?
Can someone please shed a light on this?

Thanks
Jarek
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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