[postgis-users] extents of MultiLineStringZ

[Randy Horner]

Found that qgis and geoserver use st_estimated_extents by default and that postgis is aware of issue  http://trac.osgeo.org/postgis/ticket/2370
To solve, we just turned off estimated extents on geoserver store.  Sorry for the trouble.


From: postgis-users-bounces at lists.osgeo.org [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf Of Randy Horner
Sent: Tuesday, October 08, 2013 3:49 PM
To: postgis-users at lists.osgeo.org
Subject: [postgis-users] extents of MultiLineStringZ

We have a table in postgreSQL 9.3 postgis 2.1 of  MultiLineStringZ created with "geom geometry(MultiLineStringZ,3857)" When we add this table to QGIS 2.0 or serve it through geoserver, the extents (specifically the max x) is way off (Lat/Lon max X should be about -83.0 but it is 0.34.  Postgis st_extents returns the correct values and when we throw a query using QGIS (select * from gs_span) and then add the layer, the extents are correct.  Any thoughts anyone?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20131009/aa640ccd/attachment.html>