[MapServer-users] WMS with a GPKG-based layer : different responses, dependending on version (1.1.1 vs 1.3.0)

[Rahkonen Jukka]

Hi,

Do you have any possibility to make a complete re-producible test case with a small raster GeoPackage and a minimal mapfile? I know I could do such myself, but even I am curious to try what happens I am also somewhat lazy. And because I am just another MapServer user I do not feel hard pressure.

-Jukka Rahkonen-

________________________________________
Lähettäjä: Philippe Ghesquiere <philippe.ghesquiere at airbus.com>
Lähetetty: Perjantai 27. helmikuuta 2026 10.27
Vastaanottaja: Rahkonen Jukka <jukka.rahkonen at maanmittauslaitos.fi>
Kopio: MapServer Users <mapserver-users at lists.osgeo.org>; Sylvain Pomeon <sylvain.pomeon at airbus.com>
Aihe: Re: [MapServer-users] WMS with a GPKG-based layer : different responses, dependending on version (1.1.1 vs 1.3.0)

Hi all,I ran a few more tests.As Jukka advised me, the LAYER-DATA points directly to the GPKG file (no use of Mapcache)1) Current environmentMapserver 8.2.0, PROJ 9.3,GDAL 3.8I tested several PROJECTION definitions, without modifying the request urls (V1.1.1 and V1.3.0)"init=epsg:4326" (my default parameter) : V1.1.1=OK, V1.3.0=NOK"init=EPSG:4326" (uppercase) : both WMS version give the wrong image"init=ogc:crs84" only for V1.3.0 (and any combination of upper/lowercase) : msProcessProjection(): Projection library error. proj error "Invalid value for an argument" for "init=OGC:CRS84"This is weird, since this CRS is part of the list given by : projinfo --list-crs"init=epsg:4326" and "epsgaxis=ne" (or any other added parameter) :  both WMS version give the wrong image2) Mapserver newer versionSome issues concerning epsg:4326 and weird results have been opened: Mapserver: #7019, #7074, #7121.I tested the following environment:Mapserver 8.4.1, PROJ 9.3,GDAL 3.8with the same results.3) Questionsupgrading to PROG 9.5 : could it give better results ?Mapserver V8.4.1 : is it an issue with mapserver? Should I open a new issue ?Philippe On Wed, Feb 25, 2026 at 9:41 AM Philippe Ghesquiere <philippe.ghesquiere at airbus.com> wrote:Hi Jukka,I modified the mapserver mapfile to point directly to the GPKG file.The result is exactly the same : with V1.3.0 request, mapserver is extracting data from the 'wrong' zoom level.Is there anything else I could check or try ?PhilippeOn Fri, Feb 20, 2026 at 8:55 AM Philippe Ghesquiere <philippe.ghesquiere at airbus.com> wrote:Hi Jukka,Thanks for taking your time on the problem.Both Mapserver and Mapcache are running on the same serveur.I am out of the office for a few days with no access to my development platform.I will give it a try when I am back and I will let you know.PhilippeOn Thu, Feb 19, 2026 at 7:32 PM Rahkonen Jukka <jukka.rahkonen at maanmittauslaitos.fi> wrote:Hi,Thank you very much for the information, now I start to understand. It seems that you have done everything right. Maybe it is GDAL who thinks that the closest resolution comes from another zoom level when the axis swap happens. I am not sure yet how to test that, but I am still thinking. I suppose that your Mapserver and MapCache are not on the same machine, otherwise you could use osm_4326.gpkg directly in the mapfile LAYER-DATA without going through MapCache and WMTS. And you don't want to serve WMS from MapCache, even it should be able to do it with both versions https://mapserver.org/mapcache/services.html#ogc-wms-service. Is that right?-Jukka Rahkonen-________________________________________Lähettäjä: Philippe Ghesquiere <philippe.ghesquiere at airbus.com>Lähetetty: Torstai 19. helmikuuta 2026 19.04Vastaanottaja: Rahkonen Jukka <jukka.rahkonen at maanmittauslaitos.fi>Kopio: MapServer Users <mapserver-users at lists.osgeo.org>Aihe: Fwd: [MapServer-users] WMS with a GPKG-based layer : different responses, dependending on version (1.1.1 vs 1.3.0)Hi Jukka,Our GPKG (osm_4326.gpkg) contains OSM tiles, with an InspireCRS84Quad tiling scheme. The pyramid goes from Z=0 down to Z=13.In the Mapfile, the layer's DATA is coming from the MapCache WMTS layer (i.e. the GPKG file).Mapfile excerpt :LAYER   NAME "osm_4326"   METADATA     "wms_title" "OpenStreet Map WMS"   END   TYPE RASTER   DATA "baselayers_gdal_osm.xml"   PROJECTION      "init=epsg:4326"   ENDENDbaselayers_gdal_osm.xml content:<GDAL_WMTS>   <GetCapabilitiesUrl>http://localhost/mapcache/wmts?request=GetCapabilities&SERVICE=WMTS</GetCapabilitiesUrl>   <Layer>osm_4326</Layer>   <Style>default</Style>   <TileMatrixSet>WGS84</TileMatrixSet>   <DataWindow>      <UpperLeftX>-180.0</UpperLeftX>      <UpperLeftY>90.0</UpperLeftY>      <LowerRightX>180.0</LowerRightX>      <LowerRightY>-90.0</LowerRightY>   </DataWindow>   <BandsCount>4</BandsCount>   <Cache/>   <UnsafeSSL>true</UnsafeSSL>   <ZeroBlockHttpCodes>204,404</ZeroBlockHttpCodes>   <ZeroBlockOnServerException>true</ZeroBlockOnServerException></GDAL_WMTS>WMTS cache definition:<cache name="osm_cache_4326" type="sqlite3">    <dbfile>/xxx/osm_4326.gpkg</dbfile>    <queries>       <get>select tile_data from tiles where tile_column=:x and tile_row=:inv_y and zoom_level=:z</get>    </queries></cache><tileset name="osm_4326">    <cache>osm_cache_4326</cache>    <grid restricted_extent="-180.0,-90.0,180.0,90.0">WGS84</grid>    <format>PNG</format>    <metadata>       <title>OSM (Fond de carte) WGS84</title>    </metadata></tileset>PhilippeThe information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.