Critera and SpatialRestrictions with geometries from two different tables

9 messages Options
Embed this post
Permalink
fgdrf

Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
Hello,

I'm using Hibernatespatial with the oracle spatial dialect (OracleSpatial10gDialect) and would like to select all objects from one table (with a sdo_geometry column attribute) which geometry is within (mask=INSIDE+COVEREDBY) a selected geometry of an other table.

The pure sql statement looks like this:

SELECT a.gid
  FROM polygons a, query_polys B
  WHERE <a condition o b for subselect>
  AND SDO_RELATE(A.Geometry, B.Geometry,
                   'mask=touch+coveredby') = 'TRUE';

How can create a valid hibernate Criteria with the capability of spatial relate. Are there any other class than SpatialRestrictions to define Criteria?

Can somebody help?

In regards,
Frank

_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
fgdrf

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
Hello again,

the get the features within a polygon defined in query_polys the mask should be "touch+inside" instead of "touch+coveredby". Sorry for that.

cheers,
Frank

> Hello,
>
> I'm using Hibernatespatial with the oracle spatial dialect (OracleSpatial10gDialect) and would like to select all objects from one table (with a sdo_geometry column attribute) which geometry is within (mask=INSIDE+COVEREDBY) a selected geometry of an other table.
>
> The pure sql statement looks like this:
>
> SELECT a.gid
>   FROM polygons a, query_polys B
>   WHERE <a condition o b for subselect>
>   AND SDO_RELATE(A.Geometry, B.Geometry,
>                    'mask=touch+coveredby') = 'TRUE';
>
> How can create a valid hibernate Criteria with the capability of spatial relate. Are there any other class than SpatialRestrictions to define Criteria?
>
> Can somebody help?
>
> In regards,
> Frank
>
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
>


_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
Karel Maesen

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
Hi Frank,

There exists a subclass of SpatialRestrictions specifically for the  
operations you mention here.  Have a look at http://
www.hibernatespatial.org/hibernate-spatial-oracle/apidocs/index.html.

Regards,

Karel Maesen

On 09 Jun 2009, at 16:29, [hidden email] wrote:

> Hello again,
>
> the get the features within a polygon defined in query_polys the  
> mask should be "touch+inside" instead of "touch+coveredby". Sorry  
> for that.
>
> cheers,
> Frank
>
>> Hello,
>>
>> I'm using Hibernatespatial with the oracle spatial dialect  
>> (OracleSpatial10gDialect) and would like to select all objects  
>> from one table (with a sdo_geometry column attribute) which  
>> geometry is within (mask=INSIDE+COVEREDBY) a selected geometry of  
>> an other table.
>>
>> The pure sql statement looks like this:
>>
>> SELECT a.gid
>>   FROM polygons a, query_polys B
>>   WHERE <a condition o b for subselect>
>>   AND SDO_RELATE(A.Geometry, B.Geometry,
>>                    'mask=touch+coveredby') = 'TRUE';
>>
>> How can create a valid hibernate Criteria with the capability of  
>> spatial relate. Are there any other class than SpatialRestrictions  
>> to define Criteria?
>>
>> Can somebody help?
>>
>> In regards,
>> Frank
>>
>> _______________________________________________
>> hibernatespatial-users mailing list
>> [hidden email]
>> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
>> hibernatespatial-users
>>
>
>
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> hibernatespatial-users

_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
fgdrf

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
In reply to this post by fgdrf
Hi Karel,

sorry, but I can't find a subclass of SpatialRestrictions. Could you give me some psydo code how to get this problem solved? I'm pretty new to hibernatespatial but the javadoc without any examle does not point me into the right direction. I visited the Tutorial-page (http://www.hibernatespatial.org/tutorial.html) and the oracle10g usage-guide (http://www.hibernatespatial.org/hibernate-spatial-oracle/usage.html) too. But I was not able to find any hints there matching the requirements a described.

Thanks for help and kind regards
Frank

> Hi Frank,
>
> There exists a subclass of SpatialRestrictions specifically for the  
> operations you mention here.  Have a look at http://
> www.hibernatespatial.org/hibernate-spatial-oracle/apidocs/index.html.
>
> Regards,
>
> Karel Maesen
>
> On 09 Jun 2009, at 16:29, [hidden email] wrote:
>
> > Hello again,
> >
> > the get the features within a polygon defined in query_polys the  
> > mask should be "touch+inside" instead of "touch+coveredby". Sorry  
> > for that.
> >
> > cheers,
> > Frank
> >
> >> Hello,
> >>
> >> I'm using Hibernatespatial with the oracle spatial dialect  
> >> (OracleSpatial10gDialect) and would like to select all objects  
> >> from one table (with a sdo_geometry column attribute) which  
> >> geometry is within (mask=INSIDE+COVEREDBY) a selected geometry of  
> >> an other table.
> >>
> >> The pure sql statement looks like this:
> >>
> >> SELECT a.gid
> >>   FROM polygons a, query_polys B
> >>   WHERE <a condition o b for subselect>
> >>   AND SDO_RELATE(A.Geometry, B.Geometry,
> >>                    'mask=touch+coveredby') = 'TRUE';
> >>
> >> How can create a valid hibernate Criteria with the capability of  
> >> spatial relate. Are there any other class than SpatialRestrictions  
> >> to define Criteria?
> >>
> >> Can somebody help?
> >>
> >> In regards,
> >> Frank
> >>
> >> _______________________________________________
> >> hibernatespatial-users mailing list
> >> [hidden email]
> >> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> >> hibernatespatial-users
> >>
> >
> >
> > _______________________________________________
> > hibernatespatial-users mailing list
> > [hidden email]
> > http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> > hibernatespatial-users
>
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
>


_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
fgdrf

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
In reply to this post by fgdrf
Hello again,

I just found a solution but I don't use hibernatespatial (except for maping the result to a class haveing a geometry attribute) anymore:

                [....]
                session.beginTransaction();
                List results = session.createSQLQuery(
                            "SELECT a.* FROM polygons a, query_polys B \n" +
                             "  WHERE b.name = 'a name' \n" +   // TODO use a named binding here
                             "       AND SDO_RELATE(A.Geometry, B.Geometry, 'mask=touch+inside') = 'TRUE' ", "a", MyClass.class).list();
                [....]


Cheers,

Frank
_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
Karel Maesen

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
Hi Frank,


Here is a short example of a solution using the  
OracleSpatialRestrictions. Note that this works only with a query  
geometry and a geometry column, and not with two geometry columns in  
separate tables.

mport org.hibernate.criterion.Criterion;
import org.hibernatespatial.oracle.criterion.OracleSpatialRestrictions;
import org.hibernatespatial.oracle.criterion.RelationshipMask;
import org.hibernatespatial.oracle.criterion.SDOParameterMap;
import com.vividsolutions.jts.geom.Polygon;

...
Criteria criteria = session.createCriteria(Entity.class)
//Create the SDOParameter map
   SDOParameterMap params = new SDOParameterMap();
   params.setMask("TOUCH+COVEREDBY");
//Set the query geometry
   Polygon geom = ...;
//create the Criterion. Shape is the geometry property in the Entity  
class
Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,  
params);
criteria.add(c);

//Here is an alternative for creating the Criterion

   Polygon geom = null;
   RelationshipMask[] mask = new RelationshipMask[] {
     RelationshipMask.TOUCH,
     RelationshipMask.COVEREDBY
};
   double minResolution = ....;
   double maxResolution  =  ...;
   Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,  
mask, minResolution, maxResolution);
...

Regards,

Karel


On 10 Jun 2009, at 10:31, [hidden email] wrote:

> Hello again,
>
> I just found a solution but I don't use hibernatespatial (except  
> for maping the result to a class haveing a geometry attribute)  
> anymore:
>
>                 [....]
> session.beginTransaction();
> List results = session.createSQLQuery(
>                             "SELECT a.* FROM polygons a,  
> query_polys B \n" +
>                              "  WHERE b.name = 'a name' \n" +   //  
> TODO use a named binding here
>                              "       AND SDO_RELATE(A.Geometry,  
> B.Geometry, 'mask=touch+inside') = 'TRUE' ", "a",  
> MyClass.class).list();
>                 [....]
>
>
> Cheers,
>
> Frank
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> hibernatespatial-users

_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
fgdrf

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
In reply to this post by fgdrf
Thanks Karel!

Could that be an issue as an enhancement to get Criterias defined as an alternative way to write pur sql (see post http://n2.nabble.com/Critera-and-SpatialRestrictions-with-geometries-from-two-different-tables-tp3049602p3054325.html)? It could become difficult to define an alias if there is no relation defined between the classes and even no java-class exist for the joined spatial table.

Did nobody else has requirements like that? I don't want to preselect the geometries from table A and query table B n-times from clients side. That's was the database should do for me.

The main reason why I would like to create an issue is: The dialect has allready defined how the database function is named and with the RelationshipMask it is still defined what kind of spatial relations can be executed. Pur SQL can't use this definitions right now, it's hard coded in OracleSpatialRestrictions ..

What do you think. is there a way to get criterias defined without having a geometry, only use the spatial relations within a database between tables?

That would be great!

Thanks a lot,

Frank




> Hi Frank,
>
>
> Here is a short example of a solution using the  
> OracleSpatialRestrictions. Note that this works only with a query  
> geometry and a geometry column, and not with two geometry columns in  
> separate tables.
>
> mport org.hibernate.criterion.Criterion;
> import org.hibernatespatial.oracle.criterion.OracleSpatialRestrictions;
> import org.hibernatespatial.oracle.criterion.RelationshipMask;
> import org.hibernatespatial.oracle.criterion.SDOParameterMap;
> import com.vividsolutions.jts.geom.Polygon;
>
> ...
> Criteria criteria = session.createCriteria(Entity.class)
> //Create the SDOParameter map
>    SDOParameterMap params = new SDOParameterMap();
>    params.setMask("TOUCH+COVEREDBY");
> //Set the query geometry
>    Polygon geom = ...;
> //create the Criterion. Shape is the geometry property in the Entity  
> class
> Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,  
> params);
> criteria.add(c);
>
> //Here is an alternative for creating the Criterion
>
>    Polygon geom = null;
>    RelationshipMask[] mask = new RelationshipMask[] {
>      RelationshipMask.TOUCH,
>      RelationshipMask.COVEREDBY
> };
>    double minResolution = ....;
>    double maxResolution  =  ...;
>    Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,  
> mask, minResolution, maxResolution);
> ...
>
> Regards,
>
> Karel
>
>
> On 10 Jun 2009, at 10:31, [hidden email] wrote:
>
> > Hello again,
> >
> > I just found a solution but I don't use hibernatespatial (except  
> > for maping the result to a class haveing a geometry attribute)  
> > anymore:
> >
> >                 [....]
> > session.beginTransaction();
> > List results = session.createSQLQuery(
> >                             "SELECT a.* FROM polygons a,  
> > query_polys B \n" +
> >                              "  WHERE b.name = 'a name' \n" +   //  
> > TODO use a named binding here
> >                              "       AND SDO_RELATE(A.Geometry,  
> > B.Geometry, 'mask=touch+inside') = 'TRUE' ", "a",  
> > MyClass.class).list();
> >                 [....]
> >
> >
> > Cheers,
> >
> > Frank
> > _______________________________________________
> > hibernatespatial-users mailing list
> > [hidden email]
> > http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> > hibernatespatial-users
>
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
>


_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
Karel Maesen

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
Frank,

I agree that it would be a worthwhile enhancement to Hibernate  
Spatial to be able to exploit spatial relations between tables.  
Either we can try to do it in the Criteria API, or in HQL (by  
defining the relevant functions in the dialect). But I'm not sure any  
of this will work.

I would suggest to add an issue in JIRA for this, and I'll  
investigate it  later.

Regards,

Karel

On 10 Jun 2009, at 13:45, [hidden email] wrote:

> Thanks Karel!
>
> Could that be an issue as an enhancement to get Criterias defined  
> as an alternative way to write pur sql (see post http://
> n2.nabble.com/Critera-and-SpatialRestrictions-with-geometries-from-
> two-different-tables-tp3049602p3054325.html)? It could become  
> difficult to define an alias if there is no relation defined  
> between the classes and even no java-class exist for the joined  
> spatial table.
>
> Did nobody else has requirements like that? I don't want to  
> preselect the geometries from table A and query table B n-times  
> from clients side. That's was the database should do for me.
>
> The main reason why I would like to create an issue is: The dialect  
> has allready defined how the database function is named and with  
> the RelationshipMask it is still defined what kind of spatial  
> relations can be executed. Pur SQL can't use this definitions right  
> now, it's hard coded in OracleSpatialRestrictions ..
>
> What do you think. is there a way to get criterias defined without  
> having a geometry, only use the spatial relations within a database  
> between tables?
>
> That would be great!
>
> Thanks a lot,
>
> Frank
>
>
>
>
>> Hi Frank,
>>
>>
>> Here is a short example of a solution using the
>> OracleSpatialRestrictions. Note that this works only with a query
>> geometry and a geometry column, and not with two geometry columns in
>> separate tables.
>>
>> mport org.hibernate.criterion.Criterion;
>> import  
>> org.hibernatespatial.oracle.criterion.OracleSpatialRestrictions;
>> import org.hibernatespatial.oracle.criterion.RelationshipMask;
>> import org.hibernatespatial.oracle.criterion.SDOParameterMap;
>> import com.vividsolutions.jts.geom.Polygon;
>>
>> ...
>> Criteria criteria = session.createCriteria(Entity.class)
>> //Create the SDOParameter map
>>    SDOParameterMap params = new SDOParameterMap();
>>    params.setMask("TOUCH+COVEREDBY");
>> //Set the query geometry
>>    Polygon geom = ...;
>> //create the Criterion. Shape is the geometry property in the Entity
>> class
>> Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,
>> params);
>> criteria.add(c);
>>
>> //Here is an alternative for creating the Criterion
>>
>>    Polygon geom = null;
>>    RelationshipMask[] mask = new RelationshipMask[] {
>>      RelationshipMask.TOUCH,
>>      RelationshipMask.COVEREDBY
>> };
>>    double minResolution = ....;
>>    double maxResolution  =  ...;
>>    Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,
>> mask, minResolution, maxResolution);
>> ...
>>
>> Regards,
>>
>> Karel
>>
>>
>> On 10 Jun 2009, at 10:31, [hidden email] wrote:
>>
>>> Hello again,
>>>
>>> I just found a solution but I don't use hibernatespatial (except
>>> for maping the result to a class haveing a geometry attribute)
>>> anymore:
>>>
>>>                 [....]
>>> session.beginTransaction();
>>> List results = session.createSQLQuery(
>>>                             "SELECT a.* FROM polygons a,
>>> query_polys B \n" +
>>>                              "  WHERE b.name = 'a name' \n" +   //
>>> TODO use a named binding here
>>>                              "       AND SDO_RELATE(A.Geometry,
>>> B.Geometry, 'mask=touch+inside') = 'TRUE' ", "a",
>>> MyClass.class).list();
>>>                 [....]
>>>
>>>
>>> Cheers,
>>>
>>> Frank
>>> _______________________________________________
>>> hibernatespatial-users mailing list
>>> [hidden email]
>>> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/
>>> hibernatespatial-users
>>
>> _______________________________________________
>> hibernatespatial-users mailing list
>> [hidden email]
>> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
>> hibernatespatial-users
>>
>
>
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> hibernatespatial-users

_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
fgdrf

Re: Critera and SpatialRestrictions with geometries from two different tables

Reply Threaded More More options
Print post
Permalink
In reply to this post by fgdrf
Hi Karel,

I just read an interessting statement in the "hibernate in action" book (p. 268) "Critera API doesn't provide any means for  ...  theta-style joins". Some posts in different forums confirmed that (e.g. http://www.coderanch.com/t/216690/Object-Relational-Mapping/java/Theta-style-joins-Criteria) but it'seems possible to use a subselect with joined table, like described in Post (https://forums.hibernate.org/viewtopic.php?f=1&t=961644&start=0&sid=8a333b18283dfebc09fc7a84502ae6a4)

Regards, Frank

> Frank,
>
> I agree that it would be a worthwhile enhancement to Hibernate  
> Spatial to be able to exploit spatial relations between tables.  
> Either we can try to do it in the Criteria API, or in HQL (by  
> defining the relevant functions in the dialect). But I'm not sure any  
> of this will work.
>
> I would suggest to add an issue in JIRA for this, and I'll  
> investigate it  later.
>
> Regards,
>
> Karel
>
> On 10 Jun 2009, at 13:45, [hidden email] wrote:
>
> > Thanks Karel!
> >
> > Could that be an issue as an enhancement to get Criterias defined  
> > as an alternative way to write pur sql (see post http://
> > n2.nabble.com/Critera-and-SpatialRestrictions-with-geometries-from-
> > two-different-tables-tp3049602p3054325.html)? It could become  
> > difficult to define an alias if there is no relation defined  
> > between the classes and even no java-class exist for the joined  
> > spatial table.
> >
> > Did nobody else has requirements like that? I don't want to  
> > preselect the geometries from table A and query table B n-times  
> > from clients side. That's was the database should do for me.
> >
> > The main reason why I would like to create an issue is: The dialect  
> > has allready defined how the database function is named and with  
> > the RelationshipMask it is still defined what kind of spatial  
> > relations can be executed. Pur SQL can't use this definitions right  
> > now, it's hard coded in OracleSpatialRestrictions ..
> >
> > What do you think. is there a way to get criterias defined without  
> > having a geometry, only use the spatial relations within a database  
> > between tables?
> >
> > That would be great!
> >
> > Thanks a lot,
> >
> > Frank
> >
> >
> >
> >
> >> Hi Frank,
> >>
> >>
> >> Here is a short example of a solution using the
> >> OracleSpatialRestrictions. Note that this works only with a query
> >> geometry and a geometry column, and not with two geometry columns in
> >> separate tables.
> >>
> >> mport org.hibernate.criterion.Criterion;
> >> import  
> >> org.hibernatespatial.oracle.criterion.OracleSpatialRestrictions;
> >> import org.hibernatespatial.oracle.criterion.RelationshipMask;
> >> import org.hibernatespatial.oracle.criterion.SDOParameterMap;
> >> import com.vividsolutions.jts.geom.Polygon;
> >>
> >> ...
> >> Criteria criteria = session.createCriteria(Entity.class)
> >> //Create the SDOParameter map
> >>    SDOParameterMap params = new SDOParameterMap();
> >>    params.setMask("TOUCH+COVEREDBY");
> >> //Set the query geometry
> >>    Polygon geom = ...;
> >> //create the Criterion. Shape is the geometry property in the Entity
> >> class
> >> Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,
> >> params);
> >> criteria.add(c);
> >>
> >> //Here is an alternative for creating the Criterion
> >>
> >>    Polygon geom = null;
> >>    RelationshipMask[] mask = new RelationshipMask[] {
> >>      RelationshipMask.TOUCH,
> >>      RelationshipMask.COVEREDBY
> >> };
> >>    double minResolution = ....;
> >>    double maxResolution  =  ...;
> >>    Criterion c = OracleSpatialRestrictions.SDORelate("shape", geom,
> >> mask, minResolution, maxResolution);
> >> ...
> >>
> >> Regards,
> >>
> >> Karel
> >>
> >>
> >> On 10 Jun 2009, at 10:31, [hidden email] wrote:
> >>
> >>> Hello again,
> >>>
> >>> I just found a solution but I don't use hibernatespatial (except
> >>> for maping the result to a class haveing a geometry attribute)
> >>> anymore:
> >>>
> >>>                 [....]
> >>> session.beginTransaction();
> >>> List results = session.createSQLQuery(
> >>>                             "SELECT a.* FROM polygons a,
> >>> query_polys B \n" +
> >>>                              "  WHERE b.name = 'a name' \n" +   //
> >>> TODO use a named binding here
> >>>                              "       AND SDO_RELATE(A.Geometry,
> >>> B.Geometry, 'mask=touch+inside') = 'TRUE' ", "a",
> >>> MyClass.class).list();
> >>>                 [....]
> >>>
> >>>
> >>> Cheers,
> >>>
> >>> Frank
> >>> _______________________________________________
> >>> hibernatespatial-users mailing list
> >>> [hidden email]
> >>> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/
> >>> hibernatespatial-users
> >>
> >> _______________________________________________
> >> hibernatespatial-users mailing list
> >> [hidden email]
> >> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> >> hibernatespatial-users
> >>
> >
> >
> > _______________________________________________
> > hibernatespatial-users mailing list
> > [hidden email]
> > http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/ 
> > hibernatespatial-users
>
> _______________________________________________
> hibernatespatial-users mailing list
> [hidden email]
> http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
>


_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users