Sorry, here you go:
http://docs.codehaus.org/display/GEOS/SpatialDBBox
Ciao,
Jeroen
On May 24, 2006, at 2:24 PM, Andrew Robson wrote:
On 24/05/06, Jeroen Ticheler <Jeroen.Ticheler@…1…> wrote:
Hi Andrew,
That sounds really good! We have been discussing this option a couple of times as it would indeed avoid the required use of a geodatabase like PostGIS. The concept has been worked on also by Dave Blasby (GeoServer lead developer). He referred to it as a “Spatial DB in a box”. Here’s a link to his ideas (you may have run into this!?).Think you missed off the link?
I know Dave, he’s a very nice guy and you may wish to connect to him if need be.
Very much looking forward to your experiences on implementing that on GeoNetwork and see what the (performance) implications will be.
I think it is a good idea to copy this to the devel list so others are aware!?sure
cheers
andrewGreetings,
Jeroen
On May 24, 2006, at 1:45 PM, Andrew Robson wrote:
Hi,
I thought I’d just update you on what I’m doing - after a bit of investigation I’ve decided a good route might be to use
the Java Topology Suite to do the spatial searching. I don’t know if you’re familiar with the JTS? It’s an open source
API which covers all the OGC spatial operations (http://www.vividsolutions.com/jts/jtshome.htm ). I’m assuming
metadata collections are relatively small and a lightweight solution would be attractive. Seems to me incorporating
PostGIS into Geonetwork would complicate the architecture, deployment and installation of Geonetwork unnecessarily
and we should at least consider JTS route first. Using the JTS is just a matter of adding a jar file.I’d like to use most of my remaining time on this to do some ‘proof of concept’ code. What I propose is to write a small
web app which combines Lucene text searching and spatial querying over some metadata records. I’ll use the Jeeves
framework and try and follow the geonetwork architecture as closely as possible so that it’s clear how you might go one
to develop what I do and incorporate it into geonetwork. To cut down on number of spatial calculations I’ll apply the
spatial filtering to the result set of a lucene text search. I won’t consider any other performance issues at this stage -
may be that some form of spatial indexing would be required for a production environment but we can see.If you’d prefer me to do something else please let me know.
regards
andrew