<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Michał,</p>
<div class="moz-cite-prefix">Le 10/09/2024 à 14:14, Michał Kowalczuk
via gdal-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAP+FqQB5fi8BkYspGqkJ_FXph_6PEqD-PgRXg5HydXDSEiPtZQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I found that there was a similar issue in 2021
without any specific answer:
<div><a
href="https://www.mail-archive.com/gdal-dev@lists.osgeo.org/msg35549.html"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.mail-archive.com/gdal-dev@lists.osgeo.org/msg35549.html</a></div>
<div><br>
</div>
<div>I wonder if getting SUBDATASETS shouldn't return the result
in a similar way as it does for WMTS service,</div>
<div>where GDAL generates paths to all
layer/tilematrix/tilematrixset combination.</div>
<div>For example if layer is available in 3 SRS, GDAL produces 3
subdatasets, so using only SUBDATASE_NAME property user has
access to all map services shared by WMTS server.</div>
<div>In my opinion, GDAL should use the same approach for WMS. </div>
<div><br>
</div>
<div>Does anyone object?</div>
I will then submit a new feature request/bug report.</div>
</blockquote>
<p>That sounds useful. However I'm wondering if users won't be
overwhelmed by a tons of possible SRS. WMS GetCapabilities tend
sometimes to list tons of possible SRS. With WMTS, as you need to
provide TileMatrixSet definitions, that's less likely to happen.
So perhaps add a LIST_ALL_SRS=YES/NO open option, possibly
defaulting to NO.</p>
<p>Even<span style="white-space: pre-wrap"></span><br>
</p>
<p>-- </p>
<pre class="moz-signature" cols="72"><a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>