Re: Python bindings: aliasing gdal.Open and gdal.OpenEx
Vincent Schut via gdal-dev <[email protected]> Fri, 19 Jun 2026 10:13:44 +0200
| Newsgroups | gmane.comp.gis.gdal.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============7127498577123552723==
Content-Type: multipart/alternative;
boundary="------------hyCLMH81PJe2XetTMA0DX37g"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------hyCLMH81PJe2XetTMA0DX37g
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
On 2026-06-17 1:49 pm, Even Rouault via gdal-dev wrote:
> Hi,
>
> I'd like to have a broader feedback of the community on
> https://github.com/OSGeo/gdal/pull/14763 . Please read it in detail.
> In practice, the main backwards incompatibility would be the point 1 I
> mention in the PR text, that is that for current users of
> gdal.Open(dsname), they would now get vector datasets opened in
> addition to raster ones. While I see this is as a long term benefit,
> at least one user (https://github.com/ubarsc/rios/pull/192) had to
> work around it since they expected gdal.Open() to fail on vector
> datasets. The workaround being to use gdal.OpenEx(dsname,
> gdal.OF_RASTER) that will work before and after the PR, or if
> targeting only post PR state, gdal.Open(dsname, gdal.OF_RASTER)
>
> PR 14763 would be potential material for a GDAL 4 if that did occur,
> but I don't know if it is desirable and even if it was, I don't think
> it would happen in a short or medium term (mostly because the GDAL dev
> community is too small to be able to gather a significant set of
> backwards incompatible change in a reasonable period of time, while
> not blocking features to be released at a reasonable frequency). So
> we're more in a situation where we land a few backwards incompatible
> change each (non bugfix) release.
>
> Even
>
Hi Even,
(I doubted whether to reply because it was a bit unclear to me if you
only wanted people with concerns to reply, or also people who don't see
any issue with the proposed change.)
We (as quite heavy users of gdal in our internal python software) do not
see any issues with this proposal for us, and would in fact welcome this
change because it will reduce ambiguity between the 2 possible ways to
open raster datasets.
Thanks for asking feedback,
Vincent.
--
Vincent Schut
Remote Sensing Software Engineer
+31 302272679 ~ Maliebaan 22 | 3581CP | Utrecht | Netherlands
Linkedin <https://www.linkedin.com/company/satelligence/>~
satelligence.com <http://www.satelligence.com><http://www.satelligence.com>
--------------hyCLMH81PJe2XetTMA0DX37g
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2026-06-17 1:49 pm, Even Rouault via
gdal-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:[email protected]">Hi,
<br>
<br>
I'd like to have a broader feedback of the community on
<a class="moz-txt-link-freetext" href="https://github.com/OSGeo/gdal/pull/14763">https://github.com/OSGeo/gdal/pull/14763</a> . Please read it in
detail. In practice, the main backwards incompatibility would be
the point 1 I mention in the PR text, that is that for current
users of gdal.Open(dsname), they would now get vector datasets
opened in addition to raster ones. While I see this is as a long
term benefit, at least one user
(<a class="moz-txt-link-freetext" href="https://github.com/ubarsc/rios/pull/192">https://github.com/ubarsc/rios/pull/192</a>) had to work around it
since they expected gdal.Open() to fail on vector datasets. The
workaround being to use gdal.OpenEx(dsname, gdal.OF_RASTER) that
will work before and after the PR, or if targeting only post PR
state, gdal.Open(dsname, gdal.OF_RASTER)
<br>
<br>
PR 14763 would be potential material for a GDAL 4 if that did
occur, but I don't know if it is desirable and even if it was, I
don't think it would happen in a short or medium term (mostly
because the GDAL dev community is too small to be able to gather a
significant set of backwards incompatible change in a reasonable
period of time, while not blocking features to be released at a
reasonable frequency). So we're more in a situation where we land
a few backwards incompatible change each (non bugfix) release.
<br>
<br>
Even
<br>
<br>
</blockquote>
Hi Even,<br>
<br>
(I doubted whether to reply because it was a bit unclear to me if
you only wanted people with concerns to reply, or also people who
don't see any issue with the proposed change.)<br>
<br>
We (as quite heavy users of gdal in our internal python software) do
not see any issues with this proposal for us, and would in fact
welcome this change because it will reduce ambiguity between the 2
possible ways to open raster datasets.<br>
<br>
Thanks for asking feedback,<br>
Vincent.
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title></title>
<div class="moz-signature">
<div class="moz-signature">
<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.799999999999999pt">
<td
style="border-left:solid #003c5a
1.5pt;border-right:solid #ffffff
1pt;border-bottom:solid #ffffff 1pt;border-top:solid
#ffffff 1pt;vertical-align:top;padding:4.32pt 4.32pt
4.32pt
4.32pt;overflow:hidden;overflow-wrap:break-word;">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;"><span
style="border: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-left:solid #ffffff
1pt;border-right:solid #ffffff 1pt;border-bottom:solid
#ffffff 1pt;border-top:solid #ffffff
1pt;vertical-align:middle;padding:5pt 5pt 5pt
5pt;overflow:hidden;overflow-wrap:break-word;">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:11pt;font-family:Arial;color:#003c5a;background-color:transparent;font-weight:700;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;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:#003c5a;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Remote Sensing Software Engineer
</span></p>
</td>
</tr>
<tr style="height:10.799999999999999pt">
<td colspan="2"
style="border-left:solid #003c5a
1.5pt;border-right:solid #ffffff
1pt;border-bottom:solid #ffffff 1pt;border-top:solid
#ffffff 1pt;vertical-align:top;padding:5pt 5pt 5pt
5pt;overflow:hidden;overflow-wrap:break-word;">
<p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:8pt;font-family:Arial;color:#b7b7b7;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;"><span
style="border: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="docs-internal-guid-30036d47-7fff-c8bb-a5a1-95628900a5a0"><span
style="font-size:8pt;font-family:Arial;color:#b7b7b7;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;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="docs-internal-guid-fa359a62-7fff-0882-e450-fae9010e52d8"><span
style="font-size:8pt;font-family:Arial;color:#b7b7b7;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;-webkit-text-decoration-skip:none;text-decoration-skip-ink:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Linkedin</span></a><span
style="font-size:8pt;font-family:Arial;color:#b7b7b7;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;"> ~ </span><a
href="http://www.satelligence.com"
style="text-decoration:none;"><span
style="font-size:8pt;font-family:Arial;color:#b7b7b7;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;-webkit-text-decoration-skip:none;text-decoration-skip-ink:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">satelligence.com</span></a><a
href="http://www.satelligence.com"
style="text-decoration:none;"><span
style="font-size:8pt;font-family:Arial;color:#b7b7b7;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;-webkit-text-decoration-skip:none;text-decoration-skip-ink:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;"></span></a></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
<br>
</body>
</html>
--------------hyCLMH81PJe2XetTMA0DX37g--
--===============7127498577123552723==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--===============7127498577123552723==--