Attached there is the controller I'm currently using. It requires that jts.jar be in your project's lib.
The controller receives a POST whose body is the wkt representation of the
(at most two) features, separated by a * (star).
I also perform snapping to 'clean' the geometries before the actual JTS
operation is attempted. You might not need that.
The operation param is extrapolated from the url via urlmapping :
"/jts/$operation"(controller: "jts") {
action = [GET: "exec", POST: "exec"]
}
So to perform a union you would POST to /jts/union , for a buffer
/jts/buffer and so on.
Happy hacking!
Umberto
On Thu, Aug 11, 2011 at 10:42 AM, Graham Gauld <
[email protected]> wrote:
> Umberto,
>
> Thanks for the reply. An example would be very useful.
>
> Graham.
>
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/buffering-example-using-OL-tp1829481p6675543.html
> Sent from the OpenLayers Users mailing list archive at Nabble.com.
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/openlayers-users
>
JtsController.groovy
Description: application/extension-groovy
_______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
