From johannespaul92 at gmail.com Thu Sep 10 07:58:33 2026 From: johannespaul92 at gmail.com (Johannes Paul) Date: Thu, 10 Sep 2026 16:58:33 +0200 Subject: [MapServer-dev] Mapcache bug in v1.14.1 WMS GetCapa Message-ID: Hello team, I think there is a bug introduced in mapcache v1.14.1++ when requesting GetCapabilities on a WMS service with regex or values types dimensions in the tileset. v1.14.0 is fine but v1.14.1 and v1.16.0 are raising Seg Fault on the WMS GetCapa request. Note that WMTS GetCapabilities request does not raise the error. I have open an issue: https://github.com/MapServer/mapcache/issues/379 Thanks Johannes -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmckenna at gatewaygeomatics.com Thu Sep 10 12:17:59 2026 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Thu, 10 Sep 2026 16:17:59 -0300 Subject: [MapServer-dev] Mapcache bug in v1.14.1 WMS GetCapa In-Reply-To: References: Message-ID: <3b9f65ba-0a1d-4da0-b881-303e6b547158@gatewaygeomatics.com> Hi Johannes, Thanks for the report. I can reproduce locally. Please test the pull request at https://github.com/MapServer/mapcache/pull/380 and let me know. (I am now able to see those default values for Dimension, for type="values" and type="regex", through a GetCapabilities request). thanks, -jeff On 2026-09-10 11:58 a.m., Johannes Paul via MapServer-dev wrote: > Hello team, > I think there is a bug introduced in mapcache v1.14.1++ when requesting > GetCapabilities on a WMS service with regex or values types dimensions > in the tileset. > v1.14.0 is fine but v1.14.1 and v1.16.0 are raising Seg Fault on the WMS > GetCapa request. Note that WMTS GetCapabilities request does not raise > the error. > I have open an issue: > https://github.com/MapServer/mapcache/issues/379 MapServer/mapcache/issues/379> > Thanks > Johannes > > From szekerest at gmail.com Tue Sep 15 02:15:33 2026 From: szekerest at gmail.com (Tamas Szekeres) Date: Tue, 15 Sep 2026 11:15:33 +0200 Subject: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement Message-ID: Dear PSC, I would like to motion to adopt RFC-142: Geodesic Scalebar Measurement. Based on the discussion of this RFC I've simplified the solution by removing the MEASURE parameter (therefore the RFC has been renamed) and that the result represents horizontal local scale at the map center (not bound to the actual scalebar location). According to Even's suggestion, if the project has a CRS we use the geodesic scale, otherwise fallback to cartesian method. The modified RFC can be found here: https://mapserver.org/development/rfc/ms-rfc-142.html The corresponding PR with the suggested changes: https://github.com/MapServer/MapServer/pull/7507/changes Starting with my +1, Tamas -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmckenna at gatewaygeomatics.com Tue Sep 15 06:40:36 2026 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Tue, 15 Sep 2026 10:40:36 -0300 Subject: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement In-Reply-To: References: Message-ID: Hi Tamas, Thanks for your efforts on this. I am a +1. However, my only concern is which release this should be included in - my gut feeling is that this should be included in the MapServer 9.0.0 release. It seems like quite a drastic change (but a big improvement) for a minor release. This might also push us to release 9.0.0 sooner than later. Thanks, -jeff On 2026-09-15 6:15 a.m., Tamas Szekeres via MapServer-dev wrote: > Dear PSC, > > I would like to motion to adoptRFC-142: Geodesic Scalebar > Measurement.Based on the discussion of this RFC lists.osgeo.org/pipermail/mapserver-dev/2026-May/017361.html> I've > simplified the solution by removing the MEASURE parameter (therefore the > RFC has been renamed) and that the result represents horizontal local > scale at the map center (not bound to the actual scalebar location). > According to Even's suggestion, if the project has a CRS we use the > geodesic scale, otherwise fallback to cartesian method. > > The modified RFC can be found here: https://mapserver.org/development/ > rfc/ms-rfc-142.html > > The corresponding PR with the suggested changes: https://github.com/ > MapServer/MapServer/pull/7507/changes MapServer/pull/7507/changes> > > Starting with my +1, > > Tamas > From szekerest at gmail.com Tue Sep 15 06:43:35 2026 From: szekerest at gmail.com (Tamas Szekeres) Date: Tue, 15 Sep 2026 15:43:35 +0200 Subject: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement In-Reply-To: References: Message-ID: Hi Jeff, Thank you, I'm fine with that plan. Best regards, Tamas Jeff McKenna via MapServer-dev ezt ?rta (id?pont: 2026. szept. 15., K, 15:40): > Hi Tamas, > > Thanks for your efforts on this. I am a +1. However, my only concern is > which release this should be included in - my gut feeling is that this > should be included in the MapServer 9.0.0 release. It seems like quite > a drastic change (but a big improvement) for a minor release. > > This might also push us to release 9.0.0 sooner than later. > > Thanks, > > -jeff > > > > > On 2026-09-15 6:15 a.m., Tamas Szekeres via MapServer-dev wrote: > > Dear PSC, > > > > I would like to motion to adoptRFC-142: Geodesic Scalebar > > Measurement.Based on the discussion of this RFC > lists.osgeo.org/pipermail/mapserver-dev/2026-May/017361.html> I've > > simplified the solution by removing the MEASURE parameter (therefore the > > RFC has been renamed) and that the result represents horizontal local > > scale at the map center (not bound to the actual scalebar location). > > According to Even's suggestion, if the project has a CRS we use the > > geodesic scale, otherwise fallback to cartesian method. > > > > The modified RFC can be found here: https://mapserver.org/development/ > > rfc/ms-rfc-142.html < > https://mapserver.org/development/rfc/ms-rfc-142.html> > > > > The corresponding PR with the suggested changes: https://github.com/ > > MapServer/MapServer/pull/7507/changes > MapServer/pull/7507/changes> > > > > Starting with my +1, > > > > Tamas > > > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomkralidis at gmail.com Tue Sep 15 07:01:08 2026 From: tomkralidis at gmail.com (Tom Kralidis) Date: Tue, 15 Sep 2026 10:01:08 -0400 Subject: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement In-Reply-To: References: Message-ID: +1 (targeting for 9.0.0). ..Tom On Tue, Sep 15, 2026 at 9:43?AM Tamas Szekeres via MapServer-dev wrote: > > Hi Jeff, > > Thank you, I'm fine with that plan. > > Best regards, > > Tamas > > > Jeff McKenna via MapServer-dev ezt ?rta (id?pont: 2026. szept. 15., K, 15:40): >> >> Hi Tamas, >> >> Thanks for your efforts on this. I am a +1. However, my only concern is >> which release this should be included in - my gut feeling is that this >> should be included in the MapServer 9.0.0 release. It seems like quite >> a drastic change (but a big improvement) for a minor release. >> >> This might also push us to release 9.0.0 sooner than later. >> >> Thanks, >> >> -jeff >> >> >> >> >> On 2026-09-15 6:15 a.m., Tamas Szekeres via MapServer-dev wrote: >> > Dear PSC, >> > >> > I would like to motion to adoptRFC-142: Geodesic Scalebar >> > Measurement.Based on the discussion of this RFC > > lists.osgeo.org/pipermail/mapserver-dev/2026-May/017361.html> I've >> > simplified the solution by removing the MEASURE parameter (therefore the >> > RFC has been renamed) and that the result represents horizontal local >> > scale at the map center (not bound to the actual scalebar location). >> > According to Even's suggestion, if the project has a CRS we use the >> > geodesic scale, otherwise fallback to cartesian method. >> > >> > The modified RFC can be found here: https://mapserver.org/development/ >> > rfc/ms-rfc-142.html >> > >> > The corresponding PR with the suggested changes: https://github.com/ >> > MapServer/MapServer/pull/7507/changes > > MapServer/pull/7507/changes> >> > >> > Starting with my +1, >> > >> > Tamas >> > >> _______________________________________________ >> MapServer-dev mailing list >> MapServer-dev at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev From sethg at geographika.co.uk Tue Sep 15 22:57:18 2026 From: sethg at geographika.co.uk (Seth G) Date: Wed, 16 Sep 2026 07:57:18 +0200 Subject: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement In-Reply-To: References: Message-ID: <48993ace-309f-476b-b72a-c636b79ff316@app.fastmail.com> +1 thanks Tamas. (as an aside, QGIS also seems to default to centre of the map for scale: https://docs.qgis.org/3.44/en/docs/user_manual/introduction/qgis_configuration.html#scale-calculation-method) Seth On Tue, Sep 15, 2026, at 11:15 AM, Tamas Szekeres via MapServer-dev wrote: > Dear PSC, > > I would like to motion to adopt RFC-142: Geodesic Scalebar Measurement. Based on the discussion of this RFC I've simplified the solution by removing the MEASURE parameter (therefore the RFC has been renamed) and that the result represents horizontal local scale at the map center (not bound to the actual scalebar location). According to Even's suggestion, if the project has a CRS we use the geodesic scale, otherwise fallback to cartesian method. > > The modified RFC can be found here: https://mapserver.org/development/rfc/ms-rfc-142.html > > The corresponding PR with the suggested changes: https://github.com/MapServer/MapServer/pull/7507/changes > > Starting with my +1, > > Tamas > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.smith.erdc at gmail.com Wed Sep 16 03:44:36 2026 From: michael.smith.erdc at gmail.com (Michael Smith) Date: Wed, 16 Sep 2026 06:44:36 -0400 Subject: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement In-Reply-To: <48993ace-309f-476b-b72a-c636b79ff316@app.fastmail.com> References: <48993ace-309f-476b-b72a-c636b79ff316@app.fastmail.com> Message-ID: <0DD33E7D-C819-47A2-9D0D-42844E29B504@gmail.com> +1 Mike From: MapServer-dev on behalf of Seth G via MapServer-dev Reply-To: Seth G Date: Wednesday, September 16, 2026 at 1:57?AM To: Tamas Szekeres , MapServer Devs Subject: Re: [MapServer-dev] Motion: adopt RFC-142: Geodesic Scalebar Measurement +1 thanks Tamas. (as an aside, QGIS also seems to default to centre of the map for scale: https://docs.qgis.org/3.44/en/docs/user_manual/introduction/qgis_configuration.html#scale-calculation-method) Seth On Tue, Sep 15, 2026, at 11:15 AM, Tamas Szekeres via MapServer-dev wrote: Dear PSC, I would like to motion to adopt RFC-142: Geodesic Scalebar Measurement. Based on the discussion of this RFC I've simplified the solution by removing the MEASURE parameter (therefore the RFC has been renamed) and that the result represents horizontal local scale at the map center (not bound to the actual scalebar location). According to Even's suggestion, if the project has a CRS we use the geodesic scale, otherwise fallback to cartesian method. The modified RFC can be found here: https://mapserver.org/development/rfc/ms-rfc-142.html The corresponding PR with the suggested changes: https://github.com/MapServer/MapServer/pull/7507/changes Starting with my +1, Tamas _______________________________________________ MapServer-dev mailing list MapServer-dev at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-dev _______________________________________________ MapServer-dev mailing list MapServer-dev at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: