Opened 14 years ago

Closed 14 years ago

#3568 closed defect (invalid)

Swapped X and Y in BoundingBox WMS GetCapabilities

Reported by: niccolo Owned by: mapserverbugs
Priority: normal Milestone:
Component: WMS Server Version: 5.6
Severity: normal Keywords:
Cc:

Description

This is an extract of a GetCapabilities:

    <EX_GeographicBoundingBox>
        <westBoundLongitude>9.6426</westBoundLongitude>
        <eastBoundLongitude>12.4589</eastBoundLongitude>
        <southBoundLatitude>42.2079</southBoundLatitude>
        <northBoundLatitude>44.4951</northBoundLatitude>
    </EX_GeographicBoundingBox>
        <BoundingBox CRS="EPSG:4326"
                    minx="42.2079" miny="9.6426" maxx="44.4951" maxy="12.4589" />

As you can see X and Y are swapped in the last line, both min and max.

Here it is the mapfiles that produces the error with MapServer 5.6.3:

MAP
  NAME "Test"
  PROJECTION
    'init=epsg:3003'
  END
  UNITS meters
  EXTENT 1580673.000000 4877151.977515 1617927.000000 4911408.022485
  WEB
    METADATA
      'ows_title'           'Test'
      'ows_srs'             'EPSG:3003'
    END
  END

LAYER
  NAME 'idrst10k'
  TYPE RASTER
  STATUS ON
  CONNECTION 'http://web.rete.toscana.it:80/sgrwms/com.rt.wms.RTmap/_rt_wms_wgs84?'
  CONNECTIONTYPE WMS
  PROJECTION
    'init=epsg:4326'
  END
  EXTENT 9.642603853 42.2078509685 12.4589466172 44.4951035402
  METADATA
    'wms_title'           'idrst10k'
    'wms_abstract'        'idrst10k da Geoscopio'
    'wms_srs'             'EPSG:4326'
    #'wms_extent'          '9.642603853 42.2078509685 12.4589466172 44.4951035402'
    'wms_name'            'idrst10k'
    'wms_server_version'  '1.1.1'
    'wms_format'          'image/jpeg'
  END
END

END

Change History (2)

comment:1 by assefa, 14 years ago

This is probably a wms 1.3.0 request. Axes are swapped as explained in

http://mapserver.org/ogc/wms_server.html#wms-1-3-0-support

If that is the case, please close the bug. Thanks

comment:2 by niccolo, 14 years ago

Resolution: invalid
Status: newclosed

You are right, if I request GetCapabilities with VERSION=1.1.1, I get the axis not swapped.

I really don't understand the rationale behind WMS 1.3.0 and axes swapping, but I understand that this is not a MapServer bug, so I close it.

Note: See TracTickets for help on using tickets.