|
|
Jeff Switzer created an issue |
|
CLONE - WMS Request Causes Geoserver Lat/Lon Bounding Box to Change |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.8.0, 2.8.4 |
|
Assignee: |
|
|
Attachments: |
snip1.JPG, snip2.JPG |
|
Components: |
image mosaic |
|
Created: |
29/Jun/16 9:11 PM |
|
Environment: |
Ubuntu 14.04.4 LTS |
|
Fix Versions: |
2.9.1, 2.8.5 |
|
Labels: |
geoserver wms |
|
Priority: |
|
|
Reporter: |
|
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. |
|
|
|
This message was sent by Atlassian JIRA (v1000.110.0#100004-sha1:4011b0e) |
|
|