CLONE - WMS Request Causes Geoserver Lat/Lon Bounding Box to Change

Description

The following request causes the Lat/Lon bounds of the requested layer to change:
http://myGeoserver/geoserver/wms/kml?&layers=gdd:agdd_50f

If I click "Compute from native bounds" and save the layer it will be fine until I make this request again at which point the bounds revert to the numbers they were before I clicked compute from native bounds.

agdd_50f is a time-series raster layer using imagemosaic. Imagemosaic looks to postgres to get the paths of daily geotifs which it then serves out. At this point I'm trying to figure out if it's a bug or a configuration issue.

Here's a stackexchange link where I first reported the issue in more detail with pictures:
http://gis.stackexchange.com/questions/199178/wms-request-causes-geoserver-lat-lon-bounding-box-to-change

I've also attached the before and after screenshots of what my lat long bounding box looks like.

Environment

Ubuntu 14.04.4 LTS

Activity

Show:
Andrea Aime
February 15, 2017, 11:48 AM

Mass closing all resolved issues not modified in the last 4 weeks

Andrea Aime
June 29, 2016, 7:51 PM

Please do not reopen, I have seen the other ticket update but I only have time to help people not having support contracts during the weekend. If you want to communicate use the user list, as the home page states, this is not a support forum. If this is a matter of urgency for you, consider looking here: http://geoserver.org/support/

Jeff Switzer
June 29, 2016, 7:17 PM

Hi Andrea,

Apologies if I reopened this ticket incorrectly - I wan't able to transition GEOS-7599's status to reopen so I cloned it into this ticket.

I tried your fix and still have the same issue after installing the following war:
geoserver-2.9.x-latest-war.zip 27-Jun-2016 06:58 59M

Thanks,
Jeff

Duplicate

Assignee

Andrea Aime

Reporter

Jeff Switzer

Fix versions

Affects versions