[Geoserver-devel] [jira] (GEOS-6689) Issue with custom dimensions in WMS GetMap request

GeoServer GeoServer Developer
1

Kristine created an issue

GeoServer / BugGEOS-6689

Issue with custom dimensions in WMS GetMap request

Issue Type:

BugBug

Assignee:

Andrea Aime

Created:

24/Sep/14 5:57 PM

Priority:

MajorMajor

Reporter:

Kristine

After upgrading to Geoserver 2.5 from 2.2.4, we discovered custom dimensions are no longer being recognized in a WMS GetMap request.

i.e. Given an invalid analysis time (dim_analysis_time=INVALID_TIME) should return an error. Instead, the KVP is being ignored.
http://localhost:8080/geoserver/NAVGEM/wms?service=WMS&version=1.3.0&request=GetMap&EXCEPTIONS=application%2Fvnd.ogc.se_xml&CRS=CRS%3A84&layers=NAVGEM:global_360x181.air_temp.ht_sfc&bbox=-180.5,-90.5,180.5,90.5&time=2014-09-17T18:00:00.000Z&elevation=2.0&dim_analysis_time=INVALID_TIME&width=660&height=330&format=image/png

I tracked the error down to the WMS.java class in package org.geoserver.wms when it tries to pass down custom dimensions to the readParameters. It seems to be looking for ‘custom_dimension_ANALYSIS_TIME’ in the metadata map instead of ‘custom_dimension_analysis_time’.
Our metadata map is as follows:

{time=DimensionInfoImpl [attribute=null, endAttribute=null, enabled=true, units=null, unitSymbol=null, presentation=LIST, resolution=null], elevation=DimensionInfoImpl [attribute=null, endAttribute=null, enabled=true, units=meter, unitSymbol=m, presentation=LIST, resolution=null], custom_dimension_analysis_time=DimensionInfoImpl [attribute=null, endAttribute=null, enabled=true, units=ISO8601, unitSymbol=null, presentation=LIST, resolution=null]}

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)

Atlassian logo