Here's another reason why reducing precision of responses on-the-fly would
be useful. It turn out the data as stored in EPGS:3005 essentially has 1 m
precision. However, we are requesting it reprojected to EPSG:3857. The
reprojection creates values using full double precision, which is output by
GeoServer. So in this case it is perfectly safe to round back to 1 m
precision.
We will explore requesting the data in the native CRS, since we can project
on the client-side. But it would be nice to be able to do this fully in
GeoServer.
On Tue, Oct 17, 2017 at 3:55 PM, Martin Davis <mtncl...@gmail.com> wrote:
> Is there any way in GeoServer to request that the precision of WFS output
> be reduced? (I.e. remove decimal places from the ordinates?).
>
> We have a large dataset which has far too much precision on the data.
> Removing unecessary decimal digits seems like it could significantly reduce
> WFS response size.
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
