Hi everyone,
for the Geomajas project, we are looking into separating the Geometry
functionality into an independent project. In other words, I am talking
about a Geometry project for the Web. This code would be written in Java for
GWT and thus be available on Java backends as well as client
Hi Pieter,
this may not directly answer your question, but you could use the
existing JSTS library: https://github.com/bjornharrtell/jsts - this is
basically a port of the Java Topology Suite. The advantage would be
that you don't need a JS wrapper - you could use JTS on the server and
JSTS on
Thanks for the tip.
Basically I'm looking to make advantage of the GWT by having a single API
that I can use on both client and server.
We could indeed have 2 implementations (one using JTS one using JSTS), but
what I'm mainly looking for, is what model should the API ideally follow.
2011/7/13
There is a third model; the ISO19107 model that deals with a few more things;
it is however object oriented in nature
--
Jody Garnett
On Wednesday, 13 July 2011 at 6:36 PM, Pieter De Graef wrote:
Hi everyone,
for the Geomajas project, we are looking into separating the Geometry
Hi Jody,
that's the GeoApi specification no?
At first we would be using it on the GWT client we where hoping to also
include curves, as those can be directly drawn in SVG/VML. At a later stage
we could switch the backend to make use of it as well.
Jody, you have been looking into creating you
On Wed, Jul 13, 2011 at 1:36 AM, Pieter De Graef pied...@gmail.com wrote:
On one hand there is the Simple Feature Specification which is clearly an
Object Oriented model with the advantage that it is well known but is also
more difficult to implement the JavaScript wrapper around.
On the other
The MapServer team announces the release of MapServer versions 6.0.1,
5.6.7 and 4.10.7.
No new functionality has been added. 6.0.1 is a maintence release that
fixes a few issues including recently discovered security
vulnerabilities. The list of fixes since 6.0.0 is included at the end of
Pieter,
I agree with Jody.
I'm seeing increasing demand for clients that can utilise vector data
constrained by an application schema.
Europe is probably most advanced in this work with Inspire.
In Australia we have a lot of work currently at research and at implementation
stage trying to
