No subject


Wed Jul 15 09:27:57 PDT 2009


functions
using Java stored procs.  There are several consequences of this some =
good
and some bad

The Good
 1) JASPA uses JTS directly so doesn't suffer from the need to port JTS
functionality to GEOS.  So you will probably see new features introduced =
in
JTS in Jaspa sooner than you will see it in PostGIS.

2) Good/Bad -- Not tied to a specific database platform (though it only
really supports PostgreSQL/HSQL at the moment) -- I kind of consider =
this a
good/bad of rasdaman as well.  Its good in the sense that you can run it =
in
other databases, but bad in the sense that your architecture is either =
more
complicated and/or you don't play as nicely with the native =
functionality a
database offers.  JASPA its not quite as much of an issue as it is for
rasdaman since the functions are implemented as PostgreSQL stored =
functions
and can use just like you use PostGIS functions.

3) They seem to implement a lot of things above the core JTS -
http://jaspa.forge.osor.eu/Introduction.html#id474917
Like Delaunay triangles and some topology.  Sounds interesting.
http://jaspa.forge.osor.eu/ST_DelaunayTriangles.html

They claim PostGIS 1.4 compatibility, but not sure if that means 100% -- =
it
does look like they do support at least ST_Dump functions (and have
implemented some of the PostGIS non-geography functions)

http://jaspa.forge.osor.eu/differences.html#id498020

The Bad
While PostgreSQL does support java stored procs, its not a common =
choice.
I'm not sure exactly why.  As I recall a while back -- it had something =
to
do with the way Java classes were created and so forth similar to why =
.NET
is not a supported option in PostgreSQL. Times have changed though so =
may
not be a bad option now. This means
A) Most likely it will be harder to install on all platforms. =20
B) Not as tried and tested as C binding functions.  So things such as =
memory
management between the core PostgreSQL layer and library layer  I =
suspect
will be better in PostGIS than they are in JASPA.

C) There are lots of functions implemented directly in PostGIS  that are =
not
in JTS or GEOS (and GEOS is not a direct port in and of itself of JTS -- =
it
has some 3D glue that JTS lacks).  Example are my favorite functions
implemented directly in PostGIS -  All the geography support introduced =
in
PostGIS 1.5,  ST_ClosestPoint (native PostGIS), =
ST_AsGML/ST_GeomFromGML/KML,
ST_Dump functions  etc.

I would say about 50 percent of the functions in PostGIS are not derived
from JTS/GEOS though there are some overlaps like ST_Distance that =
PostGIS
chose to reimplement because it was more efficient than using the =
JTS/GEOS.
I'm not sure if Jaspa implements these on their own or not. It looks =
like
from their documentation they try to be very compatible with PostGIS.



Hope that helps,
Regina and Leo
http://www.postgis.us

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of =
muhammad
imran
Sent: Friday, July 23, 2010 8:12 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] JASPA (JAva SPATial) for PostgreSQL and
H2released. HSQLDB is planned to be supported.

Dear All,

What are the advantages of JASPA over PostGIS. If anyone can compare =
both
spatial extensions?

regards,
Imran

--- On Fri, 7/23/10, Jose C. Martinez-Llario <jomarlla at cgf.upv.es> =
wrote:

> From: Jose C. Martinez-Llario <jomarlla at cgf.upv.es>
> Subject: [postgis-users] JASPA (JAva SPATial) for PostgreSQL and H2
released. HSQLDB is planned to be supported.
> To: "PostGIS Users Discussion" <postgis-users at postgis.refractions.net>
> Date: Friday, July 23, 2010, 6:33 PM
> =A0 (sorry for the cross posting)
>=20
> ************* text in english
> **************************
>=20
> After one year of development, we are pleased to announce the release
> 0.1RC1 of JASPA (JAva SPAtial). JASPA potentially brings around 200=20
> spatial functions to any relational database system that supports a=20
> full set of java store procedures. In this 0.1 version JASPA supports=20
> PostgreSQL and H2, and we are already working with HSQLDB.
> JASPA has a similar functionality as PostGIS 1.4, supporting spatial=20
> operators and predicates, arrays of geometries, spatial aggregates,=20
> etc. JASPA is written in java and is easy to extend using java store=20
> procedures.
> JASPA is licensed under the GNU GPL.
>=20
> This project has been possible thanks to other open source projects.=20
> Besides to take advantage of these projects we have used their mailing =

> lists and they helped us a lot. The JASPA team is very grateful to
> them:
>=20
> - PostGIS. The mirror on which JASPA has been looking at.
> - JTS (Java Topology Suite). This library is widely used in JASPA and=20
> many open source initiatives bringing the possibility to use spatial=20
> analysis to the java open source world.
> - GeoTools (used for projections, KML support and Shape to JASPA
> converters)
> - PostgreSQL and PLJAVA (Java store procedures for
> PostgreSQL)
> - H2 and H2Spatial (a Java database and its spatial extension used at=20
> the beginning of JASPA)
> - HSQLDB (a Java database which probably will be supported by JASPA in =

> the next release)
> - gvSIG (a desktop SIG which we hope it can connect to JASPA soon)
>=20
> The authors of this project are:
>=20
> =A0 Jose C. Martinez-Llario. Developer and project director. (1)
> =A0 Marta Gonzalez-Alcaide. Tester and document builder.
> (1)
> =A0 (1)=A0 =A0 Deparment of Cartographic
> Engineering, Geodesy and Photogrammetry at La Universidad Politecnica=20
> de Valencia (Spain).
>=20
> =A0 Any contributor is very welcomed to join the JASPA project.
>=20
>=20
> JASPA Download:
>=20
> - The latest software can be found at:=20
> http://forge.osor.eu/projects/jaspa/
> - The full JASPA documentation can be found at:=20
> http://jaspa.forge.osor.eu/. The online manual (the pdf version has=20
> more than 300 pages) includes the installation process from binaries=20
> and source, a tutorial and a complete reference of the JASPA commands.
> - Mailing list:=20
> http://lists.forge.osor.eu/mailman/listinfo/jaspa-users
> - JASPA is hosted on OSOR.EU at: http://www.osor.eu/projects/jaspa
>=20
>=20
> ************* text in spanish **************************
>=20
> Tras un a=F1o de desarrollo, queremos presentaros la versi=F3n 0.1RC1 =
de=20
> JASPA (JAva SPAtial). JASPA potencialmente implementa alrededor de 200 =

> funciones espaciales=A0 sobre cualquier base de datos relacional que=20
> soporte procedimientos almacenados en java. En esta primera versi=F3n=20
> JASPA soporta PostgreSQL y H2. Actualmente estamos trabajando para=20
> incorporar HSQLDB.
> JASPA tiene una funcionalidad muy similar a PostGIS 1.4, soportando=20
> predicados y operadores espaciales, arreglos de geometr=EDas, =
agregados=20
> espaciales, etc. JASPA est=E1 programado en java y es bastante f=E1cil =
de=20
> extender ampliando funcionalidades utilizando procedimientos=20
> almacenados en java. JASPA tiene una licencia GNU GPL.
>=20
> Este proyecto ha sido posible gracias a otros muchos proyectos de=20
> c=F3digo abierto. Adem=E1s de utilizar estos proyectos, sus=20
> correspondientes listas de correo nos han ayudado de forma r=E1pida y=20
> eficaz. El equipo de JASPA quiere mostrar su gratitud especialmente a:
>=20
> - PostGIS. Es el espejo en el que JASPA se ha mirado.
> - JTS (Java Topology Suite).=A0 Biblioteca ampliamente utilizada en=20
> JASPA y muchos otros proyectos de c=F3digo abierto, ofreciendo la=20
> posibilidad de realizar an=E1lisis espaciales.
> - GeoTools (biblioteca utilizada para las proyecciones y el soporte de =

> KML y los importadores shape).
> - PostgreSQL and PLJAVA (implementa procedimientos almacenados en java =

> para PostgreSQL)
> - H2 y H2Spatial (H2 es una base de datos especial desarrollada en=20
> Java, al inicio de JASPA H2 Spatial y Spatial Box ofrecieron ideas en=20
> la que se bas=F3 JASPA)
> - HSQLDB (base de datos java que posiblemente ser=E1 soportada por =
JASPA=20
> en la pr=F3xima versi=F3n)
> - gvSIG (SIG de escritorio con el que realmente deseamos que JASPA se=20
> pueda conectar)
>=20
> Los autores de este proyecto son:
>=20
> =A0 Jose C. Martinez-Llario. Developer and project director. (1)
> =A0 Marta Gonzalez-Alcaide. Tester and document builder.
> (1)
> =A0 (1)=A0 =A0 Deparment of Cartographic
> Engineering, Geodesy and Photogrammetry at La Universidad Politecnica=20
> de Valencia (Spain).
>=20
> =A0 Cualquier persona que quiera contribuir es bienvenida.
>=20
> JASPA Download:
>=20
> - Los binarios y el c=F3digo fuente se puede encontrar en:
> http://forge.osor.eu/projects/jaspa/
> - La documentaci=F3n complete de JASPA en: =
http://jaspa.forge.osor.eu/.=20
> El manual en l=EDnea (la versi=F3n pdf tiene m=E1s de 300 p=E1ginas) =
incluye=20
> el proceso de instalaci=F3n de forma detallada de los binarios y si se =

> quiere compilar el fuente, un tutorial y una gu=EDa de referencia de=20
> todos los comandos de JASPA.
> - Lista de distribuci=F3n (de momento s=F3lo en ingl=E9s):=20
> http://lists.forge.osor.eu/mailman/listinfo/jaspa-users
> - JASPA est=E1 almacenado en OSOR.EU at:=20
> http://www.osor.eu/projects/jaspa
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>=20


     =20
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users


_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users