Re: [GRASS-dev] GRASS GIS ready for PROJ 7?
On Fri, Mar 5, 2021 at 8:11 PM Helmut Kudrnovsky wrote: > > Hi devs, > > in OSGeo4W actually: > > C:\>proj --version > Rel. 6.3.2, May 1st, 2020 > > OSGeo4W next generation is in a testing phase at the moment. > > one of the biggest steps forward is: > > >PROJ 7.2 <= > > is GRASS GIS ready for PROJ 7? Yes, insofar that GRASS 7.8+9 compile and run fine with PROJ 7, but... > > in PROJ7, there is a complete change how PROJ related/needed data is > handled: > > (1) dynamically via https://cdn.proj.org/ > (2) via a revamped proj-data with file size of more than 500 MB > > * will GRASS be ready to handle it dynamically via CDN? > * including more than 500MB data into our standalone installer may explode our used NSIS system. this new functionality of PROJ 7+ is not yet used in GRASS. We need to introduce a mechanism where users can switch on and off dynamic download of PROJ-related data. Depending on the available internet connection (none, too slow, too expensive), automated download might need to be disabled, in which case we need to introduce warnings that PROJ-related data are missing for certain coordinate operations. Markus M > > kind regards > Helmut > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS GIS ready for PROJ 7?
To underpin Jürgens point: In my company we used "creatensis.pl" to create custom OSGeo4W installations with modified startup scripts (so users get prepared configurations. That worked quite well. Doing so for a "GRASS GIS standalone" installer might reduce maintenance, risk of bugs and confusion among users. So, I would definitely recommend to follow Jürgens suggestion. Cheers Stefan -Original Message- From: grass-dev On Behalf Of Jürgen E. Fischer Sent: fredag 5. mars 2021 20:53 To: grass-dev@lists.osgeo.org Subject: Re: [GRASS-dev] GRASS GIS ready for PROJ 7? Hi Helmut, On Fri, 05. Mar 2021 at 20:11:03 +0100, Helmut Kudrnovsky wrote: > in OSGeo4W actually: > > C:\>proj --version > Rel. 6.3.2, May 1st, 2020 > > OSGeo4W next generation is in a testing phase at the moment. > > one of the biggest steps forward is: > > >PROJ 7.2 <= Meanwhile PROJ 8. > * including more than 500MB data into our standalone installer may explode > our used NSIS system. The standalone installer of QGIS is directly based on OSGeo4W packages. It just starts off with the qgis-full package and includes all it's dependencies and hence also includes GRASS. The packages are fetched and extracted and packed up again for the installer, which later runs extracts them on and runs the included postinstall scripts of the OSGeo4W packages on the target machine. Except for selecting the target directory and setting whether desktop and/or start menu shortcuts should be created, there is currently no way to add more configuration. The same approach, but starting off with grass instead of qgis-full could also work for GRASS. And creatensis.pl was ported to MSI as createmsi.pl - because it now uses the Microsoft Installer instead of NSIS to work around NSIS' 2GB limit. The experimental MSI installer also includes GRASS (although not the latest updates of OSGeo4W regarding os.add_dll_directory necessary for Python 3.9). See also https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fpipermail%2Fqgis-user%2F2021-February%2F048137.html&data=04%7C01%7C%7Cde782249b1d94ada482a08d8e01057d8%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637505708089015542%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Y4%2FZboGT5QD975HderBYUfAB7Wqd6QRzPP%2B5u9KXsXY%3D&reserved=0 and https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fpipermail%2Fqgis-user%2F2021-February%2F048199.html&data=04%7C01%7C%7Cde782249b1d94ada482a08d8e01057d8%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637505708089015542%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=E2lHIE3HX0yMrmIPTZ%2BymZhoczVZ6LlOQsJ8MfqlC%2FQ%3D&reserved=0. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.norbit.de%2F&data=04%7C01%7C%7Cde782249b1d94ada482a08d8e01057d8%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637505708089015542%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FkW2HofwNj2Q7wCM19g9SWEc9LS4tO%2FcJT5VadfXwto%3D&reserved=0 QGIS release manager (PSC) GermanyIRC: jef on FreeNode ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS GIS ready for PROJ 7?
Hi Helmut, On Fri, 05. Mar 2021 at 20:11:03 +0100, Helmut Kudrnovsky wrote: > in OSGeo4W actually: > > C:\>proj --version > Rel. 6.3.2, May 1st, 2020 > > OSGeo4W next generation is in a testing phase at the moment. > > one of the biggest steps forward is: > > >PROJ 7.2 <= Meanwhile PROJ 8. > * including more than 500MB data into our standalone installer may explode > our used NSIS system. The standalone installer of QGIS is directly based on OSGeo4W packages. It just starts off with the qgis-full package and includes all it's dependencies and hence also includes GRASS. The packages are fetched and extracted and packed up again for the installer, which later runs extracts them on and runs the included postinstall scripts of the OSGeo4W packages on the target machine. Except for selecting the target directory and setting whether desktop and/or start menu shortcuts should be created, there is currently no way to add more configuration. The same approach, but starting off with grass instead of qgis-full could also work for GRASS. And creatensis.pl was ported to MSI as createmsi.pl - because it now uses the Microsoft Installer instead of NSIS to work around NSIS' 2GB limit. The experimental MSI installer also includes GRASS (although not the latest updates of OSGeo4W regarding os.add_dll_directory necessary for Python 3.9). See also https://lists.osgeo.org/pipermail/qgis-user/2021-February/048137.html and https://lists.osgeo.org/pipermail/qgis-user/2021-February/048199.html. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Nordenhttps://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: PGP signature ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] GRASS GIS ready for PROJ 7?
Hi devs, in OSGeo4W actually: C:\>proj --version Rel. 6.3.2, May 1st, 2020 OSGeo4W next generation is in a testing phase at the moment. one of the biggest steps forward is: >PROJ 7.2 <= is GRASS GIS ready for PROJ 7? in PROJ7, there is a complete change how PROJ related/needed data is handled: (1) dynamically via https://cdn.proj.org/ (2) via a revamped proj-data with file size of more than 500 MB * will GRASS be ready to handle it dynamically via CDN? * including more than 500MB data into our standalone installer may explode our used NSIS system. kind regards Helmut ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev