Re: [MapServer-users] is it possible to use other attributes stored on tileindex and querry dataset using them?

2023-05-26 Thread Rahkonen Jukka
Hi, * is there possibility to add new parameter to url request based on another attribute in vector index file, for example max_cloud_cover or polarization_type? Simple. Add query parameters into the DATA of the tileindex layer. So instead of DATA "tile-index" use DATA "select * from

Re: [MapServer-users] is it possible to use other attributes stored on tileindex and querry dataset using them?

2023-05-26 Thread Marcin Niemyjski via MapServer-users
Jukka, you were right! Now it works like a charm! Big thank you! And Thanks Tanya for a suggestion. But in reference to my first mail - is there possibility to add new parameter to url request based on another attribute in vector index file, for example max_cloud_cover or polarization_type?

Re: [MapServer-users] is it possible to use other attributes stored on tileindex and querry dataset using them?

2023-05-25 Thread Rahkonen Jukka
Hi, Read the whole documentation page. Mapserver is implementing the WMS-T standard and in the standard the time parameter is named “TIME”. See examples https://mapserver.org/ogc/wms_time.html#supported-time-requests. So even the timeitem in your tileindex is “timestamp”, the parameter to use

[MapServer-users] is it possible to use other attributes stored on tileindex and querry dataset using them?

2023-05-25 Thread Marcin Niemyjski via MapServer-users
Hello, I've managed to find solution similar solution to what I looked for in pervious mail at https://mapserver.org/ogc/wms_time.html#example-of-wms-t-with-postgis-tile-index-for-raster-imagery but when using below GetMap url request, Mapserver keeps returning data for default timestamp

[MapServer-users] is it possible to use other attributes stored on tileindex and querry dataset using them?

2023-05-25 Thread Marcin Niemyjski via MapServer-users
Hello, is it possible to use other attributes stored on tileindex and querry dataset using them? For example, here is the structure of my tileindex: geometry | location | time | cloud_cover By default, Mapserver uses only geometry and location to check the spatial extent and then uses path to