[mapserver-users] [REMINDER] OSGeo Local Chapter (TCMUG) Meeting.

[Basques, Bob (CI-StPaul)]

All,



Had a really good meeting this evening.Michael Talbot presented  on an 
“Introduction to Cloud Optimzied GeoTIFFs”.  The recording has been post to the 
Local OSGeo Chapter page below.



Casting out for presenters for next Month on March 9th.   Anyone, anyone?









https://staging.www.osgeo.org/local-chapters/twin-cities-mn-usa-chapter/





Bobb

___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Mapcache disk cache gives unexpected paths to tiles

[Trygve Aspenes]

Ah, thanks Thomas!

I did not catch that from the documentation.
I also needed to add layout like this:



/mapcache/{tileset}/{grid}/{dim:time}/{z}/{x}/{y}.{ext}



to make it work ( both from testing and looking at the documentation)

If you use the default this will be like tilecache as far as I 
understand.


Do you have any idea what will be the fastest? To use default like:

/mapcache


or the solution above with template? ( As a lot of 000 directories will 
be created with the base one)


Trygve

Den 2022-02-09 12:24, skrev thomas bonfort:

You should remove the /mapcache from the >cache> block,
as it takes precedence over your 

--
thomas

On Wed, Feb 9, 2022 at 12:10 PM Trygve Aspenes
 wrote:


Hi

I have a mapcache running using disk as cache method with config
like
this:


/mapcache



/mapcache/{tileset}#{grid}#{dim}/{z}/{x}/{y}.{ext}



But here is what I get on disk:

/mapcache//EPSG:3857/2022-02-05T00:12:00Z/05/000/000/038/000/000/043.png

What I don't understand is below the zoom level (here 05) I get 000
followed by 000. Then the y followed by another double 000 before I
get
the x with my extension.

Where does all these 000 sub directories comes from and what
functions
do they have?

I don't think this affects the performance, but this must cause
creating
thousands and thousands of unnecessary sub directories?

Thanks.

Trygve
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] [REMINDER] OSGeo Local Chapter (TCMUG) Meeting.

[Basques, Bob (CI-StPaul)]

All,



Had a light turnout last month, but the show must go on.



Michael Talbot will be presenting at our next OSGeo Local Chapter meeting on an 
“Introduction to Cloud Optimzied GeoTIFFs”



Mike is a water resources engineer at Emmons & Olivier Resources, Inc. (EOR), 
where he wears many hats. One of those hats is as a full stack web developer 
and manager of EOR's cloud infrastructure and PostgreSQL databases.



Michael Talbot

talbot.michae...@gmail.com



When, Feb 9th, 2022, 4:30 pm

Where: https://meet.jit.si/osgeo_tcmug



Bobb

___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Mapcache disk cache gives unexpected paths to tiles

[thomas bonfort]

You should remove the /mapcache from the >cache> block, as it
takes precedence over your 

--
thomas

On Wed, Feb 9, 2022 at 12:10 PM Trygve Aspenes 
wrote:

> Hi
>
> I have a mapcache running using disk as cache method with config like
> this:
>
>  
>  /mapcache
>
> /mapcache/{tileset}#{grid}#{dim}/{z}/{x}/{y}.{ext}
>  
>
> But here is what I get on disk:
>
> /mapcache/ name>/EPSG:3857/2022-02-05T00:12:00Z/05/000/000/038/000/000/043.png
>
> What I don't understand is below the zoom level (here 05) I get 000
> followed by 000. Then the y followed by another double 000 before I get
> the x with my extension.
>
> Where does all these 000 sub directories comes from and what functions
> do they have?
>
> I don't think this affects the performance, but this must cause creating
> thousands and thousands of unnecessary sub directories?
>
> Thanks.
>
> Trygve
> ___
> MapServer-users mailing list
> MapServer-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
>
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Mapcache disk cache gives unexpected paths to tiles

[Trygve Aspenes]

Hi

I have a mapcache running using disk as cache method with config like 
this:



/mapcache

/mapcache/{tileset}#{grid}#{dim}/{z}/{x}/{y}.{ext}



But here is what I get on disk:

/mapcache/name>/EPSG:3857/2022-02-05T00:12:00Z/05/000/000/038/000/000/043.png


What I don't understand is below the zoom level (here 05) I get 000 
followed by 000. Then the y followed by another double 000 before I get 
the x with my extension.


Where does all these 000 sub directories comes from and what functions 
do they have?


I don't think this affects the performance, but this must cause creating 
thousands and thousands of unnecessary sub directories?


Thanks.

Trygve
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Mapserver URL request layer

[Sander Pukk]

Hei!

I got my answers. Thanks guys!

Sander

On Wed, Feb 9, 2022 at 12:35 PM Jörg Thomsen (WhereGroup) <
joerg.thom...@wheregroup.com> wrote:

> Hello Sander,
>
>
>1. Had issues with 4326 to 3301 transformation,the extent and all
>that. (OpenLayers could manage but QGIS couldnt). Previously only had
>ows_extent.
>Is ows_extent even a thing? This only shows wms_extent
>https://mapserver.org/ogc/wms_server.html#layer-object-metadata
>Should you use wfs_extent and wms_extent instead?
>
> the wms_ / wfs_ / ows_ / oga_ (coming in MapServer 8) Metadata-entry are
> aiming on your output. So, if you only want to serve wms, you only need the
> wms_*.
> wfs_* conigures your WFS-server. If you want to serv wms and wfs and the
> parameters are the same, you can use ows_ instead.
>
>
>1. My layer is doing an OGR connection directly to the API URL. Works
>fine. My question is, the API renews itself every 2 minutes (new data).
>How does Mapserver handle the request with that connection? I move the
>map (openlayers), there's a new Mapserver request - does Mapserver make a
>new request to the API endpoint and get a new json?
>Or is there some sort of cache?
>
> No cache by default. MapServer requests the data source every time
> mapserver gets itself a getmap or get feature info request (or getfeature
> when serving wfs). So your WMS serves the actual data any time. If you want
> a cache, you have to configure mapcache or mapproxy separately.
>
>
>1. Am I missing something else from the Metadata that I should
>consider?
>
> I don't see anything missing
>
> Jörg
>
> Am 09.02.22 um 10:26 schrieb Sander Pukk:
>
> Hi there!
>
> Trying to use a geojson output from API directly in Mapserver layer.
> Geojson is per standard, 4326, but my Mapserver and OL (the client) is
> configured to 3301.
> We have hundreds of layers (mostly from Postgres) at the same time and the
> system works.
> No other direct API ones.
>
> The current MAP file's WEB part looks like this:
>
>   WEB
>>   METADATA
>> "wfs_title" "title"
>> "wfs_enable_request""*"
>> "wms_enable_request""*"
>> "wfs_encoding"  "UTF-8"
>> "wms_title" "title"
>> "wms_encoding"  "UTF-8"
>> "wms_onlineresource"
>>  "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
>> "wfs_onlineresource"
>>  "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
>> "ows_srs""EPSG:3301 EPSG:3857
>> EPSG:4326"
>> "ows_enable_request""*"
>> "wfs_getfeature_formatlist" "gml,geojson"
>> "wms_feature_info_mime_type"
>>  "application/json,application/json;
>> subtype=geojson,application/vnd.ogc.gml,text/plain"
>>   END
>>   END
>
>
>
>>   PROJECTION
>>   "init=epsg:3301"
>>   END
>
>
>
> And the layer:
>
> PROJECTION
>> "init=epsg:4326"
>> END
>>
>> METADATA
>> "wfs_srs"   "EPSG:3301"
>> "gml_msGeometry_type" "line"
>
> * #"ows_extent" "40500 5993000 1064500 7017000" copy paste lon and
>> lat from these 3301 coordinates from other layer's capabilites*
>> "ows_extent" "14.9318705986602 53.7681633673032 35.1060366818735
>> 63.2747817924556"
>> "wfs_extent""14.9318705986602 53.7681633673032
>> 35.1060366818735 63.2747817924556"
>> "wms_extent""14.9318705986602 53.7681633673032
>> 35.1060366818735 63.2747817924556"
>> "ows_title" "road_restrictions"
>> "ows_abstract" "road_restrictions"
>> "ows_keywordlist" "road_restrictions"
>> "ows_include_items" "all"
>> "gml_include_items" "all"
>> "ows_featureid" "id"
>> "gml_exclude_items" "edges,geometry"
>> "ows_exclude_items" "edges,geometry"
>> END
>
>
>
>  Couple of questions I have which I didnt really find answers for:
>
>
>1. Had issues with 4326 to 3301 transformation,the extent and all
>that. (OpenLayers could manage but QGIS couldnt). Previously only had
>ows_extent.
>Is ows_extent even a thing? This only shows wms_extent
>https://mapserver.org/ogc/wms_server.html#layer-object-metadata
>Should you use wfs_extent and wms_extent instead?
>2. My layer is doing an OGR connection directly to the API URL. Works
>fine. My question is, the API renews itself every 2 minutes (new data).
>How does Mapserver handle the request with that connection? I move the
>map (openlayers), there's a new Mapserver request - does Mapserver make a
>new request to the API endpoint and get a new json?
>Or is there some sort of cache?
>3. Am I missing something else from the Metadata that I should
>consider?
>
>
> With kind regards,
> Sander
>
> ___
> MapServer-users mailing 
> 

Re: [mapserver-users] Mapserver URL request layer

[WhereGroup]

Hello Sander,


 1. Had issues with 4326 to 3301 transformation,the extent and all
that. (OpenLayers could manage but QGIS couldnt). Previously only
had ows_extent.
Is ows_extent even a thing? This only shows wms_extent
https://mapserver.org/ogc/wms_server.html#layer-object-metadata
Should you use wfs_extent and wms_extent instead?

the wms_ / wfs_ / ows_ / oga_ (coming in MapServer 8) Metadata-entry are 
aiming on your output. So, if you only want to serve wms, you only need 
the wms_*.
wfs_* conigures your WFS-server. If you want to serv wms and wfs and the 
parameters are the same, you can use ows_ instead.


 1. My layer is doing an OGR connection directly to the API URL. Works
fine. My question is, the API renews itself every 2 minutes (new
data).
How does Mapserver handle the request with that connection? I move
the map (openlayers), there's a new Mapserver request - does
Mapserver make a new request to the API endpoint and get a new json?
Or is there some sort of cache?

No cache by default. MapServer requests the data source every time 
mapserver gets itself a getmap or get feature info request (or 
getfeature when serving wfs). So your WMS serves the actual data any 
time. If you want a cache, you have to configure mapcache or mapproxy 
separately.



 1. Am I missing something else from the Metadata that I should consider?


I don't see anything missing

Jörg

Am 09.02.22 um 10:26 schrieb Sander Pukk:

Hi there!

Trying to use a geojson output from API directly in Mapserver layer.
Geojson is per standard, 4326, but my Mapserver and OL (the client) is 
configured to 3301.
We have hundreds of layers (mostly from Postgres) at the same time and 
the system works.

No other direct API ones.

The current MAP file's WEB part looks like this:

WEB
      METADATA
        "wfs_title"                     "title"
        "wfs_enable_request"            "*"
        "wms_enable_request"            "*"
        "wfs_encoding"                  "UTF-8"
        "wms_title"                     "title"
        "wms_encoding"                  "UTF-8"
        "wms_onlineresource"
 "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
        "wfs_onlineresource"
 "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
        "ows_srs"                            "EPSG:3301 EPSG:3857
EPSG:4326"
        "ows_enable_request"            "*"
        "wfs_getfeature_formatlist"     "gml,geojson"
        "wms_feature_info_mime_type"
 "application/json,application/json;
subtype=geojson,application/vnd.ogc.gml,text/plain"
      END
  END

PROJECTION
      "init=epsg:3301"
  END

And the layer:

  PROJECTION
        "init=epsg:4326"
    END

    METADATA
        "wfs_srs"               "EPSG:3301"
        "gml_msGeometry_type" "line" 


/       #"ows_extent" "40500 5993000 1064500 7017000" copy paste
lon and lat from these 3301 coordinates from other layer's
capabilites/
        "ows_extent" "14.9318705986602 53.7681633673032
35.1060366818735 63.2747817924556"
        "wfs_extent"        "14.9318705986602 53.7681633673032
35.1060366818735 63.2747817924556"
        "wms_extent"        "14.9318705986602 53.7681633673032
35.1060366818735 63.2747817924556"
        "ows_title" "road_restrictions"
        "ows_abstract" "road_restrictions"
        "ows_keywordlist" "road_restrictions"
        "ows_include_items" "all"
        "gml_include_items" "all"
        "ows_featureid" "id"
        "gml_exclude_items"         "edges,geometry"
        "ows_exclude_items"         "edges,geometry"
    END 




 Couple of questions I have which I didnt really find answers for:

 1. Had issues with 4326 to 3301 transformation,the extent and all
that. (OpenLayers could manage but QGIS couldnt). Previously only
had ows_extent.
Is ows_extent even a thing? This only shows wms_extent
https://mapserver.org/ogc/wms_server.html#layer-object-metadata
Should you use wfs_extent and wms_extent instead?
 2. My layer is doing an OGR connection directly to the API URL. Works
fine. My question is, the API renews itself every 2 minutes (new
data).
How does Mapserver handle the request with that connection? I move
the map (openlayers), there's a new Mapserver request - does
Mapserver make a new request to the API endpoint and get a new json?
Or is there some sort of cache?
 3. Am I missing something else from the Metadata that I should consider?

With kind regards,
Sander

___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users



--
Viele Grüße,
Jörg Thomsen

 -
 Schon gewusst?

 In unserem Blog geben wir Tipps & Tricks zu
 

Re: [mapserver-users] Mapserver URL request layer

[Rahkonen Jukka (MML)]

Hi,

About ows_* from https://www.mapserver.org/ogc/wms_server.html

(Note that each of the metadata below can also be referred to as ‘ows_*’ 
instead of ‘wms_*’. MapServer tries the ‘wms_*’ metadata first, and if not 
found it tries the corresponding ‘ows_*’ name. Using this reduces the amount of 
duplication in mapfiles that support multiple OGC interfaces since “ows_*” 
metadata can be used almost everywhere for common metadata items shared by 
multiple OGC interfaces.)

-Jukka Rahkonen-

Lähettäjä: MapServer-users  Puolesta 
Sander Pukk
Lähetetty: keskiviikko 9. helmikuuta 2022 11.26
Vastaanottaja: Jason Snyder 
Aihe: [mapserver-users] Mapserver URL request layer

Hi there!

Trying to use a geojson output from API directly in Mapserver layer.
Geojson is per standard, 4326, but my Mapserver and OL (the client) is 
configured to 3301.
We have hundreds of layers (mostly from Postgres) at the same time and the 
system works.
No other direct API ones.

The current MAP file's WEB part looks like this:

  WEB
  METADATA
"wfs_title" "title"
"wfs_enable_request""*"
"wms_enable_request""*"
"wfs_encoding"  "UTF-8"
"wms_title" "title"
"wms_encoding"  "UTF-8"
"wms_onlineresource"
"url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
"wfs_onlineresource"
"url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
"ows_srs""EPSG:3301 EPSG:3857 EPSG:4326"
"ows_enable_request""*"
"wfs_getfeature_formatlist" "gml,geojson"
"wms_feature_info_mime_type""application/json,application/json; 
subtype=geojson,application/vnd.ogc.gml,text/plain"
  END
  END

  PROJECTION
  "init=epsg:3301"
  END


And the layer:

PROJECTION
"init=epsg:4326"
END

METADATA
"wfs_srs"   "EPSG:3301"
"gml_msGeometry_type" "line"
 #"ows_extent" "40500 5993000 1064500 7017000" copy paste lon and lat 
from these 3301 coordinates from other layer's capabilites
"ows_extent" "14.9318705986602 53.7681633673032 35.1060366818735 
63.2747817924556"
"wfs_extent""14.9318705986602 53.7681633673032 35.1060366818735 
63.2747817924556"
"wms_extent""14.9318705986602 53.7681633673032 35.1060366818735 
63.2747817924556"
"ows_title" "road_restrictions"
"ows_abstract" "road_restrictions"
"ows_keywordlist" "road_restrictions"
"ows_include_items" "all"
"gml_include_items" "all"
"ows_featureid" "id"
"gml_exclude_items" "edges,geometry"
"ows_exclude_items" "edges,geometry"
END


 Couple of questions I have which I didnt really find answers for:


  1.  Had issues with 4326 to 3301 transformation,the extent and all that. 
(OpenLayers could manage but QGIS couldnt). Previously only had ows_extent.
Is ows_extent even a thing? This only shows wms_extent 
https://mapserver.org/ogc/wms_server.html#layer-object-metadata
Should you use wfs_extent and wms_extent instead?
  2.  My layer is doing an OGR connection directly to the API URL. Works fine. 
My question is, the API renews itself every 2 minutes (new data).
How does Mapserver handle the request with that connection? I move the map 
(openlayers), there's a new Mapserver request - does Mapserver make a new 
request to the API endpoint and get a new json?
Or is there some sort of cache?
  3.  Am I missing something else from the Metadata that I should consider?
With kind regards,
Sander
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Mapserver URL request layer

[Sander Pukk]

Hi there!

Trying to use a geojson output from API directly in Mapserver layer.
Geojson is per standard, 4326, but my Mapserver and OL (the client) is
configured to 3301.
We have hundreds of layers (mostly from Postgres) at the same time and the
system works.
No other direct API ones.

The current MAP file's WEB part looks like this:

  WEB
>   METADATA
> "wfs_title" "title"
> "wfs_enable_request""*"
> "wms_enable_request""*"
> "wfs_encoding"  "UTF-8"
> "wms_title" "title"
> "wms_encoding"  "UTF-8"
> "wms_onlineresource"
>  "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
> "wfs_onlineresource"
>  "url/mapserv?map=/app/gis/infokihid/infolayers_other.map&"
> "ows_srs""EPSG:3301 EPSG:3857
> EPSG:4326"
> "ows_enable_request""*"
> "wfs_getfeature_formatlist" "gml,geojson"
> "wms_feature_info_mime_type"
>  "application/json,application/json;
> subtype=geojson,application/vnd.ogc.gml,text/plain"
>   END
>   END



>   PROJECTION
>   "init=epsg:3301"
>   END



And the layer:

PROJECTION
> "init=epsg:4326"
> END
>
> METADATA
> "wfs_srs"   "EPSG:3301"
> "gml_msGeometry_type" "line"

* #"ows_extent" "40500 5993000 1064500 7017000" copy paste lon and
> lat from these 3301 coordinates from other layer's capabilites*
> "ows_extent" "14.9318705986602 53.7681633673032 35.1060366818735
> 63.2747817924556"
> "wfs_extent""14.9318705986602 53.7681633673032
> 35.1060366818735 63.2747817924556"
> "wms_extent""14.9318705986602 53.7681633673032
> 35.1060366818735 63.2747817924556"
> "ows_title" "road_restrictions"
> "ows_abstract" "road_restrictions"
> "ows_keywordlist" "road_restrictions"
> "ows_include_items" "all"
> "gml_include_items" "all"
> "ows_featureid" "id"
> "gml_exclude_items" "edges,geometry"
> "ows_exclude_items" "edges,geometry"
> END



 Couple of questions I have which I didnt really find answers for:


   1. Had issues with 4326 to 3301 transformation,the extent and all that.
   (OpenLayers could manage but QGIS couldnt). Previously only had ows_extent.
   Is ows_extent even a thing? This only shows wms_extent
   https://mapserver.org/ogc/wms_server.html#layer-object-metadata
   Should you use wfs_extent and wms_extent instead?
   2. My layer is doing an OGR connection directly to the API URL. Works
   fine. My question is, the API renews itself every 2 minutes (new data).
   How does Mapserver handle the request with that connection? I move the
   map (openlayers), there's a new Mapserver request - does Mapserver make a
   new request to the API endpoint and get a new json?
   Or is there some sort of cache?
   3. Am I missing something else from the Metadata that I should consider?


With kind regards,
Sander
___
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users