From jmckenna at gatewaygeomatics.com Wed Dec 3 11:25:32 2025 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Wed, 3 Dec 2025 15:25:32 -0400 Subject: [MapServer-users] 8.6.0 released! Message-ID: The MapServer team is thrilled to announce the release of MapServer 8.6.0 Details of the new features, changelog, migration instructions, and download links can be found on the dedicated announcement page at https://mapserver.org/development/announce/8-6.html . Also included is an updated 1,155 page PDF of documentation, and of course an updated & maintained (so important) demo server of various OGC instances at https://demo.mapserver.org Direct source download: - https://download.osgeo.org/mapserver/mapserver-8.6.0.tar.gz - https://download.osgeo.org/mapserver/mapserver-8.6.0.zip Thanks for all of your feedback and passion for MapServer. -- The MapServer Team From mniemyjski at cloudferro.com Fri Dec 12 03:23:35 2025 From: mniemyjski at cloudferro.com (Marcin Niemyjski) Date: Fri, 12 Dec 2025 11:23:35 +0000 Subject: [MapServer-users] Subject: GetFeatureInfo works only for first record in FlatGeobuf TILEINDEX (MapServer 8.6.0-beta2) Message-ID: Hi all, MY MAPFILE: https://pastebin.com/6A98L6V7 I am running into an issue with WMS GetFeatureInfo when using FlatGeobuf (FGB) as a TILEINDEX source in MapServer. The problem appears to be related to how MapServer / OGR handles multiple records inside a FlatGeobuf tile index. Environment: - MapServer: 8.6.0-beta2 - GDAL: 3.12.0 - PROJ: 9.7.0 - OS: Debian Bookworm (Docker) TileIndex structure: I am using FlatGeobuf as a tile index, with a schema similar to a classic shapefile tile index. The TILEITEM column is called "location" and contains both the file path and the layer name, separated by a comma: location data/CLMS_UA_LCU_S2021_V025ha_BA001L1_SARAJEVO_03035_V01_R01_20250523.fgb,CLMS_UA_LCU_S2021_V025ha_BA001L1_SARAJEVO_03035_V01_R01_20250523 data/CLMS_UA_LCU_S2021_V025ha_AT001L3_WIEN_03035_V01_R01_20250418.fgb,CLMS_UA_LCU_S2021_V025ha_AT001L3_WIEN_03035_V01_R01_20250418 Each referenced FlatGeobuf file contains exactly one vector layer, and the layer name matches the name provided after the comma in the tile index. Problem description: - I have vector layers configured in MapServer using CONNECTIONTYPE OGR with TILEINDEX pointing to an FGB file. - The layers are only visible at large scales (MAXSCALEDENOM 300000), where vector data is queried. - When issuing a WMS GetFeatureInfo request at an appropriate zoom level: - GetFeatureInfo works correctly for features coming from the FIRST record in the tile index. - Features coming from any subsequent tile index record never return GetFeatureInfo results. - The request itself is valid (correct bbox, x/y, tolerance, scale), and rendering works correctly for all tiles ? only GetFeatureInfo is affected. Additional observations: - Reordering records inside the FlatGeobuf tile index changes which dataset GetFeatureInfo works for. Whichever record is first starts working; the others stop working. - If I bypass the tile index and connect directly to a single FlatGeobuf file using: CONNECTION "path/to/file.fgb" DATA "layer_name" then GetFeatureInfo works as expected. - To further isolate the issue, I created a separate MapServer layer only for the Vienna dataset (the dataset affected by the problem), with an explicit CONNECTION and DATA pointing directly to the FlatGeobuf file and its internal layer name (no TILEINDEX involved). - In this setup, with the layer name explicitly defined, GetFeatureInfo works correctly and consistently for Vienna features. - This strongly suggests that the problem is not related to the data itself, styles, templates, or scale settings, but specifically to the use of FlatGeobuf as a TILEINDEX source during GetFeatureInfo processing. - It appears that during GetFeatureInfo MapServer / OGR only evaluates the first tile index record and does not properly iterate over or reset OGR datasets for subsequent records, especially when different internal layer names are involved. My suspicion is that this may be a limitation or bug in how FlatGeobuf is handled as a TILEINDEX source, particularly for GetFeatureInfo requests. Has anyone encountered similar behaviour when using FlatGeobuf tile indexes with GetFeatureInfo, or can confirm whether this is a known limitation in MapServer or GDAL/OGR? Thanks, Marcin -------------- next part -------------- An HTML attachment was scrubbed... URL: From sethg at geographika.co.uk Fri Dec 19 05:13:51 2025 From: sethg at geographika.co.uk (Seth G) Date: Fri, 19 Dec 2025 14:13:51 +0100 Subject: [MapServer-users] mappyfile v.1.10 released Message-ID: <38f81675-e219-4fde-b9c6-8b42176d30f2@app.fastmail.com> Hi all, mappyfile v1.1.0 was released today. mappyfile is Python parser for working with MapServer MapFiles, and is an OSGeo Community Project. The new version supports reading, writing, validating, and formatting MapServer CONFIG files. See release notes at https://mappyfile.readthedocs.io/en/latest/HISTORY.html. There is a summary presentation from FOSS4G Europe 2024 online at https://geographika.github.io/mappyfile-foss4geurope-2024/ that provides an overview of the project. Code: https://github.com/geographika/mappyfile PyPI: https://pypi.org/project/mappyfile/ Docs: https://mappyfile.readthedocs.io/en/latest/index.html Seth -- web:https://geographika.net & https://mapserverstudio.net mastodon: @geographika at mastodon.social From atlantageek at gmail.com Wed Dec 24 08:59:21 2025 From: atlantageek at gmail.com (Atlanta Geek) Date: Wed, 24 Dec 2025 11:59:21 -0500 Subject: [MapServer-users] docker image Message-ID: I'm trying to run the latest docker image and get complaints that its trying to do a sudo command in the docker file. Anyone have the same issue. Which mapserver docker image is best. Im running on a mac fyi -- http://www.atlantageek.com -------------- next part -------------- An HTML attachment was scrubbed... URL: