<div dir="ltr"><div>Yes, internally the GDAL TileDB driver remaps vsis3 requests to s3 requests within the TileDB library. To a user the vsi notation still works the same. <br></div><div><br></div><div>I will look over the PR, thanks Vincent!</div><div><br></div><div>Norman<br></div></div><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 23, 2021 at 9:30 AM Vincent Schut <<a href="mailto:schut@satelligence.com" target="_blank">schut@satelligence.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div>
    Even's understanding is correct. I've made a small PR to add this
    functionality: <a href="https://github.com/OSGeo/gdal/pull/3728" target="_blank">https://github.com/OSGeo/gdal/pull/3728</a>. I'm not an
    experienced c++ programmer, so I hope I've done things the right
    way. At least it works here.<br>
    <br>
    Let's move the rest of the discussion - if any - to the PR.<br>
    <br>
    Vincent.<br>
    <br>
    <div>On 4/23/21 4:20 PM, Even Rouault wrote:<br>
    </div>
    <blockquote type="cite">
      
      <p>Sean,</p>
      <p>my understanding of the commit is that internally the tiledb
        SDK handles cloud storage by itself (ie not relying on GDAL
        virtual file systems) and using s3:// / gcs:// naming
        conventions, and the purpose of the below referenced commit is,
        for the GDALOpen() code path, to remap /vsis3/ to s3:// , since
        that's what tiledb SDK expects. But Norman might better comment
        on.</p>
      <p>Even<br>
      </p>
      <div>Le 23/04/2021 à 16:14, Sean Gillies a
        écrit :<br>
      </div>
      <blockquote type="cite">
        <div dir="ltr">
          <div>Hi Vincent, Even.</div>
          <div><br>
          </div>
          <div>Why would we do this when /vsigcs/... should work?
            Letting individual drivers set their own conventions for
            dataset names seems, to me, to hurt long-term maintenance
            and interoperability.</div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Fri, Apr 23, 2021 at
              7:34 AM Vincent Schut <<a href="mailto:schut@satelligence.com" target="_blank">schut@satelligence.com</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote">
              <div> Thanks for confirming, Even. That doesn't look too
                difficult. I'll give it a try.<br>
                <br>
                <div>On 4/23/21 3:09 PM, Even Rouault wrote:<br>
                </div>
                <blockquote type="cite">
                  <p>I guess you should add something similar to <a href="https://github.com/OSGeo/gdal/commit/3623f9c91a2c513af204d30fe25314dbe5c7b9be" target="_blank">https://github.com/OSGeo/gdal/commit/3623f9c91a2c513af204d30fe25314dbe5c7b9be</a>
                    for /vsigs<br>
                  </p>
                  <div>Le 23/04/2021 à 14:59, Vincent Schut a écrit :<br>
                  </div>
                  <blockquote type="cite"> On 4/23/21 2:17 PM, Vincent
                    Schut wrote:<br>
                    <blockquote type="cite"> Hi, how should I specify a
                      tiledb dataset's url that resides on gcs (google
                      cloud storage) to gdal? I've tried several
                      combinations of gcs://, /vsigs/, prefixed with
                      TILEDB:// or not, but no luck. I've looked in the
                      driver source, and apparently there is only a
                      /vsis3/ -> tiledb uri translation, but no
                      equivalent gcs one?<br>
                      <br>
                    </blockquote>
                    To clarify this a bit: writing works:<br>
                    <br>
                    gdal_translate -of tiledb -co COMPRESSION=ZSTD
                    S2B_MSIL1C_20210227T032659_N0209_R018_T47MQV_20210227T072433.tif
gcs://s11-dev-vincent-tiledb-test-public/S2B_MSIL1C_20210227T032659_N0209_R018_T47MQV_20210227T072433.tiledb<br>
                    <br>
                    and the file is correctly created in the bucket.
                    However, when I want to open it, it fails:<br>
                    <br>
                    gdalinfo -if tiledb
gcs://s11-dev-vincent-tiledb-test-public/S2B_MSIL1C_20210227T032659_N0209_R018_T47MQV_20210227T072433.tiledb<br>
                    ERROR 4:
gcs://s11-dev-vincent-tiledb-test-public/S2B_MSIL1C_20210227T032659_N0209_R018_T47MQV_20210227T072433.tiledb:
                    No such file or directory<br>
                    gdalinfo failed - unable to open
'gcs://s11-dev-vincent-tiledb-test-public/S2B_MSIL1C_20210227T032659_N0209_R018_T47MQV_20210227T072433.tiledb'.<br>
                    <br>
                    Is there any way to correctly specify this tiledb
                    url on gcs for gdal?<br>
                    <br>
                    Vincent.</blockquote>
                </blockquote>
              </div>
            </blockquote>
          </div>
          -- <br>
          <div dir="ltr">
            <div dir="ltr">Sean Gillies</div>
          </div>
        </div>
      </blockquote>
      <pre cols="72">-- 
<a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
    </blockquote>
    <br>
    <div>-- <br>
      
      
      <div>
        <div>
          <div dir="ltr" style="margin-left:2.88pt" align="left"><br>
            <table style="border:medium none;border-collapse:collapse" width="408" height="179">
              <colgroup><col width="60"><col width="283"></colgroup><tbody>
                <tr style="height:10.8pt">
                  <td style="border-color:rgb(255,255,255) rgb(255,255,255) rgb(255,255,255) rgb(0,60,90);border-style:solid;border-width:1pt 1pt 1pt 1.5pt;vertical-align:top;padding:4.32pt;overflow:hidden">
                    <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><span style="border:medium none;display:inline-block;overflow:hidden;width:53px;height:53px"><img src="https://lh6.googleusercontent.com/t1GD8ftw5REdi0_kM1UjrXeX-Y-jF5xKxDqUGLsLKzftVahqw_CWQhqciHkLLYkldd9pcYmNd-pmzNnY1fc93vYpJ0Q0P-O1VC51jsTJUy-yhjF4ioK2hGq156_JYVROec9im6tW" style="margin-left: 0px; margin-top: 0px;" width="53" height="53"></span></span></p>
                  </td>
                  <td style="border-color:rgb(255,255,255);border-style:solid;border-width:1pt;vertical-align:middle;padding:5pt;overflow:hidden">
                    <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:Arial;color:rgb(0,60,90);background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Vincent Schut</span></p>
                    <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,60,90);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Remote Sensing Software Engineer
</span></p>
                  </td>
                </tr>
                <tr style="height:10.8pt">
                  <td colspan="2" style="border-color:rgb(255,255,255) rgb(255,255,255) rgb(255,255,255) rgb(0,60,90);border-style:solid;border-width:1pt 1pt 1pt 1.5pt;vertical-align:top;padding:5pt;overflow:hidden">
                    <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:8pt;font-family:Arial;color:rgb(183,183,183);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><span style="border:medium none;display:inline-block;overflow:hidden;width:217px;height:34px"><img src="https://lh5.googleusercontent.com/H6PdQi9jrkkJRWy7wGQ92waInTqhh3atodO0R0CNgKm2YooJBK2vOEU2M7t5HB5FMJyOUhyFxsTqtEnqLi3zXnRbPNJEvoEyr9RyBFKKHUjT8py8Pu92ga3Urmp_zARoHqtNFY6K" style="margin-left: 0px; margin-top: 0px;" width="217" height="34"></span></span></p>
                    <p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt" id="gmail-m_-3668696205911003637gmail-m_-421161769854529924docs-internal-guid-30036d47-7fff-c8bb-a5a1-95628900a5a0"><span style="font-size:8pt;font-family:Arial;color:rgb(183,183,183);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">+31 302272679 ~ Maliebaan 22 | 3581CP | Utrecht | Netherlands</span></p>
                    <a href="https://www.linkedin.com/company/satelligence/" style="text-decoration:none" id="gmail-m_-3668696205911003637gmail-m_-421161769854529924docs-internal-guid-fa359a62-7fff-0882-e450-fae9010e52d8" target="_blank"><span style="font-size:8pt;font-family:Arial;color:rgb(183,183,183);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">Linkedin</span></a><span style="font-size:8pt;font-family:Arial;color:rgb(183,183,183);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"> ~ </span><a href="http://www.satelligence.com" style="text-decoration:none" target="_blank"><span style="font-size:8pt;font-family:Arial;color:rgb(183,183,183);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">satelligence.com</span></a><a href="http://www.satelligence.com" style="text-decoration:none" target="_blank"><span style="font-size:8pt;font-family:Arial;color:rgb(183,183,183);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap"></span></a></td>
                </tr>
              </tbody>
            </table>
          </div>
        </div>
      </div>
    </div>
  </div>

_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</blockquote></div>