fyi
https://lists.osgeo.org/pipermail/qgis-developer/2018-April/052916.html
---
Hi all,
Please see https://github.com/qgis/QGIS-Enhancement-Proposals/issues/120
for a new QEP regarding handling of optional parameter groups for
processing algorithms, design
This mail has also been sent to osgeo4w-dev initially
Hi guys
Don't know if this is the right place to ask.
Grass 7.1 dev was just made 64 bit, and can be installed via osgeo4w. It
is available in QGIS processing, but not as a plugin unlike the QGIS Grass
7 plugin for 32 bit.
Anyone working on
Hi,
the GRASS 7 plugin is enabled in QGIS master, but there are many
options which changed in GRASS 7 and has to be fixed in .qgm files.
Because some people already promised to help with the upgrade of
modules' configuration I want to ask them and everybody who is
interested, to start the upgrade
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=5d1jZz
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 im
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.
Best regards
Soeren
2015-03-23 19:56 GMT+01:00 Radim Blazek :
> Hi all,
>
> I have fi
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 packa
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. Brie
On Tue, Mar 24, 2015 at 1:30 PM, Pietro wrote:
> Hi Vaclav,
>
> On Tue, Mar 24, 2015 at 3:54 PM, Vaclav Petras
> wrote:
> > On Tue, Mar 24, 2015 at 2:00 AM, Pietro wrote:
> >> together with Francesco Geri, last week we started to write a first
> >> draft that generate the GUI for the GRASS modu
Hi Radim,
On Tue, Mar 24, 2015 at 5:11 PM, Radim Blazek wrote:
> On Tue, Mar 24, 2015 at 7:00 AM, Pietro wrote:
>> together with Francesco Geri, last week we started to write a first
>> draft that generate the GUI for the GRASS module dynamically (based on
>> the xml generated with: --interface-
Hi Vaclav,
On Tue, Mar 24, 2015 at 3:54 PM, Vaclav Petras wrote:
> On Tue, Mar 24, 2015 at 2:00 AM, Pietro wrote:
>> together with Francesco Geri, last week we started to write a first
>> draft that generate the GUI for the GRASS module dynamically (based on
>> the xml generated with: --interfac
On Tue, Mar 24, 2015 at 7:00 AM, Pietro wrote:
> Hi Radim,
>
> together with Francesco Geri, last week we started to write a first
> draft that generate the GUI for the GRASS module dynamically (based on
> the xml generated with: --interface-description), so far it is based
> on grass7 but should
On Tue, Mar 24, 2015 at 2:00 AM, Pietro wrote:
> Hi Radim,
>
> together with Francesco Geri, last week we started to write a first
> draft that generate the GUI for the GRASS module dynamically (based on
> the xml generated with: --interface-description), so far it is based
> on grass7 but should
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 tempo
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 GRAS
Hi Radim,
2015-03-24 9:40 GMT+01:00 Radim Blazek :
> 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 f
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, sin
Hi Radim,
together with Francesco Geri, last week we started to write a first
draft that generate the GUI for the GRASS module dynamically (based on
the xml generated with: --interface-description), so far it is based
on grass7 but should work also on grass6 (not tested, should be enough
to backpo
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 t
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/
Pl
Paolo Cavallini wrote:
> I would like to do a poll on qgis-grass usage: which would be the best
> web tool to use? Probably better not to use qgis or grass pages;
do you mean the toolbox or the two softwares as independent entities?
if the toolbox, why not on the qgis.org site? that's were most of
Hi all.
I would like to do a poll on qgis-grass usage: which would be the best
web tool to use? Probably better not to use qgis or grass pages; does
osgeo provides polling facilities?
Thanks.
--
Paolo Cavallini: http://www.faunalia.it/pc
___
grass-dev m
The QGIS people ask for help with these open bugs:
Qgis 1.6/trunk, osgeo4w/standalone crashes when importing vectors
in a GRASS mapset or when adding them to the project
https://trac.osgeo.org/qgis/ticket/3648
-> v.in.ogr
shapefiles fails to be imported into GRASS mapset with qgis 1.6/trunk
under
Hi all.
From the hackfest: we started working on the modules as listed in [0],
and added comments to them. Please check them and add your own.
All the best.
--
http://www.faunalia.it/pc
[0] http://grass.osgeo.org/wiki/GRASS-QGIS_relevant_module_list
_
On Fri, May 8, 2009 at 3:39 PM, Massimiliano Cannata
wrote:
...
> Maybe web site hits statistics are more relevant? or number of download?
Find them here (That's *real* data):
http://grass.osgeo.org/logs-bin/awstats.pl?config=grass.osgeo.org
Not sure if it exists for QGIS, too.
Markus
_
Massimiliano Cannata ha scritto:
> thanks for the stats, but I believe that the comparison is quite
> inappropriate.
I'm aware of this, and I pointed it out. Nevertheless, the *trends* are
interesting, and I think they are well explained by my hypotheses.
All the best.
--
Paolo Cavallini: http:/
Hi Paolo,
thanks for the stats, but I believe that the comparison is quite
inappropriate.
My 2 cents...
The graph grass vs. qgis
(http://www.google.com/insights/search/overviewReport?cat=&q=qgis&geo=&date=&gprop=&clp=&cmpt=q#q=qgis%2Cgrass&cmpt=q)
shows that grass is much more searched then q
On Mon, May 4, 2009 at 8:49 AM, Paolo Cavallini wrote:
...
> Unfortunately, it seems that both qgis and grass devs are mainly
> concentrated on their core sw, with limited attention to the interaction
> between the two (eg the qgis-plugin-grass does not have a dedicated dev,
> and in grass a lot o
Hi all.
Even though these "web statistics" are always to be taken with caution:
http://www.google.com/insights/search/overviewReport?cat=&q=qgis&geo=&date=&gprop=&clp=&cmpt=q#q=qgis%2Cgrass
gis&cmpt=q
(thanks Maxim for pointing it out)
I think they tell us several interesting things, particularly f
29 matches
Mail list logo
