Hi all: Is anyone using geonetwork at the poles? Straight lat/lon (epsg:4326) doesn't work too well so it would
be beneficial to store geographic and native (say, polar stereographic) extents for each metadata record. Do
the schema allow for that or is it possible to extent them easily?
Steve
Excellent on the multiple extent front. We found a paper on the topic that talks about some
of the problems of using equatorial coordinate systems in case anyone is interested.
http://chukchi.colorado.edu/PAPER/
We'll probably not use lat/lon for searches at all.
Steve
On Jan 25, 2008, at 12:47 AM, Jeroen Ticheler wrote:
Hi Steve,
On Jan 25, 2008, at 7:03 AM, Stephen Lime wrote:
Hi all: Is anyone using geonetwork at the poles?
Leave that to others
Straight lat/lon
(epsg:4326) doesn't work too well so it would
be beneficial to store geographic and native (say, polar stereographic)
extents for each metadata record. Do
the schema allow for that or is it possible to extent them easily?Yes, the ISO19115 allows for multiple extents, even if 1 of them should be in lat/lon.
The index & search for BBOX are now based on a text indexing API, Lucene. You may have to make changes to the GN code to allow proper searching on BBOX's with other projections. Even more so when they have to go hand in hand with 4326.
Others may have more thoughts on this than me.
Ciao,
JeroenSteve
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
