I checked the gwt-google-apis Maps API and there is no union for polygons (unfortunately). These things can get pretty ugly if you try to union polygons which don't intersect (I am not sure what you'll end up with, in JTS a MultiPolygon perhaps).
On you post "I think the big thing will be to make converting from JTS to GWT and vice-versa again very efficient." - did you mean Google Maps instead of GWT? If so, you have a point. What I have now is: pure Java JTS -> RPC -> client emulated JTS -> Google Maps geometries I could skip the client emulated JTS and instantiate wrappers for the Google Maps geometry classes like Polyline and Polygon, which would contain the Maps geometry and all other information JTS might need, instead of instantiating emulated JTS classes and then converting them. I would end up with: pure Java JTS -> RPC -> wrapped Google Maps geometries Thanks for the insight, I'll jot that down and look at it carefully on the weekend. Regards, Alexandre Pretyman On Sep 2, 1:57 pm, Eric B <[EMAIL PROTECTED]> wrote: > Ah, I see now. I thought the Google Maps Polygon had union > functionality already. Now your implementation looks like the way to > go. > > Thanks, > Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
