From bob.basques at ci.stpaul.mn.us  Wed Feb  1 17:25:46 2023
From: bob.basques at ci.stpaul.mn.us (Basques, Bob (CI-StPaul))
Date: Thu, 2 Feb 2023 01:25:46 +0000
Subject: [MapServer-users] Twin Cities Local OSGeo Chapter Meeting for Feb
 2023
Message-ID: <45750065-0396-4090-8569-50BF0FC2A76C@ci.stpaul.mn.us>

All,

Just sending out a request for presenter or presenters for our next virtual meeting on Feb 8th, 2023

Time: 4:30 pm CDT



Anything Geo related.   I?ll take care of setting up the presentation, and recording of the session, etc.

Thanks

Bobb



Get me in Teams<https://teams.microsoft.com/l/chat/0/0?users=bob.basques at ci.stpaul.mn.us>
PW19-S295-C024


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230202/5e750251/attachment.htm>

From Marcel.Clausen at swisstopo.ch  Thu Feb  2 01:27:44 2023
From: Marcel.Clausen at swisstopo.ch (Marcel.Clausen at swisstopo.ch)
Date: Thu, 2 Feb 2023 09:27:44 +0000
Subject: [MapServer-users] wms time validation of time parameter against
 timeextent gives unexpected results
Message-ID: <dc866283280b45bcb334e916aa296b6b@swisstopo.ch>


Dear all

We have the following question concerning the configuration and usage of time enabled wms layers.

We are using?the following metadata section for a time-enabled layer:

? ? METADATA
? ? ? ? "wms_enable_request" "*"
? ? ? ? "wms_title" "lubis_bildstreifen"
? ? ? ? "wms_extent" "2100000 1050000 2850000 1400000"
? ? ? ? "wms_timeextent" "2005/2022"
? ? ? ? "wms_timeitem" "flugdatum" # this is a date column in postgres
? ? END


The time precision/resolution of the timeextent has to be set as year.

The validation of the time parameter against the time extent with year precision gives some strange results. We were using the following getmap request for the tests:  

localhost:7777/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022

parameter:		time=2005
result: 			returns all features of 2005
expected result:	ok

parameter:		time=2022
result: 			returns all features of 2022
expected result:	ok

parameter:		time=2023
result: 			returns ServiceException [1]
expected result:	ok

parameter:		time=2022-01-01
result: 			returns ServiceException [2]
expected result:	we would expect this to be a valid timestamp

parameter:		time=2022-01-01/2022-12-31
result: 			returns ServiceException [3]
expected result:	we would expect this to be a valid timestamp

It seems that if the precision of the time parameter is of YYYY-MM or YYYY-MM-TT the upper bound of the defined timextent 2005/2022 is not respected correctly.
We got the same result with the timextent defined  as: 2005/2022/P1Y

our mapserver version is:
<!--  MapServer version 7.6.4 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE  -->

Does someone have some insights or hints?

Best regards 
Clausen Marcel

[1]
<ServiceException code="InvalidDimensionValue">msWMSApplyTime: WMS server error. Time value(s) 2023 given is invalid or outside the time extent defined (2005/2022).</ServiceException>

[2]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01 given is invalid or outside the time extent defined (2005/2022). </ServiceException>

[3]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022). </ServiceException>








      

From jmckenna at gatewaygeomatics.com  Fri Feb  3 05:52:46 2023
From: jmckenna at gatewaygeomatics.com (Jeff McKenna)
Date: Fri, 3 Feb 2023 09:52:46 -0400
Subject: [MapServer-users] Fwd: pygeoapi 0.14.0 released
In-Reply-To: <CAFWXLWUnxcazwjP0_RkDuuc42w23n8a6K5kHUy8gbyw8Qd6eWQ@mail.gmail.com>
References: <CAFWXLWUnxcazwjP0_RkDuuc42w23n8a6K5kHUy8gbyw8Qd6eWQ@mail.gmail.com>
Message-ID: <777b7e97-43a0-1d00-9f00-4b66aa653fdb@gatewaygeomatics.com>

Super news (below) from the pygeoapi team, MapServer MapScript support....


-------- Forwarded Message --------



The pygeoapi team announces the release of pygeoapi 0.14.0.

This release provides new support for OGC API - Maps draft specification,
improvement to OGC API - Tiles support,
numerous bugfixes

Source and binary downloads
----------------------------------------

The source code is available at:https://pygeoapi.io/download 
<https://pygeoapi.io/download>

PyPI packages are available at:https://pypi.org/project/pygeoapi 
<https://pypi.org/project/pygeoapi>

Version 0.14.0 (2023-02-03)
---------------------------

- add support for OGC API - Maps (MapServer MapScript and WMS Facade 
backends)
- update OGC API - Tiles support
- fix various Starlette front end issues
- update reuse of OpenAPI generation for downstream applications
- autodetect SQLiteGPKG geometry columns, fix provider get_fields JSON 
Schema types
- update to Ubuntu jammy in Docker image
- fix field typing in CSV and GeoJSON feature providers
- add 413 support for providers
- add links to /processes endpoint
- update all string interpolations to f-string notation

All contributions are always welcome.

The pygeoapi team

https://pygeoapi.io  <https://pygeoapi.io>



From sdlime at gmail.com  Mon Feb  6 08:48:26 2023
From: sdlime at gmail.com (Steve Lime)
Date: Mon, 6 Feb 2023 10:48:26 -0600
Subject: [MapServer-users] wms time validation of time parameter against
 timeextent gives unexpected results
In-Reply-To: <dc866283280b45bcb334e916aa296b6b@swisstopo.ch>
References: <dc866283280b45bcb334e916aa296b6b@swisstopo.ch>
Message-ID: <CAMrKZ9_8XHMrem5MghDCX7MwEibsf6OKKv0OCA3z-JxRbX9wBA@mail.gmail.com>

Does WMS 1.1 behave the same? I suppose it comes down to how 2022 is
interpreted as part of a range, I would have expected it would mean any
date in that year. Sounds like it's behaving like strictly less than
2022-01-01. What happens if you set the range using full dates, so
something like: 20050101/20221231?

--Steve

On Thu, Feb 2, 2023 at 3:33 AM Clausen Marcel via MapServer-users <
mapserver-users at lists.osgeo.org> wrote:

>
> Dear all
>
> We have the following question concerning the configuration and usage of
> time enabled wms layers.
>
> We are using the following metadata section for a time-enabled layer:
>
>     METADATA
>         "wms_enable_request" "*"
>         "wms_title" "lubis_bildstreifen"
>         "wms_extent" "2100000 1050000 2850000 1400000"
>         "wms_timeextent" "2005/2022"
>         "wms_timeitem" "flugdatum" # this is a date column in postgres
>     END
>
>
> The time precision/resolution of the timeextent has to be set as year.
>
> The validation of the time parameter against the time extent with year
> precision gives some strange results. We were using the following getmap
> request for the tests:
>
>
> localhost:7777/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022
>
> parameter:              time=2005
> result:                         returns all features of 2005
> expected result:        ok
>
> parameter:              time=2022
> result:                         returns all features of 2022
> expected result:        ok
>
> parameter:              time=2023
> result:                         returns ServiceException [1]
> expected result:        ok
>
> parameter:              time=2022-01-01
> result:                         returns ServiceException [2]
> expected result:        we would expect this to be a valid timestamp
>
> parameter:              time=2022-01-01/2022-12-31
> result:                         returns ServiceException [3]
> expected result:        we would expect this to be a valid timestamp
>
> It seems that if the precision of the time parameter is of YYYY-MM or
> YYYY-MM-TT the upper bound of the defined timextent 2005/2022 is not
> respected correctly.
> We got the same result with the timextent defined  as: 2005/2022/P1Y
>
> our mapserver version is:
> <!--  MapServer version 7.6.4 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML
> SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO
> SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI
> SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER
> SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER
> SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG
> INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE  -->
>
> Does someone have some insights or hints?
>
> Best regards
> Clausen Marcel
>
> [1]
> <ServiceException code="InvalidDimensionValue">msWMSApplyTime: WMS server
> error. Time value(s) 2023 given is invalid or outside the time extent
> defined (2005/2022).</ServiceException>
>
> [2]
> <ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server
> error. Time value(s) 2022-01-01 given is invalid or outside the time extent
> defined (2005/2022). </ServiceException>
>
> [3]
> <ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server
> error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the
> time extent defined (2005/2022). </ServiceException>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230206/a4217f6b/attachment.htm>

From bob.basques at ci.stpaul.mn.us  Mon Feb  6 13:43:26 2023
From: bob.basques at ci.stpaul.mn.us (Basques, Bob (CI-StPaul))
Date: Mon, 6 Feb 2023 21:43:26 +0000
Subject: [MapServer-users] Twin Cities Local OSGeo Chapter Meeting for Feb
 2023
Message-ID: <DM8PR09MB63428E07C4A7CBA87EE461A4F7DA9@DM8PR09MB6342.namprd09.prod.outlook.com>

All,

No takers on presenting for this months meeting.   Going with a face to face meeting at Keg and Case.

928 7th Street West
Saint Paul MN, 55102


Time 4:30 pm.   Feb. 8th

Upstairs in one of the sitting areas.





Bobb



My machine - - - PW19-S295-C024

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 15405 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230206/1bdd2b9c/attachment.bin>

From Marcel.Clausen at swisstopo.ch  Tue Feb  7 05:37:27 2023
From: Marcel.Clausen at swisstopo.ch (Marcel.Clausen at swisstopo.ch)
Date: Tue, 7 Feb 2023 13:37:27 +0000
Subject: [MapServer-users] wms time validation of time parameter against
 timeextent gives unexpected results
In-Reply-To: <CAMrKZ9_8XHMrem5MghDCX7MwEibsf6OKKv0OCA3z-JxRbX9wBA@mail.gmail.com>
References: <dc866283280b45bcb334e916aa296b6b@swisstopo.ch>,
 <CAMrKZ9_8XHMrem5MghDCX7MwEibsf6OKKv0OCA3z-JxRbX9wBA@mail.gmail.com>
Message-ID: <96c3465e974b4338823e94b766c9b768@swisstopo.ch>

Hello Steve


Thank you for your response,
we would have expected that too.

with wms 1.1 the service response is the same.

with this metadata "wms_timeextent" "2005/2022"
the service response is:

http://localhost:7777/local/?SERVICE=WMS&VERSION=1.1.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&SRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022-01-01/2022-12-31

<?xml version='1.0' encoding="UTF-8" standalone="no" ?>
<!DOCTYPE ServiceExceptionReport SYSTEM "http://schemas.opengis.net/wms/1.1.0/exception_1_1_0.dtd">
<ServiceExceptionReport version="1.1.0">
<ServiceException code="InvalidDimensionValue">
msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022).
</ServiceException>
</ServiceExceptionReport>

The only work-around we found so far is to set the time-range in the metadata with a date precision of day:
"wms_timeextent" "2005-01-01/2022-12-31" but then in the getcap we would have this information:

<Dimension name="time" units="ISO8601" nearestValue="0">2005-01-01/2022-12-31</Dimension>

which is not representing the real nature of this dataset, the time resolution here should be a year.

Best regards
Marcel



________________________________
Von: Steve Lime <sdlime at gmail.com>
Gesendet: Montag, 6. Februar 2023 17:48:26
An: Clausen Marcel swisstopo
Cc: mapserver-users at lists.osgeo.org
Betreff: Re: [MapServer-users] wms time validation of time parameter against timeextent gives unexpected results

Does WMS 1.1 behave the same? I suppose it comes down to how 2022 is interpreted as part of a range, I would have expected it would mean any date in that year. Sounds like it's behaving like strictly less than 2022-01-01. What happens if you set the range using full dates, so something like: 20050101/20221231?

--Steve

On Thu, Feb 2, 2023 at 3:33 AM Clausen Marcel via MapServer-users <mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>> wrote:

Dear all

We have the following question concerning the configuration and usage of time enabled wms layers.

We are using the following metadata section for a time-enabled layer:

    METADATA
        "wms_enable_request" "*"
        "wms_title" "lubis_bildstreifen"
        "wms_extent" "2100000 1050000 2850000 1400000"
        "wms_timeextent" "2005/2022"
        "wms_timeitem" "flugdatum" # this is a date column in postgres
    END


The time precision/resolution of the timeextent has to be set as year.

The validation of the time parameter against the time extent with year precision gives some strange results. We were using the following getmap request for the tests:

localhost:7777/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022

parameter:              time=2005
result:                         returns all features of 2005
expected result:        ok

parameter:              time=2022
result:                         returns all features of 2022
expected result:        ok

parameter:              time=2023
result:                         returns ServiceException [1]
expected result:        ok

parameter:              time=2022-01-01
result:                         returns ServiceException [2]
expected result:        we would expect this to be a valid timestamp

parameter:              time=2022-01-01/2022-12-31
result:                         returns ServiceException [3]
expected result:        we would expect this to be a valid timestamp

It seems that if the precision of the time parameter is of YYYY-MM or YYYY-MM-TT the upper bound of the defined timextent 2005/2022 is not respected correctly.
We got the same result with the timextent defined  as: 2005/2022/P1Y

our mapserver version is:
<!--  MapServer version 7.6.4 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE  -->

Does someone have some insights or hints?

Best regards
Clausen Marcel

[1]
<ServiceException code="InvalidDimensionValue">msWMSApplyTime: WMS server error. Time value(s) 2023 given is invalid or outside the time extent defined (2005/2022).</ServiceException>

[2]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01 given is invalid or outside the time extent defined (2005/2022). </ServiceException>

[3]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022). </ServiceException>









_______________________________________________
MapServer-users mailing list
MapServer-users at lists.osgeo.org<mailto:MapServer-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/mapserver-users


From gkvoelkl at nelson-games.de  Tue Feb  7 06:08:52 2023
From: gkvoelkl at nelson-games.de (=?utf-8?Q?Gerhard_V=C3=B6lkl?=)
Date: Tue, 7 Feb 2023 15:08:52 +0100
Subject: [MapServer-users] Using getMetadata with xml file
Message-ID: <0B717CB6-5132-4186-A908-FF2C3B1FECD7@nelson-games.de>

Hello,

I am looking for an getMetadata example

I want to call mapserver to get metadata xml file

Example:

https://mapservice.test.org/cgi-bin/mapserv?map=/data/ows/maps/metatest.map&request=GetMetadata&layer=testlayer

In the map file I used this
 
 'ows_metadataurl_href' "https://mapservice.test.org/data/Test.XML"

But it does not work.

Any examples. Perhaps with example xml file
 
 
Best Regards Gerhard

Von meinem iPad gesendet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230207/8e853977/attachment.htm>

From sethg at geographika.co.uk  Tue Feb  7 06:40:43 2023
From: sethg at geographika.co.uk (Seth G)
Date: Tue, 07 Feb 2023 15:40:43 +0100
Subject: [MapServer-users] Using getMetadata with xml file
In-Reply-To: <0B717CB6-5132-4186-A908-FF2C3B1FECD7@nelson-games.de>
References: <0B717CB6-5132-4186-A908-FF2C3B1FECD7@nelson-games.de>
Message-ID: <60a67a4d-76aa-4975-92c2-5cf99de3b0ff@app.fastmail.com>

Hi,

Did you set the metadata at the LAYER level?

LAYER
  NAME "testlayer"
  METADATA
    'ows_metadataurl_href' "https://mapservice.test.org/data/Test.XML"
  END
END

Then a request to https://mapservice.test.org/cgi-bin/mapserv?map=/data/ows/maps/metatest.map&request=GetMetadata&layer=testlayer should return the following HTTP response:

Status: 301 Moved Permanently
Location: D:\TFS\PublicLighting\Main\Python\plpy\mapfiles\generated\test.xml


Seth

--
web:https://geographika.net
twitter: @geographika

On Tue, Feb 7, 2023, at 3:08 PM, Gerhard V?lkl wrote:
> 
> Hello,
> __
> _I am looking for an getMetadata example_
> __
> _I want to call mapserver to get metadata xml file_
> __
> _Example:_
> __
> _https://mapservice.test.org/cgi-bin/mapserv?map=/data/ows/maps/metatest.map&request=GetMetadata&layer=testlayer_
> __
> _In the map file I used this_
>  
>  'ows_metadataurl_href' "_https://mapservice.test.org/data/Test.XML_"
> 
> But it does not work.
> 
> Any examples. Perhaps with example xml file
> 
>  
>  
> Best Regards Gerhard
> 
> Von meinem iPad gesendet
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230207/1de3be90/attachment.htm>

From Sylvia.Preuss at obk.de  Tue Feb  7 23:23:30 2023
From: Sylvia.Preuss at obk.de (=?iso-8859-1?Q?Preu=DF=2C_Sylvia?=)
Date: Wed, 8 Feb 2023 07:23:30 +0000
Subject: [MapServer-users] Two regular expressions
In-Reply-To: <8b3046f5d26e4b6cbb7dc02b9321cecc@obk.de>
References: <8b3046f5d26e4b6cbb7dc02b9321cecc@obk.de>
Message-ID: <827ec68a396e4431aa6d4e480dbe2d06@obk.de>

Hello,

is it possible to do something like that with a regular expression
MAP...
EXPRESSION ('[LANGUAGE]' eq 'GERMAN' OR '[LANGUAGE]' eq 'FRENCH')?
...END

my regular expressions include ^ and $:

EXPRESSION /^RMA$/
EXPRESSION /^RENC$/

Thanks
sylviaobk

________________________________

Der E-Mail-Dienst des Oberbergischen Kreises dient ausschlie?lich der dienstlichen Kommunikation.
Senden Sie deshalb keine E-Mails privaten Inhalts an E-Mail-Adressen des Oberbergischen Kreises.
Es wird darauf hingewiesen, dass neben der Person, an die Ihre E-Mail gerichtet ist, auch deren Vertretung im Amt einen unmittelbaren Zugriff auf Ihre Nachricht hat. F?r Berufsgeheimnistr?ger und besondere Funktionstr?ger gelten abweichende Regelungen.
Es wird au?erdem darauf hingewiesen, dass die Kommunikation per E-Mail ohne Authentifizierung und Verschl?sselung unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die M?glichkeit der Kenntnisnahme und Manipulation besteht.
Es wird deshalb keine Verantwortung f?r den Inhalt dieser Nachricht ?bernommen, da eine Manipulation nicht ausgeschlossen werden kann.
Obwohl alle angemessenen Vorkehrungen getroffen wurden, um sicherzustellen, dass Anlagen dieser E-Mail virusgepr?ft sind, wird empfohlen, anh?ngende Dateien vor dem ?ffnen durch Ihr eigenes Virus-Programm zu pr?fen, da keinerlei Haftung f?r Sch?den ?bernommen wird, die infolge etwaiger Software-Viren entstehen k?nnten.
Der Inhalt dieser E-Mail ist ausschlie?lich f?r die bezeichnete Person bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertretung sein sollten, beachten Sie bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. In diesem Fall wird darum gebeten, sich mit der absendenden Person der E-Mail in Verbindung zu setzen.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230208/f531e787/attachment.htm>

From gkvoelkl at nelson-games.de  Tue Feb  7 23:41:18 2023
From: gkvoelkl at nelson-games.de (=?utf-8?Q?Gerhard_V=C3=B6lkl?=)
Date: Wed, 8 Feb 2023 08:41:18 +0100
Subject: [MapServer-users] Using getMetadata with xml file
In-Reply-To: <60a67a4d-76aa-4975-92c2-5cf99de3b0ff@app.fastmail.com>
References: <60a67a4d-76aa-4975-92c2-5cf99de3b0ff@app.fastmail.com>
Message-ID: <D98074D5-D7CD-450B-805D-0DE326D227AD@nelson-games.de>

An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230208/682a3d19/attachment.htm>

From lars.schylberg at saabgroup.com  Wed Feb  8 00:06:30 2023
From: lars.schylberg at saabgroup.com (Schylberg Lars)
Date: Wed, 8 Feb 2023 08:06:30 +0000
Subject: [MapServer-users] [EXTERNAL]  Two regular expressions
In-Reply-To: <827ec68a396e4431aa6d4e480dbe2d06@obk.de>
References: <8b3046f5d26e4b6cbb7dc02b9321cecc@obk.de>
 <827ec68a396e4431aa6d4e480dbe2d06@obk.de>
Message-ID: <40bd1e475ae044a1b2a3d16432a0a238@saabgroup.com>

Hi,

You need to use a CLASSITEM

LAYER
  ...
  CLASSITEM "LANGUAGE"

  CLASS
    EXPRESSION /^GERMAN$/
    ...
    EXPRESSION /^FRENCH$/
     ...
...

Have fun / Lars S.

From: MapServer-users <mapserver-users-bounces at lists.osgeo.org> On Behalf Of Preu?, Sylvia
Sent: den 8 februari 2023 08:24
To: 'mapserver-users at lists.osgeo.org' <mapserver-users at lists.osgeo.org>
Subject: [EXTERNAL] [MapServer-users] Two regular expressions

Hello,

is it possible to do something like that with a regular expression
MAP...
EXPRESSION ('[LANGUAGE]' eq 'GERMAN' OR '[LANGUAGE]' eq 'FRENCH')?
...END

my regular expressions include ^ and $:

EXPRESSION /^RMA$/
EXPRESSION /^RENC$/

Thanks
sylviaobk

________________________________

Der E-Mail-Dienst des Oberbergischen Kreises dient ausschlie?lich der dienstlichen Kommunikation.
Senden Sie deshalb keine E-Mails privaten Inhalts an E-Mail-Adressen des Oberbergischen Kreises.
Es wird darauf hingewiesen, dass neben der Person, an die Ihre E-Mail gerichtet ist, auch deren Vertretung im Amt einen unmittelbaren Zugriff auf Ihre Nachricht hat. F?r Berufsgeheimnistr?ger und besondere Funktionstr?ger gelten abweichende Regelungen.
Es wird au?erdem darauf hingewiesen, dass die Kommunikation per E-Mail ohne Authentifizierung und Verschl?sselung unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die M?glichkeit der Kenntnisnahme und Manipulation besteht.
Es wird deshalb keine Verantwortung f?r den Inhalt dieser Nachricht ?bernommen, da eine Manipulation nicht ausgeschlossen werden kann.
Obwohl alle angemessenen Vorkehrungen getroffen wurden, um sicherzustellen, dass Anlagen dieser E-Mail virusgepr?ft sind, wird empfohlen, anh?ngende Dateien vor dem ?ffnen durch Ihr eigenes Virus-Programm zu pr?fen, da keinerlei Haftung f?r Sch?den ?bernommen wird, die infolge etwaiger Software-Viren entstehen k?nnten.
Der Inhalt dieser E-Mail ist ausschlie?lich f?r die bezeichnete Person bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertretung sein sollten, beachten Sie bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. In diesem Fall wird darum gebeten, sich mit der absendenden Person der E-Mail in Verbindung zu setzen.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230208/1d19bc59/attachment.htm>

From steve.lime at state.mn.us  Wed Feb  8 06:36:45 2023
From: steve.lime at state.mn.us (Lime, Steve D (MNIT))
Date: Wed, 8 Feb 2023 14:36:45 +0000
Subject: [MapServer-users] [EXTERNAL]  Two regular expressions
In-Reply-To: <40bd1e475ae044a1b2a3d16432a0a238@saabgroup.com>
References: <8b3046f5d26e4b6cbb7dc02b9321cecc@obk.de>
 <827ec68a396e4431aa6d4e480dbe2d06@obk.de>
 <40bd1e475ae044a1b2a3d16432a0a238@saabgroup.com>
Message-ID: <DM6PR09MB4806611C9FC85064A9497FC5DAD89@DM6PR09MB4806.namprd09.prod.outlook.com>

You can also match either with something like:

  ^(GERMAN|FRENCH)$

A good resource for testing is https://www.regextester.com/ and there others out there too.

--Steve

From: MapServer-users <mapserver-users-bounces at lists.osgeo.org> On Behalf Of Schylberg Lars
Sent: Wednesday, February 8, 2023 2:07 AM
To: 'mapserver-users at lists.osgeo.org' <mapserver-users at lists.osgeo.org>
Subject: Re: [MapServer-users] [EXTERNAL] Two regular expressions

Hi,

You need to use a CLASSITEM

LAYER
  ...
  CLASSITEM "LANGUAGE"

  CLASS
    EXPRESSION /^GERMAN$/
    ...
    EXPRESSION /^FRENCH$/
     ...
...

Have fun / Lars S.

From: MapServer-users <mapserver-users-bounces at lists.osgeo.org<mailto:mapserver-users-bounces at lists.osgeo.org>> On Behalf Of Preu?, Sylvia
Sent: den 8 februari 2023 08:24
To: 'mapserver-users at lists.osgeo.org' <mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>>
Subject: [EXTERNAL] [MapServer-users] Two regular expressions

Hello,

is it possible to do something like that with a regular expression
MAP...
EXPRESSION ('[LANGUAGE]' eq 'GERMAN' OR '[LANGUAGE]' eq 'FRENCH')?
...END

my regular expressions include ^ and $:

EXPRESSION /^RMA$/
EXPRESSION /^RENC$/

Thanks
sylviaobk

________________________________

Der E-Mail-Dienst des Oberbergischen Kreises dient ausschlie?lich der dienstlichen Kommunikation.
Senden Sie deshalb keine E-Mails privaten Inhalts an E-Mail-Adressen des Oberbergischen Kreises.
Es wird darauf hingewiesen, dass neben der Person, an die Ihre E-Mail gerichtet ist, auch deren Vertretung im Amt einen unmittelbaren Zugriff auf Ihre Nachricht hat. F?r Berufsgeheimnistr?ger und besondere Funktionstr?ger gelten abweichende Regelungen.
Es wird au?erdem darauf hingewiesen, dass die Kommunikation per E-Mail ohne Authentifizierung und Verschl?sselung unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die M?glichkeit der Kenntnisnahme und Manipulation besteht.
Es wird deshalb keine Verantwortung f?r den Inhalt dieser Nachricht ?bernommen, da eine Manipulation nicht ausgeschlossen werden kann.
Obwohl alle angemessenen Vorkehrungen getroffen wurden, um sicherzustellen, dass Anlagen dieser E-Mail virusgepr?ft sind, wird empfohlen, anh?ngende Dateien vor dem ?ffnen durch Ihr eigenes Virus-Programm zu pr?fen, da keinerlei Haftung f?r Sch?den ?bernommen wird, die infolge etwaiger Software-Viren entstehen k?nnten.
Der Inhalt dieser E-Mail ist ausschlie?lich f?r die bezeichnete Person bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertretung sein sollten, beachten Sie bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. In diesem Fall wird darum gebeten, sich mit der absendenden Person der E-Mail in Verbindung zu setzen.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230208/a40f2553/attachment.htm>

From bob.basques at ci.stpaul.mn.us  Wed Feb  8 06:42:23 2023
From: bob.basques at ci.stpaul.mn.us (Basques, Bob (CI-StPaul))
Date: Wed, 8 Feb 2023 14:42:23 +0000
Subject: [MapServer-users] [REMINDER] Twin Cities Local OSGeo Chapter
 Meeting for Feb 2023
Message-ID: <DM8PR09MB6342D04CBF5B07FB91307FC6F7D89@DM8PR09MB6342.namprd09.prod.outlook.com>

All,

No takers on presenting for this months meeting.   Going with a face to face meeting at Keg and Case.

928 7th Street West
Saint Paul MN, 55102


Time 4:30 pm.   Feb. 8th

Upstairs in one of the sitting areas.





Bobb



My machine - - - PW19-S295-C024

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 24256 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230208/770e3298/attachment.bin>

From bob.basques at ci.stpaul.mn.us  Wed Feb  8 14:27:18 2023
From: bob.basques at ci.stpaul.mn.us (Basques, Bob (CI-StPaul))
Date: Wed, 8 Feb 2023 22:27:18 +0000
Subject: [MapServer-users] [REMINDER] Twin Cities Local OSGeo Chapter
 Meeting for Feb 2023
In-Reply-To: <DM8PR09MB6342D04CBF5B07FB91307FC6F7D89@DM8PR09MB6342.namprd09.prod.outlook.com>
References: <DM8PR09MB6342D04CBF5B07FB91307FC6F7D89@DM8PR09MB6342.namprd09.prod.outlook.com>
Message-ID: <DM8PR09MB6342B959A0FE98180255EAADF7D89@DM8PR09MB6342.namprd09.prod.outlook.com>

going to be a few min. late
________________________________
From: Basques, Bob (CI-StPaul)
Sent: Wednesday, February 8, 2023 8:42:23 AM
To: tcmug at lists.osgeo.org <tcmug at lists.osgeo.org>; geomoose-users-osgeo <geomoose-users at lists.osgeo.org>; mapserver-users at lists.osgeo.org <mapserver-users at lists.osgeo.org>
Subject: [REMINDER] Twin Cities Local OSGeo Chapter Meeting for Feb 2023


All,



No takers on presenting for this months meeting.   Going with a face to face meeting at Keg and Case.



928 7th Street West
Saint Paul MN, 55102





Time 4:30 pm.   Feb. 8th



Upstairs in one of the sitting areas.











Bobb







My machine - - - PW19-S295-C024


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230208/811adc91/attachment.htm>

From Sylvia.Preuss at obk.de  Thu Feb  9 01:16:09 2023
From: Sylvia.Preuss at obk.de (=?iso-8859-1?Q?Preu=DF=2C_Sylvia?=)
Date: Thu, 9 Feb 2023 09:16:09 +0000
Subject: [MapServer-users] [EXTERNAL]  Two regular expressions
In-Reply-To: <DM6PR09MB4806611C9FC85064A9497FC5DAD89@DM6PR09MB4806.namprd09.prod.outlook.com>
References: <8b3046f5d26e4b6cbb7dc02b9321cecc@obk.de>
 <827ec68a396e4431aa6d4e480dbe2d06@obk.de>
 <40bd1e475ae044a1b2a3d16432a0a238@saabgroup.com>
 <DM6PR09MB4806611C9FC85064A9497FC5DAD89@DM6PR09MB4806.namprd09.prod.outlook.com>
Message-ID: <0e17c47bb2014ab3bf1ac8b0f67650f7@obk.de>

Thank you very much.











Von: MapServer-users <mapserver-users-bounces at lists.osgeo.org> Im Auftrag von Lime, Steve D (MNIT) via MapServer-users
Gesendet: Mittwoch, 8. Februar 2023 15:37
An: Schylberg Lars <lars.schylberg at saabgroup.com>; mapserver-users at lists.osgeo.org
Betreff: Re: [MapServer-users] [EXTERNAL] Two regular expressions

You can also match either with something like:

  ^(GERMAN|FRENCH)$

A good resource for testing is https://www.regextester.com/ and there others out there too.

--Steve

From: MapServer-users <mapserver-users-bounces at lists.osgeo.org> On Behalf Of Schylberg Lars
Sent: Wednesday, February 8, 2023 2:07 AM
To: 'mapserver-users at lists.osgeo.org' <mapserver-users at lists.osgeo.org>
Subject: Re: [MapServer-users] [EXTERNAL] Two regular expressions

Hi,

You need to use a CLASSITEM

LAYER
  ...
  CLASSITEM "LANGUAGE"

  CLASS
    EXPRESSION /^GERMAN$/
    ...
    EXPRESSION /^FRENCH$/
     ...
...

Have fun / Lars S.

From: MapServer-users <mapserver-users-bounces at lists.osgeo.org<mailto:mapserver-users-bounces at lists.osgeo.org>> On Behalf Of Preu?, Sylvia
Sent: den 8 februari 2023 08:24
To: 'mapserver-users at lists.osgeo.org' <mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>>
Subject: [EXTERNAL] [MapServer-users] Two regular expressions

Hello,

is it possible to do something like that with a regular expression
MAP...
EXPRESSION ('[LANGUAGE]' eq 'GERMAN' OR '[LANGUAGE]' eq 'FRENCH')?
...END

my regular expressions include ^ and $:

EXPRESSION /^RMA$/
EXPRESSION /^RENC$/

Thanks
sylviaobk

________________________________

Der E-Mail-Dienst des Oberbergischen Kreises dient ausschlie?lich der dienstlichen Kommunikation.
Senden Sie deshalb keine E-Mails privaten Inhalts an E-Mail-Adressen des Oberbergischen Kreises.
Es wird darauf hingewiesen, dass neben der Person, an die Ihre E-Mail gerichtet ist, auch deren Vertretung im Amt einen unmittelbaren Zugriff auf Ihre Nachricht hat. F?r Berufsgeheimnistr?ger und besondere Funktionstr?ger gelten abweichende Regelungen.
Es wird au?erdem darauf hingewiesen, dass die Kommunikation per E-Mail ohne Authentifizierung und Verschl?sselung unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die M?glichkeit der Kenntnisnahme und Manipulation besteht.
Es wird deshalb keine Verantwortung f?r den Inhalt dieser Nachricht ?bernommen, da eine Manipulation nicht ausgeschlossen werden kann.
Obwohl alle angemessenen Vorkehrungen getroffen wurden, um sicherzustellen, dass Anlagen dieser E-Mail virusgepr?ft sind, wird empfohlen, anh?ngende Dateien vor dem ?ffnen durch Ihr eigenes Virus-Programm zu pr?fen, da keinerlei Haftung f?r Sch?den ?bernommen wird, die infolge etwaiger Software-Viren entstehen k?nnten.
Der Inhalt dieser E-Mail ist ausschlie?lich f?r die bezeichnete Person bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertretung sein sollten, beachten Sie bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. In diesem Fall wird darum gebeten, sich mit der absendenden Person der E-Mail in Verbindung zu setzen.
________________________________
________________________________

Der E-Mail-Dienst des Oberbergischen Kreises dient ausschlie?lich der dienstlichen Kommunikation.
Senden Sie deshalb keine E-Mails privaten Inhalts an E-Mail-Adressen des Oberbergischen Kreises.
Es wird darauf hingewiesen, dass neben der Person, an die Ihre E-Mail gerichtet ist, auch deren Vertretung im Amt einen unmittelbaren Zugriff auf Ihre Nachricht hat. F?r Berufsgeheimnistr?ger und besondere Funktionstr?ger gelten abweichende Regelungen.
Es wird au?erdem darauf hingewiesen, dass die Kommunikation per E-Mail ohne Authentifizierung und Verschl?sselung unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die M?glichkeit der Kenntnisnahme und Manipulation besteht.
Es wird deshalb keine Verantwortung f?r den Inhalt dieser Nachricht ?bernommen, da eine Manipulation nicht ausgeschlossen werden kann.
Obwohl alle angemessenen Vorkehrungen getroffen wurden, um sicherzustellen, dass Anlagen dieser E-Mail virusgepr?ft sind, wird empfohlen, anh?ngende Dateien vor dem ?ffnen durch Ihr eigenes Virus-Programm zu pr?fen, da keinerlei Haftung f?r Sch?den ?bernommen wird, die infolge etwaiger Software-Viren entstehen k?nnten.
Der Inhalt dieser E-Mail ist ausschlie?lich f?r die bezeichnete Person bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertretung sein sollten, beachten Sie bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. In diesem Fall wird darum gebeten, sich mit der absendenden Person der E-Mail in Verbindung zu setzen.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230209/454c63da/attachment.htm>

From mniemyjski at cloudferro.com  Thu Feb  9 01:55:02 2023
From: mniemyjski at cloudferro.com (Marcin Niemyjski)
Date: Thu, 9 Feb 2023 09:55:02 +0000
Subject: [MapServer-users] How to count quantity of S3 requests sent by
 mapserver while GetMap request
Message-ID: <AS1PR03MB814996C2596F8ACB32D0F122A8D99@AS1PR03MB8149.eurprd03.prod.outlook.com>


Hello,


after short break I coming back to you with another question.

I've got to check how many s3 requests is sent by mapserver to bucket containing WMS source data while performing GetMap requests.

Any recommendations on how to do that?

Best,
Marcin




[cid:a545b0b0-2736-4113-8933-f6c75c10fe13]<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>           Book time to meet with me<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230209/d38db562/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-usah4pyb.png
Type: image/png
Size: 528 bytes
Desc: Outlook-usah4pyb.png
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230209/d38db562/attachment.png>

From steve.lime at state.mn.us  Thu Feb  9 14:04:03 2023
From: steve.lime at state.mn.us (Lime, Steve D (MNIT))
Date: Thu, 9 Feb 2023 22:04:03 +0000
Subject: [MapServer-users] wms time validation of time parameter against
 timeextent gives unexpected results
In-Reply-To: <96c3465e974b4338823e94b766c9b768@swisstopo.ch>
References: <dc866283280b45bcb334e916aa296b6b@swisstopo.ch>,
 <CAMrKZ9_8XHMrem5MghDCX7MwEibsf6OKKv0OCA3z-JxRbX9wBA@mail.gmail.com>
 <96c3465e974b4338823e94b766c9b768@swisstopo.ch>
Message-ID: <DM6PR09MB48067E683DAD5DE4FBFA0DFBDAD99@DM6PR09MB4806.namprd09.prod.outlook.com>

So, if you turn on logging, what shows up in terms of Pg queries.

-----Original Message-----
From: MapServer-users <mapserver-users-bounces at lists.osgeo.org> On Behalf Of Clausen Marcel via MapServer-users
Sent: Tuesday, February 7, 2023 7:37 AM
To: sdlime at gmail.com
Cc: mapserver-users at lists.osgeo.org
Subject: Re: [MapServer-users] wms time validation of time parameter against timeextent gives unexpected results

Hello Steve


Thank you for your response,
we would have expected that too.

with wms 1.1 the service response is the same.

with this metadata "wms_timeextent" "2005/2022"
the service response is:

http://localhost:7777/local/?SERVICE=WMS&VERSION=1.1.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&SRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022-01-01/2022-12-31

<?xml version='1.0' encoding="UTF-8" standalone="no" ?> <!DOCTYPE ServiceExceptionReport SYSTEM "...">
<ServiceExceptionReport version="1.1.0"> <ServiceException code="InvalidDimensionValue">
msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022).
</ServiceException>
</ServiceExceptionReport>

The only work-around we found so far is to set the time-range in the metadata with a date precision of day:
"wms_timeextent" "2005-01-01/2022-12-31" but then in the getcap we would have this information:

<Dimension name="time" units="ISO8601" nearestValue="0">2005-01-01/2022-12-31</Dimension>

which is not representing the real nature of this dataset, the time resolution here should be a year.

Best regards
Marcel



________________________________
Von: Steve Lime <sdlime at gmail.com>
Gesendet: Montag, 6. Februar 2023 17:48:26
An: Clausen Marcel swisstopo
Cc: mapserver-users at lists.osgeo.org
Betreff: Re: [MapServer-users] wms time validation of time parameter against timeextent gives unexpected results

Does WMS 1.1 behave the same? I suppose it comes down to how 2022 is interpreted as part of a range, I would have expected it would mean any date in that year. Sounds like it's behaving like strictly less than 2022-01-01. What happens if you set the range using full dates, so something like: 20050101/20221231?

--Steve

On Thu, Feb 2, 2023 at 3:33 AM Clausen Marcel via MapServer-users <mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>> wrote:

Dear all

We have the following question concerning the configuration and usage of time enabled wms layers.

We are using the following metadata section for a time-enabled layer:

    METADATA
        "wms_enable_request" "*"
        "wms_title" "lubis_bildstreifen"
        "wms_extent" "2100000 1050000 2850000 1400000"
        "wms_timeextent" "2005/2022"
        "wms_timeitem" "flugdatum" # this is a date column in postgres
    END


The time precision/resolution of the timeextent has to be set as year.

The validation of the time parameter against the time extent with year precision gives some strange results. We were using the following getmap request for the tests:

localhost:7777/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022

parameter:              time=2005
result:                         returns all features of 2005
expected result:        ok

parameter:              time=2022
result:                         returns all features of 2022
expected result:        ok

parameter:              time=2023
result:                         returns ServiceException [1]
expected result:        ok

parameter:              time=2022-01-01
result:                         returns ServiceException [2]
expected result:        we would expect this to be a valid timestamp

parameter:              time=2022-01-01/2022-12-31
result:                         returns ServiceException [3]
expected result:        we would expect this to be a valid timestamp

It seems that if the precision of the time parameter is of YYYY-MM or YYYY-MM-TT the upper bound of the defined timextent 2005/2022 is not respected correctly.
We got the same result with the timextent defined  as: 2005/2022/P1Y

our mapserver version is:
<!--  MapServer version 7.6.4 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE  -->

Does someone have some insights or hints?

Best regards
Clausen Marcel

[1]
<ServiceException code="InvalidDimensionValue">msWMSApplyTime: WMS server error. Time value(s) 2023 given is invalid or outside the time extent defined (2005/2022).</ServiceException>

[2]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01 given is invalid or outside the time extent defined (2005/2022). </ServiceException>

[3]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022). </ServiceException>









_______________________________________________
MapServer-users mailing list
MapServer-users at lists.osgeo.org<mailto:MapServer-users at lists.osgeo.org>
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-users&data=05%7C01%7Csteve.lime%40state.mn.us%7C20a25ea5e6e1488c95a708db0910782a%7Ceb14b04624c445198f26b89c2159828c%7C0%7C0%7C638113738576533245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ha1sFKw7qRtLxB7ei0D%2FjhcGNTQlgwYz5U0WhLnN3Iw%3D&reserved=0
_______________________________________________
MapServer-users mailing list
MapServer-users at lists.osgeo.org
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-users&data=05%7C01%7Csteve.lime%40state.mn.us%7C20a25ea5e6e1488c95a708db0910782a%7Ceb14b04624c445198f26b89c2159828c%7C0%7C0%7C638113738576689260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iDvdDXh8CCndm%2BbmfJPK1XaU5o10%2Ff9L2vp1PbvYbMA%3D&reserved=0


From mniemyjski at cloudferro.com  Fri Feb 10 06:41:23 2023
From: mniemyjski at cloudferro.com (Marcin Niemyjski)
Date: Fri, 10 Feb 2023 14:41:23 +0000
Subject: [MapServer-users] Can Mapserver store .vrt / TileIndex.shp files in
 cache?
Message-ID: <AS1PR03MB8149F567A82E512E1B91C88BA8DE9@AS1PR03MB8149.eurprd03.prod.outlook.com>


Hello,

Can Mapserver store .vrt / TileIndex.shp files in cache so while connecting to layer Mapserver read vrt/tiletindex from cache and reach directyl to requested subdata?
Thanks,
Marcin



[cid:c3fe1e7e-d684-4ff4-86ed-adb7380bc84e]<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>           Book time to meet with me<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230210/25414b32/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-ehjyxfrm.png
Type: image/png
Size: 528 bytes
Desc: Outlook-ehjyxfrm.png
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230210/25414b32/attachment.png>

From mniemyjski at cloudferro.com  Fri Feb 10 08:27:02 2023
From: mniemyjski at cloudferro.com (Marcin Niemyjski)
Date: Fri, 10 Feb 2023 16:27:02 +0000
Subject: [MapServer-users] Multiple requests to s3 bucket to the same Tiff
 after GetMap request
Message-ID: <AS1PR03MB814919052981B7BB2CFAA827A8DE9@AS1PR03MB8149.eurprd03.prod.outlook.com>

Hello,
I wasn't happy with the time it took for the GetMap request to complete, so I decided to check apache's error logs. I realized that S3 Get request is performed multiple times and I have no idea why.

Below you can see GET request which appears in log file of one request 5 times.

[Fri Feb 10 15:49:45.456184 2023] [cgi:error] [pid 1300229] [client 127.0.0.1:37842] AH01215: > GET /DIAS/Sentinel-1-COG/SAR/GRD-COG/2022/03/01/S1A_IW_GRDH_1SDV_20220301T045236_20220301T045301_042123_0504C2_3E5D_COG.SAFE/measurement/s1a-iw-grd-vh-20220301t045236-20220301t045301-042123-0504c2-002.tiff HTTP/1.1\r: /usr/lib/cgi-bin/mapserv

The way my mapfile gets source raster data:

TileIndex -> VRT -> COG with Ground Control Points (this is caused by GCP)

I would be grateful if you could check full log file -> https://pastecode.io/s/xdyuay0f

Thanks,
Marcin




[cid:dd7197db-b623-4a72-8451-2d23a47f62f6]<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>           Book time to meet with me<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230210/76b7245c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-akft20vs.png
Type: image/png
Size: 528 bytes
Desc: Outlook-akft20vs.png
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230210/76b7245c/attachment.png>

From public at postholer.com  Fri Feb 10 08:37:34 2023
From: public at postholer.com (Scott)
Date: Fri, 10 Feb 2023 08:37:34 -0800
Subject: [MapServer-users] Multiple requests to s3 bucket to the same
 Tiff after GetMap request
In-Reply-To: <AS1PR03MB814919052981B7BB2CFAA827A8DE9@AS1PR03MB8149.eurprd03.prod.outlook.com>
References: <AS1PR03MB814919052981B7BB2CFAA827A8DE9@AS1PR03MB8149.eurprd03.prod.outlook.com>
Message-ID: <c198b21a-36c2-c497-34cb-1336093729bc@postholer.com>

That file appears to be a cloud optimized geotiff. If that's the case 
multiple gets is perfectly normal as it's possibly retrieving overviews.

I don't see a server return code, but if it's 206, everything is fine.

Additionally, you can open your dev tools in your browser (Ctrl+Shift+I) 
and watch how many bytes each request gets. With COG it should never be 
the whole file.

On 2/10/23 08:27, Marcin Niemyjski via MapServer-users wrote:
> Hello,
> I wasn't happy with the time it took for the GetMap request to complete, 
> so I decided to check apache's error logs. I realized that S3 Get 
> request is performed multiple times and I have no idea why.
> 
> Below you can see GET request which appears in log file of one request 5 
> times.
> 
> [Fri Feb 10 15:49:45.456184 2023] [cgi:error] [pid 1300229] [client 
> 127.0.0.1:37842] AH01215: > GET 
> /DIAS/Sentinel-1-COG/SAR/GRD-COG/2022/03/01/S1A_IW_GRDH_1SDV_20220301T045236_20220301T045301_042123_0504C2_3E5D_COG.SAFE/measurement/s1a-iw-grd-vh-20220301t045236-20220301t045301-042123-0504c2-002.tiff HTTP/1.1\r: /usr/lib/cgi-bin/mapserv
> 
> The way my mapfile gets source raster data:
> 
> TileIndex -> VRT -> COG with Ground Control Points (this is caused by GCP)
> 
> I would be grateful if you could check full log file -> 
> https://pastecode.io/s/xdyuay0f <https://pastecode.io/s/xdyuay0f>
> 
> Thanks,
> Marcin
> 
> 
> 
> 
> <https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature> 		Book time to meet with me <https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature> 	
> 
> 
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users


From bahbouba.909 at gmail.com  Fri Feb 10 13:07:03 2023
From: bahbouba.909 at gmail.com (Boubacar Bah)
Date: Fri, 10 Feb 2023 21:07:03 +0000
Subject: [MapServer-users] Asking help for urgences
Message-ID: <CALOg8kGDJsM_iLasZ0EPCRnF1f9f3bgxh7LJc-CGHxOeXbn8SA@mail.gmail.com>

hello Jeff McKenna it's been a long time since I post the same question but
without a satisfactory answer I have a problem with the tinyows server.  is
tinyows functional with the ms4w by what I have checked all the required
configurations but so far the problem cannot be solved.  I followed all the
steps detailed on your Site to save new data in the Frida database but in
vain.  but I think the server has problems because the tinyows site is not
even functional, here is the address http://www.tinyows.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230210/40e4dd98/attachment.htm>

From public at postholer.com  Fri Feb 10 13:18:49 2023
From: public at postholer.com (Scott)
Date: Fri, 10 Feb 2023 13:18:49 -0800
Subject: [MapServer-users] Asking help for urgences
In-Reply-To: <CALOg8kGDJsM_iLasZ0EPCRnF1f9f3bgxh7LJc-CGHxOeXbn8SA@mail.gmail.com>
References: <CALOg8kGDJsM_iLasZ0EPCRnF1f9f3bgxh7LJc-CGHxOeXbn8SA@mail.gmail.com>
Message-ID: <dc964c88-6639-d047-f0e6-8f0367a8d61f@postholer.com>

Looks like www.tinyows.org was abandoned in 2013 and re-registered in 2021.

I think what you're looking for is: https://mapserver.org/tinyows/


On 2/10/23 13:07, Boubacar Bah wrote:
> hello Jeff McKenna it's been a long time since I post the same question 
> but without a satisfactory answer I have a problem with the tinyows 
> server.? is tinyows functional with the ms4w by what I have checked all 
> the required configurations but so far the problem cannot be solved.? I 
> followed all the steps detailed on your Site to save new data in the 
> Frida database but in vain.? but I think the server has problems because 
> the tinyows site is not even functional, here is the address 
> http://www.tinyows.org <http://www.tinyows.org>
> 
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users


From Marcel.Clausen at swisstopo.ch  Sun Feb 12 23:41:27 2023
From: Marcel.Clausen at swisstopo.ch (Marcel.Clausen at swisstopo.ch)
Date: Mon, 13 Feb 2023 07:41:27 +0000
Subject: [MapServer-users] wms time validation of time parameter against
 timeextent gives unexpected results
In-Reply-To: <DM6PR09MB48067E683DAD5DE4FBFA0DFBDAD99@DM6PR09MB4806.namprd09.prod.outlook.com>
References: <dc866283280b45bcb334e916aa296b6b@swisstopo.ch>,
 <CAMrKZ9_8XHMrem5MghDCX7MwEibsf6OKKv0OCA3z-JxRbX9wBA@mail.gmail.com>
 <96c3465e974b4338823e94b766c9b768@swisstopo.ch>,
 <DM6PR09MB48067E683DAD5DE4FBFA0DFBDAD99@DM6PR09MB4806.namprd09.prod.outlook.com>
Message-ID: <a0114d43045a44459d4e3229cdafe269@swisstopo.ch>

Hello Steve


Sure with the logging enabled i get the following:


mapfile metadata:         "wms_timeextent" "2005/2022"

request: SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022-01-01/2022-12-31

log:

wms-bgdi_1  |  [warn] [pid 9229] mod_fcgid: stderr: msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022).
wms-bgdi_1  |  [warn] [pid 9229] mod_fcgid: stderr: freeLayer(): freeing layer at 0x557566f87510.
wms-bgdi_1  |  [warn] [pid 9229] mod_fcgid: stderr: msPostGISLayerIsOpen called.
wms-bgdi_1  | 172.26.0.1 - - [13/Feb/2023:07:23:28 +0000] "GET /local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022-01-01/2022-12-31 HTTP/1.1" 200 674


With this time extent definition nothing is being sent to the database. The time value is considered as invalid (outside the time extent) by the validation code -> InvalidDimensionValue.
https://github.com/MapServer/MapServer/blob/f3f05d4cf30af615d5f443a1c47c20b6117e52cb/mapwms.cpp#L268

If we increase the upper bound of the time extent by one year we get the following logs:

mapfile metadata:         "wms_timeextent" "2005/2023"

request: SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022-01-01/2022-12-31

logs:

msPostGISLayerWhichShapes query: select "resolution"::text,"flugdatum"::text,ST_AsBinary(("the_geom"),'NDR') as geom,"bildstreifen_nr"::text from (
    SELECT
       the_geom
        , filmart
        , firma
        , flugdatum
        , objectid
        , resolution
        , bildstreifen_nr
        , bildstreifen_nr as id
        , bgdi_flugjahr
        , area
        , gsd
        , toposhop_length
        , toposhop_start_x
        , toposhop_start_y
        , toposhop_end_x
        , toposhop_end_y
        , toposhop_date
        , goal
        , georef_source as source_georef
    from ads40.view_bildstreifen
    WHERE
        firma like 'swisstopo'
    order by resolution desc
    ) AS bla where ST_Intersects("the_geom", ST_GeomFromText('POLYGON((2420250 1050250,2420250 1349750,2849750 1349750,2849750 1050250,2420250 1050250))',2056)) and (("flugdatum" >= date_trunc('day',date '2022-01-01') and "flugdatum" <= (date_trunc('day',date '2022-12-31') + interval '1 day' - interval '1 second')))
msPostGISLayerWhichShapes query status: PGRES_TUPLES_OK (2)
msPostGISLayerWhichShapes got 482 records in result.
msPostGISLayerNextShape called.
msPostGISReadShape called.

The full layer config is here: https://pastebin.com/NkJXnRJt

Thank you and best regards
Marcel


________________________________
Von: Lime, Steve D (MNIT) <steve.lime at state.mn.us>
Gesendet: Donnerstag, 9. Februar 2023 23:04:03
An: Clausen Marcel swisstopo
Cc: mapserver-users at lists.osgeo.org
Betreff: RE: [MapServer-users] wms time validation of time parameter against timeextent gives unexpected results

So, if you turn on logging, what shows up in terms of Pg queries.

-----Original Message-----
From: MapServer-users <mapserver-users-bounces at lists.osgeo.org> On Behalf Of Clausen Marcel via MapServer-users
Sent: Tuesday, February 7, 2023 7:37 AM
To: sdlime at gmail.com
Cc: mapserver-users at lists.osgeo.org
Subject: Re: [MapServer-users] wms time validation of time parameter against timeextent gives unexpected results

Hello Steve


Thank you for your response,
we would have expected that too.

with wms 1.1 the service response is the same.

with this metadata "wms_timeextent" "2005/2022"
the service response is:

http://localhost:7777/local/?SERVICE=WMS&VERSION=1.1.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&SRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022-01-01/2022-12-31

<?xml version='1.0' encoding="UTF-8" standalone="no" ?> <!DOCTYPE ServiceExceptionReport SYSTEM "...">
<ServiceExceptionReport version="1.1.0"> <ServiceException code="InvalidDimensionValue">
msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022).
</ServiceException>
</ServiceExceptionReport>

The only work-around we found so far is to set the time-range in the metadata with a date precision of day:
"wms_timeextent" "2005-01-01/2022-12-31" but then in the getcap we would have this information:

<Dimension name="time" units="ISO8601" nearestValue="0">2005-01-01/2022-12-31</Dimension>

which is not representing the real nature of this dataset, the time resolution here should be a year.

Best regards
Marcel



________________________________
Von: Steve Lime <sdlime at gmail.com>
Gesendet: Montag, 6. Februar 2023 17:48:26
An: Clausen Marcel swisstopo
Cc: mapserver-users at lists.osgeo.org
Betreff: Re: [MapServer-users] wms time validation of time parameter against timeextent gives unexpected results

Does WMS 1.1 behave the same? I suppose it comes down to how 2022 is interpreted as part of a range, I would have expected it would mean any date in that year. Sounds like it's behaving like strictly less than 2022-01-01. What happens if you set the range using full dates, so something like: 20050101/20221231?

--Steve

On Thu, Feb 2, 2023 at 3:33 AM Clausen Marcel via MapServer-users <mapserver-users at lists.osgeo.org<mailto:mapserver-users at lists.osgeo.org>> wrote:

Dear all

We have the following question concerning the configuration and usage of time enabled wms layers.

We are using the following metadata section for a time-enabled layer:

    METADATA
        "wms_enable_request" "*"
        "wms_title" "lubis_bildstreifen"
        "wms_extent" "2100000 1050000 2850000 1400000"
        "wms_timeextent" "2005/2022"
        "wms_timeitem" "flugdatum" # this is a date column in postgres
    END


The time precision/resolution of the timeextent has to be set as year.

The validation of the time parameter against the time extent with year precision gives some strange results. We were using the following getmap request for the tests:

localhost:7777/local/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=ch.swisstopo.lubis-bildstreifen&CRS=EPSG:2056&STYLES=&WIDTH=860&HEIGHT=600&BBOX=2420000,1050000,2850000,1350000&TIME=2022

parameter:              time=2005
result:                         returns all features of 2005
expected result:        ok

parameter:              time=2022
result:                         returns all features of 2022
expected result:        ok

parameter:              time=2023
result:                         returns ServiceException [1]
expected result:        ok

parameter:              time=2022-01-01
result:                         returns ServiceException [2]
expected result:        we would expect this to be a valid timestamp

parameter:              time=2022-01-01/2022-12-31
result:                         returns ServiceException [3]
expected result:        we would expect this to be a valid timestamp

It seems that if the precision of the time parameter is of YYYY-MM or YYYY-MM-TT the upper bound of the defined timextent 2005/2022 is not respected correctly.
We got the same result with the timextent defined  as: 2005/2022/P1Y

our mapserver version is:
<!--  MapServer version 7.6.4 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=GEOS SUPPORTS=POINT_Z_M SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE  -->

Does someone have some insights or hints?

Best regards
Clausen Marcel

[1]
<ServiceException code="InvalidDimensionValue">msWMSApplyTime: WMS server error. Time value(s) 2023 given is invalid or outside the time extent defined (2005/2022).</ServiceException>

[2]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01 given is invalid or outside the time extent defined (2005/2022). </ServiceException>

[3]
<ServiceException code="InvalidDimensionValue"> msWMSApplyTime: WMS server error. Time value(s) 2022-01-01/2022-12-31 given is invalid or outside the time extent defined (2005/2022). </ServiceException>









_______________________________________________
MapServer-users mailing list
MapServer-users at lists.osgeo.org<mailto:MapServer-users at lists.osgeo.org>
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-users&data=05%7C01%7Csteve.lime%40state.mn.us%7C20a25ea5e6e1488c95a708db0910782a%7Ceb14b04624c445198f26b89c2159828c%7C0%7C0%7C638113738576533245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ha1sFKw7qRtLxB7ei0D%2FjhcGNTQlgwYz5U0WhLnN3Iw%3D&reserved=0
_______________________________________________
MapServer-users mailing list
MapServer-users at lists.osgeo.org
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-users&data=05%7C01%7Csteve.lime%40state.mn.us%7C20a25ea5e6e1488c95a708db0910782a%7Ceb14b04624c445198f26b89c2159828c%7C0%7C0%7C638113738576689260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iDvdDXh8CCndm%2BbmfJPK1XaU5o10%2Ff9L2vp1PbvYbMA%3D&reserved=0


From johannespaul92 at gmail.com  Thu Feb 16 00:54:19 2023
From: johannespaul92 at gmail.com (Johannes Paul)
Date: Thu, 16 Feb 2023 09:54:19 +0100
Subject: [MapServer-users] Mapcache second level dimensions
Message-ID: <CACcmK9Zf9ywP5Yc8cQM4oFmi+6J6WPOfcA3nLo7-uDyEE0p4LA@mail.gmail.com>

Hello,

I'm trying to implement second level SQLite dimension as explained in the
doc
https://mapserver.org/mapcache/dimensions.html#second-level-dimensions

Following that exemple on mapcache v1.12, I'm expecting that the below
conf, with WMS request on 'mosa_test' tileset with 'dim_sensor=phr', shall
use the ?product? sub-dimension values to query the data source
'mosa_source' on tileset 'test_primary' with 'dim_product' for each product
returned by the 2nd level dimension request (cache 'test_cache' is
pre-existing) ...

```
<cache name="test_cache" type="sqlite3">
    <dbfile>/nfs_tiles/test/{dim:product}.sqlite3</dbfile>
</cache>
<tileset name="test_primary">
    <cache>test_cache</cache>
    <grid>worldwind</grid>
    <dimensions>
       <dimension name="product" type="regex" default="spot-img1">
         <regex>.*</regex>
       </dimension>
    </dimensions>
    <format>PNG</format>
</tileset>
<cache name="mosa_cache" type="sqlite3">
    <dbfile>/nfs_tiles/test/mosa_{dim:sensor}.sqlite3</dbfile>
</cache>
<tileset name="mosa_test">
    <format>PNG</format>
    <grid>worldwind</grid>
    <cache>mosa_cache</cache>
    <source>mosa_source</source>
    <dimensions>
      <dimension name="sensor" type="sqlite" default="default">
        <dbfile>/nfs_tiles/test/mosa.db</dbfile>
        <validate_query>select product from mosa where
sensor=:dim</validate_query>
        <list_query>select product from mosa</list_query>
      </dimension>
    </dimensions>
</tileset>
<source name="mosa_source" type="wms">
    <http>
       <url>http://server/mapcache/</url>
    </http>
    <getmap>
        <params>
            <FORMAT>PNG</FORMAT>
            <LAYERS>test_primary</LAYERS>
            <TRANSPARENT>true</TRANSPARENT>
        </params>
    </getmap>
</source>
```

However all I get is a mapcache error in the httpd log, as follows :
`dimension (sensor) for tileset (mosa_test) returned invalid number (X) of
subdimensions (1 expected)`
If my 'sensor' dimension returns X products (which is the use case), I get
the error above, and if my 'sensor' dimension returns 1 product (let say
spot-img2), I get an error on the mapcache generated WMS request to the
source 'mosa_source' on tileset 'test_primary' with parameters
'&sensor=spot-img2&DIM_sensor=spot-img2' ... which can obviously not work !
Why is mapcache not using 'dim_product' in the WMS request ?

Have I missed something ?
Thanks,
Johannes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230216/ff1a2164/attachment.htm>

From johannespaul92 at gmail.com  Thu Feb 16 02:38:16 2023
From: johannespaul92 at gmail.com (Johannes Paul)
Date: Thu, 16 Feb 2023 11:38:16 +0100
Subject: [MapServer-users] Mapcache second level dimensions
In-Reply-To: <CACcmK9Zf9ywP5Yc8cQM4oFmi+6J6WPOfcA3nLo7-uDyEE0p4LA@mail.gmail.com>
References: <CACcmK9Zf9ywP5Yc8cQM4oFmi+6J6WPOfcA3nLo7-uDyEE0p4LA@mail.gmail.com>
Message-ID: <CACcmK9b7nV+DKaJVGRhEtRiZOrqTv3WmgB_0jSpz_LxNVdtWHQ@mail.gmail.com>

Coming back on a semi-working 2nd level dimension use case, if I use the
below conf:
```
<cache name="test_cache" type="sqlite3">
    <dbfile>/nfs_tiles/test/{dim:product}.sqlite3</dbfile>
</cache>
<tileset name="mosa_test">
    <format>PNG</format>
    <grid>worldwind</grid>
    <cache>test_cache</cache>
    <dimensions>
      <dimension name="*product*" type="sqlite" default="default">
        <dbfile>/nfs_tiles/test/mosa.db</dbfile>
        <validate_query>select product from mosa where
sensor=:dim</validate_query>
        <list_query>select product from mosa</list_query>
      </dimension>
    </dimensions>
</tileset>
```
Then the *dim_product *is passed to the cache '*test_cache*' with the
sub-dimension result using parameters '
*&product=spot-img2&DIM_product=spot-img2*', only if the result returns
only 1 sud-dimension value ... if it returns X sub-dimensions values I
still get an error : `*dimension (product) for tileset (mosa_test) returned
invalid number (X) of subdimensions (1 expected)*`

It seems the mechanism is not working the way it should be, isn't it ?
Johannes

On Thu, 16 Feb 2023 at 09:54, Johannes Paul <johannespaul92 at gmail.com>
wrote:

> Hello,
>
> I'm trying to implement second level SQLite dimension as explained in the
> doc
> https://mapserver.org/mapcache/dimensions.html#second-level-dimensions
>
> Following that exemple on mapcache v1.12, I'm expecting that the below
> conf, with WMS request on 'mosa_test' tileset with 'dim_sensor=phr', shall
> use the ?product? sub-dimension values to query the data source
> 'mosa_source' on tileset 'test_primary' with 'dim_product' for each product
> returned by the 2nd level dimension request (cache 'test_cache' is
> pre-existing) ...
>
> ```
> <cache name="test_cache" type="sqlite3">
>     <dbfile>/nfs_tiles/test/{dim:product}.sqlite3</dbfile>
> </cache>
> <tileset name="test_primary">
>     <cache>test_cache</cache>
>     <grid>worldwind</grid>
>     <dimensions>
>        <dimension name="product" type="regex" default="spot-img1">
>          <regex>.*</regex>
>        </dimension>
>     </dimensions>
>     <format>PNG</format>
> </tileset>
> <cache name="mosa_cache" type="sqlite3">
>     <dbfile>/nfs_tiles/test/mosa_{dim:sensor}.sqlite3</dbfile>
> </cache>
> <tileset name="mosa_test">
>     <format>PNG</format>
>     <grid>worldwind</grid>
>     <cache>mosa_cache</cache>
>     <source>mosa_source</source>
>     <dimensions>
>       <dimension name="sensor" type="sqlite" default="default">
>         <dbfile>/nfs_tiles/test/mosa.db</dbfile>
>         <validate_query>select product from mosa where
> sensor=:dim</validate_query>
>         <list_query>select product from mosa</list_query>
>       </dimension>
>     </dimensions>
> </tileset>
> <source name="mosa_source" type="wms">
>     <http>
>        <url>http://server/mapcache/</url>
>     </http>
>     <getmap>
>         <params>
>             <FORMAT>PNG</FORMAT>
>             <LAYERS>test_primary</LAYERS>
>             <TRANSPARENT>true</TRANSPARENT>
>         </params>
>     </getmap>
> </source>
> ```
>
> However all I get is a mapcache error in the httpd log, as follows :
> `dimension (sensor) for tileset (mosa_test) returned invalid number (X) of
> subdimensions (1 expected)`
> If my 'sensor' dimension returns X products (which is the use case), I get
> the error above, and if my 'sensor' dimension returns 1 product (let say
> spot-img2), I get an error on the mapcache generated WMS request to the
> source 'mosa_source' on tileset 'test_primary' with parameters
> '&sensor=spot-img2&DIM_sensor=spot-img2' ... which can obviously not work !
> Why is mapcache not using 'dim_product' in the WMS request ?
>
> Have I missed something ?
> Thanks,
> Johannes
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230216/a90634ba/attachment.htm>

From mniemyjski at cloudferro.com  Mon Feb 20 03:31:00 2023
From: mniemyjski at cloudferro.com (Marcin Niemyjski)
Date: Mon, 20 Feb 2023 11:31:00 +0000
Subject: [MapServer-users] Using of GCP file in Mapserver based on Layers
 Object's Extent and Projection
Message-ID: <AS1PR03MB81493DA0419B528E0A2F20ACA8A49@AS1PR03MB8149.eurprd03.prod.outlook.com>

Hello,

I'm struggling with rasters with Ground Control Points (GCP). My previous workflow of dealing with them looks like:

Original GCP raster -> gdal warp -of VRT to vrt -> TileIndex created from multiple VRTs

I have found similiar problem on mapserver mailing list. I confirm that creating VRT files helps also in my use case - https://lists.osgeo.org/pipermail/mapserver-users/2020-September/081858.html

But the problem is - i really want to avoid the need of creating VRTs

What I have now:
https://paste.ofcode.org/JJWL2E4EEzs5TzJeLUpRYS

How WMS is projected:
https://pasteboard.co/wQwovivslGDa.png

How it should be:
https://pasteboard.co/xWiLv6LYVgG8.png

Adding more PROJ4 lib attributes (like "axis=neu") fails.

Any recommedation/sugestions?

Thanks,
Marcin







[cid:2ddd8133-13e4-4837-b5e8-a8521d17d5ca]<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>           Book time to meet with me<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230220/e619341a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-vk12rjwf.png
Type: image/png
Size: 528 bytes
Desc: Outlook-vk12rjwf.png
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230220/e619341a/attachment.png>

From grabermtw at gmail.com  Tue Feb 21 08:52:04 2023
From: grabermtw at gmail.com (Matthew Graber)
Date: Tue, 21 Feb 2023 11:52:04 -0500
Subject: [MapServer-users] Changing opacity of one layer in a multilayer WMS
 request URL with MapServer 8
Message-ID: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>

Hello all!

With MapServer 8, I'm wondering what the proper way to change the opacity
of a single layer in a multilayer WMS request is.

For example, the following URL excerpt shows the old way of accomplishing
this that worked while using MapServer 7:

SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50

My understanding is that this would have the same effect as adding "OPACITY
50" to the test_b layer in the mapfile. The mapfile containing test_a and
test_b did not have OPACITY included when they were written. Obviously,
this no longer works with MapServer 8, and now that request has the same
results as omitting the "&map.layer[test_b]=OPACITY+50" portion entirely.

Based on https://mapserver.org/fr/MIGRATION_GUIDE.html, I see that OPACITY
now belongs inside a COMPOSITE object. I tried the following modifications
to the request URL:

SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50

I also tried this both with the mapfile left as-is, and with an empty
COMPOSITE object being included in each layer object, and each time I got
the same unsuccessful result as before.

Is there a way to accomplish this in MapServer 8?

Also, does this map.layer[layername]=... syntax still work in MapServer 8?
The documentation at
https://mapserver.org/cgi/controls.html#using-mapserver-version-8 suggests
it might no longer work for MapServer 8 (based on the heading "Using
MapServer version < 8"), but the documentation at
https://mapserver.org/pdf/MapServer.pdf shows the same examples with the
heading "Using MapServer version <= 8" on page 1065 of the PDF, so I'm
unsure if this is still intended to work in MapServer 8.

Thank you,
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230221/f98c0e42/attachment.htm>

From jmckenna at gatewaygeomatics.com  Tue Feb 21 10:03:14 2023
From: jmckenna at gatewaygeomatics.com (Jeff McKenna)
Date: Tue, 21 Feb 2023 14:03:14 -0400
Subject: [MapServer-users] Changing opacity of one layer in a multilayer
 WMS request URL with MapServer 8
In-Reply-To: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
References: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
Message-ID: <cba8fa18-56b6-5f65-2203-8d6dd60e6c4e@gatewaygeomatics.com>

Wonderful to hear that you are using the MapServer.pdf!  (I actually put 
much effort into maintaining that PDF output, that but I never hear 
feedback...until someone reports a problem, like you did now, ha). 
Sometimes my updates differ from website rebuilds, will be sure to 
update the PDF for the upcoming 8.0.1 release.

Again, thanks for this report!

(also, don't be afraid to report doc issues like this at 
https://github.com/MapServer/MapServer-documentation/issues )

thanks again for the report!

-jeff




-- 
Jeff McKenna
GatewayGeo: Developers of MS4W, MapServer Consulting and Training
co-founder of FOSS4G
http://gatewaygeo.com/



On 2023-02-21 12:52 p.m., Matthew Graber wrote:
> Hello all!
> 
> With MapServer 8, I'm wondering what the proper way to change the 
> opacity of a single layer in a multilayer WMS request is.
> 
> For example, the following URL excerpt shows the old way of 
> accomplishing this that worked while using MapServer 7:
> 
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50
> 
> My understanding is that this would have the same effect as adding 
> "OPACITY 50" to the test_b layer in the mapfile. The mapfile containing 
> test_a and test_b did not have OPACITY included when they were written. 
> Obviously, this no longer works with MapServer 8, and now that request 
> has the same results as omitting the "&map.layer[test_b]=OPACITY+50" 
> portion entirely.
> 
> Based on https://mapserver.org/fr/MIGRATION_GUIDE.html 
> <https://mapserver.org/fr/MIGRATION_GUIDE.html>, I see that OPACITY now 
> belongs inside a COMPOSITE object. I tried the following modifications 
> to the request URL:
> 
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50
> 
> I also tried this both with the mapfile left as-is, and with an empty 
> COMPOSITE object being included in each layer object, and each time I 
> got the same unsuccessful result as before.
> 
> Is there a way to accomplish this in MapServer 8?
> 
> Also, does this map.layer[layername]=... syntax still work in MapServer 
> 8? The documentation at 
> https://mapserver.org/cgi/controls.html#using-mapserver-version-8 
> <https://mapserver.org/cgi/controls.html#using-mapserver-version-8> 
> suggests it might no longer work for MapServer 8 (based on the heading 
> "Using MapServer version < 8"), but the documentation at 
> https://mapserver.org/pdf/MapServer.pdf 
> <https://mapserver.org/pdf/MapServer.pdf> shows the same examples with 
> the heading "Using MapServer version <= 8" on page 1065 of the PDF, so 
> I'm unsure if this is still intended to work in MapServer 8.
> 
> Thank you,
> Matt
> 
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users



From bob.basques at ci.stpaul.mn.us  Tue Feb 21 18:03:35 2023
From: bob.basques at ci.stpaul.mn.us (Basques, Bob (CI-StPaul))
Date: Wed, 22 Feb 2023 02:03:35 +0000
Subject: [MapServer-users] OSGeo Chapter meeting,
 request for presenters . . .
Message-ID: <CC75CC93-64A8-4D0A-8581-243F462459C2@ci.stpaul.mn.us>

All,

Looking for presenters for the next meeting on March 8th.  Can be about anything Geo related.

Show something you?ve been working on to others, or even bring up problems you having with software or implementing ideas, anything is game.

Bobb



Get me in Teams<https://teams.microsoft.com/l/chat/0/0?users=bob.basques at ci.stpaul.mn.us>
PW19-S295-C024


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/551ac53b/attachment.htm>

From mniemyjski at cloudferro.com  Wed Feb 22 06:19:24 2023
From: mniemyjski at cloudferro.com (Marcin Niemyjski)
Date: Wed, 22 Feb 2023 14:19:24 +0000
Subject: [MapServer-users] Can Mapserver store VRT content in cache?
Message-ID: <AS1PR03MB8149F8590580E6BA5800F14EA8AA9@AS1PR03MB8149.eurprd03.prod.outlook.com>

Hello,

can Mapserver store VRT content in cache so is uses cached file to connect to source data when requesting it? I want to limit S3 requests (because all data is stored on s3, including VRT) so Mapserver sends only S3 requests for source data.

Any sugestions?

Thanks,
Marcin





[cid:096981c4-895a-4af8-ba57-c05126170280]<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>           Book time to meet with me<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae948648789d at cloudferro.com?anonymous&ep=signature>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/ca520f8b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-fxftb1xe.png
Type: image/png
Size: 528 bytes
Desc: Outlook-fxftb1xe.png
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/ca520f8b/attachment.png>

From sdlime at gmail.com  Wed Feb 22 07:46:33 2023
From: sdlime at gmail.com (Steve Lime)
Date: Wed, 22 Feb 2023 09:46:33 -0600
Subject: [MapServer-users] Changing opacity of one layer in a multilayer
 WMS request URL with MapServer 8
In-Reply-To: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
References: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
Message-ID: <CAMrKZ98pm37xjpCDYumYkbM8F92-s_yuP6KPyJUMaOkLEyAO3g@mail.gmail.com>

Hi Matthew: That functionality was indeed removed as part of 8.0. I kind of
expect that we might build back something for more limited use cases if
necessary, Does SLD support opacity/transparency?

--Steve


On Tue, Feb 21, 2023 at 10:52 AM Matthew Graber <grabermtw at gmail.com> wrote:

> Hello all!
>
> With MapServer 8, I'm wondering what the proper way to change the opacity
> of a single layer in a multilayer WMS request is.
>
> For example, the following URL excerpt shows the old way of accomplishing
> this that worked while using MapServer 7:
>
>
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50
>
> My understanding is that this would have the same effect as adding
> "OPACITY 50" to the test_b layer in the mapfile. The mapfile containing
> test_a and test_b did not have OPACITY included when they were written.
> Obviously, this no longer works with MapServer 8, and now that request has
> the same results as omitting the "&map.layer[test_b]=OPACITY+50" portion
> entirely.
>
> Based on https://mapserver.org/fr/MIGRATION_GUIDE.html, I see that
> OPACITY now belongs inside a COMPOSITE object. I tried the following
> modifications to the request URL:
>
>
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
>
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50
>
> I also tried this both with the mapfile left as-is, and with an empty
> COMPOSITE object being included in each layer object, and each time I got
> the same unsuccessful result as before.
>
> Is there a way to accomplish this in MapServer 8?
>
> Also, does this map.layer[layername]=... syntax still work in MapServer 8?
> The documentation at
> https://mapserver.org/cgi/controls.html#using-mapserver-version-8
> suggests it might no longer work for MapServer 8 (based on the heading
> "Using MapServer version < 8"), but the documentation at
> https://mapserver.org/pdf/MapServer.pdf shows the same examples with the
> heading "Using MapServer version <= 8" on page 1065 of the PDF, so I'm
> unsure if this is still intended to work in MapServer 8.
>
> Thank you,
> Matt
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/8a3885e6/attachment.htm>

From sethg at geographika.co.uk  Wed Feb 22 08:26:25 2023
From: sethg at geographika.co.uk (Seth G)
Date: Wed, 22 Feb 2023 17:26:25 +0100
Subject: [MapServer-users] Changing opacity of one layer in a multilayer
 WMS request URL with MapServer 8
In-Reply-To: <CAMrKZ98pm37xjpCDYumYkbM8F92-s_yuP6KPyJUMaOkLEyAO3g@mail.gmail.com>
References: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
 <CAMrKZ98pm37xjpCDYumYkbM8F92-s_yuP6KPyJUMaOkLEyAO3g@mail.gmail.com>
Message-ID: <ea7e89d1-0559-4b74-a434-a8d74068251b@app.fastmail.com>

Hi,

I think OPACITY should still work at the STYLE level: https://mapserver.org/mapfile/style.html#mapfile-style-opacity
If you are using WMS then you could setup different styles with different OPACITY values, and then use named styles to select the appropriate style (with the STYLES= added to the WMS request). 

Seth


--
web:https://geographika.net
twitter: @geographika

On Wed, Feb 22, 2023, at 4:46 PM, Steve Lime wrote:
> Hi Matthew: That functionality was indeed removed as part of 8.0. I kind of expect that we might build back something for more limited use cases if necessary, Does SLD support opacity/transparency? 
> 
> --Steve
> 
> 
> On Tue, Feb 21, 2023 at 10:52 AM Matthew Graber <grabermtw at gmail.com> wrote:
>> Hello all!
>> 
>> With MapServer 8, I'm wondering what the proper way to change the opacity of a single layer in a multilayer WMS request is.
>> 
>> For example, the following URL excerpt shows the old way of accomplishing this that worked while using MapServer 7:
>> 
>> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50
>> 
>> My understanding is that this would have the same effect as adding "OPACITY 50" to the test_b layer in the mapfile. The mapfile containing test_a and test_b did not have OPACITY included when they were written. Obviously, this no longer works with MapServer 8, and now that request has the same results as omitting the "&map.layer[test_b]=OPACITY+50" portion entirely.
>> 
>> Based on https://mapserver.org/fr/MIGRATION_GUIDE.html, I see that OPACITY now belongs inside a COMPOSITE object. I tried the following modifications to the request URL:
>> 
>> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
>> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50
>> 
>> I also tried this both with the mapfile left as-is, and with an empty COMPOSITE object being included in each layer object, and each time I got the same unsuccessful result as before.
>> 
>> Is there a way to accomplish this in MapServer 8?
>> 
>> Also, does this map.layer[layername]=... syntax still work in MapServer 8? The documentation at https://mapserver.org/cgi/controls.html#using-mapserver-version-8 suggests it might no longer work for MapServer 8 (based on the heading "Using MapServer version < 8"), but the documentation at https://mapserver.org/pdf/MapServer.pdf shows the same examples with the heading "Using MapServer version <= 8" on page 1065 of the PDF, so I'm unsure if this is still intended to work in MapServer 8.
>> 
>> Thank you,
>> Matt
>> _______________________________________________
>> MapServer-users mailing list
>> MapServer-users at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/bf74df5f/attachment.htm>

From jukka.rahkonen at maanmittauslaitos.fi  Wed Feb 22 08:51:03 2023
From: jukka.rahkonen at maanmittauslaitos.fi (Rahkonen Jukka)
Date: Wed, 22 Feb 2023 16:51:03 +0000
Subject: [MapServer-users] Changing opacity of one layer in a multilayer
 WMS request URL with MapServer 8
In-Reply-To: <CAMrKZ98pm37xjpCDYumYkbM8F92-s_yuP6KPyJUMaOkLEyAO3g@mail.gmail.com>
References: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
 <CAMrKZ98pm37xjpCDYumYkbM8F92-s_yuP6KPyJUMaOkLEyAO3g@mail.gmail.com>
Message-ID: <AM0PR09MB32197442862FCAB4D3ECA381FDAA9@AM0PR09MB3219.eurprd09.prod.outlook.com>

Hi,

About the SLD, opacity appears in stroke, fill, graphic, and raster in SLD 1.0.

-Jukka Rahkonen-

L?hett?j?: MapServer-users <mapserver-users-bounces at lists.osgeo.org> Puolesta Steve Lime
L?hetetty: keskiviikko 22. helmikuuta 2023 17.47
Vastaanottaja: Matthew Graber <grabermtw at gmail.com>
Kopio: mapserver-users at lists.osgeo.org
Aihe: Re: [MapServer-users] Changing opacity of one layer in a multilayer WMS request URL with MapServer 8

Hi Matthew: That functionality was indeed removed as part of 8.0. I kind of expect that we might build back something for more limited use cases if necessary, Does SLD support opacity/transparency?

--Steve


On Tue, Feb 21, 2023 at 10:52 AM Matthew Graber <grabermtw at gmail.com<mailto:grabermtw at gmail.com>> wrote:
Hello all!

With MapServer 8, I'm wondering what the proper way to change the opacity of a single layer in a multilayer WMS request is.

For example, the following URL excerpt shows the old way of accomplishing this that worked while using MapServer 7:

SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50

My understanding is that this would have the same effect as adding "OPACITY 50" to the test_b layer in the mapfile. The mapfile containing test_a and test_b did not have OPACITY included when they were written. Obviously, this no longer works with MapServer 8, and now that request has the same results as omitting the "&map.layer[test_b]=OPACITY+50" portion entirely.

Based on https://mapserver.org/fr/MIGRATION_GUIDE.html<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmapserver.org%2Ffr%2FMIGRATION_GUIDE.html&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CbH%2FfRUQdX9uq8H9QRy48X0BggqTStn4IDQR4jD%2B97Y%3D&reserved=0>, I see that OPACITY now belongs inside a COMPOSITE object. I tried the following modifications to the request URL:

SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50

I also tried this both with the mapfile left as-is, and with an empty COMPOSITE object being included in each layer object, and each time I got the same unsuccessful result as before.

Is there a way to accomplish this in MapServer 8?

Also, does this map.layer[layername]=... syntax still work in MapServer 8? The documentation at https://mapserver.org/cgi/controls.html#using-mapserver-version-8<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmapserver.org%2Fcgi%2Fcontrols.html%23using-mapserver-version-8&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nu1%2BBml9%2BZG%2BIvjJ8ZpRZ28kDVKzo960hSM%2F18s3Jng%3D&reserved=0> suggests it might no longer work for MapServer 8 (based on the heading "Using MapServer version < 8"), but the documentation at https://mapserver.org/pdf/MapServer.pdf<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmapserver.org%2Fpdf%2FMapServer.pdf&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OGoZ%2FK4IwX1%2FVRmcWsewiygoys24Vg4eDlGYIhtdcUk%3D&reserved=0> shows the same examples with the heading "Using MapServer version <= 8" on page 1065 of the PDF, so I'm unsure if this is still intended to work in MapServer 8.

Thank you,
Matt
_______________________________________________
MapServer-users mailing list
MapServer-users at lists.osgeo.org<mailto:MapServer-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/mapserver-users<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-users&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TonNCCvW%2FnZX%2FbNTKWsiKeXfFWrMMGXP3KnLTlUjDmA%3D&reserved=0>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/95d945e1/attachment.htm>

From grabermtw at gmail.com  Wed Feb 22 11:59:28 2023
From: grabermtw at gmail.com (Matthew Graber)
Date: Wed, 22 Feb 2023 14:59:28 -0500
Subject: [MapServer-users] Changing opacity of one layer in a multilayer
 WMS request URL with MapServer 8
In-Reply-To: <AM0PR09MB32197442862FCAB4D3ECA381FDAA9@AM0PR09MB3219.eurprd09.prod.outlook.com>
References: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
 <CAMrKZ98pm37xjpCDYumYkbM8F92-s_yuP6KPyJUMaOkLEyAO3g@mail.gmail.com>
 <AM0PR09MB32197442862FCAB4D3ECA381FDAA9@AM0PR09MB3219.eurprd09.prod.outlook.com>
Message-ID: <CAC0Dnw=czPrG1FyVG2PeFX3cmcShtH589gfD_DObK88UQigTbw@mail.gmail.com>

Hi all,

Thanks for your help! I was able to get the SLD_BODY WMS parameter to serve
as a workaround for setting opacity. In case anyone else has this problem,
the SLD I used in this case was:

<StyledLayerDescriptor xmlns:sld="http://www.opengis.net/sld"
version="1.0.0" xsi:schemaLocation="http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xmlns:ogc="
http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml">

<NamedLayer>

<Name>test_b</Name>

<UserStyle>

<FeatureTypeStyle>

<Rule>

<Name>default</Name>

<RasterSymbolizer>

<Opacity>0.5</Opacity>

</RasterSymbolizer>

</Rule>

</FeatureTypeStyle>

</UserStyle>

</NamedLayer>

</StyledLayerDescriptor>

Appreciate everyone's help!
-Matt

On Wed, Feb 22, 2023 at 11:51 AM Rahkonen Jukka <
jukka.rahkonen at maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> About the SLD, opacity appears in stroke, fill, graphic, and raster in SLD
> 1.0.
>
>
>
> -Jukka Rahkonen-
>
>
>
> *L?hett?j?:* MapServer-users <mapserver-users-bounces at lists.osgeo.org> *Puolesta
> *Steve Lime
> *L?hetetty:* keskiviikko 22. helmikuuta 2023 17.47
> *Vastaanottaja:* Matthew Graber <grabermtw at gmail.com>
> *Kopio:* mapserver-users at lists.osgeo.org
> *Aihe:* Re: [MapServer-users] Changing opacity of one layer in a
> multilayer WMS request URL with MapServer 8
>
>
>
> Hi Matthew: That functionality was indeed removed as part of 8.0. I kind
> of expect that we might build back something for more limited use cases if
> necessary, Does SLD support opacity/transparency?
>
>
>
> --Steve
>
>
>
>
>
> On Tue, Feb 21, 2023 at 10:52 AM Matthew Graber <grabermtw at gmail.com>
> wrote:
>
> Hello all!
>
>
>
> With MapServer 8, I'm wondering what the proper way to change the opacity
> of a single layer in a multilayer WMS request is.
>
>
>
> For example, the following URL excerpt shows the old way of accomplishing
> this that worked while using MapServer 7:
>
>
>
>
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50
>
>
>
> My understanding is that this would have the same effect as adding
> "OPACITY 50" to the test_b layer in the mapfile. The mapfile containing
> test_a and test_b did not have OPACITY included when they were written.
> Obviously, this no longer works with MapServer 8, and now that request has
> the same results as omitting the "&map.layer[test_b]=OPACITY+50" portion
> entirely.
>
>
>
> Based on https://mapserver.org/fr/MIGRATION_GUIDE.html
> <https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmapserver.org%2Ffr%2FMIGRATION_GUIDE.html&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CbH%2FfRUQdX9uq8H9QRy48X0BggqTStn4IDQR4jD%2B97Y%3D&reserved=0>,
> I see that OPACITY now belongs inside a COMPOSITE object. I tried the
> following modifications to the request URL:
>
>
>
>
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
>
>
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50
>
>
>
> I also tried this both with the mapfile left as-is, and with an empty
> COMPOSITE object being included in each layer object, and each time I got
> the same unsuccessful result as before.
>
>
>
> Is there a way to accomplish this in MapServer 8?
>
>
>
> Also, does this map.layer[layername]=... syntax still work in MapServer 8?
> The documentation at
> https://mapserver.org/cgi/controls.html#using-mapserver-version-8
> <https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmapserver.org%2Fcgi%2Fcontrols.html%23using-mapserver-version-8&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nu1%2BBml9%2BZG%2BIvjJ8ZpRZ28kDVKzo960hSM%2F18s3Jng%3D&reserved=0>
> suggests it might no longer work for MapServer 8 (based on the heading
> "Using MapServer version < 8"), but the documentation at
> https://mapserver.org/pdf/MapServer.pdf
> <https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmapserver.org%2Fpdf%2FMapServer.pdf&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OGoZ%2FK4IwX1%2FVRmcWsewiygoys24Vg4eDlGYIhtdcUk%3D&reserved=0>
> shows the same examples with the heading "Using MapServer version <= 8" on
> page 1065 of the PDF, so I'm unsure if this is still intended to work in
> MapServer 8.
>
>
>
> Thank you,
>
> Matt
>
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> <https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-users&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C751680624f65498df41008db14ec07c5%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C1%7C638126776216198394%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TonNCCvW%2FnZX%2FbNTKWsiKeXfFWrMMGXP3KnLTlUjDmA%3D&reserved=0>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/f9bebb56/attachment.htm>

From grabermtw at gmail.com  Wed Feb 22 12:00:38 2023
From: grabermtw at gmail.com (Matthew Graber)
Date: Wed, 22 Feb 2023 15:00:38 -0500
Subject: [MapServer-users] Changing opacity of one layer in a multilayer
 WMS request URL with MapServer 8
In-Reply-To: <cba8fa18-56b6-5f65-2203-8d6dd60e6c4e@gatewaygeomatics.com>
References: <CAC0DnwnZjB1MzoL-7qUob0AVSxce561U=ABqCue8Fgd3k7W_NQ@mail.gmail.com>
 <cba8fa18-56b6-5f65-2203-8d6dd60e6c4e@gatewaygeomatics.com>
Message-ID: <CAC0DnwmUBTdyqk6NedPROU42LhNtmEKsMCnys5H2fvui_AafCQ@mail.gmail.com>

Glad I could help, Jeff! MapServer.pdf is a great resource!

-Matt

On Tue, Feb 21, 2023 at 1:02 PM Jeff McKenna <jmckenna at gatewaygeomatics.com>
wrote:

> Wonderful to hear that you are using the MapServer.pdf!  (I actually put
> much effort into maintaining that PDF output, that but I never hear
> feedback...until someone reports a problem, like you did now, ha).
> Sometimes my updates differ from website rebuilds, will be sure to
> update the PDF for the upcoming 8.0.1 release.
>
> Again, thanks for this report!
>
> (also, don't be afraid to report doc issues like this at
> https://github.com/MapServer/MapServer-documentation/issues )
>
> thanks again for the report!
>
> -jeff
>
>
>
>
> --
> Jeff McKenna
> GatewayGeo: Developers of MS4W, MapServer Consulting and Training
> co-founder of FOSS4G
> http://gatewaygeo.com/
>
>
>
> On 2023-02-21 12:52 p.m., Matthew Graber wrote:
> > Hello all!
> >
> > With MapServer 8, I'm wondering what the proper way to change the
> > opacity of a single layer in a multilayer WMS request is.
> >
> > For example, the following URL excerpt shows the old way of
> > accomplishing this that worked while using MapServer 7:
> >
> >
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b]=OPACITY+50
> >
> > My understanding is that this would have the same effect as adding
> > "OPACITY 50" to the test_b layer in the mapfile. The mapfile containing
> > test_a and test_b did not have OPACITY included when they were written.
> > Obviously, this no longer works with MapServer 8, and now that request
> > has the same results as omitting the "&map.layer[test_b]=OPACITY+50"
> > portion entirely.
> >
> > Based on https://mapserver.org/fr/MIGRATION_GUIDE.html
> > <https://mapserver.org/fr/MIGRATION_GUIDE.html>, I see that OPACITY now
> > belongs inside a COMPOSITE object. I tried the following modifications
> > to the request URL:
> >
> >
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite=OPACITY+50
> >
> SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&LAYERS=test_a,test_b&map.layer[test_b].composite[0]=OPACITY+50
> >
> > I also tried this both with the mapfile left as-is, and with an empty
> > COMPOSITE object being included in each layer object, and each time I
> > got the same unsuccessful result as before.
> >
> > Is there a way to accomplish this in MapServer 8?
> >
> > Also, does this map.layer[layername]=... syntax still work in MapServer
> > 8? The documentation at
> > https://mapserver.org/cgi/controls.html#using-mapserver-version-8
> > <https://mapserver.org/cgi/controls.html#using-mapserver-version-8>
> > suggests it might no longer work for MapServer 8 (based on the heading
> > "Using MapServer version < 8"), but the documentation at
> > https://mapserver.org/pdf/MapServer.pdf
> > <https://mapserver.org/pdf/MapServer.pdf> shows the same examples with
> > the heading "Using MapServer version <= 8" on page 1065 of the PDF, so
> > I'm unsure if this is still intended to work in MapServer 8.
> >
> > Thank you,
> > Matt
> >
> > _______________________________________________
> > MapServer-users mailing list
> > MapServer-users at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230222/c389752b/attachment.htm>

From lars.schylberg at blixtmail.se  Wed Feb 22 12:00:34 2023
From: lars.schylberg at blixtmail.se (Lars Schylberg)
Date: Wed, 22 Feb 2023 21:00:34 +0100
Subject: [MapServer-users] ITEMS and PROCESSING
Message-ID: <4e183c56-6e49-9f2c-596e-2221576ab446@blixtmail.se>

Hi list,

I just have to check if there is some way to read a ITEMS from a 
variable, ie ITEMS="[labels]".? The processing of items is "so good" for 
inline features.? What I would like, is to write ITEMS on the layer 
level without a feature block and read it from a variable.? Splitting 
strings with sql sqlite syntax is really a pain, when splitting the data 
while reading the data. I made several test myself, trying to specify 
ITEMS outside feature blocks without success. My sub labels could be 
between 1-5 characters which makes the substr commands in sql really 
complicated.

 ??? FEATURE
 ????? POINTS
 ??????? 50 50
 ????? END
 ????? ITEMS "E4;55;655;9"
 ??? END

 ?? PROCESSING "ITEMS=label1,label2,label3,label4"

Just wondering if I have overlooked something in the Mapserver manual.

Thanks in advance / Lars Schylberg




From johannespaul92 at gmail.com  Fri Feb 24 07:38:46 2023
From: johannespaul92 at gmail.com (Johannes Paul)
Date: Fri, 24 Feb 2023 16:38:46 +0100
Subject: [MapServer-users] Mapcache authentication in source http requests
Message-ID: <CACcmK9ZDFyixBNpPRgnwLR78xuaUB6DuixpUnusN01qAKq-pcA@mail.gmail.com>

Hello,
I can't find anywhere in the documentation if and how mapcache handles
authentication in data sources http requests.
I found this old post
https://lists.osgeo.org/pipermail/mapserver-users/2013-April/074509.html
dealing with basic authentication headers.
Is there any built-in mechanism for dealing with NTLM authentication ?
Thanks,
Johannes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20230224/b03e2ecd/attachment.htm>