Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] master from OSGeo:master #80

Merged
merged 237 commits into from
May 31, 2024
Merged

[pull] master from OSGeo:master #80

merged 237 commits into from
May 31, 2024

Conversation

pull[bot]
Copy link

@pull pull bot commented May 27, 2024

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

rouault added 30 commits May 9, 2024 23:52
…dle sources fully overlapping others, and taking into accout nodata values

```
-  .. oo:: OVERLAP_STRATEGY
      :choices: REMOVE_IF_NO_NODATA, USE_ALL, USE_MOST_RECENT
      :default: REMOVE_IF_NO_NODATA
      :since: 3.9.1

      Strategy to use when the ItemCollections contains overlapping items, and
      that some items are fully covered by other items that are more recent.

      Starting with GDAL 3.9.1, the ``REMOVE_IF_NO_NODATA`` strategy is applied
      by default. The STACIT virtual mosaic will omit fully covered items,
      only if no band declares a nodata value.
      (Note that the determination whether a band has a nodata value of not is
      done by opening one of the items, and assuming it is representative of
      the characteristics of the others in the collection).

      This strategy can be forced in all cases by selecting the ``USE_MOST_RECENT``
      strategy (this was the strategy applied prior to 3.9.1)

      The ``USE_ALL`` strategy always causes all items to be listed in the virtual
      mosaic, with the most recent ones being rendered on top of the less recent ones.
```
The method had a fallback path when allocating a temporary buffer of the
size of the one passed ot the method, that intended to use a less memory
intensive block-based approach, but this was buggy.
Fix this, and add testing for the fallback.
Also, when attempting the fallback, emits a CE_Warning instead of a
CE_Failure.

Fixes rasterio/rasterio#3028
also remove comment suggesting using std::aligned_storage since it is
deprecated in C++23
… GeoArrow struct Point even when there is no bounding box column
…on from WKB column as a Arrow compute function
```
 * \fn VSIVirtualHandle::Error()
 * \brief Test the error indicator.
 *
 * Returns TRUE (non-zero) if an error condition occurred during the
 * previous read operation. The error indicator is cleared by a call to
 * VSIFClearErrL(). Note that a end-of-file situation, reported by VSIFEofL(),
 * is *not* an error reported by VSIFErrorL().
```

```
 * \fn VSIVirtualHandle::ClearErr()
 * \brief Reset the error and end-of-file indicators.
```
rouault and others added 29 commits May 30, 2024 00:44
Proof that the man page was wrong:
```
$ gdal_fillnodata 0.tif
usage:  ...
gdal_fillnodata: error: the following arguments are required: dst_filename
```
Update gdal_fillnodata.rst adding destination file requirement
…s-CI plan being downgraded to 2 concurrent builds [ci skip]
Doc: mark GDALSimpleImageWarp() and GDALReprojectImage() as superseded per GDALWarp()
…atureRecord

MiraMonVector: fixing MMResetFeatureRecord
Fix "intput" typo in gdal_merge.rst
…ntize (#10087)

* Update gdal_footprint.rst adding periods

* Update ogr2ogr.rst clarifying units
RFC96 Deferred driver loading adjustment to fix functional regression
@pull pull bot merged commit c483e42 into innFactory:master May 31, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants