[QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Kristian Evers]

On 19 Dec 2019, at 03:37, Mathieu Pellerin <nirvn.asia at gmail.com<mailto:nirvn.asia at gmail.com>> wrote:

Having helped out chasing down some of these CRS and transformation issues under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the next QGIS point release with anything lesser than GDAL3 and PROJ6 master as of yesterday.

To be clear, QGIS had plenty to fix itself, and that’s been taken care of (thanks to QGIS’s PSC for financing Nyall here). But those fixes are half of the story, and if we are to ship a QGIS version built against GDAL3/PROJ6 that can be trusted to project and transform data properly, we can’t do so unless we ship with the latest revisions of those libraries.

On the short term, since the next point release is in 24-ish hours, I’d suggest to update the osgeo4w gdal and proj non-dev libraries to the latest master revisions (with versions like proj6 version 6.3pre or something) and have QGIS 3.10.2 built against those. Jürgen, since you’d carry that library update burden, how do you feel about this solution?

Following that, we should discuss with GDAL and PROJ to see if they can package an official release prior to QGIS’ next point release (which is to take place on January 17, 2019 according to our schedule). Once that’s done, we should consider raising QGIS’ minimum version requirement for those libraries.


PROJ 6.3.0 is scheduled for release January 1st.

Math

On Thu, Dec 19, 2019 at 8:30 AM Nyall Dawson <nyall.dawson at gmail.com<mailto:nyall.dawson at gmail.com>> wrote:
Hi list,

Just want to raise this discussion prior to the 3.10.2 patch release.
The situation as I see it is that there is absolutely critical fixes
in GDAL and PROJ master branches which are not available in any of the
GDAL/PROJ stable releases, all relating to CRS and transformation
handling.

Many of these fixes have been implemented as a direct result of bug
reports filed against QGIS when running under the Proj6/GDAL3
combination.

I personally do not feel comfortable with anyone running QGIS on
GDAL3/Proj6 without these fixes (in fact, I think that we should block
QGIS builds on GDAL/PROJ builds less than master, and greater than
PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
position, because the next round of GDAL/PROJ releases aren't
happening anytime soon.

Thoughts welcome on how we should proceed here....

Nyall
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer at lists.osgeo.org<mailto:QGIS-Developer at lists.osgeo.org>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer at lists.osgeo.org<mailto:QGIS-Developer at lists.osgeo.org>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20191219/e015d113/attachment.html>