[GRASS-user] Drop GRASS 6 support in QGIS 3 GRASS plugin
Are there any objections to drop GRASS 6 support from GRASS plugin in QGIS 3? Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] GRASS Plugin ready
Another bug you should know about: http://hub.qgis.org/issues/13815 - attributes of a vector imported in browser may be messed up. Fixed in master and 2.12 branch (will be in 2.12.1). Radim On Sun, Nov 1, 2015 at 10:09 PM, Radim Blazek wrote: > Hi all, > > I would like to formally conclude the upgrade of the GRASS Plugin in > QGIS. Everything specified in the crowdfunding campaign is implemented > in recently released QGIS 2.12. The source code supports both GRASS 6 > and 7. Version(s) supported in binary distributions may vary and > depend on packagers' decision. > > screenshots: > http://www.gissula.eu/qgis-grass-plugin-crowdfunding/screenshots.html > videos: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/videos.html > summary: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/progress.html > documentation: > http://docs.qgis.org/testing/en/docs/user_manual/grass_integration/grass_integration.html > > Thanks to Pedro Venâncio, Stefan Blumentrath and Andrew McAninch who > helped with upgrade of modules' configuration. Especially Pedro also > did great work doing extensive testing. Thanks to Jürgen Fischer for > patient fixing of Windows builds, Paolo Cavallini for documentation > review and to everybody who contributed to the campaign. > > If you find a problem, please create a new issue: > https://hub.qgis.org/issues/, set Category to GRASS and assign it to > me (Radim Blazek). Unfortunately I have found already two issues: > https://hub.qgis.org/issues/13725, https://hub.qgis.org/issues/13726, > both are fixed in master and backported to 2.12 (will be in 2.12.1 if > it'll ever be released). > > Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [Qgis-user] GRASS Plugin ready
On Mon, Nov 2, 2015 at 12:52 AM, William Kyngesburye wrote: > As one of those packagers, is there any reason to include support for both in > a build? Or is GRASS 7 support good enough? The only reason to build version 6 is to support users who haven't switched yet to GRASS 7. The plugin is identical for both versions, differences are only in available GRASS modules and their options. Radim >> On Nov 1, 2015, at 3:09 PM, Radim Blazek wrote: >> >> Hi all, >> >> I would like to formally conclude the upgrade of the GRASS Plugin in >> QGIS. Everything specified in the crowdfunding campaign is implemented >> in recently released QGIS 2.12. The source code supports both GRASS 6 >> and 7. Version(s) supported in binary distributions may vary and >> depend on packagers' decision. >> > > - > William Kyngesburye > http://www.kyngchaos.com/ > > "Oh, look, I seem to have fallen down a deep, dark hole. Now what does that > remind me of? Ah, yes - life." > > - Marvin > > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] GRASS Plugin ready
Hi all, I would like to formally conclude the upgrade of the GRASS Plugin in QGIS. Everything specified in the crowdfunding campaign is implemented in recently released QGIS 2.12. The source code supports both GRASS 6 and 7. Version(s) supported in binary distributions may vary and depend on packagers' decision. screenshots: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/screenshots.html videos: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/videos.html summary: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/progress.html documentation: http://docs.qgis.org/testing/en/docs/user_manual/grass_integration/grass_integration.html Thanks to Pedro Venâncio, Stefan Blumentrath and Andrew McAninch who helped with upgrade of modules' configuration. Especially Pedro also did great work doing extensive testing. Thanks to Jürgen Fischer for patient fixing of Windows builds, Paolo Cavallini for documentation review and to everybody who contributed to the campaign. If you find a problem, please create a new issue: https://hub.qgis.org/issues/, set Category to GRASS and assign it to me (Radim Blazek). Unfortunately I have found already two issues: https://hub.qgis.org/issues/13725, https://hub.qgis.org/issues/13726, both are fixed in master and backported to 2.12 (will be in 2.12.1 if it'll ever be released). Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] GRASS toolbar in QGIS
We are discussing possible UI cleanup related also to GRASS: https://hub.qgis.org/issues/13537 Questions for plugin users: - Can be open/new/close items removed from the toolbar? There is a possibility to open mapset from browser and close it from tools dock widget and there are menu items for all three actions. - Should we keep Region action (region display on/off) in the toolbar, it could be moved to the top of tools widget, beside Close mapset button - Is it "Open Tools" action in the toolbar useful? It is also in the menu and tools may be opened like any other docked widget from Settings > Panels Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] QGIS GRASS Plugin Upgrade Crowdfunding
Hi all. The project is funded! Thanks to everybody who contributed or promoted the project. The first two parts are implemented, you can follow the work progress here: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/progress.html browser demo video: https://www.youtube.com/watch?v=5d1jZzyRyRY Many thanks to Jef for the help with dual build port to Windows, which saved me a lot of headache and for patient fixing of the bugs I introduced on Windows. You can now build QGIS with GRASS 6, 7 or both. For the GRASS 7, there are three new cmake options: WITH_GRASS7, GRASS_INCLUDE_DIR7, GRASS_PREFIX7. Libs and binaries for each version have GRASS major version number appended to file names. You can choose the version of provider/plugin on runtime setting LD_LIBRARY_PATH to the directory where GRASS libs are installed. For example: LD_LIBRARY_PATH=/home/user/apps/grass-6.4.4/lib /home/user/apps/bin/qgis Similarly, there are bat files in OSGEO4W 32bit for each GRASS version (GRASS 7 is not dependency and must be selected manually). There is no GRASS 7 provider in OSGEO4W 64bit, because there is no GRASS 7 in OSGEO4W 64bit yet. Please test but be aware that there are still many issues, especially on Windows which I hope to fix for QGIS 2.10 release. Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] QGIS GRASS Plugin Upgrade Crowdfunding
On Mon, May 18, 2015 at 2:22 PM, Sören Gebbert wrote: > Dear all, > just a short reminder. The crowd funding period for the QGIS GRASS > Plugin is still running but will end soon. Everyone who may be > willingly to fund this great project can contribute funds until May > 23. BTW, raster/vector import via browser is in master (pushed today), you can test. Dual build (with GRASS 6 + 7) is also available. Big thanks to Jef for porting dual build to Windows. Currently there is unfortunately some problem in browser with GRASS 7 vectors (crash), but GRASS 7 vectors load correctly from project file (e.g. project created in GRASS 6, vectors upgraded to GRASS 7 and project reopened in QGIS with GRASS 7). I'll do more detailed announcement after QGIS 2.10 freeze. Radim > Best regards > Soeren > > 2015-03-23 19:56 GMT+01:00 Radim Blazek : >> Hi all, >> >> I have finally launched the crowdfunding campaign to support the GRASS >> plugin upgrade. Briefly, it covers upgrade to GRASS 7, browser >> integration, drag-and-drop import and new vector editing. All the >> details are available here: >> >> http://www.gissula.eu/qgis-grass-plugin-crowdfunding/ >> >> Please propagate this info to all relevant channels, national mailing lists >> etc. >> >> Radim >> ___ >> grass-dev mailing list >> grass-...@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] r.external -o
Are there rasters in a projection different from current location, registered by r.external -o, reprojected on the fly when used? Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] QGIS GRASS Plugin Upgrade Crowdfunding
Special thanks to Andreas Neumann from City of Uster (http://gis.uster.ch/), Switzerland. Thanks to his 1000 euro we quickly got over 2000! Only 234 euro missing to reach the second package. Thanks to all contributors. Radim On Wed, Mar 25, 2015 at 9:33 AM, Radim Blazek wrote: > The first package is financed by 29 contributors! > Many thanks to everybody who contributed so far. > > Please keep on contributing. > > Radim > > > On Mon, Mar 23, 2015 at 7:56 PM, Radim Blazek wrote: >> Hi all, >> >> I have finally launched the crowdfunding campaign to support the GRASS >> plugin upgrade. Briefly, it covers upgrade to GRASS 7, browser >> integration, drag-and-drop import and new vector editing. All the >> details are available here: >> >> http://www.gissula.eu/qgis-grass-plugin-crowdfunding/ >> >> Please propagate this info to all relevant channels, national mailing lists >> etc. >> >> Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] QGIS GRASS Plugin Upgrade Crowdfunding
The first package is financed by 29 contributors! Many thanks to everybody who contributed so far. Please keep on contributing. Radim On Mon, Mar 23, 2015 at 7:56 PM, Radim Blazek wrote: > Hi all, > > I have finally launched the crowdfunding campaign to support the GRASS > plugin upgrade. Briefly, it covers upgrade to GRASS 7, browser > integration, drag-and-drop import and new vector editing. All the > details are available here: > > http://www.gissula.eu/qgis-grass-plugin-crowdfunding/ > > Please propagate this info to all relevant channels, national mailing lists > etc. > > Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] QGIS GRASS Plugin Upgrade Crowdfunding
On Wed, Mar 25, 2015 at 12:44 AM, Daniel Victoria wrote: > Hi Radim, > > I'm using grass 7 and QGis installed from OSGeo4Win so maybe it was compiled > against some old libraries? I've no idea how to compile in windows so I'll > just try to re-install everything and hope things work... QGis from OSGeo4Win is compiled with GRASS 6, you cannot get it working with GRASS 7. Reinstalling will not help. The provider and the plugin has first to be fixed to support build with both GRASS 6 and GRASS 7. This is in the first package of proposed upgrade: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/ Then a bat to start QGIS with GRASS 7 could be added also to OSGeo4Win. Radim > Daniel > > On Tue, Mar 24, 2015 at 4:18 PM, Radim Blazek > wrote: >> >> On Tue, Mar 24, 2015 at 5:31 PM, Daniel Victoria >> wrote: >> > Hi Radim, >> > >> > Is this why my QGis crashes when i try to load a Grass 7.0 vector file? >> > [1] >> >> AFAIC, it should only crash if you try to open a GRASS mapset with >> GRASS 6 vectors in QGIS browser compiled and run with GRASS 7 >> provider. It is described here: >> http://lists.osgeo.org/pipermail/qgis-user/2015-March/031177.html >> >> I think that I know already what the problem is. If GRASS 7 lib is >> tries to open a vector which it is not in format 7, it calls >> G_fatal_error(), which normally opens a warning dialog. Because items >> in the browser are populated in threads, it happens on non GUI thread, >> but to open a dialog with an icon, it has to use QIcon which can only >> be used on GUI thread. >> >> >> Radim >> >> >> > Thanks >> > Daniel >> > >> > [1] - >> > >> > http://gis.stackexchange.com/questions/138477/loading-grass-7-0-vectors-in-qgis-broken >> > >> > On Tue, Mar 24, 2015 at 11:47 AM, Vaclav Petras >> > wrote: >> >> >> >> On Tue, Mar 24, 2015 at 5:56 AM, Radim Blazek >> >> wrote: >> >>> >> >>> >> Are there functions in time series implementation which need to be >> >>> >> called directly from the plugin or everything may be done just >> >>> >> calling >> >>> >> t.rast.* modules? >> >>> > >> >>> > Most of the temporal functionality is available through the temporal >> >>> > modules. However some important algorithms (temporal re-sampling) >> >>> > are >> >>> > available only in the Python framework. This is needed for time >> >>> > series >> >>> > animation creation. Using the framework directly will speed things >> >>> > up, >> >>> > because the module calls, the parsing and interpretation of the >> >>> > module >> >>> > outputs can be avoided. >> >>> >> >>> If it should be used for dynamic animation in QGIS canvas you could >> >>> consider the possibility to subclass raster renderer in Python and >> >>> insert it into raster layer pipe from Python plugin. >> >> >> >> >> >> Speaking about animations, some things from GRASS GIS GUI could be >> >> perhaps >> >> used directly in the same was as Tcl/Tk NVIZ is used in processing for >> >> GRASS >> >> 6. Animation tool is one of them. This would be great since we would >> >> get al >> >> least some functionality/code sharing between GRASS and QGIS GUIs which >> >> is >> >> otherwise not possible due to Python/wxPython and C++/Qt (and would be >> >> only >> >> possible if both things would be at least in the same language). >> >> >> >> This is of course not fulfilling the requirement to be general, i.e. >> >> work >> >> with other data providers in QGIS, but surely some things just have to >> >> be >> >> like that if they are using GRASS-specific formats (temporal data) or >> >> algorithms (e.g. algorithms to work with temporal data, their topology, >> >> ...). >> >> >> >> Vaclav >> >> >> >> ___ >> >> grass-user mailing list >> >> grass-user@lists.osgeo.org >> >> http://lists.osgeo.org/mailman/listinfo/grass-user >> > >> > > > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] QGIS GRASS Plugin Upgrade Crowdfunding
On Tue, Mar 24, 2015 at 5:31 PM, Daniel Victoria wrote: > Hi Radim, > > Is this why my QGis crashes when i try to load a Grass 7.0 vector file? [1] AFAIC, it should only crash if you try to open a GRASS mapset with GRASS 6 vectors in QGIS browser compiled and run with GRASS 7 provider. It is described here: http://lists.osgeo.org/pipermail/qgis-user/2015-March/031177.html I think that I know already what the problem is. If GRASS 7 lib is tries to open a vector which it is not in format 7, it calls G_fatal_error(), which normally opens a warning dialog. Because items in the browser are populated in threads, it happens on non GUI thread, but to open a dialog with an icon, it has to use QIcon which can only be used on GUI thread. Radim > Thanks > Daniel > > [1] - > http://gis.stackexchange.com/questions/138477/loading-grass-7-0-vectors-in-qgis-broken > > On Tue, Mar 24, 2015 at 11:47 AM, Vaclav Petras > wrote: >> >> On Tue, Mar 24, 2015 at 5:56 AM, Radim Blazek >> wrote: >>> >>> >> Are there functions in time series implementation which need to be >>> >> called directly from the plugin or everything may be done just calling >>> >> t.rast.* modules? >>> > >>> > Most of the temporal functionality is available through the temporal >>> > modules. However some important algorithms (temporal re-sampling) are >>> > available only in the Python framework. This is needed for time series >>> > animation creation. Using the framework directly will speed things up, >>> > because the module calls, the parsing and interpretation of the module >>> > outputs can be avoided. >>> >>> If it should be used for dynamic animation in QGIS canvas you could >>> consider the possibility to subclass raster renderer in Python and >>> insert it into raster layer pipe from Python plugin. >> >> >> Speaking about animations, some things from GRASS GIS GUI could be perhaps >> used directly in the same was as Tcl/Tk NVIZ is used in processing for GRASS >> 6. Animation tool is one of them. This would be great since we would get al >> least some functionality/code sharing between GRASS and QGIS GUIs which is >> otherwise not possible due to Python/wxPython and C++/Qt (and would be only >> possible if both things would be at least in the same language). >> >> This is of course not fulfilling the requirement to be general, i.e. work >> with other data providers in QGIS, but surely some things just have to be >> like that if they are using GRASS-specific formats (temporal data) or >> algorithms (e.g. algorithms to work with temporal data, their topology, >> ...). >> >> Vaclav >> >> ___ >> grass-user mailing list >> grass-user@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-user > > ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] QGIS GRASS Plugin Upgrade Crowdfunding
Hi Soeren On Tue, Mar 24, 2015 at 10:04 AM, Sören Gebbert wrote: > 2015-03-24 9:40 GMT+01:00 Radim Blazek : >> I completely agree that Python would be better, the advantages of >> Python are obvious and that would be definitely my choice if I had to >> start from scratch. Un(fortunately) the GRASS plugin + qgsgrassgislib >> have already 22500 lines of C++ so porting to Python is not an option >> and mixing C++ in single plugin either (as far to my knowledge). > > Indeed, porting the C++ code to Python is a large effort. However, > maybe you can define a stretch-goal in the crowd funding campaign? If > this goal is met, then you have enough funds to port the C++ code to > Python and you can add more features? I don't have any serious estimation how much porting from C++ to Python costs, but new line of code costs 10-50euro (according to quick internet search). To be really very modest, say that porting would cost 2 euro per line, i.e. 22500*2 = 45000 euro for somethings which brings no new features to users. That is not something I would ever propose. > I think that using C++ and Python in a Plugin shouldn't be a big > problem in my humble opinion. The main issue would be that the C++ > code of the data provide will be part of QGIS and the Python code that > makes use of the GRASS data provider will be a separate GRASS Python > QGIS plugin. The plugin and the provider are sharing some C++ code (qgsgrass and qgsgrasslib). To port the plugin to Python you also have to write and maintain Python bindings for that shared classes which is just extra work. > Maybe this approach will allow to implement several > independent Python plugins that make use of the GRASS data provider to > implement specific algorithms? That should not depend on the GRASS plugin in C++. If you write Python bindings for the provider, you can use it (non standard) in your Python plugin. I believe however that plugins implementing algorithms should be preferably provider independent. >> Are there functions in time series implementation which need to be >> called directly from the plugin or everything may be done just calling >> t.rast.* modules? > > Most of the temporal functionality is available through the temporal > modules. However some important algorithms (temporal re-sampling) are > available only in the Python framework. This is needed for time series > animation creation. Using the framework directly will speed things up, > because the module calls, the parsing and interpretation of the module > outputs can be avoided. If it should be used for dynamic animation in QGIS canvas you could consider the possibility to subclass raster renderer in Python and insert it into raster layer pipe from Python plugin. >>> Btw: Otto Dassau and i mentioned your crowd funding idea at the >>> FOSSGIS in Germany two weeks ago. It is on Youtube[2] but only in >>> German. Thank you a lot! Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [GRASS-dev] QGIS GRASS Plugin Upgrade Crowdfunding
Hi Soeren, thanks for your reaction. I remember we already discussed the possibility to move to Python. On Mon, Mar 23, 2015 at 9:19 PM, Sören Gebbert wrote: > Hi Radim, > this is a beautiful idea and i hope you will get plenty of funds. > > I have some questions regarding the implementation, since this is not > mentioned in the project description: > > Do you plan to implement the plugin in C++ only, or will you try to > combine C++ (data provider) and Python (all the rest)? The reason i am > asking is, that using Python for the user interaction, module calling, > vector editing and mapset/location handling would allow us GRASS > developer to provide possible improvements and bugfixes for the plugin > more easily. For example, the time series handling [1] in GRASS GIS is > mainly implemented in Python and provides a Python API that could be > used in the QGIS GRASS Plugin to implement time series analysis > support. > Using the QGIS Python plugin approach will reduce the need for > compilation, which allows much faster development of modifications and > bugfix testing. I completely agree that Python would be better, the advantages of Python are obvious and that would be definitely my choice if I had to start from scratch. Un(fortunately) the GRASS plugin + qgsgrassgislib have already 22500 lines of C++ so porting to Python is not an option and mixing C++ in single plugin either (as far to my knowledge). Are there functions in time series implementation which need to be called directly from the plugin or everything may be done just calling t.rast.* modules? Radim > The data provider and vector editing helper classes must be of course > implemented in C++ and should stay in the QGIS source tree. > > Best regards > Soeren > > [1] http://ifgi.uni-muenster.de/~epebe_01/tgrass.pdf > > Btw: Otto Dassau and i mentioned your crowd funding idea at the > FOSSGIS in Germany two weeks ago. It is on Youtube[2] but only in > German. > > [2] https://www.youtube.com/watch?v=rxmPbh2igmM&t=1407 > > 2015-03-23 19:56 GMT+01:00 Radim Blazek : >> Hi all, >> >> I have finally launched the crowdfunding campaign to support the GRASS >> plugin upgrade. Briefly, it covers upgrade to GRASS 7, browser >> integration, drag-and-drop import and new vector editing. All the >> details are available here: >> >> http://www.gissula.eu/qgis-grass-plugin-crowdfunding/ >> >> Please propagate this info to all relevant channels, national mailing lists >> etc. >> >> Radim >> ___ >> grass-dev mailing list >> grass-...@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] QGIS GRASS Plugin Upgrade Crowdfunding
Hi all, I have finally launched the crowdfunding campaign to support the GRASS plugin upgrade. Briefly, it covers upgrade to GRASS 7, browser integration, drag-and-drop import and new vector editing. All the details are available here: http://www.gissula.eu/qgis-grass-plugin-crowdfunding/ Please propagate this info to all relevant channels, national mailing lists etc. Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] [Qgis-developer] QGIS and GRASS 7.0.0
The new GRASS vector editing tool preview screencast: https://www.youtube.com/watch?v=PPno1aLYHFE Radim On Tue, Feb 24, 2015 at 10:08 AM, Paolo Cavallini wrote: > Hi Radim, > thanks a lot for this. > > Il 24/02/2015 09:28, Radim Blazek ha scritto: > >> - modules GUI - my idea is to throw away the qgm and qgc definitions >> and auto generate GUI for modules with all options based on >> --interface-description only, also the list of modules would be auto >> generated for all modules. The reason is my impression that there are >> no volunteers willing to maintain qgm and qgc. If there are volunteers >> to do that (no programming, xml editing only) let me know and I'll >> include keeping of current system in the proposal. > > IMHO having the possibility of making simplified modules is a bi plus, > and would better not be missed. > > Thanks again. > -- > Paolo Cavallini - www.faunalia.eu > QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Patch tiles faster
Hi, I need to patch more non overlapping raster maps into one map. Currently I am using r.patch, but it is very slow for larger maps (about 40 minutes in my case). It is so slow probably because it is reading and processing all input tile maps with extent of the output map. Is there a faster way how to combine more non overlapping maps? Radim ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
