I think this must be related to the configuration of the plugins folder.
The script provider reads scripts in the scripts folder, which is
configured as an option. Maybe that setting is not available in your
stand-alone script...since it is stored using QSettings. You can check
it calling ScriptUt
Nyall, that would be useful. And GUI changes as well. In Docs we have tags
for identify the need to create new screenshots for users manual.
DelazJ escreveu no dia qui, 26/11/2015 às 23:06:
> Hi,
> BTW, it's not against Documentation repo but could this also be used to
> fetch bug fixes so that
Hi,
BTW, it's not against Documentation repo but could this also be used to
fetch bug fixes so that a list of bug fixes can be generated to accompany
qgis releases?
2015-11-26 22:40 GMT+01:00 Nyall Dawson :
> Hi all,
>
> Just a thought I had - could the new hook which creates a documentation
> is
On Thu, Nov 26, 2015 at 11:17 PM, Luigi Pirelli wrote:
> processing.alglist('script') to retrieve the list of commands with
> "script" string inside it's name or description
> e.g.
> processing.alglist('ogr')
> returns a lot of elements... if we get one of them
>
--- >8 -
processing.alglist('script') to retrieve the list of commands with
"script" string inside it's name or description
e.g.
processing.alglist('ogr')
returns a lot of elements... if we get one of them
OGR default-->quickosm:ogrdefault
I've the command name "q
Hi all,
Just a thought I had - could the new hook which creates a documentation
issue when the message contains "feature" be amended so that it detects an
additional "needs docs" tag too?
My thoughts are that sometimes a change should be accompanied by
documentation updates but isn't a new featur
On 26-11-15 09:50, Matthias Kuhn wrote:
> I just disabled grass 7 Tests because of Travis failures [1]. This was
> not introdced by malicious code but by disappearing packages from a ppa.
> I think it was in grass-stable which is now empty and says that grass
> gis packages are maintained in ubuntu
Very excited to find the answer to this. It's exactly where I had to stop when
trying to write some tests for processing. :)
> On Nov 26, 2015, at 6:55 AM, qgis-developer-requ...@lists.osgeo.org wrote:
>
> Re: Processing scripts in stand-alone Pythonscripts
__
On Thu, Nov 26, 2015 at 4:33 AM, Eugenio Trumpy
wrote:
> We hope r.mapcalc will be added in the toolbox, soon.
As far as I know, nobody is working on that now. But it is certainly a
topic open for contributions.
___
Qgis-developer mailing list
Qgis-d
On Thu, Nov 26, 2015 at 3:40 AM, Radim Blazek
wrote:
> Just a note, r.mapcalc including visual editor is present in the GRASS
> Plugin
> http://www.gissula.eu/qgis-grass-plugin-crowdfunding/images/r.mapcalc.png
>
This looks pretty cool, Radim. It might be really helpful to some people.
_
Making changes to the present georeferencer would be a great improvement.
I have used this georeferencer for many years, but it has a major drawback
- when loading a *.points file > 200-300 points
-- it becomes very slow
A *.points file of 1000 points can take up to an hour to load
- to add/move/
On Thu, Nov 26, 2015 at 2:44 PM, Anita Graser wrote:
> HI Victor,
>
> On Thu, Nov 26, 2015 at 1:12 PM, Victor Olaya wrote:
>
>> does Processing.getAlgorithm("script:helloworld") work in a normal
>> QGIS Python console?
>>
>
> Yes it does.
>
> Just in case, the name of the script is the name of
HI Victor,
On Thu, Nov 26, 2015 at 1:12 PM, Victor Olaya wrote:
> does Processing.getAlgorithm("script:helloworld") work in a normal
> QGIS Python console?
>
Yes it does.
Just in case, the name of the script is the name of the file (without
> the extension)
>
> Maybe you can try
>
> Proce
does Processing.getAlgorithm("script:helloworld") work in a normal
QGIS Python console?
Just in case, the name of the script is the name of the file (without
the extension)
Maybe you can try Processing.alghelp("script") to get the name of
available algorithms from the script provider
Hope this h
;>
>>> The message was checked by ESET Mail Security.
>>> http://www.eset.com
>>>
>>>
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> List info: http://lists.osgeo.org/mailman/lis
On 26 November 2015 at 07:41, Andreas Neumann wrote:
> Hi,
>
> Is there a reason why the QGIS georeferencer is still a plugin and not
> part of QGIS core?
>
> Do you think that the existing QGIS raster georeferencer could be
> enhanced/extended to also allow the georeferencing of one or more vect
Hi,
I'm trying to run Processing scripts in a stand-alone Python script. The
examples available online for calling default, e.g. QGIS algorithms, work
fine but when I try to access a script instead, it cannot be found, i.e.
getAlgorithm() returns None.
Am I missing something or is this a bug?
#
Il giorno Thu, 26 Nov 2015 08:41:21 +0100
Andreas Neumann ha scritto:
> Hi,
Hi Andreas,
> .
> I know that there is a Python plugin to do vector georeferencing -
Daniele, Luca, Giuseppe and I, we are the developers of the vectorgeoref
plugin (*);
> but I really think that both raster and
info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
__ Information from ESET Mail Security, version of virus
signature database 12626 (20151126) __
The message was checked by ESET Mail Security.
http://ww
Thank you Giovanni,
my only solution is to install grass64, which is not simple on ubuntu 15.04
because the different libraries version and dependencies.
>
> > Only solution to install in some way grass64.
>
> yes
We hope r.mapcalc will be added in the toolbox, soon.
r.null is a minor problem
> Only solution to install in some way grass64.
yes
> However r.mapcalc is present in grass7 as well as r.null, I thought if would
> have added r.null.text and r.mapcalc in
> /usr/share/qgis/plugin/processing/algs/grass7/description
>
> those modules should have been present in the processing too
Hi all,
thanks for your hints, I understand r.mapcalculator is not present in grass7,
at least for now, so it cannot appear on processing toolbox.
Only solution to install in some way grass64.
However r.mapcalc is present in grass7 as well as r.null, I thought if would
have added r.null.text and
Hi,
I just disabled grass 7 Tests because of Travis failures [1]. This was
not introdced by malicious code but by disappearing packages from a ppa.
I think it was in grass-stable which is now empty and says that grass
gis packages are maintained in ubuntugis-unstable [2]. It looks to me as
if the
On Wed, Nov 25, 2015 at 9:35 PM, Giovanni Manghi
wrote:
>> Then I searched for r.mapcalculator, which was present in the old processing
>> toolbox. I didn't find it
>> in the grass7 processing modules list. Although the grass7 stand alone has
>> r.mapcalc (not r.mapcalculator),
>> in the grass7
er mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
__ Information from ESET Mail Security, version of virus signature
database 12626 (20151126) __
T
25 matches
Mail list logo
