We did consider this option as well, but we don't think it will move the needle enough on download size and processing time. Problematic datasets have features with over 10K coordinates. Even if we dropped half the coordinate digits, this would still only reduce the response size to 50%. That's better, but not down to the "< 5%" improvement that the NONE or BBOX strategy would provide.
On Wed, Jun 10, 2015 at 2:09 PM, Rahkonen Jukka (MML) < [email protected]> wrote: > Hi, > > > I would add one more > > > 0. Reduce the precision of coordinates > > > > -Jukka Rahkonen- > ------------------------------ > Martin Davis 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. > > The #2 option of returning only BBOX would be ideal - is that possible? > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
