Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

All good advice, but unfortunately not so easy to take advantage of in our environment. We allow all visible layers to be queried. This is why we prefer GetFeatureInfo to WFS, since it's sensitive to scale limits. The propertynames option is one way to do this, but we have hundreds of layers, so

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

> I would say take a leaf from ESRI REST services and add > ReturnGeometry=true/false to getFeatureInfo would be a good extension to > the WMS format. If you dont really need to execute against multiple > layers, then consider using WFS getFeature instead where you can specify > propertynames. ( M

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

I would say take a leaf from ESRI REST services and add ReturnGeometry=true/false to getFeatureInfo would be a good extension to the WMS format. If you dont really need to execute against multiple layers, then consider using WFS getFeature instead where you can specify propertynames. ( My maps

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

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 b

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

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 ne

Re: [Geoserver-users] geoserver 2.7 publish style

I believe it is set to false. Request Logging Filter org.geoserver.filters.LoggingFilter enabled false log-request-bodies false Dominique Bessette Software Engineer General Dynamics Information T

[Geoserver-users] GeoServer on Java 8 VM

I'm doing testing on how GeoServer runs on Java 8 (Although compiled with Java 7). As yet I'm not seeing any issues, including when I run the unit tests for the release profile. I'll be throwing some automated stress tests at it today. There's no particular reason to expect this to be problemati

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

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

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

On Wed, Jun 10, 2015 at 7:41 PM, 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 re

Re: [Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

I should add that it's probably not feasible to use FreeMarker templates, since we have a lot of layers defined, and in some cases we don't have the ability to modify the server configuration. Also, we also want to be able to retrieve the geometry via GetFeatureInfo in some situations. Ideally th

[Geoserver-users] Reduce Geometry size in GetFeatureInfo responses?

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 response