WMS Request Causes Geoserver Lat/Lon Bounding Box to Change


The following request causes the Lat/Lon bounds of the requested layer to change:

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:

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


Ubuntu 14.04.4 LTS


Andrea Aime
February 15, 2017, 11:48 AM

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

Andrea Aime
July 9, 2016, 11:40 AM

Closing again as I find no way to reproduce the problem. If you have a way to reproduce please let me know.

Andrea Aime
July 2, 2016, 3:29 PM

I've tried again using the build of the 27th from Ares, using this request: http://localhost:8080/geoserver/wms/kml?&layers=nurc:mosaic
Neither of the layer bounding boxes changed. I forced both manually to some other numbers, easy to remember, repeated the request, and again, they did not change.

Are you sure we are talking about the same build? Here are the information in "about geoserver" from my build:

Andrea Aime
June 29, 2016, 7:54 PM

I don't know how to reproduce, it's working for me, but I'll have another look

Jeff Switzer
June 27, 2016, 10:27 PM

Hi Andrea,

I gave it a shot, but still have the same issue after installing the following war:
geoserver-2.9.x-latest-war.zip 27-Jun-2016 06:58 59M




Andrea Aime


Jeff Switzer

Fix versions

Affects versions