Releases: koordinates/gdal
Releases · koordinates/gdal
CI: kx-3.2-bionic.363
Build (for bionic) with openJP2 we're switching to openJP2 for jammy but it turns out our Kakadu license has now expired and so we need to switch Now
CI: kx-3.2-bionic.362
Build (for bionic) with openJP2 we're switching to openJP2 for jammy but it turns out our Kakadu license has now expired and so we need to switch Now
CI: kx-3.2-bionic.354
WFS: Don't issue STARTINDEX if feature count is small Backports https://github.com/OSGeo/gdal/pull/8146 Datasources with no primary key cannot be naturally ordered by the server, and so using the STARTINDEX argument causes a 400 error with the response: > Cannot do natural order without a primary key, please add it or > specify a manual sort over existing attributes This change avoids issuing STARTINDEX if: * the feature count is known by the time the first GetFeature request is issued * the feature count is less than the page size. In other words, this change allows us to use small datasets that have no primary key, while still allowing paging in larger datasets (as long as they have a primary key)
CI: kx-3.2-bionic.340
WFS: Don't issue STARTINDEX if feature count is small Backports https://github.com/OSGeo/gdal/pull/8146 Datasources with no primary key cannot be naturally ordered by the server, and so using the STARTINDEX argument causes a 400 error with the response: > Cannot do natural order without a primary key, please add it or > specify a manual sort over existing attributes This change avoids issuing STARTINDEX if: * the feature count is known by the time the first GetFeature request is issued * the feature count is less than the page size. In other words, this change allows us to use small datasets that have no primary key, while still allowing paging in larger datasets (as long as they have a primary key)
CI: kx-3.2-bionic.338
WFS: Don't issue STARTINDEX if feature count is small Backports https://github.com/OSGeo/gdal/pull/8146 Datasources with no primary key cannot be naturally ordered by the server, and so using the STARTINDEX argument causes a 400 error with the response: > Cannot do natural order without a primary key, please add it or > specify a manual sort over existing attributes This change avoids issuing STARTINDEX if: * the feature count is known by the time the first GetFeature request is issued * the feature count is less than the page size. In other words, this change allows us to use small datasets that have no primary key, while still allowing paging in larger datasets (as long as they have a primary key)
CI: kx-3.3-focal.310
Use the `proj` package (kx custom proj), not libproj proj (9) builds for arm64 too
CI: kx-3.3-focal.306
kx-release-3.3.3+ci306 Build for arm64
CI: kx-3.3-focal.296
Build without spatialite libspatialite7 in focal depends on libproj15, which conflicts with libproj22, and so installs of this fail. I could build libspatialite7 again to depend on libproj22 but where will it end? I don't need libspatialite atm
CI: kx-3.3-focal.295
kx-release-3.3.3+ci295 fix pipeline to upload debs to focal ;)
CI: kx-3.2-bionic.292
kx-release-3.2.2+ci292 Expand KMLSuperOverlay tile size to 512 < side < 1024px rather than 2…