WMS clients with EXTENT cut BBOX #4931

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants
@tbonfort
Member

tbonfort commented Aug 4, 2014

The following mapfile with data shows an issue when using a LAYER with CONNECTIONTYPE WMS and EXTENT or METADATA "ows_extent" parameters.

This wms layer call another layer inside the same mapfile (but this could be in another webservice). An EXTENT parameter is set up with the correct extent of the data (ogrinfo -so has been used for this).

The Extent parameter seems force MapServer to cut the bbox asked by the initial resquest:

I asked for

  • LAYERS=test
  • BBOX=591029.94832393,7034780.744266,601196.09341815,7044946.8893603
  • WIDTH=532&HEIGHT=532

full parameter for testing:

LAYERS=test&TRANSPARENT=true&VERSION=1.3&FORMAT=image%2Fpng&SERVICE=WMS&REQUEST=GetMap&STYLES=&CRS=EPSG%3A2154&BBOX=591029.94832393,7034780.744266,601196.09341815,7044946.8893603&WIDTH=532&HEIGHT=532&LAYERS=SXT_PHOTOANCIENNE_PICARDIE_BAIE_AUTHIE&TRANSPARENT=true&VERSION=1.3&FORMAT=image%2Fpng&SERVICE=WMS&REQUEST=GetMap&STYLES=&CRS=EPSG%3A2154&BBOX=591029.94832393,7034780.744266,601196.09341815,7044946.8893603&WIDTH=532&HEIGHT=532

MapServer WMS Client layer request:

  • LAYERS=emprise
  • BBOX=595000,7034780.744266,601196.09341819,7043000
  • HEIGHT=431&WIDTH=325

full parameter for testing:

LAYERS=emprise&REQUEST=GetMap&SERVICE=WMS&FORMAT=image/png&STYLES=&HEIGHT=431&VERSION=1.1.1&SRS=EPSG:2154&WIDTH=325&BBOX=595000,7034780.744266,601196.09341819,7043000&TRANSPARENT=TRUE&EXCEPTIONS=application/vnd.ogc.se_inimage

As you can see the size of the picture has been changed to HEIGHT=431&WIDTH=325

This change imply a shift in the final image sent to the final WMS client (see mapserv_notcorrect).

  • picture correct :
    mapserv_correct
  • picture not correct :
    mapserv_notcorrect

Shapefile + picture + mapfile = http://dl.free.fr/fANDyiIPP

@yjacolin

This comment has been minimized.

Show comment
Hide comment
@yjacolin

yjacolin Jun 12, 2014

Contributor

this issue occurs only with french projection (EPSG:2154).

Contributor

yjacolin commented Jun 12, 2014

this issue occurs only with french projection (EPSG:2154).

@tbonfort

This comment has been minimized.

Show comment
Hide comment
@tbonfort

tbonfort Aug 4, 2014

Member

Adding a PROCESSING RESAMPLE=nearest to the client wms layer fixes the issue and can be used as a temporary workaround. From some preliminary examination it would seem that mapserver does not create a worldfile for the returned image when not using this PROCESSING option.

Member

tbonfort commented Aug 4, 2014

Adding a PROCESSING RESAMPLE=nearest to the client wms layer fixes the issue and can be used as a temporary workaround. From some preliminary examination it would seem that mapserver does not create a worldfile for the returned image when not using this PROCESSING option.

@tbonfort

This comment has been minimized.

Show comment
Hide comment
@tbonfort

tbonfort Aug 26, 2014

Member

applied to master in 529e26e

Member

tbonfort commented Aug 26, 2014

applied to master in 529e26e

@tbonfort tbonfort closed this Aug 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment