[Geoserver-devel] [JIRA] (GEOS-8542) Since 2.10.3 attached GeoTIFFs fail to render in WMS queries

Matt Fisher created an issue

GeoServer / BugGEOS-8542

Since 2.10.3 attached GeoTIFFs fail to render in WMS queries

Issue Type:

BugBug

Affects Versions:

2.10.3, 2.10.4, 2.10.5, 2.12.0, 2.12.1

Assignee:

Unassigned

Attachments:

20100101_N_20100101_concentration_v3.0.tif, 20100101_S_20100101_concentration_v3.0.tif

Created:

22/Jan/18 6:31 PM

Environment:

Ubuntu Linux

Priority:

HighHigh

Reporter:

Matt Fisher

Mailing list post for reference:

https://sourceforge.net/p/geoserver/mailman/message/36192759/

Hello,

My team recently upgraded our GeoServer install and found that
some of our ImageMosaic layers started displaying as “blank” or
all-white. GetFeatureInfo requests return the correct values from 0-255,
but any GetMap request over the same area returns a white image.

I believe this is a bug, as it only manifests in certain versions of
GeoServer. We were able to reproduce this issue with a fresh GeoServer
config with a single-GeoTIFF store using the following files:

20100101_N_20100101_concentration_v3.0.tif (attached)

  • Works in any version of geoserver I tested (>= 2.9)

20100101_S_20100101_concentration_v3.0.tif (attached)

  • Works in any version of geoserver I tested up to 2.10.2. WMS requests return
    a white image in geoserver >=2.10.3

I believe this issue can be reproduced only in >=2.10.3 by the following
steps:

  1. For each 20100101_S_20100101_concentration_v3.0.tif,
    20100101_N_20100101_concentration_v3.0.tif:

  2. Create a GeoTIFF store from the file

  3. Publish a layer from the new store

  4. View OpenLayers layer preview for the new layer

North should display grayscale data, South should be a white, empty
image. User should be able to click anywhere on either image and get
correct floating point values from 0-255 via GetFeatureInfo requests.
When requesting a GeoTIFF, the south image displays all-white while the
north image displays the correct data.

Example requests and results in geoserver >=2.10.3 (everything works as
expected in prior versions):

wms?service=WMS&version=1.1.0&request=GetMap&layers=NSIDC:20100101_S_20100101_concentration_v3.0&styles=&bbox=-3950000.0,-3950000.0,3950000.0,4350000.0&width=730&height=768&srs=EPSG:3412&format=application/openlayers

-> Blank image

wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&FORMAT=image%2Fjpeg&TRANSPARENT=true&QUERY_LAYERS=NSIDC%3A20100101_S_20100101_concentration_v3.0&STYLES&LAYERS=NSIDC%3A20100101_S_20100101_concentration_v3.0&INFO_FORMAT=text%2Fhtml&FEATURE_COUNT=50&X=50&Y=50&SRS=EPSG%3A3412&WIDTH=101&HEIGHT=101&BBOX=-2883031.164314732%2C-1553904.9326306523%2C-908887.7907839662%2C420238.4409001132

-> Value: 54.400001525878906

wms?service=WMS&version=1.1.0&request=GetMap&layers=NSIDC:20100101_N_20100101_concentration_v3.0&styles=&bbox=-3850000.0,-5350000.0,3750000.0,5850000.0&width=521&height=768&srs=EPSG:3411&format=application/openlayers

-> Fully rendered sea concentration imagery

WCS requests for the same data show no issues in 2.10.3.

Additionally, one of my colleagues reported another GeoTIFF issue that manifested at the exact same version that we speculate may be related:

http://osgeo-org.1560.x6.nabble.com/Offset-wrong-bounding-box-td5325092.html

Thanks!

Matt Fisher

National Snow and Ice Data Center

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS


This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100076-sha1:948d923)

Atlassian logo