citizens

Big ole geometries

Discussion created by citizens on Jul 10, 2011
Latest reply on Jul 11, 2011 by citizens
I have a web app that exposes many very intricate geometries, i.e. the actual coastline of Florida, by county. Many, many vertices.

The user can essentially copy the geometries in the application and modify them as he sees fit, buffer them as he sees fit and then submit the resulting geometry to conduct a spatial query.

The user (yes the app is for 1 person, nice to be Senior Mgmt) requested the coastline be provided as it is. The problem I keep seeing is that with the user using this complex geometry the browser has to send geometries back to the server that have upwards of 10,000 vertices.

I'm sending the geometry to the server as a "feature set", is there a better way to do this?

Perhaps a way to compress it and then uncompress it?

I've told him to use simplier geometries, but again he's Senior Mgmt...I'm just a GIS Manager.

Thanks for any thoughts.

Outcomes