Re: [Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Nyall Dawson]

On Fri, 18 Feb 2022 at 09:22, Nyall Dawson  wrote:

> By
> not setting a "maximum" value in the row we indicate that the range is
> from 100 < input value < +infinity.

Gah, that should be "1 < input value < +infinity"!
Nyall
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Nyall Dawson]

On Fri, 18 Feb 2022 at 08:56, Bernd Vogelgesang
 wrote:
>
> Hi Nyall,
>
> sorry, mixed things up. The native raster calculator only threw errors,
> while the GDAL worked.

Thanks for the clarification! Indeed there are some open tickets
regarding the native raster calculator.

FWIW, I'd actually suggest going with the native "reclassify by table"
to perform this task. It's a very efficient tool and will handle
massive rasters without issue. The table parameter would be set to a
single row with "minimum" = 1, "maximum" = blank/not set, and "value"
= 0. Leave everything else at their default values.

To explain: If you don't check the advanced parameter "use no data
when no range matches value" (the default is that it's unchecked!)
then any input pixel value which doesn't fall into one of the ranges
defined in the table will be copied unchanged to the output. So only
pixel values > 1 will match a rule, and will output a "0" value. By
not setting a "maximum" value in the row we indicate that the range is
from 100 < input value < +infinity. It's a bit clearer when you run
the algorithm, as the log will show a descriptive explanation of the
classes. Something like this:

"Using classes:
1) 1 < x ≤ ∞ → 0"

ie. values > 1 and <= infinity will map to 0, others will be unchanged.

Hope that helps!

Nyall











>
> Now that I tried again, everything is fine. Strange hickup.
>
> Anyway, everything ist fine now and things start getting sorted.
>
> Happy again :)
>
> Cheers,
>
> Bernd
>
>
>
> Am 17.02.22 um 23:22 schrieb Nyall Dawson:
> > On Fri, 18 Feb 2022 at 08:08, Bernd Vogelgesang
> >  wrote:
> >> Hi Sebastian,
> >>
> >> thanx, that worked.
> >>
> >> But somehow, the hole process feels a bit clumsy.
> >>
> >> Having to fumble together a classification with "thru" (juck!), then the 
> >> toolbox reclassify just seems to be broken,
> > Which reclassify tool are you referring to exactly? The native QGIS
> > ones are 100% NOT broken. (The SAGA one may be, but that's a 3rd party
> > tool.)
> >
> > Nyall
> >
> >
> > gladly gdal calculator does ...
> >> Why isn't there some "raster SQL" that saves one from all these stupid 
> >> single steps?
> >>
> >> Ok, will then try to build a model and hope it will work for the tests to 
> >> come…
> >>
> >> Thanks a lot,
> >>
> >> Bernd
> >>
> >>
> >> Am 17.02.22 um 22:19 schrieb Sebastian Gutwein:
> >>
> >> Reclassify your Layer 1 to be anything greater than 1 = 0 everything else 
> >> equals 1. This will give you a binary 1 and 0 raster (Layer 3)  that you 
> >> can use in the raster calculator: Layer 2 * Layer 3.  Anywhere where layer 
> >> 3 is 1 your layer 2 values will stay the same and anywhere where layer 3 
> >> is 0 your layer 2 values will become 0.
> >>
> >> On Thu, Feb 17, 2022 at 3:19 PM Bernd Vogelgesang 
> >>  wrote:
> >>> Hi folk,
> >>>
> >>> I hardly never work with raster calculations, and unfortunately there is 
> >>> nowhere a collection of syntax examples for different use cases to be 
> >>> found (documentation :( ).
> >>>
> >>> Anything apart from +-*/ is beyond my scope.
> >>>
> >>> So,
> >>>
> >>> I made a viewshed analysis over a digital surface model (try the awesome 
> >>> Visibility Analysis plugin form Zoran Čučković and buy him a beer!)
> >>>
> >>> A lot of "views" are caught by tree canopy, but I am only interest in the 
> >>> flat grounds.
> >>>
> >>> So I substracted the surface model layer from the ground model layer, and 
> >>> this is Layer 1.
> >>>
> >>> Giving a threshold of 1 meters difference for inaccuracities, all pixels 
> >>> in this layer above 1 should result in 0 (zero) in my viewshed raster 
> >>> (Layer 2)
> >>>
> >>> Please give me some hints,
> >>>
> >>> Cheers,
> >>>
> >>> Bernd
> >>>
> >>>
> >>> ___
> >>> Qgis-user mailing list
> >>> Qgis-user@lists.osgeo.org
> >>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >> ___
> >> Qgis-user mailing list
> >> Qgis-user@lists.osgeo.org
> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Bernd Vogelgesang]

Hi Nyall,

sorry, mixed things up. The native raster calculator only threw errors,
while the GDAL worked.

Now that I tried again, everything is fine. Strange hickup.

Anyway, everything ist fine now and things start getting sorted.

Happy again :)

Cheers,

Bernd



Am 17.02.22 um 23:22 schrieb Nyall Dawson:

On Fri, 18 Feb 2022 at 08:08, Bernd Vogelgesang
 wrote:

Hi Sebastian,

thanx, that worked.

But somehow, the hole process feels a bit clumsy.

Having to fumble together a classification with "thru" (juck!), then the 
toolbox reclassify just seems to be broken,

Which reclassify tool are you referring to exactly? The native QGIS
ones are 100% NOT broken. (The SAGA one may be, but that's a 3rd party
tool.)

Nyall


gladly gdal calculator does ...

Why isn't there some "raster SQL" that saves one from all these stupid single 
steps?

Ok, will then try to build a model and hope it will work for the tests to come…

Thanks a lot,

Bernd


Am 17.02.22 um 22:19 schrieb Sebastian Gutwein:

Reclassify your Layer 1 to be anything greater than 1 = 0 everything else 
equals 1. This will give you a binary 1 and 0 raster (Layer 3)  that you can 
use in the raster calculator: Layer 2 * Layer 3.  Anywhere where layer 3 is 1 
your layer 2 values will stay the same and anywhere where layer 3 is 0 your 
layer 2 values will become 0.

On Thu, Feb 17, 2022 at 3:19 PM Bernd Vogelgesang  
wrote:

Hi folk,

I hardly never work with raster calculations, and unfortunately there is 
nowhere a collection of syntax examples for different use cases to be found 
(documentation :( ).

Anything apart from +-*/ is beyond my scope.

So,

I made a viewshed analysis over a digital surface model (try the awesome 
Visibility Analysis plugin form Zoran Čučković and buy him a beer!)

A lot of "views" are caught by tree canopy, but I am only interest in the flat 
grounds.

So I substracted the surface model layer from the ground model layer, and this 
is Layer 1.

Giving a threshold of 1 meters difference for inaccuracities, all pixels in 
this layer above 1 should result in 0 (zero) in my viewshed raster (Layer 2)

Please give me some hints,

Cheers,

Bernd


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Nyall Dawson]

On Fri, 18 Feb 2022 at 08:08, Bernd Vogelgesang
 wrote:
>
> Hi Sebastian,
>
> thanx, that worked.
>
> But somehow, the hole process feels a bit clumsy.
>
> Having to fumble together a classification with "thru" (juck!), then the 
> toolbox reclassify just seems to be broken,

Which reclassify tool are you referring to exactly? The native QGIS
ones are 100% NOT broken. (The SAGA one may be, but that's a 3rd party
tool.)

Nyall


gladly gdal calculator does ...
>
> Why isn't there some "raster SQL" that saves one from all these stupid single 
> steps?
>
> Ok, will then try to build a model and hope it will work for the tests to 
> come…
>
> Thanks a lot,
>
> Bernd
>
>
> Am 17.02.22 um 22:19 schrieb Sebastian Gutwein:
>
> Reclassify your Layer 1 to be anything greater than 1 = 0 everything else 
> equals 1. This will give you a binary 1 and 0 raster (Layer 3)  that you can 
> use in the raster calculator: Layer 2 * Layer 3.  Anywhere where layer 3 is 1 
> your layer 2 values will stay the same and anywhere where layer 3 is 0 your 
> layer 2 values will become 0.
>
> On Thu, Feb 17, 2022 at 3:19 PM Bernd Vogelgesang  
> wrote:
>>
>> Hi folk,
>>
>> I hardly never work with raster calculations, and unfortunately there is 
>> nowhere a collection of syntax examples for different use cases to be found 
>> (documentation :( ).
>>
>> Anything apart from +-*/ is beyond my scope.
>>
>> So,
>>
>> I made a viewshed analysis over a digital surface model (try the awesome 
>> Visibility Analysis plugin form Zoran Čučković and buy him a beer!)
>>
>> A lot of "views" are caught by tree canopy, but I am only interest in the 
>> flat grounds.
>>
>> So I substracted the surface model layer from the ground model layer, and 
>> this is Layer 1.
>>
>> Giving a threshold of 1 meters difference for inaccuracities, all pixels in 
>> this layer above 1 should result in 0 (zero) in my viewshed raster (Layer 2)
>>
>> Please give me some hints,
>>
>> Cheers,
>>
>> Bernd
>>
>>
>> ___
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Bernd Vogelgesang]

Hi Sebastian,

thanx, that worked.

But somehow, the hole process feels a bit clumsy.

Having to fumble together a classification with "thru" (juck!), then the
toolbox reclassify just seems to be broken, gladly gdal calculator does ...

Why isn't there some "raster SQL" that saves one from all these stupid
single steps?

Ok, will then try to build a model and hope it will work for the tests
to come…

Thanks a lot,

Bernd


Am 17.02.22 um 22:19 schrieb Sebastian Gutwein:

Reclassify your Layer 1 to be anything greater than 1 = 0 everything
else equals 1. This will give you a binary 1 and 0 raster (Layer 3) 
that you can use in the raster calculator: Layer 2 * Layer 3. 
Anywhere where layer 3 is 1 your layer 2 values will stay the same and
anywhere where layer 3 is 0 your layer 2 values will become 0.

On Thu, Feb 17, 2022 at 3:19 PM Bernd Vogelgesang
 wrote:

Hi folk,

I hardly never work with raster calculations, and unfortunately
there is nowhere a collection of syntax examples for different use
cases to be found (documentation :( ).

Anything apart from +-*/ is beyond my scope.

So,

I made a viewshed analysis over a digital surface model (try the
awesome Visibility Analysis plugin form Zoran Čučković and buy him
a beer!)

A lot of "views" are caught by tree canopy, but I am only interest
in the flat grounds.

So I substracted the surface model layer from the ground model
layer, and this is Layer 1.

Giving a threshold of 1 meters difference for inaccuracities, all
pixels in this layer above 1 should result in 0 (zero) in my
viewshed raster (Layer 2)

Please give me some hints,

Cheers,

Bernd


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] How to import a XML color ramp ?

[Allan López]

Dear all,
I got a color ramp parula.XML, but I do not see a way to import it along
with the other ramps.
I appreciate your kind assistance
Best,
Allan Lopez
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Sebastian Gutwein]

Reclassify your Layer 1 to be anything greater than 1 = 0 everything else
equals 1. This will give you a binary 1 and 0 raster (Layer 3)  that you
can use in the raster calculator: Layer 2 * Layer 3.  Anywhere where layer
3 is 1 your layer 2 values will stay the same and anywhere where layer 3 is
0 your layer 2 values will become 0.

On Thu, Feb 17, 2022 at 3:19 PM Bernd Vogelgesang 
wrote:

> Hi folk,
>
> I hardly never work with raster calculations, and unfortunately there is
> nowhere a collection of syntax examples for different use cases to be found
> (documentation :( ).
>
> Anything apart from +-*/ is beyond my scope.
>
> So,
>
> I made a viewshed analysis over a digital surface model (try the awesome
> Visibility Analysis plugin form Zoran Čučković and buy him a beer!)
>
> A lot of "views" are caught by tree canopy, but I am only interest in the
> flat grounds.
>
> So I substracted the surface model layer from the ground model layer, and
> this is Layer 1.
>
> Giving a threshold of 1 meters difference for inaccuracities, all pixels
> in this layer above 1 should result in 0 (zero) in my viewshed raster
> (Layer 2)
>
> Please give me some hints,
>
> Cheers,
>
> Bernd
>
>
> 
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Raster calculation: if Layer1 is > 1, then Layer2 should be 0

[Bernd Vogelgesang]

Hi folk,

I hardly never work with raster calculations, and unfortunately there is
nowhere a collection of syntax examples for different use cases to be
found (documentation :( ).

Anything apart from +-*/ is beyond my scope.

So,

I made a viewshed analysis over a digital surface model (try the awesome
Visibility Analysis plugin form Zoran Čučković and buy him a beer!)

A lot of "views" are caught by tree canopy, but I am only interest in
the flat grounds.

So I substracted the surface model layer from the ground model layer,
and this is Layer 1.

Giving a threshold of 1 meters difference for inaccuracities, all pixels
in this layer above 1 should result in 0 (zero) in my viewshed raster
(Layer 2)

Please give me some hints,

Cheers,

Bernd



___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [QGIS-it-user] Ordine di scrittura del file qgs

[Marco Guiducci]

Il 17/02/2022 11:28, Andrea Giudiceandrea ha scritto:

Il 17/02/2022 11:17, Marco Guiducci ha scritto:

Grazie!
funziona al 99%.
scombina, almeno nel mio progetto, i figli di questo elemento: 
 che son rimangono nell'ordine e vengono 
inserite extra linee bianche (diverse ad ogni salvataggio).


Ciao Marco,
come puoi leggere nel repository del plugin su GitHub, il problema è 
già stato segnalato qualche mese fa 
https://github.com/opengisch/qgis_trackable_project_files/issues/21


Comunque stai usando delle versioni di QGIS rilasciate un anno fa e 
nel frattempo il problema potrebbe essere stato risolto.


A presto.

Andrea
___



ah ecco. ho letto.
anche questo |false, segnalato 
nell'intervento che mi dai, è veramente ganzo.

Io non l'avevo rammentato ma me ne ero accorto.
il plugin l'ho testato con la 3.16.4.
Lo testerò anche con la 3.18.1. Altre versioni più recenti, al momento, 
non le uso.|

ciao e grazie

--
Marco Guiducci
Regione Toscana - Settore Sistema Informativo e pianificazione del territorio

___
QGIS-it-user mailing list
QGIS-it-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-it-user

Re: [QGIS-it-user] Ordine di scrittura del file qgs

[Paolo Cavallini]

Suggerirei di aprire un ticket sul plugin, quello che hai notato non dovrebbe 
essere difficile da sistemare, almeno in parte.

Il 17 febbraio 2022 12:17:56 EET, Marco Guiducci 
 ha scritto:
>Il 16/02/2022 18:19, Andrea Giudiceandrea ha scritto:
>> Ciao Marco,
>> c'è un plugin che dovrebbe risolvere questo problema: 
>> https://plugins.qgis.org/plugins/trackable_project_files/
>>
>> A presto.
>>
>> Andrea
>>
>> Il 16/02/2022 15:48, Marco Guiducci ha scritto:
>>> Ho notato che QGis, ogni volta che salva il file (sia con Salva con 
>>> nome che non) scrive il qgs in maniera diversa: le righe sono
>scritte 
>>> nello stesso ordine, ma il loro contenuto è ordinato diversamente se
>
>>> il tag xml prevede più attributi.
>>> Questo fa si che mi sia impossibile, su un file da oltre
>20.000righe, 
>>> isolare le poche differenze.
>>
>
>
>Grazie!
>funziona al 99%.
>scombina, almeno nel mio progetto, i figli di questo elemento: 
> che son rimangono nell'ordine e vengono 
>inserite extra linee bianche (diverse ad ogni salvataggio).
>ma direi che il passo è enorme.
>da ieri penso alla causa: non conoscendo i gangli di QGis, ho pensato 
>che il progetto, all'apertura, sia caricato in un db sqlite. il 
>salvataggio avverrà attraverso query sql che, senza un parametro order 
>by, restituiscono la soluzione in ordine "sparso".
>ma ho anche  notato che la proprietà "prop" era sempre ordinata nello 
>stesso  modo, tutte le altre no.
>Ci sono alcune proprietà con due soli attributi e ho pensato che 
>statisticamente una volta su due l'ordine dovrebbe essere giusto.
>ma qui interviene la legge di murphy...
>
>comunque il mio problema è risolto. grazie ancora
>
>-- 
>Marco Guiducci
>Regione Toscana - Settore Sistema Informativo e pianificazione del
>territorio
>
>___
>QGIS-it-user mailing list
>QGIS-it-user@lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/qgis-it-user

-- 
Sorry for being short___
QGIS-it-user mailing list
QGIS-it-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-it-user

Re: [QGIS-it-user] Ordine di scrittura del file qgs

[Marco Guiducci]

Il 16/02/2022 18:19, Andrea Giudiceandrea ha scritto:

Ciao Marco,
c'è un plugin che dovrebbe risolvere questo problema: 
https://plugins.qgis.org/plugins/trackable_project_files/


A presto.

Andrea

Il 16/02/2022 15:48, Marco Guiducci ha scritto:
Ho notato che QGis, ogni volta che salva il file (sia con Salva con 
nome che non) scrive il qgs in maniera diversa: le righe sono scritte 
nello stesso ordine, ma il loro contenuto è ordinato diversamente se 
il tag xml prevede più attributi.
Questo fa si che mi sia impossibile, su un file da oltre 20.000righe, 
isolare le poche differenze.





Grazie!
funziona al 99%.
scombina, almeno nel mio progetto, i figli di questo elemento: 
 che son rimangono nell'ordine e vengono 
inserite extra linee bianche (diverse ad ogni salvataggio).

ma direi che il passo è enorme.
da ieri penso alla causa: non conoscendo i gangli di QGis, ho pensato 
che il progetto, all'apertura, sia caricato in un db sqlite. il 
salvataggio avverrà attraverso query sql che, senza un parametro order 
by, restituiscono la soluzione in ordine "sparso".
ma ho anche  notato che la proprietà "prop" era sempre ordinata nello 
stesso  modo, tutte le altre no.
Ci sono alcune proprietà con due soli attributi e ho pensato che 
statisticamente una volta su due l'ordine dovrebbe essere giusto.

ma qui interviene la legge di murphy...

comunque il mio problema è risolto. grazie ancora

--
Marco Guiducci
Regione Toscana - Settore Sistema Informativo e pianificazione del territorio

___
QGIS-it-user mailing list
QGIS-it-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-it-user

[QGIS-it-user] Visualizzare una foto

[Franco Cazzola]

Buongiorno a tutti

Ho un layer puntuale e in un campo della tabella associata ho il nome della 
foto.

Vorrei attivare una azione che  visualizza la foto (non all'interno di una 
form) ma lanciando un visualizzatore.

Questo è abbastanza facile usando il Tipo: Generico perché ci pensa Windows  ma 
poiché devo applicare dei filtri uso un'azione con codice python



Da python, che visualizzatore posso lanciare  e con quale comando ?

Ho provato ad eseguire qview con la riga   process = 
subprocess.Popen([path_to_jpg, path_to_file], shell=False) ma va in errore

Ho provato con "Foto di Windows" ma ha una stringa path un po' lunga e forse 
cambia con la versione e aggiornamento di Windows

Mi basta eseguire il visualizzatore più semplice possibile



QGis 3.16.14

Windows 10



Grazie

Franco Cazzola
___
QGIS-it-user mailing list
QGIS-it-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-it-user

[Qgis-user] Plugin Builder: ImportError: attempted relative import

[L.W.]

Hello,

can someone point me to resolve the error?

I made a plugin-template with plugin builder and tried to run this in
qgis (python editor) without making any changes.

regards


# Python Console
# Use iface to access QGIS API interface or type help(iface) for more info
# Security warning: typing commands from an untrusted source can harm
your computer
exec(open('[...]light.py'.encode('utf-8')).read())
Traceback (most recent call last):
  File "C:\PROGRA~1\QGIS32~2.3\apps\Python39\lib\code.py", line 90, in
runcode
    exec(code, self.locals)
  File "", line 1, in 
  File "", line 28, in 
  File "C:\PROGRA~1/QGIS32~2.3/apps/qgis/./python\qgis\utils.py", line
888, in _import
    mod = _builtin_import(name, globals, locals, fromlist, level)
ImportError: attempted relative import with no known parent package


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[QGIS-it-user] [promo] Corso di cartografia

[matteo]

Salve a tutti,

abbiamo pubblicato ancora posto per il corso di cartografia online di 
QGIS della settimana prossima 21-24 Febbraio 2022.


Ecco tutti gli appuntamenti con la formazione di Faunalia:

* Cartografia con QGIS: 21-24 Febbraio 2022
* Analisi con QGIS: 21-24 Marzo 2022
* Geodatabase: PostgreSQL e PostGIS: 12-15 Aprile 2022
* WebMapping con QGIS:17-20 Maggio 2022
* Python e pyqgis: 13-17 Giugno 2022

Tutte le informazioni sui programmi dei corsi sono disponibili sul 
nostro sito:


https://www.faunalia.eu/it/training


Per ulteriori informazioni i...@faunalia.eu

Saluti

Matteo Ghetta
___
QGIS-it-user mailing list
QGIS-it-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-it-user

[Qgis-user] Keyboard Shortcuts

[Patrick Dunford]

Good day

I am looking at the keyboard shortcuts settings, specifically the 
ability to load a set of shortcuts from a file.


As far as I can tell, there is no global settings or ini file that 
stores all the shortcuts for the software. Instead, there is an option 
to create a file by saving it from the keyboard shortcuts dialog box, 
and this file can then be loaded back in at some future time.


As it looks to me now, I can't see a way in which it might be possible 
to wipe out all the existing settings before loading this file, or 
having the file that is loaded completely replace all of the existing 
shortcuts. In other words, loading that file appears to add to the 
already defined shortcuts.


My preference would be to have some simple way to load all the settings 
from a file to avoid having to manually customise the existing shortcuts 
each time (in this case to remove the three single letter shortcuts that 
appear to be default allocations in the user interface). Is there any 
way of achieving this?


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user