[GeoNetwork-devel] How are Regions used in LuceneSearcher

GeoNetwork GeoNetwork Developer
1

Hi,

In the lucene searcher, all regions are added to the request data but I do not see where the regions are used in creating the query.

Is this a remanent of some older functionality or are they still used in some cases?

I need to know because of the work i am doing for the http://trac.osgeo.org/geonetwork/wiki/ExtendedRegions proposal.

Jesse

2

Not sure about the answer to your question Jesse at the moment - but had a look at your proposal - which is interesting!

Just wondering whether you could encode the regions hierarchy in an RDF/SKOS file, store that RDF/SKOS file in sesame/open RDF and use (or add to the existing) SPARQL/GeoSPARQL services to query the relationships and search etc?
An additional advantage of this is that if you are going to offer a tree structure/hierarchical view of regions from RDF/SKOS as a user interface widget then the same widget might also be used for allowing a user to browse the hierarchy of an RDF/SKOS vocab in the thesaurus picker?

In short: Why treat regions differently to any another RDF/SKOS file?

Cheers,
Simon
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Tuesday, 13 November 2012 3:01 AM
To: Devel geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] How are Regions used in LuceneSearcher

Hi,

In the lucene searcher, all regions are added to the request data but I do not see where the regions are used in creating the query.

Is this a remanent of some older functionality or are they still used in some cases?

I need to know because of the work i am doing for the ExtendedRegions – GeoNetwork opensource Developer website proposal.

Jesse

3

The main reason I was planning on making regions different than just a RDF/SKOS file is because I have 2 other projects that have regions in other locations. For example one project has them in a postgis database and another have the regions in a WFS.

I think it would be difficult to take a RDF query and convert it to WFS or postgis. Also there are optimizations that can be made if the API is a bit more specific. RDF/SKOS is extremely general.

I have not yet added the hierarchical aspect yet but that is a good additional extension. As you say in the regions file one can have Africa which can have a narrower relation to all of the african countries. At the moment I simply have a category which is a broader category in the default implementation.

···

On Thu, Nov 15, 2012 at 3:54 PM, <Simon.Pigot@anonymised.com> wrote:

Not sure about the answer to your question Jesse at the moment - but had a look at your proposal - which is interesting!

Just wondering whether you could encode the regions hierarchy in an RDF/SKOS file, store that RDF/SKOS file in sesame/open RDF and use (or add to the existing) SPARQL/GeoSPARQL services to query the relationships and search etc?
An additional advantage of this is that if you are going to offer a tree structure/hierarchical view of regions from RDF/SKOS as a user interface widget then the same widget might also be used for allowing a user to browse the hierarchy of an RDF/SKOS vocab in the thesaurus picker?

In short: Why treat regions differently to any another RDF/SKOS file?

Cheers,
Simon

From: Jesse Eichar [jesse.eichar@…189…]
Sent: Tuesday, 13 November 2012 3:01 AM
To: Devel geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] How are Regions used in LuceneSearcher

Hi,

In the lucene searcher, all regions are added to the request data but I do not see where the regions are used in creating the query.

Is this a remanent of some older functionality or are they still used in some cases?

I need to know because of the work i am doing for the http://trac.osgeo.org/geonetwork/wiki/ExtendedRegions proposal.

Jesse

4

Actually the WFS is one of the use cases we have here - we take the regions from the WFS using the WFS GetFeatures harvester and convert to ISO19135 and then from there to SKOS for use in the thesaurus tools - it would certainly be possible to skip the ISO19135 intermediate step and go straight to SKOS (ISO19135 is for those that want to manage a vocab outside of the db) especially for very large vocabs.

Cheers,
Simon

________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Friday, 16 November 2012 2:03 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: Devel geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] How are Regions used in LuceneSearcher

The main reason I was planning on making regions different than just a RDF/SKOS file is because I have 2 other projects that have regions in other locations. For example one project has them in a postgis database and another have the regions in a WFS.

I think it would be difficult to take a RDF query and convert it to WFS or postgis. Also there are optimizations that can be made if the API is a bit more specific. RDF/SKOS is extremely general.

I have not yet added the hierarchical aspect yet but that is a good additional extension. As you say in the regions file one can have Africa which can have a narrower relation to all of the african countries. At the moment I simply have a category which is a broader category in the default implementation.

On Thu, Nov 15, 2012 at 3:54 PM, <Simon.Pigot@anonymised.com<mailto:Simon.Pigot@…192…>> wrote:
Not sure about the answer to your question Jesse at the moment - but had a look at your proposal - which is interesting!

Just wondering whether you could encode the regions hierarchy in an RDF/SKOS file, store that RDF/SKOS file in sesame/open RDF and use (or add to the existing) SPARQL/GeoSPARQL services to query the relationships and search etc?
An additional advantage of this is that if you are going to offer a tree structure/hierarchical view of regions from RDF/SKOS as a user interface widget then the same widget might also be used for allowing a user to browse the hierarchy of an RDF/SKOS vocab in the thesaurus picker?

In short: Why treat regions differently to any another RDF/SKOS file?

Cheers,
Simon
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com<mailto:jesse.eichar@anonymised.com>]
Sent: Tuesday, 13 November 2012 3:01 AM
To: Devel geonetwork-devel@lists.sourceforge.net<mailto:geonetwork-devel@anonymised.comsts.sourceforge.net>
Subject: [GeoNetwork-devel] How are Regions used in LuceneSearcher

Hi,

In the lucene searcher, all regions are added to the request data but I do not see where the regions are used in creating the query.

Is this a remanent of some older functionality or are they still used in some cases?

I need to know because of the work i am doing for the ExtendedRegions – GeoNetwork opensource Developer website proposal.

Jesse

5

Hi Simon,

I think I misunderstood your point. I just re-read your email and I think what you want is that the default regions strategy is based on RDF files. Is that correct?

I hope that was your point because that is exactly what I have done. The implementation I have made for Geonetwork uses the regions thesaurus instead of the database. In fact it is a configuration value to set the name of the thesaurus you want to use.

Jesse

···

On Fri, Nov 16, 2012 at 1:11 AM, <Simon.Pigot@anonymised.com2…> wrote:

Actually the WFS is one of the use cases we have here - we take the regions from the WFS using the WFS GetFeatures harvester and convert to ISO19135 and then from there to SKOS for use in the thesaurus tools - it would certainly be possible to skip the ISO19135 intermediate step and go straight to SKOS (ISO19135 is for those that want to manage a vocab outside of the db) especially for very large vocabs.

Cheers,
Simon

From: Jesse Eichar [jesse.eichar@…189…]

Sent: Friday, 16 November 2012 2:03 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: Devel geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] How are Regions used in LuceneSearcher

The main reason I was planning on making regions different than just a RDF/SKOS file is because I have 2 other projects that have regions in other locations. For example one project has them in a postgis database and another have the regions in a WFS.

I think it would be difficult to take a RDF query and convert it to WFS or postgis. Also there are optimizations that can be made if the API is a bit more specific. RDF/SKOS is extremely general.

I have not yet added the hierarchical aspect yet but that is a good additional extension. As you say in the regions file one can have Africa which can have a narrower relation to all of the african countries. At the moment I simply have a category which is a broader category in the default implementation.

On Thu, Nov 15, 2012 at 3:54 PM, <Simon.Pigot@anonymised.com.192…mailto:[Simon.Pigot@anonymised.com92...](mailto:Simon.Pigot@anonymised.com)> wrote:
Not sure about the answer to your question Jesse at the moment - but had a look at your proposal - which is interesting!

Just wondering whether you could encode the regions hierarchy in an RDF/SKOS file, store that RDF/SKOS file in sesame/open RDF and use (or add to the existing) SPARQL/GeoSPARQL services to query the relationships and search etc?
An additional advantage of this is that if you are going to offer a tree structure/hierarchical view of regions from RDF/SKOS as a user interface widget then the same widget might also be used for allowing a user to browse the hierarchy of an RDF/SKOS vocab in the thesaurus picker?

In short: Why treat regions differently to any another RDF/SKOS file?

Cheers,
Simon

From: Jesse Eichar [jesse.eichar@anonymised.commailto:[jesse.eichar@anonymised.com](mailto:jesse.eichar@anonymised.com)]

Sent: Tuesday, 13 November 2012 3:01 AM

To: Devel geonetwork-devel@lists.sourceforge.netmailto:[geonetwork-devel@lists.sourceforge.net](mailto:geonetwork-devel@lists.sourceforge.net)

Subject: [GeoNetwork-devel] How are Regions used in LuceneSearcher

Hi,

In the lucene searcher, all regions are added to the request data but I do not see where the regions are used in creating the query.

Is this a remanent of some older functionality or are they still used in some cases?

I need to know because of the work i am doing for the http://trac.osgeo.org/geonetwork/wiki/ExtendedRegions proposal.

Jesse