Re: [Qgis-developer] QGIS and GRASS 7.0.0
Il 09/03/2015 00:38, Pedro Venâncio ha scritto: It looks really really great! Awesome, chapeau! Looking forward to see the crowdfunding. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [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 cavall...@faunalia.it 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 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi Radim, The new GRASS vector editing tool preview screencast: https://www.youtube.com/watch?v=PPno1aLYHFE It looks really really great! Best regards, Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
On Wed, Feb 25, 2015 at 10:36 AM, Pedro Venâncio pedrongvenan...@gmail.com wrote: Hi Radim, I would be willing to volunteer to help maintain the qgm and qgc files. Great, I'll keep current config system also for GRASS 7. If you explain me what to do, I also volunteer for that task. Good, I'll provide you with more info once we get to that point. Radim ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
On Wed, Feb 25, 2015 at 2:45 AM, Radim Blazek radim.bla...@gmail.com wrote: it would be good if you can include GRASS Addons, too. There is a lot of requests for installing/running GRASS Addons from QGIS, e.g. at gis.stackexchange.com. How can I get list of installed GRASS Addons? For basic list you can just use `g.extension -a` [1]. wxGUI is using more complex approach implemented in UpdateGRASSAddOnCommands function [2]. One reason for higher complexity is handling calls of Python scripts on MS Windows (which would use some code review). [1] https://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/toolboxes.py?rev=64678#L475 [2] https://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/core/globalvar.py?rev=64678#L136 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi Radim, I would be willing to volunteer to help maintain the qgm and qgc files. Great, I'll keep current config system also for GRASS 7. If you explain me what to do, I also volunteer for that task. Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi Radim, I would be willing to volunteer to help maintain the qgm and qgc files. Andrew On Tue, Feb 24, 2015 at 12:28 AM, Radim Blazek radim.bla...@gmail.com wrote: Olá todos, I'am already preparing crowdfunding campaign for GRASS plugin upgrade. It will include: - qgisgrasslib upgrade to GRASS 7 - single build with both GRASS 6 and 7 (GRASS version chosen by environmental variables on start up) - move plugin browser functionality to standard QGIS browser (meta info widget, delete and rename action) - implement raster and vector import via browser drag and drop (including reprojection) - new/open/close location tools upgrade to GRASS 7 - region editor upgrade to GRASS 7 - upgrade GRASS shell to the last qtermwidget - 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. - vector editing overall upgrade and enhancement more integrated with standard QGIS tools - standard editing tools (e.g. node tool) - snapping to other layers - undo/redo - attribute forms - possibility to change topological symbology via standard style dialog - standard rendering of not edited layers based on edited map (i.e. draw filled polygons on background during editing) I am currently coding proof of concept for vector editing to be sure that it is feasible at all. I hope to launch the campaign in about 2-3 weeks. Radim On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio pedrongvenan...@gmail.com wrote: Olá Paolo, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Thanks! Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi GRASS plugin users ;-) +1 Pedro GRASS plugin is definitely the most convenient way to access GRASS functionalities… With plugin you have GRASS embedded in QGIS, you get the best of both worlds Sylvain De : qgis-developer-boun...@lists.osgeo.org [mailto:qgis-developer-boun...@lists.osgeo.org] De la part de Pedro Venâncio Envoyé : lundi 23 février 2015 22:07 À : Paolo Cavallini Cc : qgis-developer Objet : Re: [Qgis-developer] QGIS and GRASS 7.0.0 Olá Paolo, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Thanks! Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Olá todos, I'am already preparing crowdfunding campaign for GRASS plugin upgrade. It will include: - qgisgrasslib upgrade to GRASS 7 - single build with both GRASS 6 and 7 (GRASS version chosen by environmental variables on start up) - move plugin browser functionality to standard QGIS browser (meta info widget, delete and rename action) - implement raster and vector import via browser drag and drop (including reprojection) - new/open/close location tools upgrade to GRASS 7 - region editor upgrade to GRASS 7 - upgrade GRASS shell to the last qtermwidget - 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. - vector editing overall upgrade and enhancement more integrated with standard QGIS tools - standard editing tools (e.g. node tool) - snapping to other layers - undo/redo - attribute forms - possibility to change topological symbology via standard style dialog - standard rendering of not edited layers based on edited map (i.e. draw filled polygons on background during editing) I am currently coding proof of concept for vector editing to be sure that it is feasible at all. I hope to launch the campaign in about 2-3 weeks. Radim On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio pedrongvenan...@gmail.com wrote: Olá Paolo, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Thanks! Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
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 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Il 24/02/2015 09:02, PIERRE Sylvain ha scritto: Hi GRASS plugin users ;-) +1 Pedro GRASS plugin is definitely the most convenient way to access GRASS functionalities… With plugin you have GRASS embedded in QGIS, you get the best of both worlds Merci Pierre. Unfortunately, +1 is not enough here: we need someone to either coding, or sponsoring a developer. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
On Tue, Feb 24, 2015 at 3:28 AM, Radim Blazek radim.bla...@gmail.com wrote: - 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. Hi Radim, it would be good if you can include GRASS Addons, too. There is a lot of requests for installing/running GRASS Addons from QGIS, e.g. at gis.stackexchange.com. Also, there are some files in GRASS GIS which might be quite useful [1]. toolboxes.xml [2] contains GRASS GIS modules sorted into different tooboxes. They are currently not part of the official API but it is just a matter of declaring them as part of API I guess [3]. GRASS wxGUI is using these files to create a menu and module tree in Search module tab. It is also a way to customize wxGUI [4] but that's not related to QGIS use case. Loading Addons dynamically to menu or module tree including their descriptions seems to be a bit challenging but if nothing else wxGUI can always run a module installed using g.extension (or custom user script) if it can run and give --interface-description. Best, Vaclav [1] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml [2] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml/toolboxes.xml [3] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/docs/wxgui_sphinx/src/wxgui_toolboxes.rst [4] http://grass.osgeo.org/grass70/manuals/wxGUI.toolboxes.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi, On Tue, Feb 24, 2015 at 7:11 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Tue, Feb 24, 2015 at 3:28 AM, Radim Blazek radim.bla...@gmail.com wrote: - 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. Hi Radim, it would be good if you can include GRASS Addons, too. There is a lot of requests for installing/running GRASS Addons from QGIS, e.g. at gis.stackexchange.com. How can I get list of installed GRASS Addons? Also, there are some files in GRASS GIS which might be quite useful [1]. toolboxes.xml [2] The toolboxes.xml looks interesting, fortunately we have already volunteer to maintain qgc (tree configuration). Radim contains GRASS GIS modules sorted into different tooboxes. They are currently not part of the official API but it is just a matter of declaring them as part of API I guess [3]. GRASS wxGUI is using these files to create a menu and module tree in Search module tab. It is also a way to customize wxGUI [4] but that's not related to QGIS use case. Loading Addons dynamically to menu or module tree including their descriptions seems to be a bit challenging but if nothing else wxGUI can always run a module installed using g.extension (or custom user script) if it can run and give --interface-description. Best, Vaclav [1] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml [2] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml/toolboxes.xml [3] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/docs/wxgui_sphinx/src/wxgui_toolboxes.rst [4] http://grass.osgeo.org/grass70/manuals/wxGUI.toolboxes.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
On Tue, Feb 24, 2015 at 9:51 PM, Andrew amcani...@gmail.com wrote: Hi Radim, I would be willing to volunteer to help maintain the qgm and qgc files. Great, I'll keep current config system also for GRASS 7. Radim Andrew On Tue, Feb 24, 2015 at 12:28 AM, Radim Blazek radim.bla...@gmail.com wrote: Olá todos, I'am already preparing crowdfunding campaign for GRASS plugin upgrade. It will include: - qgisgrasslib upgrade to GRASS 7 - single build with both GRASS 6 and 7 (GRASS version chosen by environmental variables on start up) - move plugin browser functionality to standard QGIS browser (meta info widget, delete and rename action) - implement raster and vector import via browser drag and drop (including reprojection) - new/open/close location tools upgrade to GRASS 7 - region editor upgrade to GRASS 7 - upgrade GRASS shell to the last qtermwidget - 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. - vector editing overall upgrade and enhancement more integrated with standard QGIS tools - standard editing tools (e.g. node tool) - snapping to other layers - undo/redo - attribute forms - possibility to change topological symbology via standard style dialog - standard rendering of not edited layers based on edited map (i.e. draw filled polygons on background during editing) I am currently coding proof of concept for vector editing to be sure that it is feasible at all. I hope to launch the campaign in about 2-3 weeks. Radim On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio pedrongvenan...@gmail.com wrote: Olá Paolo, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Thanks! Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Olá Paolo, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Thanks! Best regards, Pedro Venâncio QGIS_Processing_GRASS_6_vs_7.ods Description: application/vnd.oasis.opendocument.spreadsheet ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Paolo Cavallini wrote Il 23/02/2015 00:06, Pedro Venâncio ha scritto: QGIS GRASS plugin (qgis-plugin-grass) still depends on the 6.4.4, so it will no longer be available for those who upgrade to GRASS 7.0.0. GRASS 6.4 in Processing has 168 algorithms, GRASS 7 has 153, are a few less, but it will be easier to solve. So how can the issue of GRASS plugin be overcome with the GRASS 7? Ola Pedro, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. Thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html *New course* QGIS for naturalists: http://www.faunalia.eu/en/nat_course.html ___ Qgis-developer mailing list Qgis-developer@.osgeo http://lists.osgeo.org/mailman/listinfo/qgis-developer the grass 7 command list in qgis processing should be uptodate. see: https://github.com/qgis/QGIS/commit/b7dcd67f3eb2e330742c2dd30f035ea6c31a9973 - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-and-GRASS-7-0-0-tp5189299p5189554.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Olá Pedro, Il 23/02/2015 22:06, Pedro Venâncio ha scritto: Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. Agreed. Moreover, the overhead of importing/exporting data for each step of a complex analysis puts GRASS algs to a disadvantage for Processing users. BTW, I'm unsure about the G7 support in the Browser: could someone check thoroughly? If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? Yes, I have been talking about that. Radim did most of the work on the plugin. If he (or eventually others) are available, a crowdfounding initiative could be appropriate. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Obrigado for this. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Yes, these are adaptations of the original commands, in order to make them more usable from QGIS. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Overall, I think these are minor issues. If someone really miss them, they can ask, and we can add them. All the best, and thanks again. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Il 23/02/2015 00:06, Pedro Venâncio ha scritto: QGIS GRASS plugin (qgis-plugin-grass) still depends on the 6.4.4, so it will no longer be available for those who upgrade to GRASS 7.0.0. GRASS 6.4 in Processing has 168 algorithms, GRASS 7 has 153, are a few less, but it will be easier to solve. So how can the issue of GRASS plugin be overcome with the GRASS 7? Ola Pedro, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. Thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html *New course* QGIS for naturalists: http://www.faunalia.eu/en/nat_course.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
