From sethg at geographika.co.uk Fri Aug 12 02:25:17 2022 From: sethg at geographika.co.uk (Seth G) Date: Fri, 12 Aug 2022 11:25:17 +0200 Subject: [mapserver-dev] Heads-up: 8.0 version branched In-Reply-To: References: <28db659f-92e2-c916-f62e-a2966461ba8c@gatewaygeomatics.com> <1266c6f5-7069-fded-fcb9-8f9e04d645c5@gatewaygeomatics.com> <8848c6aa-607e-96ca-9e39-f7ccc4588414@gatewaygeomatics.com> <6ea0da50-5ddc-aecb-928c-4a7ad7aaac82@gatewaygeomatics.com> Message-ID: Hi, We need to provide an update to OSGeo on the MapServer project status for the AGM slides. It would be good to announce the 8.0 release, or at least have a release candidate out. Looking at remaining issues in https://github.com/MapServer/MapServer/milestone/54 I don't think any are blockers to proceeding to a release candidate (many issues are several years old so not particular to 8.0)? Seth -- web:https://geographika.net twitter: @geographika On Tue, Jul 26, 2022, at 4:43 PM, Jeff McKenna wrote: > Hi Seth, > > I'm planning for a beta2 on this Friday. I was also thinking of the > FOSS4G deadline. If you all have changes to make (or tickets/pull > requests to give feedback in or test) please do so in the next few days. > > Thanks all :) > > -jeff > > > > > On 2022-07-26 11:38 a.m., Seth G wrote: >> Hi Jeff, >> >> Are there any outstanding issues that need to be addressed prior to a beta2 release? >> It would be good to get the 8.0 release out prior to FOSS4G next month if possible. >> >> Thanks, >> >> Seth >> >> >> -- >> web:https://geographika.net >> twitter: @geographika >> >> On Tue, Jul 5, 2022, at 10:26 PM, Jeff McKenna wrote: >>> You can change the word "announcement" to website, or changelog, or >>> download link, or docs...but you get the point I'm sure. The point is: >>> the world will get to see the beta2 on Friday ha! >>> >>> Thanks, >>> >>> -jeff >>> >>> >>> >>> On 2022-07-05 5:20 p.m., Jeff McKenna wrote: >>>> Hi all, >>>> >>>> Some may have noticed that a beta1 was quietly made available last week, >>>> but no official announcement: this was no coincidence.? The (great) fast >>>> feedback received from those watching this space closely (Bas, etc.) was >>>> priceless, so I felt it was best to work through those issues before the >>>> announcement. >>>> >>>> Long story short: beta2 is planned for this coming Friday, with a more >>>> official announcement etc.? So please if you are working on a pull >>>> request now, try to get your changes in before then (with appropriate >>>> msautotests). >>>> >>>> Thanks! >>>> >>>> -jeff >>>> >>>> >>>> >>>>> >>>>> >>>>> Starting from now: >>>>> - please use the new label 'backport branch-8-0' to apply your changes >>>>> from 'main' into the new branch-8-0 >>>>> - I'm working on the website updates, so that the mapserver.org >>>>> website will serve up 8.0 docs. >>>>> - beta1 release will happen shortly (once website is ready) >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> -jeff >>>>> >>>>> >>>> >>> >>> -- >>> Jeff McKenna >>> GatewayGeo: Developers of MS4W, MapServer Consulting and Training >>> co-founder of FOSS4G >>> http://gatewaygeo.com/ >>> >>> _______________________________________________ >>> MapServer-dev mailing list >>> MapServer-dev at lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >> > > -- > Jeff McKenna > GatewayGeo: Developers of MS4W, MapServer Consulting and Training > co-founder of FOSS4G > http://gatewaygeo.com/ > > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev From jmckenna at gatewaygeomatics.com Fri Aug 12 02:51:09 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Fri, 12 Aug 2022 06:51:09 -0300 Subject: [mapserver-dev] Heads-up: 8.0 version branched In-Reply-To: References: <28db659f-92e2-c916-f62e-a2966461ba8c@gatewaygeomatics.com> <1266c6f5-7069-fded-fcb9-8f9e04d645c5@gatewaygeomatics.com> <8848c6aa-607e-96ca-9e39-f7ccc4588414@gatewaygeomatics.com> <6ea0da50-5ddc-aecb-928c-4a7ad7aaac82@gatewaygeomatics.com> Message-ID: <3ebe1602-17de-2c76-81de-d988fa8d92f5@gatewaygeomatics.com> I've been working on website updates for a few weeks now, so today, the beta2 will be announced (along with the website updates) as had cut the beta2 release earlier this week, putting us on schedule for RC1 a week from today. Watch your inbox today for the good news ;) -jeff On 2022-08-12 6:25 a.m., Seth G wrote: > Hi, > > We need to provide an update to OSGeo on the MapServer project status for the AGM slides. It would be good to announce the 8.0 release, or at least have a release candidate out. > > Looking at remaining issues in https://github.com/MapServer/MapServer/milestone/54 I don't think any are blockers to proceeding to a release candidate (many issues are several years old so not particular to 8.0)? > > Seth > > -- > web:https://geographika.net > twitter: @geographika > > On Tue, Jul 26, 2022, at 4:43 PM, Jeff McKenna wrote: >> Hi Seth, >> >> I'm planning for a beta2 on this Friday. I was also thinking of the >> FOSS4G deadline. If you all have changes to make (or tickets/pull >> requests to give feedback in or test) please do so in the next few days. >> >> Thanks all :) >> >> -jeff >> >> >> >> >> On 2022-07-26 11:38 a.m., Seth G wrote: >>> Hi Jeff, >>> >>> Are there any outstanding issues that need to be addressed prior to a beta2 release? >>> It would be good to get the 8.0 release out prior to FOSS4G next month if possible. >>> >>> Thanks, >>> >>> Seth >>> >>> >>> -- >>> web:https://geographika.net >>> twitter: @geographika >>> >>> On Tue, Jul 5, 2022, at 10:26 PM, Jeff McKenna wrote: >>>> You can change the word "announcement" to website, or changelog, or >>>> download link, or docs...but you get the point I'm sure. The point is: >>>> the world will get to see the beta2 on Friday ha! >>>> >>>> Thanks, >>>> >>>> -jeff >>>> >>>> >>>> >>>> On 2022-07-05 5:20 p.m., Jeff McKenna wrote: >>>>> Hi all, >>>>> >>>>> Some may have noticed that a beta1 was quietly made available last week, >>>>> but no official announcement: this was no coincidence.? The (great) fast >>>>> feedback received from those watching this space closely (Bas, etc.) was >>>>> priceless, so I felt it was best to work through those issues before the >>>>> announcement. >>>>> >>>>> Long story short: beta2 is planned for this coming Friday, with a more >>>>> official announcement etc.? So please if you are working on a pull >>>>> request now, try to get your changes in before then (with appropriate >>>>> msautotests). >>>>> >>>>> Thanks! >>>>> >>>>> -jeff >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> Starting from now: >>>>>> - please use the new label 'backport branch-8-0' to apply your changes >>>>>> from 'main' into the new branch-8-0 >>>>>> - I'm working on the website updates, so that the mapserver.org >>>>>> website will serve up 8.0 docs. >>>>>> - beta1 release will happen shortly (once website is ready) >>>>>> >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> -jeff >>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> Jeff McKenna >>>> GatewayGeo: Developers of MS4W, MapServer Consulting and Training >>>> co-founder of FOSS4G >>>> http://gatewaygeo.com/ >>>> >>>> _______________________________________________ >>>> MapServer-dev mailing list >>>> MapServer-dev at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >>> >> >> -- >> Jeff McKenna >> GatewayGeo: Developers of MS4W, MapServer Consulting and Training >> co-founder of FOSS4G >> http://gatewaygeo.com/ >> >> _______________________________________________ >> MapServer-dev mailing list >> MapServer-dev at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev > -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ From richard.greenwood at gmail.com Mon Aug 15 20:16:38 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Mon, 15 Aug 2022 21:16:38 -0600 Subject: [mapserver-dev] Mapserver 8.0 beta documentation Message-ID: Nice work on Mapserver 8.0! TEMPLATEPATTERN appears to be gone? In the mapserver.conf file documentation it says that MS_MAP_PATTERN is required (in the comments) but it's working for me w/o. -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmckenna at gatewaygeomatics.com Tue Aug 16 05:00:26 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Tue, 16 Aug 2022 09:00:26 -0300 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: References: Message-ID: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> Hi Rich, Correct, TEMPLATEPATTERN was removed (this is already noted in the documentation at https://mapserver.org/mapfile/map.html ). If you see it mentioned elsewhere please let me know. Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will correct the docs (as throughout this 8.0 process I always assumed it was now required). Thanks, -jeff -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ On 2022-08-16 12:16 a.m., Richard Greenwood wrote: > Nice work on?Mapserver 8.0! > > TEMPLATEPATTERN?appears to be gone? > > In the mapserver.conf file documentation it says that MS_MAP_PATTERN is > required (in the comments) but it's working for me w/o. From jmckenna at gatewaygeomatics.com Tue Aug 16 05:05:23 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Tue, 16 Aug 2022 09:05:23 -0300 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> Message-ID: <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> Hi Rich, I just tested the 8.0.0-beta2 and it is in fact required: "Web application error. Required configuration value MS_MAP_PATTERN not set". -jeff On 2022-08-16 9:00 a.m., Jeff McKenna wrote: > Hi Rich, > > Correct, TEMPLATEPATTERN was removed (this is already noted in the > documentation at https://mapserver.org/mapfile/map.html ).? If you see > it mentioned elsewhere please let me know. > > Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will > correct the docs (as throughout this 8.0 process I always assumed it was > now required). > > Thanks, > > -jeff > > > -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ From jmckenna at gatewaygeomatics.com Tue Aug 16 05:06:45 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Tue, 16 Aug 2022 09:06:45 -0300 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> Message-ID: <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> (I tested in my browser with a CGI MODE=map call) -jeff On 2022-08-16 9:05 a.m., Jeff McKenna wrote: > Hi Rich, > > I just tested the 8.0.0-beta2 and it is in fact required: "Web > application error.? Required configuration value MS_MAP_PATTERN not set". > > -jeff > > > > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: >> Hi Rich, >> >> Correct, TEMPLATEPATTERN was removed (this is already noted in the >> documentation at https://mapserver.org/mapfile/map.html ).? If you see >> it mentioned elsewhere please let me know. >> >> Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will >> correct the docs (as throughout this 8.0 process I always assumed it >> was now required). >> >> Thanks, >> >> -jeff >> >> >> > From richard.greenwood at gmail.com Tue Aug 16 05:31:06 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Tue, 16 Aug 2022 06:31:06 -0600 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> Message-ID: Sorry I missed the TEMPLATEPATTERN documentation (reading too quickly in all the excitement over a new MS version)! Regarding MS_MAP_PATTERN, I'm doing a WMS GetMap request. Rich On Tue, Aug 16, 2022 at 6:07 AM Jeff McKenna wrote: > (I tested in my browser with a CGI MODE=map call) > > -jeff > > > > On 2022-08-16 9:05 a.m., Jeff McKenna wrote: > > Hi Rich, > > > > I just tested the 8.0.0-beta2 and it is in fact required: "Web > > application error. Required configuration value MS_MAP_PATTERN not set". > > > > -jeff > > > > > > > > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: > >> Hi Rich, > >> > >> Correct, TEMPLATEPATTERN was removed (this is already noted in the > >> documentation at https://mapserver.org/mapfile/map.html ). If you see > >> it mentioned elsewhere please let me know. > >> > >> Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will > >> correct the docs (as throughout this 8.0 process I always assumed it > >> was now required). > >> > >> Thanks, > >> > >> -jeff > >> > >> > >> > > > > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdlime at gmail.com Tue Aug 16 06:10:08 2022 From: sdlime at gmail.com (Steve Lime) Date: Tue, 16 Aug 2022 08:10:08 -0500 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> Message-ID: There are 2 scenarios when you won't get the error Jeff references when MS_MAP_PATTERN is not set in the config file: 1. If using an map alias (set in the map section of the config file) - these can only be read from the config file. 2. If MS_MAP_PATTERN is set in the underlying environment - that is, by the web server. Things are set up to fall back to the environment variables (we're using GDAL functionality) if they exist for any of the MS* variables. Do either of these apply? --Steve On Tue, Aug 16, 2022 at 7:31 AM Richard Greenwood < richard.greenwood at gmail.com> wrote: > Sorry I missed the TEMPLATEPATTERN documentation (reading too quickly in > all the excitement over a new MS version)! > > Regarding MS_MAP_PATTERN, I'm doing a WMS GetMap request. > > Rich > > > > > On Tue, Aug 16, 2022 at 6:07 AM Jeff McKenna < > jmckenna at gatewaygeomatics.com> wrote: > >> (I tested in my browser with a CGI MODE=map call) >> >> -jeff >> >> >> >> On 2022-08-16 9:05 a.m., Jeff McKenna wrote: >> > Hi Rich, >> > >> > I just tested the 8.0.0-beta2 and it is in fact required: "Web >> > application error. Required configuration value MS_MAP_PATTERN not >> set". >> > >> > -jeff >> > >> > >> > >> > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: >> >> Hi Rich, >> >> >> >> Correct, TEMPLATEPATTERN was removed (this is already noted in the >> >> documentation at https://mapserver.org/mapfile/map.html ). If you >> see >> >> it mentioned elsewhere please let me know. >> >> >> >> Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will >> >> correct the docs (as throughout this 8.0 process I always assumed it >> >> was now required). >> >> >> >> Thanks, >> >> >> >> -jeff >> >> >> >> >> >> >> > >> >> _______________________________________________ >> MapServer-dev mailing list >> MapServer-dev at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >> > > > -- > Richard W. Greenwood > www.greenwoodmap.com > _______________________________________________ > 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 richard.greenwood at gmail.com Tue Aug 16 06:27:40 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Tue, 16 Aug 2022 07:27:40 -0600 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> Message-ID: On Tue, Aug 16, 2022 at 7:10 AM Steve Lime wrote: > There are 2 scenarios when you won't get the error Jeff references > when MS_MAP_PATTERN is not set in the config file: > > 1. If using an map alias (set in the map section of the config file) - > these can only be read from the config file. > 2. If MS_MAP_PATTERN is set in the underlying environment - that is, > by the web server. Things are set up to fall back to the environment > variables (we're using GDAL functionality) if they exist for any of the MS* > variables. > > Do either of these apply? > Yep, I'm using aliases in the MAP section. > On Tue, Aug 16, 2022 at 7:31 AM Richard Greenwood < > richard.greenwood at gmail.com> wrote: > >> Sorry I missed the TEMPLATEPATTERN documentation (reading too quickly in >> all the excitement over a new MS version)! >> >> Regarding MS_MAP_PATTERN, I'm doing a WMS GetMap request. >> >> Rich >> >> >> >> >> On Tue, Aug 16, 2022 at 6:07 AM Jeff McKenna < >> jmckenna at gatewaygeomatics.com> wrote: >> >>> (I tested in my browser with a CGI MODE=map call) >>> >>> -jeff >>> >>> >>> >>> On 2022-08-16 9:05 a.m., Jeff McKenna wrote: >>> > Hi Rich, >>> > >>> > I just tested the 8.0.0-beta2 and it is in fact required: "Web >>> > application error. Required configuration value MS_MAP_PATTERN not >>> set". >>> > >>> > -jeff >>> > >>> > >>> > >>> > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: >>> >> Hi Rich, >>> >> >>> >> Correct, TEMPLATEPATTERN was removed (this is already noted in the >>> >> documentation at https://mapserver.org/mapfile/map.html ). If you >>> see >>> >> it mentioned elsewhere please let me know. >>> >> >>> >> Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will >>> >> correct the docs (as throughout this 8.0 process I always assumed it >>> >> was now required). >>> >> >>> >> Thanks, >>> >> >>> >> -jeff >>> >> >>> >> >>> >> >>> > >>> >>> _______________________________________________ >>> MapServer-dev mailing list >>> MapServer-dev at lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >>> >> >> >> -- >> Richard W. Greenwood >> www.greenwoodmap.com >> _______________________________________________ >> MapServer-dev mailing list >> MapServer-dev at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >> > -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdlime at gmail.com Tue Aug 16 07:15:35 2022 From: sdlime at gmail.com (Steve Lime) Date: Tue, 16 Aug 2022 09:15:35 -0500 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> Message-ID: Ok, then that is expected. If you pass a map with a file path then (and assuming you haven't set MS_MAP_NO_PATH) you should see the error message Jeff referenced. On Tue, Aug 16, 2022 at 8:27 AM Richard Greenwood < richard.greenwood at gmail.com> wrote: > On Tue, Aug 16, 2022 at 7:10 AM Steve Lime wrote: > >> There are 2 scenarios when you won't get the error Jeff references >> when MS_MAP_PATTERN is not set in the config file: >> >> 1. If using an map alias (set in the map section of the config file) >> - these can only be read from the config file. >> 2. If MS_MAP_PATTERN is set in the underlying environment - that is, >> by the web server. Things are set up to fall back to the environment >> variables (we're using GDAL functionality) if they exist for any of the MS* >> variables. >> >> Do either of these apply? >> > > Yep, I'm using aliases in the MAP section. > > > >> On Tue, Aug 16, 2022 at 7:31 AM Richard Greenwood < >> richard.greenwood at gmail.com> wrote: >> >>> Sorry I missed the TEMPLATEPATTERN documentation (reading too quickly in >>> all the excitement over a new MS version)! >>> >>> Regarding MS_MAP_PATTERN, I'm doing a WMS GetMap request. >>> >>> Rich >>> >>> >>> >>> >>> On Tue, Aug 16, 2022 at 6:07 AM Jeff McKenna < >>> jmckenna at gatewaygeomatics.com> wrote: >>> >>>> (I tested in my browser with a CGI MODE=map call) >>>> >>>> -jeff >>>> >>>> >>>> >>>> On 2022-08-16 9:05 a.m., Jeff McKenna wrote: >>>> > Hi Rich, >>>> > >>>> > I just tested the 8.0.0-beta2 and it is in fact required: "Web >>>> > application error. Required configuration value MS_MAP_PATTERN not >>>> set". >>>> > >>>> > -jeff >>>> > >>>> > >>>> > >>>> > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: >>>> >> Hi Rich, >>>> >> >>>> >> Correct, TEMPLATEPATTERN was removed (this is already noted in the >>>> >> documentation at https://mapserver.org/mapfile/map.html ). If you >>>> see >>>> >> it mentioned elsewhere please let me know. >>>> >> >>>> >> Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will >>>> >> correct the docs (as throughout this 8.0 process I always assumed it >>>> >> was now required). >>>> >> >>>> >> Thanks, >>>> >> >>>> >> -jeff >>>> >> >>>> >> >>>> >> >>>> > >>>> >>>> _______________________________________________ >>>> MapServer-dev mailing list >>>> MapServer-dev at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >>>> >>> >>> >>> -- >>> Richard W. Greenwood >>> www.greenwoodmap.com >>> _______________________________________________ >>> MapServer-dev mailing list >>> MapServer-dev at lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >>> >> > > -- > Richard W. Greenwood > www.greenwoodmap.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.greenwood at gmail.com Tue Aug 16 08:29:11 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Tue, 16 Aug 2022 09:29:11 -0600 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> Message-ID: So an improved comment might be "Required when referencing map file(s) by path". On Tue, Aug 16, 2022 at 8:15 AM Steve Lime wrote: > Ok, then that is expected. If you pass a map with a file path then (and > assuming you haven't set MS_MAP_NO_PATH) you should see the error message > Jeff referenced. > > On Tue, Aug 16, 2022 at 8:27 AM Richard Greenwood < > richard.greenwood at gmail.com> wrote: > >> On Tue, Aug 16, 2022 at 7:10 AM Steve Lime wrote: >> >>> There are 2 scenarios when you won't get the error Jeff references >>> when MS_MAP_PATTERN is not set in the config file: >>> >>> 1. If using an map alias (set in the map section of the config file) >>> - these can only be read from the config file. >>> 2. If MS_MAP_PATTERN is set in the underlying environment - that is, >>> by the web server. Things are set up to fall back to the environment >>> variables (we're using GDAL functionality) if they exist for any of the MS* >>> variables. >>> >>> Do either of these apply? >>> >> >> Yep, I'm using aliases in the MAP section. >> >> >> >>> On Tue, Aug 16, 2022 at 7:31 AM Richard Greenwood < >>> richard.greenwood at gmail.com> wrote: >>> >>>> Sorry I missed the TEMPLATEPATTERN documentation (reading too quickly >>>> in all the excitement over a new MS version)! >>>> >>>> Regarding MS_MAP_PATTERN, I'm doing a WMS GetMap request. >>>> >>>> Rich >>>> >>>> >>>> >>>> >>>> On Tue, Aug 16, 2022 at 6:07 AM Jeff McKenna < >>>> jmckenna at gatewaygeomatics.com> wrote: >>>> >>>>> (I tested in my browser with a CGI MODE=map call) >>>>> >>>>> -jeff >>>>> >>>>> >>>>> >>>>> On 2022-08-16 9:05 a.m., Jeff McKenna wrote: >>>>> > Hi Rich, >>>>> > >>>>> > I just tested the 8.0.0-beta2 and it is in fact required: "Web >>>>> > application error. Required configuration value MS_MAP_PATTERN not >>>>> set". >>>>> > >>>>> > -jeff >>>>> > >>>>> > >>>>> > >>>>> > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: >>>>> >> Hi Rich, >>>>> >> >>>>> >> Correct, TEMPLATEPATTERN was removed (this is already noted in the >>>>> >> documentation at https://mapserver.org/mapfile/map.html ). If you >>>>> see >>>>> >> it mentioned elsewhere please let me know. >>>>> >> >>>>> >> Regarding MS_MAP_PATTERN, let's let SteveL respond here, and I will >>>>> >> correct the docs (as throughout this 8.0 process I always assumed >>>>> it >>>>> >> was now required). >>>>> >> >>>>> >> Thanks, >>>>> >> >>>>> >> -jeff >>>>> >> >>>>> >> >>>>> >> >>>>> > >>>>> >>>>> _______________________________________________ >>>>> MapServer-dev mailing list >>>>> MapServer-dev at lists.osgeo.org >>>>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >>>>> >>>> >>>> >>>> -- >>>> Richard W. Greenwood >>>> www.greenwoodmap.com >>>> _______________________________________________ >>>> MapServer-dev mailing list >>>> MapServer-dev at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev >>>> >>> >> >> -- >> Richard W. Greenwood >> www.greenwoodmap.com >> > -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmckenna at gatewaygeomatics.com Tue Aug 16 08:47:21 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Tue, 16 Aug 2022 12:47:21 -0300 Subject: [mapserver-dev] Mapserver 8.0 beta documentation In-Reply-To: References: <057ac379-2911-9e38-8e0a-6475960f9f9a@gatewaygeomatics.com> <8f6bfc44-eee6-5286-383e-3e39bb14c541@gatewaygeomatics.com> <0ada77f3-641f-eac7-e9b8-9c748dc36ed2@gatewaygeomatics.com> Message-ID: <3600f213-4e37-1e1d-2b05-0bb5d1af3085@gatewaygeomatics.com> I'm on the case now :) -jeff On 2022-08-16 12:29 p.m., Richard Greenwood wrote: > So an improved comment might be "Required when referencing map file(s) > by path". > > On Tue, Aug 16, 2022 at 8:15 AM Steve Lime > wrote: > > Ok, then that is expected. If you pass a map with a file path then > (and assuming you haven't set MS_MAP_NO_PATH) you should see the > error message Jeff referenced. > > On Tue, Aug 16, 2022 at 8:27 AM Richard Greenwood > > > wrote: > > On Tue, Aug 16, 2022 at 7:10 AM Steve Lime > wrote: > > There are 2 scenarios when you won't get the error Jeff > references when?MS_MAP_PATTERN?is not set in the config file: > > 1. If using an map alias (set in the map section of the > config file) - these can only be read from the config file. > 2. If?MS_MAP_PATTERN is set in the underlying environment - > that is, by the web server. Things are set up to fall > back to the environment variables (we're using GDAL > functionality) if they exist for any of the MS* variables. > > Do either of these apply? > > > Yep, I'm using aliases in the MAP section. > > On Tue, Aug 16, 2022 at 7:31 AM Richard Greenwood > > wrote: > > Sorry I missed the TEMPLATEPATTERN?documentation > (reading too quickly in all the excitement over a new MS > version)! > > Regarding MS_MAP_PATTERN, I'm doing a WMS GetMap request. > > Rich > > > > > On Tue, Aug 16, 2022 at 6:07 AM Jeff McKenna > > wrote: > > (I tested in my browser with a CGI MODE=map call) > > -jeff > > > > On 2022-08-16 9:05 a.m., Jeff McKenna wrote: > > Hi Rich, > > > > I just tested the 8.0.0-beta2 and it is in fact > required: "Web > > application error.? Required configuration value > MS_MAP_PATTERN not set". > > > > -jeff > > > > > > > > On 2022-08-16 9:00 a.m., Jeff McKenna wrote: > >> Hi Rich, > >> > >> Correct, TEMPLATEPATTERN was removed (this is > already noted in the > >> documentation at > https://mapserver.org/mapfile/map.html > ).? If you see > >> it mentioned elsewhere please let me know. > >> > >> Regarding MS_MAP_PATTERN, let's let SteveL > respond here, and I will > >> correct the docs (as throughout this 8.0 process > I always assumed it > >> was now required). > >> > >> Thanks, > >> > >> -jeff > >> > >> > >> > > > > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > > > -- > Richard W. Greenwood > www.greenwoodmap.com > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > > > > -- > Richard W. Greenwood > www.greenwoodmap.com > > From sdlime at gmail.com Thu Aug 25 14:54:02 2022 From: sdlime at gmail.com (Steve Lime) Date: Thu, 25 Aug 2022 16:54:02 -0500 Subject: [MapServer-dev] [MapServer-users] Mapserver 8 rc1 In-Reply-To: <97b798ed-5084-67bf-993f-78af7a792855@postholer.com> References: <97b798ed-5084-67bf-993f-78af7a792855@postholer.com> Message-ID: Thanks for checking! Looks like there might be an issue with the msPostGISReplaceBoxToken() rewrite in C++ in mappostgis.cpp. On Thu, Aug 25, 2022 at 4:20 PM Scott wrote: > ms_error log is telling me it's unable to build the SQL query. There are > no errors in the postgresql log. > > Even if I comment the line out I get an error, such as: > --where st_intersects(geom, !BOX!) > or: > /* !BOX! */ > > If it exists any where in the DATA block, it fails. > > Here's the ms error log: > > [Thu Aug 25 13:46:55 2022].451955 msPostGISBuildSQL(): General error > message. Failed to build SQL 'where'. > [Thu Aug 25 13:46:55 2022].451980 msPostGISLayerWhichShapes(): Query > error. Failed to build query SQL. > [Thu Aug 25 13:46:55 2022].452010 msDrawMap(): Image handling error. > Failed to draw layer named 'wptByTrailType'. > > On 8/25/22 13:03, Steve Lime wrote: > > Hmmm... Wasn't an intentional omission. If you have logging turned on > > and can see the resulting SQL, does the !BOX! get replaced but just > > incorrectly or is the !BOX! still in the SQL. > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.greenwood at gmail.com Sun Aug 28 06:53:15 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Sun, 28 Aug 2022 07:53:15 -0600 Subject: [MapServer-dev] Possibly undocumented 8.0 change Message-ID: I didn't see mention of this in the docs, apologies if I missed it. It appears that as of 8.0 a layer must have a NAME. In the past it has been possible for a layer not to have a NAME if it had a GROUP. -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sethg at geographika.co.uk Sun Aug 28 14:07:35 2022 From: sethg at geographika.co.uk (Seth G) Date: Sun, 28 Aug 2022 23:07:35 +0200 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: <40092c47-a8b5-4136-8086-e54d413e56b4@www.fastmail.com> Hi Richard, Do you have more details - is this when using WMS? Is there an error that appears? For WMS there is a known conflict between GROUP and wms_layer_group in a METADATA block, but this sounds like something different. Seth -- web:https://geographika.net twitter: @geographika On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: > I didn't see mention of this in the docs, apologies if I missed it. It appears that as of 8.0 a layer must have a NAME. In the past it has been possible for a layer not to have a NAME if it had a GROUP. > > -- > Richard W. Greenwood > www.greenwoodmap.com > _______________________________________________ > 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 richard.greenwood at gmail.com Sun Aug 28 23:05:33 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Mon, 29 Aug 2022 00:05:33 -0600 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: <40092c47-a8b5-4136-8086-e54d413e56b4@www.fastmail.com> References: <40092c47-a8b5-4136-8086-e54d413e56b4@www.fastmail.com> Message-ID: Yes, it's with a WMS request. Apache throws a 500 error "End of script output before headers". I define a LAYER with a GROUP but no NAME. I don't believe METADATA plays into it because I commented out the METADATA block and it fails in the same way. On Sun, Aug 28, 2022 at 3:07 PM Seth G wrote: > Hi Richard, > > Do you have more details - is this when using WMS? Is there an error that > appears? > For WMS there is a known conflict between GROUP and wms_layer_group in a > METADATA block, but this sounds like something different. > > Seth > > -- > web:https://geographika.net > twitter: @geographika > > > On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: > > I didn't see mention of this in the docs, apologies if I missed it. It > appears that as of 8.0 a layer must have a NAME. In the past it has been > possible for a layer not to have a NAME if it had a GROUP. > > -- > Richard W. Greenwood > www.greenwoodmap.com > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > > -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jukka.rahkonen at maanmittauslaitos.fi Sun Aug 28 23:44:46 2022 From: jukka.rahkonen at maanmittauslaitos.fi (Rahkonen Jukka) Date: Mon, 29 Aug 2022 06:44:46 +0000 Subject: [MapServer-dev] Possibly undocumented 8.0 change Message-ID: Hi, What happens if you use an empty NAME? -Jukka Rahkonen- L?hett?j?: MapServer-dev Puolesta Richard Greenwood L?hetetty: maanantai 29. elokuuta 2022 9.06 Vastaanottaja: Seth G Kopio: MapServer Devs Aihe: Re: [MapServer-dev] Possibly undocumented 8.0 change Yes, it's with a WMS request. Apache throws a 500 error "End of script output before headers". I define a LAYER with a GROUP but no NAME. I don't believe METADATA plays into it because I commented out the METADATA block and it fails in the same way. On Sun, Aug 28, 2022 at 3:07 PM Seth G > wrote: Hi Richard, Do you have more details - is this when using WMS? Is there an error that appears? For WMS there is a known conflict between GROUP and wms_layer_group in a METADATA block, but this sounds like something different. Seth -- web:https://geographika.net twitter: @geographika On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: I didn't see mention of this in the docs, apologies if I missed it. It appears that as of 8.0 a layer must have a NAME. In the past it has been possible for a layer not to have a NAME if it had a GROUP. -- Richard W. Greenwood www.greenwoodmap.com _______________________________________________ MapServer-dev mailing list MapServer-dev at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-dev -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.greenwood at gmail.com Mon Aug 29 00:34:11 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Mon, 29 Aug 2022 01:34:11 -0600 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: An empty string for the NAME works without error. I set the MS_DEBUGLEVEL to 5 and nothing is written to the error file when this error occurs. On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka < jukka.rahkonen at maanmittauslaitos.fi> wrote: > Hi, > > > > What happens if you use an empty NAME? > > > > -Jukka Rahkonen- > > > > *L?hett?j?:* MapServer-dev *Puolesta > *Richard Greenwood > *L?hetetty:* maanantai 29. elokuuta 2022 9.06 > *Vastaanottaja:* Seth G > *Kopio:* MapServer Devs > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change > > > > Yes, it's with a WMS request. Apache throws a 500 error "End of script > output before headers". I define a LAYER with a GROUP but no NAME. I don't > believe METADATA plays into it because I commented out the METADATA block > and it fails in the same way. > > > > On Sun, Aug 28, 2022 at 3:07 PM Seth G wrote: > > Hi Richard, > > > > Do you have more details - is this when using WMS? Is there an error that > appears? > > For WMS there is a known conflict between GROUP and wms_layer_group in a > METADATA block, but this sounds like something different. > > > > Seth > > > > -- > > web:https://geographika.net > > > twitter: @geographika > > > > > > On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: > > I didn't see mention of this in the docs, apologies if I missed it. It > appears that as of 8.0 a layer must have a NAME. In the past it has been > possible for a layer not to have a NAME if it had a GROUP. > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > _______________________________________________ > > MapServer-dev mailing list > > MapServer-dev at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > > > > > > > > > -- > > Richard W. Greenwood > www.greenwoodmap.com > > -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sethg at geographika.co.uk Mon Aug 29 00:45:25 2022 From: sethg at geographika.co.uk (Seth G) Date: Mon, 29 Aug 2022 09:45:25 +0200 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: Hi Richard, Could you create an issue for this on GitHub? It looks like it could relate to the move to C++. Thanks, Seth -- web:https://geographika.net twitter: @geographika On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote: > An empty string for the NAME works without error. I set the MS_DEBUGLEVEL to 5 and nothing is written to the error file when this error occurs. > > On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka wrote: >> Hi,____ >> __ __ >> What happens if you use an empty NAME?____ >> __ __ >> -Jukka Rahkonen-____ >> __ __ >> *L?hett?j?:* MapServer-dev *Puolesta *Richard Greenwood >> *L?hetetty:* maanantai 29. elokuuta 2022 9.06 >> *Vastaanottaja:* Seth G >> *Kopio:* MapServer Devs >> *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change____ >> >> __ __ >> Yes, it's with a WMS request. Apache throws a 500 error "End of script output before headers". I define a LAYER with a GROUP but no NAME. I don't believe METADATA plays into it because I commented out the METADATA block and it fails in the same way.____ >> __ __ >> On Sun, Aug 28, 2022 at 3:07 PM Seth G wrote:____ >>> Hi Richard,____ >>> __ __ >>> Do you have more details - is this when using WMS? Is there an error that appears?____ >>> For WMS there is a known conflict between GROUP and wms_layer_group in a METADATA block, but this sounds like something different.____ >>> __ __ >>> Seth____ >>> __ __ >>> --____ >>> web:https://geographika.net ____ >>> twitter: @geographika____ >>> __ __ >>> __ __ >>> On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote:____ >>>> I didn't see mention of this in the docs, apologies if I missed it. It appears that as of 8.0 a layer must have a NAME. In the past it has been possible for a layer not to have a NAME if it had a GROUP.____ >>>> __ __ >>>> -- ____ >>>> Richard W. Greenwood____ >>>> www.greenwoodmap.com ____ >>>> ___________________________________________________ >>>> MapServer-dev mailing list____ >>>> MapServer-dev at lists.osgeo.org____ >>>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev ____ >>>> __ __ >>> __ __ >> ____ >> __ __ >> -- ____ >> Richard W. Greenwood >> www.greenwoodmap.com ____ >> > > > -- > Richard W. Greenwood > www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jukka.rahkonen at maanmittauslaitos.fi Mon Aug 29 02:58:38 2022 From: jukka.rahkonen at maanmittauslaitos.fi (Rahkonen Jukka) Date: Mon, 29 Aug 2022 09:58:38 +0000 Subject: [MapServer-dev] Possibly undocumented 8.0 change Message-ID: Hi Richard, Is your aim with using GROUP without NAME to hide the layer from GetCapabilities so that users cannot see or request that layer separately but only as a member of a group? Like "opaque container" in Geoserver https://docs.geoserver.org/latest/en/user/data/webadmin/layergroups.html -Jukka Rahkonen- L?hett?j?: Seth G L?hetetty: maanantai 29. elokuuta 2022 10.45 Vastaanottaja: Richard Greenwood ; Rahkonen Jukka Kopio: MapServer Devs Aihe: Re: [MapServer-dev] Possibly undocumented 8.0 change Hi Richard, Could you create an issue for this on GitHub? It looks like it could relate to the move to C++. Thanks, Seth -- web:https://geographika.net twitter: @geographika On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote: An empty string for the NAME works without error. I set the MS_DEBUGLEVEL to 5 and nothing is written to the error file when this error occurs. On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka > wrote: Hi, What happens if you use an empty NAME? -Jukka Rahkonen- L?hett?j?: MapServer-dev > Puolesta Richard Greenwood L?hetetty: maanantai 29. elokuuta 2022 9.06 Vastaanottaja: Seth G > Kopio: MapServer Devs > Aihe: Re: [MapServer-dev] Possibly undocumented 8.0 change Yes, it's with a WMS request. Apache throws a 500 error "End of script output before headers". I define a LAYER with a GROUP but no NAME. I don't believe METADATA plays into it because I commented out the METADATA block and it fails in the same way. On Sun, Aug 28, 2022 at 3:07 PM Seth G > wrote: Hi Richard, Do you have more details - is this when using WMS? Is there an error that appears? For WMS there is a known conflict between GROUP and wms_layer_group in a METADATA block, but this sounds like something different. Seth -- web:https://geographika.net twitter: @geographika On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: I didn't see mention of this in the docs, apologies if I missed it. It appears that as of 8.0 a layer must have a NAME. In the past it has been possible for a layer not to have a NAME if it had a GROUP. -- Richard W. Greenwood www.greenwoodmap.com _______________________________________________ MapServer-dev mailing list MapServer-dev at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-dev -- Richard W. Greenwood www.greenwoodmap.com -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.greenwood at gmail.com Mon Aug 29 03:39:38 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Mon, 29 Aug 2022 12:39:38 +0200 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: No, just laziness. It's not a big deal, but maybe should be documented. On Mon, Aug 29, 2022, 11:58 AM Rahkonen Jukka < jukka.rahkonen at maanmittauslaitos.fi> wrote: > Hi Richard, > > > > Is your aim with using GROUP without NAME to hide the layer from > GetCapabilities so that users cannot see or request that layer separately > but only as a member of a group? Like ?opaque container? in Geoserver > https://docs.geoserver.org/latest/en/user/data/webadmin/layergroups.html > > > > -Jukka Rahkonen- > > > > > > > > *L?hett?j?:* Seth G > *L?hetetty:* maanantai 29. elokuuta 2022 10.45 > *Vastaanottaja:* Richard Greenwood ; > Rahkonen Jukka > *Kopio:* MapServer Devs > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change > > > > Hi Richard, > > > > Could you create an issue for this on GitHub? > > It looks like it could relate to the move to C++. > > Thanks, > > > > Seth > > > > -- > > web:https://geographika.net > > > twitter: @geographika > > > > > > On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote: > > An empty string for the NAME works without error. I set the MS_DEBUGLEVEL > to 5 and nothing is written to the error file when this error occurs. > > > > On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka < > jukka.rahkonen at maanmittauslaitos.fi> wrote: > > Hi, > > > > What happens if you use an empty NAME? > > > > -Jukka Rahkonen- > > > > *L?hett?j?:* MapServer-dev *Puolesta > *Richard Greenwood > > *L?hetetty:* maanantai 29. elokuuta 2022 9.06 > > *Vastaanottaja:* Seth G > > *Kopio:* MapServer Devs > > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change > > > > Yes, it's with a WMS request. Apache throws a 500 error "End of script > output before headers". I define a LAYER with a GROUP but no NAME. I don't > believe METADATA plays into it because I commented out the METADATA block > and it fails in the same way. > > > > On Sun, Aug 28, 2022 at 3:07 PM Seth G wrote: > > Hi Richard, > > > > Do you have more details - is this when using WMS? Is there an error that > appears? > > For WMS there is a known conflict between GROUP and wms_layer_group in a > METADATA block, but this sounds like something different. > > > > Seth > > > > -- > > web:https://geographika.net > > > twitter: @geographika > > > > > > On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: > > I didn't see mention of this in the docs, apologies if I missed it. It > appears that as of 8.0 a layer must have a NAME. In the past it has been > possible for a layer not to have a NAME if it had a GROUP. > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > _______________________________________________ > > MapServer-dev mailing list > > MapServer-dev at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > > > > > > > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jukka.rahkonen at maanmittauslaitos.fi Mon Aug 29 04:09:52 2022 From: jukka.rahkonen at maanmittauslaitos.fi (Rahkonen Jukka) Date: Mon, 29 Aug 2022 11:09:52 +0000 Subject: [MapServer-dev] Possibly undocumented 8.0 change Message-ID: Hi, So no need for the "opaque container" that is actually kind of a hack in Geoserver. In WMS normal layers must have names, this is from WMS 1.3.0 standard: 7.2.4.6.3 Name If, and only if, a layer has a , then it is a map layer that can be requested by using that Name in the LAYERS parameter of a GetMap request. A Layer that contains a element is referred to as a "named layer" in this International Standard. If the layer has a Title but no Name, then that layer is only a category title for all the layers nested within. A server that advertises a Layer containing a Name element shall be able to accept that Name as the value of LAYERS argument in a GetMap request and return the corresponding map. A client shall not attempt to request a layer that has a Title but no Name. There is something documented about the layer names in https://mapserver.gis.umn.edu/ogc/wms_server.html but not really that the rules apply also if layer belongs to a group: "Layer Name and wms_title metadata: Every individual layer needs its own unique name and title. Layer names are also used in GetMap and GetFeatureInfo requests to refer to layers that should be included in the map output and in the query. Layer names must start with a letter when setting up a WMS server (layer names should not start with a digit or have spaces in them)." -Jukka Rahkonen- L?hett?j?: Richard Greenwood L?hetetty: maanantai 29. elokuuta 2022 13.40 Vastaanottaja: Rahkonen Jukka Kopio: Seth G ; MapServer Devs Aihe: Re: [MapServer-dev] Possibly undocumented 8.0 change No, just laziness. It's not a big deal, but maybe should be documented. On Mon, Aug 29, 2022, 11:58 AM Rahkonen Jukka > wrote: Hi Richard, Is your aim with using GROUP without NAME to hide the layer from GetCapabilities so that users cannot see or request that layer separately but only as a member of a group? Like "opaque container" in Geoserver https://docs.geoserver.org/latest/en/user/data/webadmin/layergroups.html -Jukka Rahkonen- L?hett?j?: Seth G > L?hetetty: maanantai 29. elokuuta 2022 10.45 Vastaanottaja: Richard Greenwood >; Rahkonen Jukka > Kopio: MapServer Devs > Aihe: Re: [MapServer-dev] Possibly undocumented 8.0 change Hi Richard, Could you create an issue for this on GitHub? It looks like it could relate to the move to C++. Thanks, Seth -- web:https://geographika.net twitter: @geographika On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote: An empty string for the NAME works without error. I set the MS_DEBUGLEVEL to 5 and nothing is written to the error file when this error occurs. On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka > wrote: Hi, What happens if you use an empty NAME? -Jukka Rahkonen- L?hett?j?: MapServer-dev > Puolesta Richard Greenwood L?hetetty: maanantai 29. elokuuta 2022 9.06 Vastaanottaja: Seth G > Kopio: MapServer Devs > Aihe: Re: [MapServer-dev] Possibly undocumented 8.0 change Yes, it's with a WMS request. Apache throws a 500 error "End of script output before headers". I define a LAYER with a GROUP but no NAME. I don't believe METADATA plays into it because I commented out the METADATA block and it fails in the same way. On Sun, Aug 28, 2022 at 3:07 PM Seth G > wrote: Hi Richard, Do you have more details - is this when using WMS? Is there an error that appears? For WMS there is a known conflict between GROUP and wms_layer_group in a METADATA block, but this sounds like something different. Seth -- web:https://geographika.net twitter: @geographika On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: I didn't see mention of this in the docs, apologies if I missed it. It appears that as of 8.0 a layer must have a NAME. In the past it has been possible for a layer not to have a NAME if it had a GROUP. -- Richard W. Greenwood www.greenwoodmap.com _______________________________________________ MapServer-dev mailing list MapServer-dev at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapserver-dev -- Richard W. Greenwood www.greenwoodmap.com -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.greenwood at gmail.com Mon Aug 29 06:18:21 2022 From: richard.greenwood at gmail.com (Richard Greenwood) Date: Mon, 29 Aug 2022 07:18:21 -0600 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: Rahkonen, Thank you for the explanation of the WMS definitions, but my point is that this is a breaking change from MapServer map files prior to 8.0. The change does not return an error message that helps the user identify the problem, so I thought that it might be helpful to note the change in the migration guide: https://mapserver.org/MIGRATION_GUIDE.html#migration-8-0 On Mon, Aug 29, 2022 at 5:10 AM Rahkonen Jukka < jukka.rahkonen at maanmittauslaitos.fi> wrote: > Hi, > > > > So no need for the ?opaque container? that is actually kind of a hack in > Geoserver. In WMS normal layers must have names, this is from WMS 1.3.0 > standard: > > > 7.2.4.6.3 Name > > If, and only if, a layer has a , then it is a map layer that can be > requested by using that Name in the > > LAYERS parameter of a GetMap request. A Layer that contains a > element is referred to as a ?named > > layer? in this International Standard. If the layer has a Title but no > Name, then that layer is only a category title for > > all the layers nested within. A server that advertises a Layer containing > a Name element shall be able to accept > > that Name as the value of LAYERS argument in a GetMap request and return > the corresponding map. A client > > shall not attempt to request a layer that has a Title but no Name. > > > > There is something documented about the layer names in > https://mapserver.gis.umn.edu/ogc/wms_server.html but not really that the > rules apply also if layer belongs to a group: > > > > ?Layer Name and wms_title metadata: > > > > Every individual layer needs its own unique name and title. Layer names > are also used in GetMap and GetFeatureInfo requests to refer to layers that > should be included in the map output and in the query. Layer names must > start with a letter when setting up a WMS server (layer names should not > start with a digit or have spaces in them).? > > > > -Jukka Rahkonen- > > > > > > *L?hett?j?:* Richard Greenwood > *L?hetetty:* maanantai 29. elokuuta 2022 13.40 > *Vastaanottaja:* Rahkonen Jukka > *Kopio:* Seth G ; MapServer Devs < > mapserver-dev at lists.osgeo.org> > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change > > > > No, just laziness. It's not a big deal, but maybe should be documented. > > > > On Mon, Aug 29, 2022, 11:58 AM Rahkonen Jukka < > jukka.rahkonen at maanmittauslaitos.fi> wrote: > > Hi Richard, > > > > Is your aim with using GROUP without NAME to hide the layer from > GetCapabilities so that users cannot see or request that layer separately > but only as a member of a group? Like ?opaque container? in Geoserver > https://docs.geoserver.org/latest/en/user/data/webadmin/layergroups.html > > > > > -Jukka Rahkonen- > > > > > > > > *L?hett?j?:* Seth G > *L?hetetty:* maanantai 29. elokuuta 2022 10.45 > *Vastaanottaja:* Richard Greenwood ; > Rahkonen Jukka > *Kopio:* MapServer Devs > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change > > > > Hi Richard, > > > > Could you create an issue for this on GitHub? > > It looks like it could relate to the move to C++. > > Thanks, > > > > Seth > > > > -- > > web:https://geographika.net > > > twitter: @geographika > > > > > > On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote: > > An empty string for the NAME works without error. I set the MS_DEBUGLEVEL > to 5 and nothing is written to the error file when this error occurs. > > > > On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka < > jukka.rahkonen at maanmittauslaitos.fi> wrote: > > Hi, > > > > What happens if you use an empty NAME? > > > > -Jukka Rahkonen- > > > > *L?hett?j?:* MapServer-dev *Puolesta > *Richard Greenwood > > *L?hetetty:* maanantai 29. elokuuta 2022 9.06 > > *Vastaanottaja:* Seth G > > *Kopio:* MapServer Devs > > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change > > > > Yes, it's with a WMS request. Apache throws a 500 error "End of script > output before headers". I define a LAYER with a GROUP but no NAME. I don't > believe METADATA plays into it because I commented out the METADATA block > and it fails in the same way. > > > > On Sun, Aug 28, 2022 at 3:07 PM Seth G wrote: > > Hi Richard, > > > > Do you have more details - is this when using WMS? Is there an error that > appears? > > For WMS there is a known conflict between GROUP and wms_layer_group in a > METADATA block, but this sounds like something different. > > > > Seth > > > > -- > > web:https://geographika.net > > > twitter: @geographika > > > > > > On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood wrote: > > I didn't see mention of this in the docs, apologies if I missed it. It > appears that as of 8.0 a layer must have a NAME. In the past it has been > possible for a layer not to have a NAME if it had a GROUP. > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > _______________________________________________ > > MapServer-dev mailing list > > MapServer-dev at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > > > > > > > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > > > > > -- > > Richard W. Greenwood > > www.greenwoodmap.com > > > > > -- Richard W. Greenwood www.greenwoodmap.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmckenna at gatewaygeomatics.com Mon Aug 29 06:35:45 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Mon, 29 Aug 2022 10:35:45 -0300 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: Thanks Rich, I'll add it into the MigrationGuide today, great catch. -jeff -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ On 2022-08-29 10:18 a.m., Richard Greenwood wrote: > Rahkonen, > > Thank you for the explanation of the WMS definitions, but my point is > that this is a breaking change from MapServer map files prior to 8.0. > The change does not return an error message that helps the user identify > the problem, so I thought that it might be helpful to note the change in > the migration guide: > https://mapserver.org/MIGRATION_GUIDE.html#migration-8-0 > > > On Mon, Aug 29, 2022 at 5:10 AM Rahkonen Jukka > > wrote: > > Hi,____ > > __ __ > > So no need for the ?opaque container? that is actually kind of a > hack in Geoserver. In WMS normal layers must have names, this is > from WMS 1.3.0 standard:____ > > > 7.2.4.6.3 Name____ > > If, and only if, a layer has a , then it is a map layer that > can be requested by using that Name in the____ > > LAYERS parameter of a GetMap request. A Layer that contains a > element is referred to as a ?named____ > > layer? in this International Standard. If the layer has a Title but > no Name, then that layer is only a category title for____ > > all the layers nested within. A server that advertises a Layer > containing a Name element shall be able to accept____ > > that Name as the value of LAYERS argument in a GetMap request and > return the corresponding map. A client____ > > shall not attempt to request a layer that has a Title but no Name.____ > > __ __ > > There is something documented about the layer names in > https://mapserver.gis.umn.edu/ogc/wms_server.html > but not really > that the rules apply also if layer belongs to a group:____ > > __ __ > > ?Layer Name and wms_title metadata:____ > > __ __ > > Every individual layer needs its own unique name and title. Layer > names are also used in GetMap and GetFeatureInfo requests to refer > to layers that should be included in the map output and in the > query. Layer names must start with a letter when setting up a WMS > server (layer names should not start with a digit or have spaces in > them).?____ > > __ __ > > -Jukka Rahkonen-____ > > __ __ > > __ __ > > *L?hett?j?:* Richard Greenwood > > *L?hetetty:* maanantai 29. elokuuta 2022 13.40 > *Vastaanottaja:* Rahkonen Jukka > > *Kopio:* Seth G >; MapServer Devs > > > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change____ > > __ __ > > No, just laziness. It's not a big deal, but maybe should be > documented. ____ > > __ __ > > On Mon, Aug 29, 2022, 11:58 AM Rahkonen Jukka > > wrote:____ > > Hi Richard,____ > > ____ > > Is your aim with using GROUP without NAME to hide the layer from > GetCapabilities so that users cannot see or request that layer > separately but only as a member of a group? Like ?opaque > container? in Geoserver > https://docs.geoserver.org/latest/en/user/data/webadmin/layergroups.html ____ > > ____ > > -Jukka Rahkonen-____ > > ____ > > ____ > > ____ > > *L?hett?j?:* Seth G > > *L?hetetty:* maanantai 29. elokuuta 2022 10.45 > *Vastaanottaja:* Richard Greenwood >; Rahkonen Jukka > > > *Kopio:* MapServer Devs > > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change____ > > ____ > > Hi Richard,____ > > ____ > > Could you create an issue for this on GitHub?____ > > It looks like it could relate to the move to C++.____ > > Thanks,____ > > ____ > > Seth____ > > ____ > > --____ > > web:https://geographika.net > ____ > > twitter: @geographika____ > > ____ > > ____ > > On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote:____ > > An empty string for the NAME works without error. I set > the?MS_DEBUGLEVEL to 5 and nothing is written to the error > file when this error?occurs.____ > > ____ > > On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka > > wrote:____ > > Hi,____ > > ____ > > What happens if you use an empty NAME?____ > > ____ > > -Jukka Rahkonen-____ > > ____ > > *L?hett?j?:* MapServer-dev > > > *Puolesta *Richard Greenwood____ > > *L?hetetty:* maanantai 29. elokuuta 2022 9.06____ > > *Vastaanottaja:* Seth G >____ > > *Kopio:* MapServer Devs >____ > > *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 > change____ > > ____ > > Yes, it's with a WMS request. Apache throws a 500 error > "End of script output before headers". I define a LAYER > with a GROUP but no NAME. I don't believe METADATA plays > into it because?I commented out the METADATA block and > it fails in the same way.____ > > ____ > > On Sun, Aug 28, 2022 at 3:07 PM Seth G > > wrote:____ > > Hi Richard,____ > > ____ > > Do you have more details - is this when using WMS? > Is there an error that appears?____ > > For WMS there is a known conflict between GROUP and > wms_layer_group in a METADATA block, but this sounds > like something different.____ > > ____ > > Seth____ > > ____ > > --____ > > web:https://geographika.net > ____ > > twitter: @geographika____ > > ____ > > ____ > > On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood > wrote:____ > > I didn't see mention of this in the docs, > apologies?if I missed?it. It appears that as of > 8.0 a layer must have a NAME. In the past it has > been possible for a layer not to have a NAME if > it had a? GROUP.____ > > ____ > > -- ____ > > Richard W. Greenwood____ > > www.greenwoodmap.com > ____ > > ___________________________________________________ > > MapServer-dev mailing list____ > > MapServer-dev at lists.osgeo.org > ____ > > https://lists.osgeo.org/mailman/listinfo/mapserver-dev ____ > > ____ > > ____ > > ____ > > ____ > > -- ____ > > Richard W. Greenwood____ > > www.greenwoodmap.com > ____ > > ____ > > ____ > > -- ____ > > Richard W. Greenwood____ > > www.greenwoodmap.com > ____ > > ____ > > > > -- > Richard W. Greenwood > www.greenwoodmap.com > > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev From sethg at geographika.co.uk Mon Aug 29 08:38:02 2022 From: sethg at geographika.co.uk (Seth G) Date: Mon, 29 Aug 2022 17:38:02 +0200 Subject: [MapServer-dev] Possibly undocumented 8.0 change In-Reply-To: References: Message-ID: Ideally Mapfiles shouldn't be able to crash the server. This change was introduced with the move to C++. The patch at https://github.com/MapServer/MapServer/pull/6603 should avoid crashes and keep the previous behaviour. Ideally though all LAYERS should have a NAME as there are several gotchas if they aren't present. Seth -- web:https://geographika.net twitter: @geographika On Mon, Aug 29, 2022, at 3:35 PM, Jeff McKenna wrote: > Thanks Rich, I'll add it into the MigrationGuide today, great catch. > > -jeff > > > > -- > Jeff McKenna > GatewayGeo: Developers of MS4W, MapServer Consulting and Training > co-founder of FOSS4G > http://gatewaygeo.com/ > > > > On 2022-08-29 10:18 a.m., Richard Greenwood wrote: >> Rahkonen, >> >> Thank you for the explanation of the WMS definitions, but my point is >> that this is a breaking change from MapServer map files prior to 8.0. >> The change does not return an error message that helps the user identify >> the problem, so I thought that it might be helpful to note the change in >> the migration guide: >> https://mapserver.org/MIGRATION_GUIDE.html#migration-8-0 >> >> >> On Mon, Aug 29, 2022 at 5:10 AM Rahkonen Jukka >> > > wrote: >> >> Hi,____ >> >> __ __ >> >> So no need for the ?opaque container? that is actually kind of a >> hack in Geoserver. In WMS normal layers must have names, this is >> from WMS 1.3.0 standard:____ >> >> >> 7.2.4.6.3 Name____ >> >> If, and only if, a layer has a , then it is a map layer that >> can be requested by using that Name in the____ >> >> LAYERS parameter of a GetMap request. A Layer that contains a >> element is referred to as a ?named____ >> >> layer? in this International Standard. If the layer has a Title but >> no Name, then that layer is only a category title for____ >> >> all the layers nested within. A server that advertises a Layer >> containing a Name element shall be able to accept____ >> >> that Name as the value of LAYERS argument in a GetMap request and >> return the corresponding map. A client____ >> >> shall not attempt to request a layer that has a Title but no Name.____ >> >> __ __ >> >> There is something documented about the layer names in >> https://mapserver.gis.umn.edu/ogc/wms_server.html >> but not really >> that the rules apply also if layer belongs to a group:____ >> >> __ __ >> >> ?Layer Name and wms_title metadata:____ >> >> __ __ >> >> Every individual layer needs its own unique name and title. Layer >> names are also used in GetMap and GetFeatureInfo requests to refer >> to layers that should be included in the map output and in the >> query. Layer names must start with a letter when setting up a WMS >> server (layer names should not start with a digit or have spaces in >> them).?____ >> >> __ __ >> >> -Jukka Rahkonen-____ >> >> __ __ >> >> __ __ >> >> *L?hett?j?:* Richard Greenwood > > >> *L?hetetty:* maanantai 29. elokuuta 2022 13.40 >> *Vastaanottaja:* Rahkonen Jukka > > >> *Kopio:* Seth G > >; MapServer Devs >> > >> *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change____ >> >> __ __ >> >> No, just laziness. It's not a big deal, but maybe should be >> documented. ____ >> >> __ __ >> >> On Mon, Aug 29, 2022, 11:58 AM Rahkonen Jukka >> > > wrote:____ >> >> Hi Richard,____ >> >> ____ >> >> Is your aim with using GROUP without NAME to hide the layer from >> GetCapabilities so that users cannot see or request that layer >> separately but only as a member of a group? Like ?opaque >> container? in Geoserver >> https://docs.geoserver.org/latest/en/user/data/webadmin/layergroups.html ____ >> >> ____ >> >> -Jukka Rahkonen-____ >> >> ____ >> >> ____ >> >> ____ >> >> *L?hett?j?:* Seth G > > >> *L?hetetty:* maanantai 29. elokuuta 2022 10.45 >> *Vastaanottaja:* Richard Greenwood > >; Rahkonen Jukka >> > > >> *Kopio:* MapServer Devs > > >> *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 change____ >> >> ____ >> >> Hi Richard,____ >> >> ____ >> >> Could you create an issue for this on GitHub?____ >> >> It looks like it could relate to the move to C++.____ >> >> Thanks,____ >> >> ____ >> >> Seth____ >> >> ____ >> >> --____ >> >> web:https://geographika.net >> ____ >> >> twitter: @geographika____ >> >> ____ >> >> ____ >> >> On Mon, Aug 29, 2022, at 9:34 AM, Richard Greenwood wrote:____ >> >> An empty string for the NAME works without error. I set >> the?MS_DEBUGLEVEL to 5 and nothing is written to the error >> file when this error?occurs.____ >> >> ____ >> >> On Mon, Aug 29, 2022 at 12:44 AM Rahkonen Jukka >> > > wrote:____ >> >> Hi,____ >> >> ____ >> >> What happens if you use an empty NAME?____ >> >> ____ >> >> -Jukka Rahkonen-____ >> >> ____ >> >> *L?hett?j?:* MapServer-dev >> > > >> *Puolesta *Richard Greenwood____ >> >> *L?hetetty:* maanantai 29. elokuuta 2022 9.06____ >> >> *Vastaanottaja:* Seth G > >____ >> >> *Kopio:* MapServer Devs > >____ >> >> *Aihe:* Re: [MapServer-dev] Possibly undocumented 8.0 >> change____ >> >> ____ >> >> Yes, it's with a WMS request. Apache throws a 500 error >> "End of script output before headers". I define a LAYER >> with a GROUP but no NAME. I don't believe METADATA plays >> into it because?I commented out the METADATA block and >> it fails in the same way.____ >> >> ____ >> >> On Sun, Aug 28, 2022 at 3:07 PM Seth G >> > > wrote:____ >> >> Hi Richard,____ >> >> ____ >> >> Do you have more details - is this when using WMS? >> Is there an error that appears?____ >> >> For WMS there is a known conflict between GROUP and >> wms_layer_group in a METADATA block, but this sounds >> like something different.____ >> >> ____ >> >> Seth____ >> >> ____ >> >> --____ >> >> web:https://geographika.net >> ____ >> >> twitter: @geographika____ >> >> ____ >> >> ____ >> >> On Sun, Aug 28, 2022, at 3:53 PM, Richard Greenwood >> wrote:____ >> >> I didn't see mention of this in the docs, >> apologies?if I missed?it. It appears that as of >> 8.0 a layer must have a NAME. In the past it has >> been possible for a layer not to have a NAME if >> it had a? GROUP.____ >> >> ____ >> >> -- ____ >> >> Richard W. Greenwood____ >> >> www.greenwoodmap.com >> ____ >> >> ___________________________________________________ >> >> MapServer-dev mailing list____ >> >> MapServer-dev at lists.osgeo.org >> ____ >> >> https://lists.osgeo.org/mailman/listinfo/mapserver-dev ____ >> >> ____ >> >> ____ >> >> ____ >> >> ____ >> >> -- ____ >> >> Richard W. Greenwood____ >> >> www.greenwoodmap.com >> ____ >> >> ____ >> >> ____ >> >> -- ____ >> >> Richard W. Greenwood____ >> >> www.greenwoodmap.com >> ____ >> >> ____ >> >> >> >> -- >> Richard W. Greenwood >> www.greenwoodmap.com >> >> _______________________________________________ >> 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 Mon Aug 29 15:10:44 2022 From: sethg at geographika.co.uk (Seth G) Date: Tue, 30 Aug 2022 00:10:44 +0200 Subject: [MapServer-dev] MapServer at FOSS4G 2022 Message-ID: <37e56ea7-a12b-4c7e-a809-d84a9c138d41@www.fastmail.com> Hi all, FOSS4G was held in Florence/Firenze last week [1], and included a "State of MapServer 2022" talk [2]. The slides for this can be seen online [3]. The source HTML for this presentation is available on GitHub [4] - please feel free to reuse and adapt this content for any MapServer related talks. The MapServer ecosystem is wide and growing, so if there are new tools and systems that would be of interest to MapServer users please raise awareness of them on this user's list, and via the MapServer Wiki, and they can be mentioned in any future MapServer updates. 7 members of the PSC (Project Steering Committee) were present, and from general discussions MapServer is widely used across many countries and organisations. Please add to the MapServer Site Gallery [5] if possible! Below is a selection of other MapServer related presentations - I believe the slides and audio for these will be published on YoutTube later this year: + MapServer - Make beautiful maps - https://talks.osgeo.org/foss4g-2022/talk/SQMVXH/ (slides at https://github.com/LarsSchy/FOSS4G-2022) + Mapserver layer handling, production, and management in larger scale environment - https://talks.osgeo.org/foss4g-2022/talk/CXXKVU/ + A crawler for spatial (meta)data as a base for Mapserver configuration - https://talks.osgeo.org/foss4g-2022/talk/QW3NYC/ + EVRYMAP - An extensible web mapping framework based on Angular, NodeJS, Leaflet and Mapserver - https://talks.osgeo.org/foss4g-2022/talk/Q9G7EH/ Last year's online talk "State of Mapserver 2021" is also available on YouTube [6] and covers many of the new features arriving in MapServer 8.0. Seth [1] https://2022.foss4g.org/ [2] https://talks.osgeo.org/foss4g-2022/talk/CBVAT9/ [3] https://geographika.github.io/mapserver-state-2022/ [4] https://github.com/geographika/mapserver-state-2022 [5] https://github.com/mapserver/mapserver/wiki/MapServer-Site-Gallery [6] https://www.youtube.com/watch?v=me5UyqG03Pg -- web:https://geographika.net twitter: @geographika From public at postholer.com Tue Aug 30 07:49:53 2022 From: public at postholer.com (Scott) Date: Tue, 30 Aug 2022 07:49:53 -0700 Subject: [MapServer-dev] Accessing FlatGeoBuf (.fgb) in S3 bucket? Message-ID: <9f56750b-8050-14a3-6cbe-917792924501@postholer.com> Using mapserver 7.6 or 8rc1 I've been unable to serve .fgb from an S3 bucket. Local disk works fine as does ogrinfo on S3 .fgb. COG raster data works fine off S3. Accessing .fgb from cloud storage seems to be the whole point of the .fgb format. So, I'm very curious if I'm doing something wrong or is it by design. Map file configs: v8rc1: CONNECTIONTYPE flatgeobuf DATA "/vsis3/bucket/path/data.fgb" v7.6.4 CONNECTIONTYPE OGR CONNECTION "/vsis3/bucket/path/data.fgb" DATA "rm_trace" v8rc ms_error log: [Fri Aug 26 10:24:13 2022].854479 msDrawMap(): Image handling error. Failed to draw layer named 'rm_trace'. v7.6.4 ms_error log [Fri Aug 26 10:06:59 2022].388096 msOGRFileOpen(): OGR error. Open failed for OGR connection in layer `rm_trace'. File not found or unsupported format. Check server logs. [Fri Aug 26 10:06:59 2022].388132 Open failed for OGR connection in layer `rm_trace'. -- www.postholer.com From bjorn.harrtell at gmail.com Tue Aug 30 09:42:36 2022 From: bjorn.harrtell at gmail.com (=?UTF-8?Q?Bj=C3=B6rn_Harrtell?=) Date: Tue, 30 Aug 2022 18:42:36 +0200 Subject: [MapServer-dev] Accessing FlatGeoBuf (.fgb) in S3 bucket? In-Reply-To: <9f56750b-8050-14a3-6cbe-917792924501@postholer.com> References: <9f56750b-8050-14a3-6cbe-917792924501@postholer.com> Message-ID: Hi Scott, The OGR method should work but it might be confusing about naming of file vs specified in DATA. Does it work if you omit the DATA parameter or set it to the same name as the file name (possibly without extension)? The new native FlatGeobuf driver ("CONNECTIONTYPE flatgeobuf") only supports local file access. While it could possibly be extended to support access via HTTP/HTTPS that would be non-trivial work and I'm not sure it's worth it because the overhead of going through OGR is likely insignificant when you have network I/O involved. PS. I don't quite agree that it's the whole point of the format. :) Den tis 30 aug. 2022 kl 16:49 skrev Scott : > Using mapserver 7.6 or 8rc1 I've been unable to serve .fgb from an S3 > bucket. Local disk works fine as does ogrinfo on S3 .fgb. COG raster > data works fine off S3. > > Accessing .fgb from cloud storage seems to be the whole point of the > .fgb format. So, I'm very curious if I'm doing something wrong or is it > by design. > > > Map file configs: > > v8rc1: > CONNECTIONTYPE flatgeobuf > DATA "/vsis3/bucket/path/data.fgb" > > v7.6.4 > CONNECTIONTYPE OGR > CONNECTION "/vsis3/bucket/path/data.fgb" > DATA "rm_trace" > > v8rc ms_error log: > [Fri Aug 26 10:24:13 2022].854479 msDrawMap(): Image handling error. > Failed to draw layer named 'rm_trace'. > > v7.6.4 ms_error log > [Fri Aug 26 10:06:59 2022].388096 msOGRFileOpen(): OGR error. Open > failed for OGR connection in layer `rm_trace'. File not found or > unsupported format. Check server logs. > [Fri Aug 26 10:06:59 2022].388132 Open failed for OGR connection in > layer `rm_trace'. > > -- > www.postholer.com > _______________________________________________ > 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 jmckenna at gatewaygeomatics.com Tue Aug 30 10:04:38 2022 From: jmckenna at gatewaygeomatics.com (Jeff McKenna) Date: Tue, 30 Aug 2022 14:04:38 -0300 Subject: [MapServer-dev] rc2 this Friday Message-ID: <6ffabea4-6588-a026-8914-1f6323ed8455@gatewaygeomatics.com> Hi all! We've had some great feedback on RC1, so we're on schedule for an 8.0.0-rc2 this coming Friday. (I spent a few days of effort on setting up a !BOX! token msautotest, on several machines, so 20 years from now we don't have to face this again for the MapServer 16.0 release, ha) Thanks! -jeff -- Jeff McKenna GatewayGeo: Developers of MS4W, MapServer Consulting and Training co-founder of FOSS4G http://gatewaygeo.com/ From public at postholer.com Tue Aug 30 10:22:24 2022 From: public at postholer.com (Scott) Date: Tue, 30 Aug 2022 10:22:24 -0700 Subject: [MapServer-dev] Accessing FlatGeoBuf (.fgb) in S3 bucket? In-Reply-To: References: <9f56750b-8050-14a3-6cbe-917792924501@postholer.com> Message-ID: Thanks for the response Bjorn! Using this without DATA, still returns the same error: CONNECTIONTYPE OGR CONNECTION "/vsis3/bucket/path/traceseg.fgb" Ogrinfo works fine, COG works fine, all aws keys/pw set. .fgb with it's range requests is ideally suited for cloud storage/retrieval, like COG for raster. COG/.fgb are the perfect pair for cloud raster/vector data sources. Yet, I can't get .fgb to work within a .map file. Ugh! v8 rc1 ms_error message: [Tue Aug 30 09:53:20 2022].395601 msOGRFileOpen(): OGR error. Open failed for OGR connection in layer `traceseg'. File not found or unsupported format. Check server logs. [Tue Aug 30 09:53:20 2022].395617 Open failed for OGR connection in layer `traceseg'. [Tue Aug 30 09:53:20 2022].395625 msDrawMap(): Image handling error. Failed to draw layer named 'traceseg'. Thanks again! On 8/30/22 09:42, Bj?rn Harrtell wrote: > Hi Scott, > > The OGR method should work but it might be confusing about naming of > file?vs specified in DATA. Does it work if you omit the DATA parameter > or set it to the same name as the file name (possibly without extension)? > > The new native FlatGeobuf driver ("CONNECTIONTYPE flatgeobuf") only > supports local file access. While it could possibly be extended to > support access via HTTP/HTTPS that would be non-trivial work and I'm not > sure it's worth it because the overhead of going through OGR is likely > insignificant when you have network I/O involved. > > PS. I don't quite agree that it's the whole point of the format. :) > > Den tis 30 aug. 2022 kl 16:49 skrev Scott >: > > Using mapserver 7.6 or 8rc1 I've been unable to serve .fgb from an S3 > bucket. Local disk works fine as does ogrinfo on S3 .fgb. COG raster > data works fine off S3. > > Accessing .fgb from cloud storage seems to be the whole point of the > .fgb format. So, I'm very curious if I'm doing something wrong or is it > by design. > > > Map file configs: > > v8rc1: > CONNECTIONTYPE flatgeobuf > DATA "/vsis3/bucket/path/data.fgb" > > v7.6.4 > CONNECTIONTYPE OGR > CONNECTION "/vsis3/bucket/path/data.fgb" > DATA "rm_trace" > > v8rc ms_error log: > [Fri Aug 26 10:24:13 2022].854479 msDrawMap(): Image handling error. > Failed to draw layer named 'rm_trace'. > > v7.6.4 ms_error log > [Fri Aug 26 10:06:59 2022].388096 msOGRFileOpen(): OGR error. Open > failed for OGR connection in layer `rm_trace'.? File not found or > unsupported format. Check server logs. > [Fri Aug 26 10:06:59 2022].388132 Open failed for OGR connection in > layer `rm_trace'. > > -- > www.postholer.com > _______________________________________________ > MapServer-dev mailing list > MapServer-dev at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapserver-dev > > From bjorn.harrtell at gmail.com Tue Aug 30 10:50:36 2022 From: bjorn.harrtell at gmail.com (=?UTF-8?Q?Bj=C3=B6rn_Harrtell?=) Date: Tue, 30 Aug 2022 19:50:36 +0200 Subject: [MapServer-dev] Accessing FlatGeoBuf (.fgb) in S3 bucket? In-Reply-To: References: <9f56750b-8050-14a3-6cbe-917792924501@postholer.com> Message-ID: Hmm strange indeed! Not sure what/where but still feels like there is a bug somewhere to me. Feel free to file your findings as an issue at https://github.com/MapServer/MapServer and I (or someone else) will hopefully find some time to look into it. Den tis 30 aug. 2022 kl 19:22 skrev Scott : > Thanks for the response Bjorn! > > Using this without DATA, still returns the same error: > > CONNECTIONTYPE OGR > CONNECTION "/vsis3/bucket/path/traceseg.fgb" > > Ogrinfo works fine, COG works fine, all aws keys/pw set. > > .fgb with it's range requests is ideally suited for cloud > storage/retrieval, like COG for raster. COG/.fgb are the perfect pair > for cloud raster/vector data sources. Yet, I can't get .fgb to work > within a .map file. Ugh! > > v8 rc1 ms_error message: > [Tue Aug 30 09:53:20 2022].395601 msOGRFileOpen(): OGR error. Open > failed for OGR connection in layer `traceseg'. File not found or > unsupported format. Check server logs. > [Tue Aug 30 09:53:20 2022].395617 Open failed for OGR connection in > layer `traceseg'. > > [Tue Aug 30 09:53:20 2022].395625 msDrawMap(): Image handling error. > Failed to draw layer named 'traceseg'. > > Thanks again! > > > On 8/30/22 09:42, Bj?rn Harrtell wrote: > > Hi Scott, > > > > The OGR method should work but it might be confusing about naming of > > file vs specified in DATA. Does it work if you omit the DATA parameter > > or set it to the same name as the file name (possibly without extension)? > > > > The new native FlatGeobuf driver ("CONNECTIONTYPE flatgeobuf") only > > supports local file access. While it could possibly be extended to > > support access via HTTP/HTTPS that would be non-trivial work and I'm not > > sure it's worth it because the overhead of going through OGR is likely > > insignificant when you have network I/O involved. > > > > PS. I don't quite agree that it's the whole point of the format. :) > > > > Den tis 30 aug. 2022 kl 16:49 skrev Scott > >: > > > > Using mapserver 7.6 or 8rc1 I've been unable to serve .fgb from an S3 > > bucket. Local disk works fine as does ogrinfo on S3 .fgb. COG raster > > data works fine off S3. > > > > Accessing .fgb from cloud storage seems to be the whole point of the > > .fgb format. So, I'm very curious if I'm doing something wrong or is > it > > by design. > > > > > > Map file configs: > > > > v8rc1: > > CONNECTIONTYPE flatgeobuf > > DATA "/vsis3/bucket/path/data.fgb" > > > > v7.6.4 > > CONNECTIONTYPE OGR > > CONNECTION "/vsis3/bucket/path/data.fgb" > > DATA "rm_trace" > > > > v8rc ms_error log: > > [Fri Aug 26 10:24:13 2022].854479 msDrawMap(): Image handling error. > > Failed to draw layer named 'rm_trace'. > > > > v7.6.4 ms_error log > > [Fri Aug 26 10:06:59 2022].388096 msOGRFileOpen(): OGR error. Open > > failed for OGR connection in layer `rm_trace'. File not found or > > unsupported format. Check server logs. > > [Fri Aug 26 10:06:59 2022].388132 Open failed for OGR connection in > > layer `rm_trace'. > > > > -- > > www.postholer.com > > _______________________________________________ > > 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: From sethg at geographika.co.uk Wed Aug 31 12:45:27 2022 From: sethg at geographika.co.uk (Seth G) Date: Wed, 31 Aug 2022 21:45:27 +0200 Subject: [MapServer-dev] Random MapServer FOSS4G Development Notes Message-ID: <1e0ba706-cbbe-4b0f-bd04-f8ba6142c58e@www.fastmail.com> Hi devs, Some random notes from discussions with various MapServer users and devs at FOSS4G. It might help drive discussions at a future PSC meeting. - OGC Maps API would ideally be the next big MapServer feature, but this would require developers and funding - The R language is popular in the data science community. SWIG supports R so R-MapScript bindings could possibly be added in a future version. I can send a message to the users-list to gauge interest. - MapServer is likely to be used as the rendering engine for the pygeoapi backend. - Having to add TEMPLATE "ttt" to layers seems strange to new users. Maybe something to look at removing or replacing? - Both CGI and FastCGI are used in production deployments. FastCGI usage is unaffected by the warm-up times for connecting to proj.db in newer versions of PROJ, however only CGI can be used in Amazon Lambda deployments. If no reprojections are required and inline projections are used, then it may be possible to skip this connection (paraphrasing - and possible a misunderstanding on my part, but it could be something to investigate). - From speaking to users, there are a few misunderstandings and gaps in docs/tutorials, including: - how to set up cloud deployments of MapServer - how multiple Mapfiles are run from a single MapServer instance (there is no overhead in having several Mapfiles) - no tutorials on OGC Features setup - there are many hidden cartographic features (thanks Lars for your talk that highlighted these!) Finally, people are very keen to try out MapServer 8.0, and lots of people are already using that branch. Feel free to comment or add to any of the above. Seth -- web:https://geographika.net twitter: @geographika