[GeoNetwork-users] Limit of keyword list

GeoNetwork GeoNetwork User
1

Hi list,

It seems that the keyword list in the advanced search is limited to 100
keywords. So if you have more than 100 keywords you can't see all of them.
Does anyone know how to modify this limit?

Thanks.
Pierre
--
View this message in context: http://n2.nabble.com/Limit-of-keyword-list-tp3506224p3506224.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

2

Hi Pierre,

In WEB-INF\config-summary.xml I suppose :
item name="keyword" plural="keywords" indexKey="keyword" order="freq"
type="string" max="*100*"/>

Jean

2009/8/24 pierre vernier <pierre.vernier@anonymised.com>

Hi list,

It seems that the keyword list in the advanced search is limited to 100
keywords. So if you have more than 100 keywords you can't see all of them.
Does anyone know how to modify this limit?

Thanks.
Pierre
--
View this message in context:
http://n2.nabble.com/Limit-of-keyword-list-tp3506224p3506224.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

3

Hi Jean,

Indeed that was it.

Thanks.
Pierre

Jean Pommier (IGE) wrote:

Hi Pierre,

In WEB-INF\config-summary.xml I suppose :
item name="keyword" plural="keywords" indexKey="keyword" order="freq"
type="string" max="*100*"/>

Jean

2009/8/24 pierre vernier <pierre.vernier@anonymised.com>

Hi list,

It seems that the keyword list in the advanced search is limited to 100
keywords. So if you have more than 100 keywords you can't see all of
them.
Does anyone know how to modify this limit?

Thanks.
Pierre
--
View this message in context:
http://n2.nabble.com/Limit-of-keyword-list-tp3506224p3506224.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and
focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

--
View this message in context: http://n2.nabble.com/Limit-of-keyword-list-tp3506224p3510784.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.

4

Hi.

I'm trying to use GN for metadata from surveys in the Ross Sea (Antarctica) and of the Chatham Rise (E of New Zealand).

Both surveys, & the datasets I need to describe, cross 180 degrees.

With most FOSS tools (PostGIS, mapserver, OpenLayers, GMT, etc) I can use longitudes in a 0-360 degree space, so my extent becomes (for example)

        -35
  160 195
        -55

GN accepts these values, but a map search fails to locate them.

How can I properly represent & map search datasets crossing 180 in GN?

Thanks,

  Brent Wood

5

Hi Brent,

I'm not a GN expert but we sometimes show the west bounding coordinate to be larger than the east bounding coordinate to span over the international date line. For example, your bounding box ordinates would be:

        -35
160 -165
        -55

I don't know if GN allows this type of thing.

John

-----Original Message-----
From: pcreso@anonymised.com [mailto:pcreso@anonymised.com]
Sent: Monday, 14 September 2009 1:39 PM
To: geonetwork-users@lists.sourceforge.net
Subject: [GeoNetwork-users] 180 degree issue

Hi.

I'm trying to use GN for metadata from surveys in the Ross
Sea (Antarctica) and of the Chatham Rise (E of New Zealand).

Both surveys, & the datasets I need to describe, cross 180 degrees.

With most FOSS tools (PostGIS, mapserver, OpenLayers, GMT,
etc) I can use longitudes in a 0-360 degree space, so my
extent becomes (for example)

        -35
  160 195
        -55

GN accepts these values, but a map search fails to locate them.

How can I properly represent & map search datasets crossing 180 in GN?

Thanks,

  Brent Wood

--------------------------------------------------------------
----------------
Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day
trial. Simplify your report design, integration and
deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

6

I have had the same problem and the only solution that we could get to work
in geonetwork was to create 2 metadata records with bounding boxes that
described the area each side of the date line

e.g.
  -35
-180 -165
  -55

  -35
160 180
  -55

This obviously doesn't totally solve the searching problem and users would
also have to do two searches to check for things either side of the
boundary.

This is not a great solution, and I didn't get any different ideas from GN
users yet, but if anyone can come up with anything then would be much
appreciated.

Cheers
Caroline

-----Original Message-----
From: John.Hockaday@anonymised.com [mailto:John.Hockaday@anonymised.com]
Sent: 14 September 2009 07:20
To: pcreso@anonymised.com; geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] 180 degree issue [SEC=UNCLASSIFIED]

Hi Brent,

I'm not a GN expert but we sometimes show the west bounding coordinate to be
larger than the east bounding coordinate to span over the international date
line. For example, your bounding box ordinates would be:

        -35
160 -165
        -55

I don't know if GN allows this type of thing.

John

-----Original Message-----
From: pcreso@anonymised.com [mailto:pcreso@anonymised.com]
Sent: Monday, 14 September 2009 1:39 PM
To: geonetwork-users@lists.sourceforge.net
Subject: [GeoNetwork-users] 180 degree issue

Hi.

I'm trying to use GN for metadata from surveys in the Ross
Sea (Antarctica) and of the Chatham Rise (E of New Zealand).

Both surveys, & the datasets I need to describe, cross 180 degrees.

With most FOSS tools (PostGIS, mapserver, OpenLayers, GMT,
etc) I can use longitudes in a 0-360 degree space, so my
extent becomes (for example)

        -35
  160 195
        -55

GN accepts these values, but a map search fails to locate them.

How can I properly represent & map search datasets crossing 180 in GN?

Thanks,

  Brent Wood

--------------------------------------------------------------
----------------
Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day
trial. Simplify your report design, integration and
deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

7

Hello Brent,

2009/9/14 <pcreso@anonymised.com>:

I'm trying to use GN for metadata from surveys in the Ross Sea (Antarctica) and of the Chatham Rise (E of New Zealand).
Both surveys, & the datasets I need to describe, cross 180 degrees.
With most FOSS tools (PostGIS, mapserver, OpenLayers, GMT, etc) I can use longitudes in a 0-360 degree space, so my extent becomes (for example)

   \-35

160 195
-55

GN accepts these values, but a map search fails to locate them.

How can I properly represent & map search datasets crossing 180 in GN?

As suggested in previous post, some workaround could help.

Anyway, I've been testing this use case on the extent editor committed
last week which will allow to set such a bounding box.
The bounding box is indexed and CSW search is also working [1].

The issue remains on the search form based on Intermap.
We have to address that issue in current discussion in the replacing
intermap proposal.

Ciao.

Francois
[1] http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/web/geonetwork/xml/csw/test/csw-GetRecordsFilterGeoBboxForMoreThan180degrees.xml?revision=5194&view=markup

Thanks,

Brent Wood

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
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

8

Thanks Francois,

I was looking at the GCMD spec here:
http://gcmd.gsfc.nasa.gov/User/difguide/spatial_coverage.html

I'm not sure if the ISO 19115 or CSW spec has similar guidelines or not, but this suggests the use of 0-360 is not allowed, but supports tests where the E limit is less than the W limit & E limit is negative to imply a 180 cross.

In which case, the issue is not one of accepting 180-360 coordinates, but instead is one of supporting proper searches by creating either a 0-360 bounding box, or 2 boxes, one at +180 and one at -180 for such cases.

This may be a more elegant solution, as data is always stored consistently, and the issue is then recognised and dealt with correctly in the code.

Ideally the search map can then be implemented in +-180 or 0-360 (chosen at install time), allowing cross 180 searches, and again, the search code can build appropriate +-180 bounding boxes from the users' selection to suit the underlying values in the metadata records.

Regards,

  Brent Wood

--- On Wed, 9/23/09, Francois Prunayre <fx.prunayre@anonymised.com> wrote:

From: Francois Prunayre <fx.prunayre@anonymised.com>
Subject: Re: [GeoNetwork-users] 180 degree issue
To: pcreso@anonymised.com
Cc: geonetwork-users@lists.sourceforge.net
Date: Wednesday, September 23, 2009, 3:21 AM
Hello Brent,

2009/9/14 <pcreso@anonymised.com>:
> I'm trying to use GN for metadata from surveys in the
Ross Sea (Antarctica) and of the Chatham Rise (E of New
Zealand).
> Both surveys, & the datasets I need to describe,
cross 180 degrees.
> With most FOSS tools (PostGIS, mapserver, OpenLayers,
GMT, etc) I can use longitudes in a 0-360 degree space, so
my extent becomes (for example)
>
> -35
> 160 195
> -55
>
> GN accepts these values, but a map search fails to
locate them.
>
> How can I properly represent & map search datasets
crossing 180 in GN?

As suggested in previous post, some workaround could help.

Anyway, I've been testing this use case on the extent
editor committed
last week which will allow to set such a bounding box.
The bounding box is indexed and CSW search is also working
[1].

The issue remains on the search form based on Intermap.
We have to address that issue in current discussion in the
replacing
intermap proposal.

Ciao.

Francois
[1] http://geonetwork.svn.sourceforge.net/viewvc/geonetwork/trunk/web/geonetwork/xml/csw/test/csw-GetRecordsFilterGeoBboxForMoreThan180degrees.xml?revision=5194&view=markup
>
>
> Thanks,
>
> Brent Wood
>
>
------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free
Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and
deployment - and focus on
> what you do best, core application coding. Discover
what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> 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
>