Thanks. That's pretty much what I expected to hear. The vendor option idea sounds good, particularly for the none|bbox options.
Agreed that the simplify option would also require a tolerance value. On further thought I'm not sure this would provide an effect that is all that useful, since it's so tied to view map scale. We'll have to weigh the cost of a code enhancement versus the pain of other options... On Wed, Jun 10, 2015 at 10:57 AM, Andrea Aime <[email protected]> wrote: > On Wed, Jun 10, 2015 at 7:41 PM, Martin Davis <[email protected]> wrote: > >> We're looking for ways to improve performance of Identify operations in a >> web map client (using OpenLayers). We are seeing poor performance due to >> the network latency of retrieving large GetFeatureInfo reponses. Is there >> any way to reduce the size of geometries returned in GetFeatureInfo >> responses? >> >> In order of decreasing preference, things that might work for us include: >> >> 1. simplify the geometry >> 2. provide only the bounding box rather than full geometry >> 3. eliminate the geometry entirely >> >> Does the WMS vendor parameter propertyName [1] allow removing the >> geometry from the response? In any case this isn't ideal for us, because >> we'd prefer to not have to specify the required properties explicitly. >> >> > Yeah, you can get whatever property you want, but you have to list > explicitly the ones you require > > >> The #2 option of returning only BBOX would be ideal - is that possible? >> > > Not without changing the code, I guess you could roll a new vendor option, > e.g., &geometry=none|bbox|standard > Simplifying would require yet another param to specify how much to > simplify it. > > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
