locationtech / locationtech/geomesa

Heatmap fails to take WMS1.3 axes switch into account

Open
#9,334 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.5k
Forks
446
Avg merge
1d 8h
Merged PRs (30d)
31

Description

Heatmap fails to take WMS1.3 axes switch into account

Using WMS 1.1.1 everything looks OK: the heatmap and the polygon layer in my example are well aligned.

http://localhost:8080/geoserver/geomesa/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&STYLES=polygon,heatmap&TIME=2017-08-01T11:00:00.000Z/2017-08-01T12:00:00.000Z&DPI=14&LAYERS=geomesa:zbez,geomesa:origins&SRS=EPSG:4326&WIDTH=1430&HEIGHT=768&BBOX=15.759201049804688,47.93609619140625,16.741104125976562,48.46343994140625

In WMS 1.3.0, the axes switch, i.e. the order of lat and lon has to be changed in the BBOX parameter. The heatmap vanishes:

http://localhost:8080/geoserver/geomesa/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&STYLES=polygon,heatmap&TIME=2017-08-01T11:00:00.000Z/2017-08-01T12:00:00.000Z&DPI=14&LAYERS=geomesa:zbez,geomesa:origins&SRS=EPSG:4326&WIDTH=1430&HEIGHT=768&BBOX=47.93609619140625,15.759201049804688,48.46343994140625,16.741104125976562

To see the heatmap, one has to send a request with the 1.1.1 axis order:

http://localhost:8080/geoserver/geomesa/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&STYLES=polygon,heatmap&TIME=2017-08-01T11:00:00.000Z/2017-08-01T12:00:00.000Z&DPI=14&LAYERS=geomesa:zbez,geomesa:origins&SRS=EPSG:4326&WIDTH=1430&HEIGHT=768&BBOX=15.759201049804688,47.93609619140625,16.741104125976562,48.46343994140625

Of course, now we only see the heatmap and the second layer is gone.

Update 1: The situation seems even more complex: "WMS 1.3.0 server and client code needs to be aware of the axis order for each SRS that it supports and to use the correct coordinate order in its BBOX"
Source: http://dmorissette.blogspot.co.at/2012/12/dont-upgrade-to-wms-130-unless-you.html


Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2054

Key: GEOMESA-2054
Type: Bug
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Anita Graser
Created: Fri, 6 Oct 2017 09:24:53 -0400
Updated: Fri, 6 Oct 2017 15:14:03 -0400
Affects Version(s): 2.0.0, 1.3.3
JIRA Labels: geoserver

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the supplied WMS 1.1.1 and 1.3.0 GetMap requests and compare the BBOX axis order with the rendered polygon and heatmap layers. Trace the GeoServer WMS heatmap handling from the request entry point; done means the heatmap and polygon remain aligned for the correct WMS 1.3.0 EPSG:4326 axis order.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
data-visualization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.