[GeoNetwork-devel] Geonetwork / CSW 2.0

Hi jeroen,

Thank for your additional information (I'm little bit long to understand...).

During the GeoEvenements in France, we're a discussion with a other team working in the implementation of CSW - ISO 19115 API (MDWeb with a re-factory with GeoTools). We would like to complete the current implementation and test with other tools the interoperability. The main goal is to success in exchanging MD between organizations...

I know the question could be a bit hard but could you briefly indicate the "missing" elements to finalize the implementation CSW 2.0 ISO 19115 ? I hope that we could do it in few months...

Cheers,

Pierre

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : vendredi 30 mars 2007 15:51
À : Lagarde Pierre
Cc : acarboni@anonymised.com; geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] Geonetwork / CSW 2.0

Hi Pierre,
I see a big misunderstanding here :slight_smile:
The CSW implementation is server side only at this point. No harvesting through CSW has been implemented yet. Harvesting setup through the management interface can only be done between GeoNetwork nodes for that reason. (The Web Accessible folder harvesting still needs some development.) To use the CSW functionality of GeoNetwork one can use a CSW client.
A test client is provided with the installer.
Harvesting through CSW is something that is still pending / open for someone to implement it.
Hope that helps resolve the issue.
Ciao,
Jeroen

On Mar 30, 2007, at 2:06 PM, Lagarde Pierre wrote:

Hi andrea,

Thank for your answers.

But, I don't really understand how to use the interface of harvest
management. The server to query has a adress as http://site.brgm.fr/
ionicwrs/wrs/WRS (KVP binding).

What do you indicate in host : http://site.brgm.fr/ionicwrs/wrs/ WRS ?
Site.brgm.fr ? ...

Port --> 80

Servlet --> ??? WRS ?

Thank you for your help...

Pierre

-----Message d'origine-----
De : geonetwork-devel-bounces@lists.sourceforge.net
[mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
Andrea Carboni Envoyé : mardi 27 mars 2007 13:51 À :
geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] Geonetwork / CSW 2.0

Hi Pierre,

GN has passed the CITE tests against the base CSW/2.0.1 spec.
This means that it can be queried to obtain metadata in the dublin
core format.

The ISO 19115/19119 profile is implemented but it is based on an old
draft which seems pretty different from the latest one.
I don't expect interoperability using the ISO profile.

The implemented operations are the mandatory ones:
   - getCapabilities
   - describeRecord
   - getRecords
   - getRecordByID

and you can use GET/POST/SOAP bindings.

Metadata affected by CSW queries are those in dc and iso19115/139
format. There are some stylesheets that convert these metadata into
the proper dc output format.

Cheers,
Andrea

Hi all,

I downloaded the last beta version of GN and I would like to try to
use the CSW 2.0 implementation with a connection betwwen GN and the
commercial product IONIC Catalog (to test ! ).

I studied the doc but I don't see how GN implements the CSW 2.0
standards. Some questions...

The CSW 2.0 describes these operations :
  - getCapabilities
  - describeRecord
  - getDomain
  - getRecords
  - getRecordByID
  - Transaction
  - Harvest

Does GN implement all ? Which binding is available (KVP, SOAP,....)

If I remember the last workshop, you decide to use the ISO
19115/19119
API profile. Do I mean that you transform each metadata file in GN in
a valide XML file according profile ? Do you integrate the 19119
schema ?

After, I will be able to start a "testbed" !

Pierre LAGARDE

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork
**********************************************************************
************************
Le contenu de ce mél et de ses pièces jointes est destiné à l'usage
exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
réception de ce mél par erreur, le signaler à son expéditeur et ne
pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient
néanmoins de vérifier l'absence de contamination à sa réception.
The contents of this email and any attachments are confidential.
They are intended for
the named recipient(s) only. If you have received this email in error
please notify the system manager or the sender immediately and do not
disclose the contents to anyone or make copies. eSafe scanned this
email for viruses, vandals and malicious content.
**********************************************************************
************************

----------------------------------------------------------------------
---
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share
your opinions on IT & business topics through brief surveys-and earn
cash http://www.techsay.com/default.php?
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/
projects/geonetwork

**********************************************************************************************
Le contenu de ce mél et de ses pièces jointes est destiné à l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de ce
mél par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de
vérifier l'absence de contamination à sa réception.
The contents of this email and any attachments are confidential. They are intended for
the named recipient(s) only. If you have received this email in error please notify the
system manager or the sender immediately and do not disclose the contents to
anyone or make copies. eSafe scanned this email for viruses, vandals and malicious
content.
**********************************************************************************************

Hi Pierre,

here is the current CS/W status in geonetwork:

=== Current implementation=======================

The current CS/W implementation is based on the following main specifications:

- Catalogue services specification 2.0 with corregendum 1 (OGC 04-021r3)
  dated 2005-05-20.

- Catalogue services specification 2.0.1 ISO metadata application profile
(OGC 04-038r4) dated 2006-03-23.

Implemented operations are GetCapabilities, DescribeRecord, GetRecords and
GetRecordById which accept requests in HTTP/GET, HTTP/POST, XML on HTTP/POST
and SOAP format. The GetRecords operation can accept queries in both CQL and
filter expressions language.

The CQL parser accepts And and Or predicates. The following relational operators are
supported: EqualTo, NotEqualTo, LessThan, GreaterThan, LessThanEqualTo,
GreaterThanEqualTo.

The filter expressions engine implements the following comparison operators: EqualTo,
NotEqualTo, Like, LessThan, GreaterThan, LessThanEqualTo, GreaterThanEqualTo,
Between. All logical operators are implemented (And, Or, Not) while the only spatial
operator implemented is the Bounding Box which accepts an Envelope geometry
operand (the only one implemented).

===Limitations ===============================

- Missing operations: GetDomain, Transaction, Harvest.

- The distributed search is not implemented.

- Missing spatial operators: Equals, Overlaps, Disjoint, Intersects, Touches, Crosses,
  Within, Contains, Beyond, DWithin. Up to now, only spatial queries using a bounding
  box are allowed.

- Missing geometry operands: as a consequence of the previous point, all geometry
  operands are missing except for Envelope.

- The CQL implementation uses a naive library and can support only a small subset
  of CQL queries. It does not parse the Not operator and does not handle the
  bounding box. Furthermore, terms containing spaces, like 'basic africa', are not
  parsed correctly.

- It is not possible to query the extended ISO properties and ISO 19119 services.

- The implementation of the ISO profile is based on a rather old draft. The latest draft
  is quite different.

- The search engine does not implement neither arithmetic operators nor accepts
  functions in the query. The NullCheck comparison operator is not implemented.
  The comparison is not typed (it is string based) and this can cause problems with
  some datatypes like dates.

- No support to multiple type names. A type name is a kind of queryable object.
  The base specification defines only one type name, namely csw:Record, and this
  means that this object is the only queryable one. As a consequence, no joins are
  allowed on multiple type names and variables substitution has not been implemented.

- As a consequence of the previous point, no XPath handling of queryable fields is
  implemented. This is also due to the limited capabilities of the current search engine.

Cheers,
Andrea

Hi jeroen,

Thank for your additional information (I'm little bit long to understand...).

During the GeoEvenements in France, we're a discussion with a other team working in the implementation of CSW - ISO 19115 API (MDWeb with a re-factory with GeoTools). We would like to complete the current implementation and test with other tools the interoperability. The main goal is to success in exchanging MD between organizations...

I know the question could be a bit hard but could you briefly indicate the "missing" elements to finalize the implementation CSW 2.0 ISO 19115 ? I hope that we could do it in few months...

Cheers,

Pierre

-----Message d'origine-----
De : Jeroen Ticheler [mailto:Jeroen.Ticheler@anonymised.com]
Envoyé : vendredi 30 mars 2007 15:51
À : Lagarde Pierre
Cc : acarboni@anonymised.com; geonetwork-devel@lists.sourceforge.net
Objet : Re: [GeoNetwork-devel] Geonetwork / CSW 2.0

Hi Pierre,
I see a big misunderstanding here :slight_smile:
The CSW implementation is server side only at this point. No harvesting through CSW has been implemented yet. Harvesting setup through the management interface can only be done between GeoNetwork nodes for that reason. (The Web Accessible folder harvesting still needs some development.) To use the CSW functionality of GeoNetwork one can use a CSW client.
A test client is provided with the installer.
Harvesting through CSW is something that is still pending / open for someone to implement it.
Hope that helps resolve the issue.
Ciao,
Jeroen

On Mar 30, 2007, at 2:06 PM, Lagarde Pierre wrote:

> Hi andrea,
>
> Thank for your answers.
>
> But, I don't really understand how to use the interface of harvest
> management. The server to query has a adress as http://site.brgm.fr/
> ionicwrs/wrs/WRS (KVP binding).
>
>
> What do you indicate in host : http://site.brgm.fr/ionicwrs/wrs/ WRS ?
> Site.brgm.fr ? ...
>
> Port --> 80
>
> Servlet --> ??? WRS ?
>
>
> Thank you for your help...
>
> Pierre
>
>
>
> -----Message d'origine-----
> De : geonetwork-devel-bounces@lists.sourceforge.net
> [mailto:geonetwork-devel-bounces@lists.sourceforge.net] De la part de
> Andrea Carboni Envoyé : mardi 27 mars 2007 13:51 À :
> geonetwork-devel@lists.sourceforge.net
> Objet : Re: [GeoNetwork-devel] Geonetwork / CSW 2.0
>
> Hi Pierre,
>
> GN has passed the CITE tests against the base CSW/2.0.1 spec.
> This means that it can be queried to obtain metadata in the dublin
> core format.
>
> The ISO 19115/19119 profile is implemented but it is based on an old
> draft which seems pretty different from the latest one.
> I don't expect interoperability using the ISO profile.
>
> The implemented operations are the mandatory ones:
> - getCapabilities
> - describeRecord
> - getRecords
> - getRecordByID
>
> and you can use GET/POST/SOAP bindings.
>
> Metadata affected by CSW queries are those in dc and iso19115/139
> format. There are some stylesheets that convert these metadata into
> the proper dc output format.
>
> Cheers,
> Andrea
>
>> Hi all,
>>
>> I downloaded the last beta version of GN and I would like to try to
>> use the CSW 2.0 implementation with a connection betwwen GN and the
>> commercial product IONIC Catalog (to test ! ).
>>
>> I studied the doc but I don't see how GN implements the CSW 2.0
>> standards. Some questions...
>>
>> The CSW 2.0 describes these operations :
>> - getCapabilities
>> - describeRecord
>> - getDomain
>> - getRecords
>> - getRecordByID
>> - Transaction
>> - Harvest
>>
>>
>> Does GN implement all ? Which binding is available (KVP, SOAP,....)
>>
>> If I remember the last workshop, you decide to use the ISO
>> 19115/19119
>> API profile. Do I mean that you transform each metadata file in GN in
>> a valide XML file according profile ? Do you integrate the 19119
>> schema ?
>>
>> After, I will be able to start a "testbed" !
>>
>> Pierre LAGARDE
>
> ----------------------------------------------------------------------
> ---
> Take Surveys. Earn Cash. Influence the Future of IT Join
> SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys-and earn
> cash http://www.techsay.com/default.php?
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> GeoNetwork-devel mailing list
> GeoNetwork-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
> GeoNetwork OpenSource is maintained at http://sourceforge.net/
> projects/geonetwork
> **********************************************************************
> ************************
> Le contenu de ce mél et de ses pièces jointes est destiné à l'usage
> exclusif du
> (des) destinataire(s) expressément désigné(s) comme tel(s). En cas de
> réception de ce mél par erreur, le signaler à son expéditeur et ne
> pas en divulguer le contenu.
> L'absence de virus a été vérifié à l'émission du message. Il convient
> néanmoins de vérifier l'absence de contamination à sa réception.
> The contents of this email and any attachments are confidential.
> They are intended for
> the named recipient(s) only. If you have received this email in error
> please notify the system manager or the sender immediately and do not
> disclose the contents to anyone or make copies. eSafe scanned this
> email for viruses, vandals and malicious content.
> **********************************************************************
> ************************
>
>
> ----------------------------------------------------------------------
> ---
> Take Surveys. Earn Cash. Influence the Future of IT Join
> SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys-and earn
> cash http://www.techsay.com/default.php?
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> GeoNetwork-devel mailing list
> GeoNetwork-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
> GeoNetwork OpenSource is maintained at http://sourceforge.net/
> projects/geonetwork
**********************************************************************************************
Le contenu de ce mél et de ses pièces jointes est destiné à l'usage exclusif du
(des) destinataire(s) expressément désigné(s) comme tel(s). En cas de réception de ce
mél par erreur, le signaler à son expéditeur et ne pas en divulguer le contenu.
L'absence de virus a été vérifié à l'émission du message. Il convient néanmoins de
vérifier l'absence de contamination à sa réception.
The contents of this email and any attachments are confidential. They are intended for
the named recipient(s) only. If you have received this email in error please notify the
system manager or the sender immediately and do not disclose the contents to
anyone or make copies. eSafe scanned this email for viruses, vandals and malicious
content.
**********************************************************************************************