Rasterio's tests are broken by changes coming in GDAL 3.11.0, but for known
and understood reasons. I'm fine with the release.
On Wed, May 7, 2025 at 10:05 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> +1 Even
>
>
--
Sean Gillies
__
inputs, because in my
> experience they lead to difficult-to-track errors in user code.
>
> Dan
>
> On Sun, Apr 20, 2025 at 9:42 PM Sean Gillies via gdal-dev <
> gdal-dev@lists.osgeo.org> wrote:
>
>> Hi Even, Dan, and everyone,
>>
>> https://github.c
Hi Even, Dan, and everyone,
https://github.com/OSGeo/gdal/pull/11978 breaks Rasterio's reproject().
Could we consider reverting the change at
https://github.com/OSGeo/gdal/pull/11978/files#diff-4ff2c1ac40e44d829d06107ff9d5ca0a19364b1793264488f41441da8e22R789?
I've never seen a problem with thi
RTD is indispensable! +1 ftom me.
Sean Gillies
On Thu, Apr 17, 2025, 10:39 AM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Dear PSC,
>
> GDAL and PROJ depend upon ReadTheDocs for documentation generation and
> hosting. RTD does not charge for open source projects to host
> doc
Hi Adriano,
I'm the maintainer of Rasterio and have been distributing wheels that
include GDAL on PyPI for a few years. I do not recommend the experience of
doing this. I'm writing a blog post about it, but it's not done yet. The
TL;DR is: it's hard, there's endless toil, and you spend time intera
+1
On Mon, Mar 3, 2025 at 9:30 AM Daniel Morissette via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi PSC members,
>
> I would like to nominate Michael Smith to become a member of the GDAL
> Project Steering Committee.
>
>https://www.osgeo.org/member/michael-smith/
>
> Mike is a long time
Hi Tim,
UseExceptions() might only affect your main thread. You may want to check
in GDAL's code to see if this is the case. At any rate, you won't be able
to handle Python exceptions that you might see raised from the warp threads.
Hope this helps,
On Sat, Mar 1, 2025 at 11:30 AM Tim Harris via
Looks good from the perspective of Rasterio, Even:
https://github.com/rasterio/rasterio/actions/runs/12654697105.
On Tue, Jan 7, 2025 at 8:56 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> I have prepared a GDAL/OGR 3.10.1 release candidate.
>
> Pick up an archive among
+1 and a happy new year to all!.
On Thu, Jan 2, 2025 at 7:54 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> Happy New Year to everyone!
>
> PSC,
>
> GDAL depends on conda-forge builds for a number of its continuous
> integration configurations, as well as offering build
Hi Even,
This episode is a reminder that making quotation marks part of the GDAL
filename syntax was a mistake. Reverting it would be a big effort, but at
the very least we should stop propagating it. Specifically, if a new driver
with subdataset capabilities were to be written tomorrow it should
Good to go here:
https://github.com/rasterio/rasterio/actions/runs/11639437093.
+1
On Mon, Nov 4, 2024 at 5:28 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> I believe RC3 is good to go, so:
>
> Motion: approve GDAL 3.10.0 RC3 as 3.10.0 release
>
> Starting with my +1
Hi Even,
Rasterio still has a problem with the lock-down of MEM:: datasets. I missed
a few spots where GDAL warp utilities open the datasets behind the scenes.
I think I should be able to make a new release by the end of the week.
On Tue, Oct 29, 2024 at 7:14 AM Even Rouault via gdal-dev <
gdal-d
Even,
Would the defaults result in overly large attribute files? By a small
amount or an excessive amount? Or would the defaults result in truncation
of values?
On Sat, Oct 5, 2024 at 4:48 PM Even Rouault
wrote:
> Sean,
>
> > What are vector field width and precision good for in 2024? These
> >
Hi all,
What are vector field width and precision good for in 2024? These concepts
were inherited from MS Access via Shapefile, I believe. I've been wondering
if I can stop supporting them in my Fiona project without breaking
workflows badly. Numpy data types don't have width and precision. Neithe
-2368801316
>
> To actually answer your last question, this is a bit more subtle than the
> above. For example, if there's a mix of strings and array of strings, we
> report a StringList field. If there's a mix of integer and floating-point
> numbers, we report a Real
Hi all,
The good thing about GeoJSON is that you don't need specialized GIS
software to create it. The bad thing about GeoJSON is that people create it
using software with none of the familiar GIS constraints.
I've been looking at a collection of features that have the same set of
properties (goo
Hi all,
In theory, we can read anything from a zip archive without extracting it to
the filesystem, but sometimes drivers have special requirements and
limitations. Is JP2 from a zipfile supported by OpenJPEG?
--
Sean Gillies
___
gdal-dev mailing list
Absolutely yes +1
On Wed, Sep 11, 2024, 8:24 PM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> PSC,
>
> I am motioning to renew Even's maintainer contract through the GDAL
> Sponsorship Program that is hosted by NumFOCUS for another year.
>
> /me starts with a +1
>
> Howard
> ___
3.9.2rc1 looks good from the Rasterio perspective:
https://github.com/rasterio/rasterio/actions/runs/10345292335/job/28632108339
On Sun, Aug 11, 2024 at 11:01 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> I have prepared a GDAL/OGR 3.9.2 release candidate.
>
> Pick up
Hi Sibylle,
It looks to me that you need to specify an environment location within your
own user directory. The page at
https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#specifying-a-location-for-an-environment
has instructions on this.
Yours,
On Tue, Aug 6, 20
Thanks for the fix and suggestions! I'm looking forward to 3.9.0.
On Mon, Apr 22, 2024 at 11:27 AM Even Rouault
wrote:
> Sean,
>
> Rasterio's test suite has 4 errors with GDAL 3.9.0beta1.
>
> Metadata output of gdalinfo has changed.
>
> ok, I've run locally rasterio tests and I see gdalinfo now
Thanks, Jukka!
On Mon, Apr 22, 2024 at 10:48 AM Rahkonen Jukka <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> Hi,
>
>
>
> The mask thing may happen due to https://github.com/OSGeo/gdal/pull/9604.
>
>
>
> -Jukka Rahkonen-
>
>
>
> *Lähettäjä:* gda
Hi Even,
Rasterio's test suite has 4 errors with GDAL 3.9.0beta1.
Metadata output of gdalinfo has changed. As soon as there are docker images
I'll look more closely at this.
Writing a mask to a Rasterio RGB.byte.tif dataset no longer creates a
RGB.byte.tif.msk
file:
https://github.com/rasterio/r
But if you open another
>> VRT (or the same one), it will not share the same GDALDataset for sources
>> that may be common with the first one, so no re-use of existing block
>> cache. For network sources, the I/O cache at the /vsicurl/ level works
>> however on filenames,
n filenames, not VSIFILE* instances, so you will save network reads
>
> Even
> Le 19/04/2024 à 16:48, Sean Gillies via gdal-dev a écrit :
>
> Happy Friday, folks!
>
> Are the source rasters of a VRT added to the block cache such that
> different VRTs using the same source can
Happy Friday, folks!
Are the source rasters of a VRT added to the block cache such that
different VRTs using the same source can avoid reads from disk or the
network? Or is it intended that the VSI cache covers this need instead?
Thanks,
--
Sean Gillies
_
Thank you for the analysis, Even!
I've made similar announcements for the fiona and rasterio projects and
plagiarized your subject line. Fiona and rasterio wheels on PyPI include
versions of liblzma no more recent than 5.4.4 and do not include libarchive.
https://github.com/Toblerity/Fiona/discus
re sidecar files
>> are optional and not used in a cloud-storage environment (namely cogs) )
>>
>> On Tue, Feb 13, 2024 at 6:12 PM Sean Gillies via gdal-dev <
>> gdal-dev@lists.osgeo.org> wrote:
>>
>>> Hi all,
>>>
>>> It's not clear t
t Readdir() (which might break drivers
> that require sidecar files to work, but speeds up those where sidecar files
> are optional and not used in a cloud-storage environment (namely cogs) )
>
> On Tue, Feb 13, 2024 at 6:12 PM Sean Gillies via gdal-dev <
> gdal-dev@lists.osgeo.org
Hi all,
It's not clear to me from reading
https://gdal.org/user/virtual_file_systems.html if VSI sidecar and sibling
file lookup works in general, by design, or whether it's an implementation
detail of the standard VSI filesystems ("vsizip", "vsicurl", etc.).
More specifically: if I have a "/vsip
Hi all,
I haven't found a specification for the empty pixel value of datasets
created by, say, gdal_create. Is it format specific?
--
Sean Gillies
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Happy New Year to you too, Abel.
Other drivers, such as PCI and NITF, include some files in the data
directory. See https://github.com/OSGeo/gdal/tree/master/data.
Distributions generally copy these to $prefix/share/gdal on unix-like
systems. I'm not aware of a practice of copying data out of a
Hi Even,
I'm wondering how this relates to STAC. Do you imagine that GDAL users
should and will use this to publish large collections of data? When should
they use this and when should they use STAC collections instead?
Back in the day our tile indexes were shapefiles. I don't think this would
be
For what it's worth, Rasterio has required Numpy for a few versions, and
there's never been a single complaint about it. The footprint and extra
complexity of numpy is just a drop in the bucket.
I suppose that someone using only the OGR parts of the Python bindings
might be inconvenienced, but not
I finally have configured a GitHub action that tests rasterio against the
latest GDAL tags and don't see any problems with 3.8.1RC3:
https://github.com/rasterio/rasterio/actions/runs/7022736307.
+1 for me
On Tue, Nov 28, 2023 at 8:32 AM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
Sounds good to me, Even. Rasterio's wheels can remain at the forefront of
terrible for now.
On Thu, Nov 16, 2023 at 5:10 AM Even Rouault
wrote:
> Hi Sean,
> >
> > I think this makes great sense for the project. I don't yet understand
> > what it means for an enterprise like Rasterio's PyPI wheel
Hi Even,
I think this makes great sense for the project. I don't yet understand what
it means for an enterprise like Rasterio's PyPI wheels.
Here's a refresher for people who aren't familiar with Python packaging
tools like delocate, auditwheel, and delvewheel. Today, these tools detect
when Rast
I'm changing Rasterio's CI to test against both the head of the master
branch and the head of the current release branch, so in the future I'll
likely only speak up if something is broken right before the release.
3.7.3RC1 looks good to me. I can't think of anything missing.
On Wed, Nov 1, 2023 at
Hi Even,
Rasterio's CI picked up a change to the AAIGrid driver in 3.8. The 3.7
version driver used to have whitespace before a row and no whitespace
after. It looks like this has flipped in 3.8. Is it intentional? I only
noticed because one of my tests is parsing the file as text. It's certainly
Thanks for the announcement, Even! I wonder if we should track such issues
in a list? Or maybe give them a unique GitHub label?
We don't plan to release a 3.6.5, correct?
I'm going to make a Rasterio post release that patches 3.6.4 by tomorrow:
https://github.com/rasterio/rasterio/issues/2943.
O
Thank you, Howard for reminding sponsors how important their support is!
On Fri, Oct 6, 2023 at 9:14 AM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Howard Butler, Even Rouault, Dan Baston, and Alessandro Pasotti held the
> monthly GDAL Maintainers Meeting on 09/28/2023. The fo
Hi Howard,
To be clear, this is a 50% time increase for Alessandro, yes? I think
that's great!
+1
On Wed, Oct 11, 2023 at 10:16 AM Howard Butler via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> PSC,
>
> I'm a little late but I would like to make the following motions in
> regards to GDAL maint
GDAL, especially if you test like
> we do which exact requests are done and in which order, if we change at
> some later point how requests are done
>
> Even
> Le 05/10/2021 à 17:44, Sean Gillies via gdal-dev a écrit :
>
> Hi all,
>
> In writing some rasterio tests I
Hi all,
In writing some rasterio tests I am able to get GDAL to retry head requests
for a vsicurl dataset, but am unable to trigger retries for range requests
to regions of the data. I don't recognize any tests for range request
retrying in or near
https://github.com/OSGeo/gdal/blob/master/autotes
On Tue, Sep 14, 2021 at 8:59 AM Howard Butler wrote:
> Dear PSC,
>
> As a result of our fundraising activity and development of NumFOCUS as a
> financial conduit, it is my pleasure to put forward a motion to approve
> Nyall Dawson as a contracted GDAL maintainer for the year 2021-2022
> beginning
Hi,
For what it's worth, In the Python package named rasterio we're using the
push/pop API:
https://github.com/mapbox/rasterio/blob/master/rasterio/_env.pyx#L336.
While Rust's needs may differ, a single handler without any support for
user data works well for Python: everything goes to the logging
Oops, forgot to reply to the list. Also, to be more specific, could we hold
3.3.2 until Monday, September 6?
On Thu, Sep 2, 2021 at 9:10 AM Sean Gillies wrote:
> I wish I'd noticed the change around EPSG:4326 sooner. I didn't see a
> particular announcement, but the breakage was obvious in raste
Hi Robert,
On Wed, Sep 1, 2021 at 1:30 AM Robert Coup
wrote:
> ...
>
> GDAL has some odd test layouts with particular inter-test dependencies
> from when the test suite was bulk-ported via automation to work under
> pytest — this made it a lot saner, but some of the "test 18 depends on test
> 17
Hi Even,
Would it be difficult to change the RC URLs and release directory to
include the "rc*" string? If the download was at
https://download.osgeo.org/gdal/3.3.2rc2/gdal-3.3.2rc2.tar.gz and extracted
to gdal-3.3.2rc2 I would only need to make a one line change to my build
system to test it.
I
Hi Thomas,
Congratulations! These look like great projects.
On Fri, Jun 4, 2021 at 4:07 AM thomas bonfort
wrote:
> Hello gdal,
>
> We're releasing two projects on github under an Apache-2.0 licence
> which may be of interest to the GDAL community.
>
> The first one, https://github.com/airbusgeo
it is widely used as an exchange format. But I'll defer for
> GeoJSON until we see if the *OGC Features* and *Geometries JSON* SWG comes
> with something regarding this.
>
> Even
> Le 27/05/2021 à 19:24, Sean Gillies via gdal-dev a écrit :
>
> Hi all,
>
> I've got a
Hi Even,
I've got two questions. I don't think they need answers before we vote, but
I'm curious if asking them leads to any useful discussion.
Will we strictly require project proposals to be submitted and approved
before work starts? Will we allow works in progress to apply for funding?
Should
Hi all,
I've got a suggestion about limiting the number of formats.
GeoJSON and KML don't need support for a coordinate epoch. Both of these
are pretty cleared intended for low accuracy data (1-2 meters). KML and
GeoJSON don't support any CRS other than OGC:CRS84, which uses (it has been
pointed
Hi Even, Howard:
I'm inclined to approve, but I feel like there should be more discussion,
not just among PROJ developers and developers of cutting edge formats. We
should work to draw a wider group in on this.
On Thu, May 13, 2021 at 10:01 AM Even Rouault
wrote:
> Howard,
> > It is magical
> >
Hi Aaron, and everyone,
It seems like interoperability could be harmed if we release GDAL with a
JP2 driver that writes JPEG 2000 files that the main open source JP2 driver
can't read. Would it make sense to add compatibility to OpenJPEG before the
PR gets merged? Or are we already in a state of
Thanks for explaining, Even. Makes sense to me.
On Wed, Apr 28, 2021 at 2:59 AM Even Rouault
wrote:
> Sean,
>
> This was the trend of the previous cycles. I see I also produced a 3.1.4
> at about the same time of 3.2.0. This offers 6 month of support for a given
> feature release. Otherwise that
Hi Vincent, Even.
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.
On Fri, Apr 23, 2021 at 7:34 AM Vincent Schut
wrote:
> Thanks for confirming, Even. That
t the organization that defines
> the format is. People could reimplement that from scratch
>
> Note that there is potentially the OGR VRT format (that could go as
> application/ogrvrt+xml), but that is a separate schema and likely less used
> than its raster counterpart.
>
> Le
Hi Jukka,
It's possible that ArcGIS has independently implemented VRT, but I think
it's more likely that it delegates to GDAL. I think it would be possible to
craft a VRT doc that would reveal some details -- such as one that uses
GDAL's embedded Python pixel functions to dump some system informat
Hi all,
I was unable to comment on https://github.com/OSGeo/gdal/pull/3682 until
now. Sorry about that.
I think we should consider removing the 2nd paragraph under "Advisory
Board" to help keep the maintenance sponsorship and new feature development
concerns separated. It would be enough, I think
I haven't seen a VRT media type in the wild, nor is there one on
https://www.iana.org/assignments/media-types/media-types.xhtml.
Maybe application/gdalvrt+xml? As far as I know, GDAL is the only software
that plays VRTs, and probably the only software that ever can, considering
the extensions and
Hi,
On Wed, Mar 24, 2021 at 2:51 PM Alan Snow wrote:
> One recommendation I have for this RFC would be to remove gdal_utils
> entirely from the main GDAL repository and into its own repository.
> The main reason would be to test against multiple versions of GDAL to
> ensure compatibility. Compat
Hi Hug,
GDALRasterizeGeometries takes an array of geometries and iterates over them
from start to end, burning them into the raster one at a time. With a
strictly ordered vector layer, you can expect the later shapes to be burned
over the earlier ones.
On Mon, Mar 8, 2021 at 7:00 AM Hugues Franço
+1
On Thu, Mar 4, 2021 at 9:33 AM Even Rouault
wrote:
> Hi,
>
> Updating my yesterday motion with the feedback received (only second
> bullet updated with a more restricted set of drivers)
>
> Motion:
>
> - remove the vector drivers BNA, AeronavFAA, HTF, OpenAir, SEGUKOOA,
> SEGY, SUA, XPlane an
Hi Jukka,
On Wed, Feb 24, 2021 at 12:20 AM jratike80 <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> GDAL - Dev mailing list wrote
> > Hi Even,
> >
> > On Tue, Feb 23, 2021 at 2:56 AM Even Rouault <
>
> > even.rouault@
>
> > >
> > wrote:
> >
> >> Hi,
> >>
> >> Please find https://github.com/OSGeo
Hi Even,
On Tue, Feb 23, 2021 at 2:56 AM Even Rouault
wrote:
> Hi,
>
> Please find https://github.com/OSGeo/gdal/pull/3473 which proposes to
> list
> service providers offering GDAL related services on the GDAL website. As
> mentioned in the RFC, this is a straightfoward port of the equivalent
>
Hi Tamas,
Are you suggesting that a RFC be required for a new driver? I would support
this 100%.
On Wed, Jan 27, 2021 at 2:17 PM Tamas Szekeres wrote:
> David,
>
> Up to this time the driver writers were highly welcomed to author new
> drivers for the project and these effort didn't require a s
Hi,
No, the MVT driver is only concerned with features in a protobuf file:
https://github.com/mapbox/vector-tile-spec/tree/master/2.1. It doesn't know
about Mapbox styles.
On Wed, Jan 20, 2021 at 2:53 PM Miller, Doug wrote:
> How does the Mapbox Vector Tiles Driver take into account styles (i.e
Hi Howard and all,
On Wed, Jan 13, 2021 at 3:58 PM Howard Butler wrote:
>
>
> On Jan 13, 2021, at 4:28 PM, Nyall Dawson wrote:
>
> On Thu, 14 Jan 2021 at 06:24, David Strip wrote:
>
> What is the path forward? One path Howard suggests is establishing a
> foundation similar to that behind Qgis
Hi Even,
On Mon, Jan 11, 2021 at 7:44 AM Even Rouault
wrote:
> Hi,
>
> trying to answer the different points raised up to now:
>
> - SVG: let's keep it as it is used. This is exactly the feedback I'm
> seeking
> for. I had developed this as a toy, crazy me, I won't do it anymore. No
> idea
> any
Hi Mateusz,
The OSGeo sysadmins found something to correct in mailman configuration,
I'm giving that a test here.
On Wed, Dec 9, 2020 at 1:32 AM Mateusz Loskot wrote:
> On Tue, 8 Dec 2020 at 23:16, Sean Gillies wrote:
> >
> > The state of the art for very thin Python bindings for a C++ project
71 matches
Mail list logo
