<div dir="ltr"><div dir="ltr">Hi Jukka,<div><br></div><div>Thanks for taking your time on the problem.</div><div><br></div><div>Both Mapserver and Mapcache are running on the same serveur.</div><div><br></div><div>I am out of the office for a few days with no access to my development platform.</div><div>I will give it a try when I am back and I will let you know.</div><div><br></div><div>Philippe</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Feb 19, 2026 at 7:32 PM Rahkonen Jukka <<a href="mailto:jukka.rahkonen@maanmittauslaitos.fi">jukka.rahkonen@maanmittauslaitos.fi</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
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. <br>
<br>
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 <a href="https://mapserver.org/mapcache/services.html#ogc-wms-service" rel="noreferrer" target="_blank">https://mapserver.org/mapcache/services.html#ogc-wms-service</a>. Is that right?<br>
<br>
-Jukka Rahkonen-<br>
________________________________________<br>
Lähettäjä: Philippe Ghesquiere <<a href="mailto:philippe.ghesquiere@airbus.com" target="_blank">philippe.ghesquiere@airbus.com</a>><br>
Lähetetty: Torstai 19. helmikuuta 2026 19.04<br>
Vastaanottaja: Rahkonen Jukka <<a href="mailto:jukka.rahkonen@maanmittauslaitos.fi" target="_blank">jukka.rahkonen@maanmittauslaitos.fi</a>><br>
Kopio: MapServer Users <<a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a>><br>
Aihe: Fwd: [MapServer-users] WMS with a GPKG-based layer : different responses, dependending on version (1.1.1 vs 1.3.0)<br>
<br>
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><a href="http://localhost/mapcache/wmts?request=GetCapabilities&SERVICE=WMTS" rel="noreferrer" target="_blank">http://localhost/mapcache/wmts?request=GetCapabilities&SERVICE=WMTS</a></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.</blockquote></div></div>
<font style="font-size: 9px;">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.<br>If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.<br>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.<br>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.</font>