Re: [Qgis-user] QGIS customized importing apparently causes problems with type checkers/Intellisense
On 12/17/21 02:05, Ari Meyer wrote: I do not see any *.pyi files in my 3.16.9 LTR's C:\OSGeo4W\apps\qgis-ltr\python\qgis dir nor in any of the subdirs. Should I be? On my virtual windows machine, I installed recently installed a fresh QGIS using the new osgeo4w v2 installer, and there I have: c:\osgeo4w\apps\qgis\python\qgis\_3d.pyi c:\osgeo4w\apps\qgis\python\qgis\_analysis.pyi c:\osgeo4w\apps\qgis\python\qgis\_core.pyi c:\osgeo4w\apps\qgis\python\qgis\_gui.pyi I had a look, and apparently I installed 'qgis-full' (giving me 3.22) there using the 'advanced' route Hope this helps, (did not try to do the full route though) Regards, Richard Duivenvoorde ___ 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] QGIS customized importing apparently causes problems with type checkers/Intellisense
Thank you, Richard. Yeah, the PyCharm config is obviously different, but I did have most of the same PYTHONPATH, PATH, etc. settings in my batch script. I did more searching, though, and found this gem: https://www.gispo.fi/en/blog/cooking-with-gispo-qgis-plugin-development-in-vs-code/ In it the author had a critical note (perhaps specifically for VS Code users): Note 1: Currently the only one language server supporting autocompletion for qgis and PyQt5 libraries is the Jedi language server. Qgis and PyQt5 packages are using compiled python code and other language servers are having troubles parsing the API from those libraries (Actually this is for security reasons). This solved my problem! I just assumed that all the language servers were functionally equivalent, so I kept banging my head against a wall trying to get it to work with M$'s recommended Pylance. So frustrating. He subsequently wrote: In the following QGIS releases python stub files that describes the API are included in the qgis package so also much better Pylance language server can be then used. If you have *.pyi files in C:/OSGeo4W64/apps/qgis-ltr/python/qgis go with the Pylance language server. I do not see any *.pyi files in my 3.16.9 LTR's C:\OSGeo4W\apps\qgis-ltr\python\qgis dir nor in any of the subdirs. Should I be? In any case, I think this should get me by for a while. Also, you're definitely right that key info like this needs to go into our centralized PyQGIS developer documentation. Cheers! (And thanks to la...@gispo.fi for the blog post!) Ari On Thu, Dec 16, 2021 at 1:30 AM Richard Duivenvoorde wrote: > Hi Ari, > > I'm not using VS Code so sorry, cannot give specific help. > But using Pycharm there also you need to take a lot of hoops to be able to > use code-completion. > See for example: > > > https://qtibia.com/how-to-setup-pycharm-for-qgis-development-under-linux-and-windows/ > and > > https://silverspringenergy.com/using-pycharm-as-an-ide-for-qgis-3-plugin-development-2/ > > The crux is that the editors need to build up some internal structures > with all (possible) types and names in it, so paths from libraries (like > PyQGIS ones) which are not in the normal python path have to be manually > added. AND because pyqgis is actually a wrapper around c++ libs you also > have to point to those (I think because else they do not have enough > information). > Also with PyCharm it is a lot of fiddling, but in the end it just works. > > IF you manage to make it work: let's write it down somewhere! > > Regards, > > Richard Duivenvoorde > > On 12/16/21 01:48, Ari Meyer wrote: > > Hi, > > > > We've been trying to use VS Code Python type checkers to reduce errors, > and leverage Intellisense for code completion. We've been unable to get > these to work with PyQGIS and PyQT classes, for instance: > > > > image.png > > > > I believe I've traced the problem to some customized importing that's > used in places like the following: > > c:\OSGeo4W\apps\qgis-ltr\python\qgis\__init__.py > > c:\OSGeo4W\apps\qgis-ltr\python\qgis\core\__init__.py > > c:\OSGeo4W\apps\qgis-ltr\python\qgis\PyQt\Qt.py > > > > I then found that apparently similar techniques have caused the same > types of problems when using libraries like TensorFlow: > > > https://stackoverflow.com/questions/65271399/vs-code-pylance-pylint-cannot-resolve-import > < > https://stackoverflow.com/questions/65271399/vs-code-pylance-pylint-cannot-resolve-import > > > > https://github.com/PyCQA/pylint/issues/2603#issuecomment-541622729 < > https://github.com/PyCQA/pylint/issues/2603#issuecomment-541622729> > > > > The convoluted ways suggested to deal with these problems aren't really > that appealing. Does anyone have any suggestions for cleaner ways to > handle this? > > > > Are there reasons why QGIS has to be implemented like this? It's not > clear from the "monkey patching" comments whether these were temporary > workarounds or not. > > > > Thanks, > > Ari > > > > ___ > > 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] Buffer by Attribute Issue
Chris and list It is working for me now. Sorry, when I said lat/long I had meant the points were imported as Lat/Long EPSG:4326 from a text file. But subsequently projected to 3857. Example point in the project CRS ( EPSG:3857) -11923424,5461258 So I think I found the problem. Seems one workflow works and the other doesn't. You must select the Attribute Field from the field list and then edit the expression. This works. I thought I had tried it yesterday but suspect I didn't have the expression right. What I spent time with was using the Assistant dialog. That did not work. I was able to reproduce that it does not work. So the workflow that works is select the attribute Field and then go to Edit the Expression. I was unable to get it working using the Assistant dialog. thanks for the great help! Peter On Thu, Dec 16, 2021 at 2:50 PM chris hermansen wrote: > Peter and list > > On Thu, Dec 16, 2021 at 7:08 AM Peter Devanney wrote: > >> Chris >> >> The buffer input is a point the lat and long are Doubles. The buffer >> distance variable is a Double. Using EPSG 3857 for all. >> > > I just created a point shapefile in EPSG:3857, added a field called > "bufferdist", added three points with bufferdist set to 1000, 2000 and 5000 > respectively. > > EPSG:3857 is in metres, are readily visible and as far as I can tell from > measuring the buffers were correctly created in the correct size. > > In the buffer dialogue did you click on the button next to the distance / > units pair and next to "field type >" select your field, which would > deactivate the distance / units pair? > > Your mention of "lat and long" troubles me. EPSG:3857 is a projected > coordinate system, not a lat/lon system. > >> >> Not sure what the protocol on the list is or if it will accept a small 2 >> MB .mp4 but I can show what I am doing for workflow if that might help? >> >> thanks Chris >> >> Peter >> >> On Wed, Dec 15, 2021 at 6:42 PM chris hermansen >> wrote: >> >>> Peter and list, >>> >>> On Wed, Dec 15, 2021 at 7:26 AM Peter Devanney >>> wrote: >>> Hi Folks Have a table full of points that I want to buffer by a variable distance. The distance is an attribute in the input table in km. Using Vector>Geoprocessing>Buffer It works fine if I specify a fixed buffer. When I run it with the attribute selected it runs fine but it will not paint the buffers. At first I thought I had a unit issue so added an expression to multiply the attribute by 1000 to get to km from m as I wasn't sure if the default was m. The buffered output behaves totally normally so I can label, and zoom to features... All looks fine except no actual buffers draw. Symbology panel looks normal. Just wondering if anyone has seen this or knows of a workaround or thoughts on what I am doing wrong. What is the type of your buffer item? What are the typical values? >>> >>> What is your CRS? >>> >>> >>> -- >>> Chris Hermansen · clhermansen "at" gmail "dot" com >>> >>> C'est ma façon de parler. >>> >> > > -- > Chris Hermansen · clhermansen "at" gmail "dot" com > > C'est ma façon de parler. > ___ 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] Buffer by Attribute Issue
Peter and list On Thu, Dec 16, 2021 at 7:08 AM Peter Devanney wrote: > Chris > > The buffer input is a point the lat and long are Doubles. The buffer > distance variable is a Double. Using EPSG 3857 for all. > I just created a point shapefile in EPSG:3857, added a field called "bufferdist", added three points with bufferdist set to 1000, 2000 and 5000 respectively. EPSG:3857 is in metres, are readily visible and as far as I can tell from measuring the buffers were correctly created in the correct size. In the buffer dialogue did you click on the button next to the distance / units pair and next to "field type >" select your field, which would deactivate the distance / units pair? Your mention of "lat and long" troubles me. EPSG:3857 is a projected coordinate system, not a lat/lon system. > > Not sure what the protocol on the list is or if it will accept a small 2 > MB .mp4 but I can show what I am doing for workflow if that might help? > > thanks Chris > > Peter > > On Wed, Dec 15, 2021 at 6:42 PM chris hermansen > wrote: > >> Peter and list, >> >> On Wed, Dec 15, 2021 at 7:26 AM Peter Devanney wrote: >> >>> Hi Folks >>> >>> Have a table full of points that I want to buffer by a variable >>> distance. The distance is an attribute in the input table in km. >>> >>> Using Vector>Geoprocessing>Buffer It works fine if I specify a fixed >>> buffer. >>> >>> When I run it with the attribute selected it runs fine but it will not >>> paint the buffers. At first I thought I had a unit issue so added an >>> expression to multiply the attribute by 1000 to get to km from m as I >>> wasn't sure if the default was m. >>> >>> The buffered output behaves totally normally so I can label, and zoom to >>> features... All looks fine except no actual buffers draw. Symbology panel >>> looks normal. >>> >>> Just wondering if anyone has seen this or knows of a workaround or >>> thoughts on what I am doing wrong. >>> >>> What is the type of your buffer item? What are the typical values? >> >> What is your CRS? >> >> >> -- >> Chris Hermansen · clhermansen "at" gmail "dot" com >> >> C'est ma façon de parler. >> > -- Chris Hermansen · clhermansen "at" gmail "dot" com C'est ma façon de parler. ___ 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] Buffer by Attribute Issue
Example point in the project CRS ( EPSG:3857) -11923424,5461258 I have had the buffer problem with a GCS like but just usually convert to a UTM to do analysis. I was using a pseudo mercator here because the web maps are in that CRS and don't distort as a base map for a quick view of some data. Buffer works with a fixed distance specified in the Buffer dialog; but not when I try to use an attribute from the table as a buffer distance variable. thanks Peter On Thu, Dec 16, 2021 at 10:19 AM Richard Duivenvoorde wrote: > On 12/16/21 16:08, Peter Devanney wrote: > > Chris > > > > The buffer input is a point the lat and long are Doubles. The buffer > distance variable is a Double. Using EPSG 3857 for all. > > So your data is in lat/lon so in degrees? > Or in EPSG:3857 units (more or less meters)? > Can you show the coordinates of your point layer (also EPSG:3857 ?) > > What if you select/copy one point, does it look like (a point in NL) > > wkt_geom > Point (542953.32029126526322216 6792876.35233329329639673) > > or > > wkt_geom > Point (5.50943334180317645 52.15814766031191851) > > ? > > > > Not sure what the protocol on the list is or if it will accept a small 2 > MB .mp4 but I can show what I am doing for workflow if that might help? > > Nope, I think attachments > 75kB are removed or held back > > Regards, > > Richard > ___ 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] errore nel collegamento di due algoritmi di processing nello stesso script
Ciao Andrea e intanto grazie.
Faccio prima ad allegare tutto lo script.
Probabilmente adesso hai una visione d'insieme più chiara
In pratica lo script dovrebbe prendere un multilayer raster, convertire
tutte le bande in decibel e rifare lo stack
Non capisco perchè QGIS tenti di aggiungere vettoriali, dato che nello
script non sono contemplati layer vettoriali.
Di nuovo grazie
giacomo
Il giorno gio 16 dic 2021 alle ore 16:11 Andrea Giudiceandrea <
andreaer...@libero.it> ha scritto:
> Il 16/12/2021 14:42, Andrea Giudiceandrea ha scritto:
> > Comunque ho corretto gli errori e ho messo il tuo pezzo di script
> > all'interno di un algoritmo generico adattandolo per l'occorrenza e
> > aggiungendo quello che mancava, e non riscontro il problema da te
> > riscontrato e le operazioni vanno a buon fine senza che si tenti di
> > aggiungere layer inutili alla mappa.
>
> Ops.. mi correggo.
> Non riscontro l'errore:
> "I seguenti layer non sono stati generati correttamente
> • /tmp/processing_xWeKZC/c39d842bacba4a1a824e685ea21c8b5c/OUTPUT.tif
> Puoi verificare il "Pannello dei messaggi" nella finestra principale di
> QGIS per trovare maggiori informazioni circa l'esecuzione dell'algoritmo".
>
> Invece effettivamente riscontro gli avvisi "Warning" nel pannello OGR.
> Questi avvisi non sono però legati all'errore relativo al layer non
> generato correttamente.
> ___
> QGIS-it-user mailing list
> QGIS-it-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-it-user
>
def initAlgorithm(self, config=None):
# 3A Input stack
self.addParameter(QgsProcessingParameterRasterLayer(
self.INPUT,
self.tr('Input linear stack'),
None,
False))
# 3B Output raster
self.addParameter(QgsProcessingParameterRasterDestination(
self.OUTPUT,
self.tr('Output dB stack')))
#
# 4 - Import layers
#
# 4A
def processAlgorithm(
self,
parameters,
context,
feedback):
# 4B Input string
pathStackIn = self.parameterAsString(
parameters,
self.INPUT,
context)
# 4C Output stack
stackOut = self.parameterAsOutputLayer(
parameters,
self.OUTPUT,
context)
# -
# 5 - Check ---
# -
# 5A If source was not found, throw an exception
if pathStackIn is None:
raise QgsProcessingException(self.invalidSourceError(parameters, INPUT))
# 5B Check for cancelation
if feedback.isCanceled():
return {}
# -
# 6 -- Processing
# -
#6A deriving input stack
stackIn = QgsRasterLayer(pathStackIn, "stack")
# 6B loop over the bands
nBand = stackIn.bandCount()
bandList = []
for band in range(1, nBand+1):
# 6C db calculation
operation = "10 * ( log10 ( " + pathStackIn + "@" + str(band) + " ) )"
parametersCalc = {
"EXPRESSION": operation,
"LAYERS": stackIn,
"CELLSIZE": None,
"EXTENT": None,
"CRS": None,
"OUTPUT": "TEMPORARY_OUTPUT"}
# 6D
outRas = processing.run(
'qgis:rastercalculator',
parametersCalc,
is_child_algorithm = True,
context = context,
feedback = feedback)
# 6E
bandList.append(outRas["OUTPUT"])
# 6F Check for cancelation
if feedback.isCanceled():
return {}
# 6G stacking
parametersStack = {
"INPUT": bandList,
"PCT": False,
"SEPARATE": True,
"NODATA_INPUT": None,
"NODATA_OUTPUT": None,
"OPTIONS":"",
Re: [Qgis-user] Buffer by Attribute Issue
The list accepts, I think, 100kb, so you might want to dump your .mp4 somewhere else and post a link. EPSG 3857 is not the most clever CRS to work with, but that depends on your points locations and what you want to do with them. Am 16.12.21 um 16:08 schrieb Peter Devanney: Chris The buffer input is a point the lat and long are Doubles. The buffer distance variable is a Double. Using EPSG 3857 for all. Not sure what the protocol on the list is or if it will accept a small 2 MB .mp4 but I can show what I am doing for workflow if that might help? thanks Chris Peter On Wed, Dec 15, 2021 at 6:42 PM chris hermansen mailto:clherman...@gmail.com>> wrote: Peter and list, On Wed, Dec 15, 2021 at 7:26 AM Peter Devanney mailto:pe...@devanney.ca>> wrote: Hi Folks Have a table full of points that I want to buffer by a variable distance. The distance is an attribute in the input table in km. Using Vector>Geoprocessing>Buffer It works fine if I specify a fixed buffer. When I run it with the attribute selected it runs fine but it will not paint the buffers. At first I thought I had a unit issue so added an expression to multiply the attribute by 1000 to get to km from m as I wasn't sure if the default was m. The buffered output behaves totally normally so I can label, and zoom to features... All looks fine except no actual buffers draw. Symbology panel looks normal. Just wondering if anyone has seen this or knows of a workaround or thoughts on what I am doing wrong. What is the type of your buffer item? What are the typical values? What is your CRS? -- Chris Hermansen · clhermansen "at" gmail "dot" com C'est ma façon de parler. ___ 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] Buffer by Attribute Issue
On 12/16/21 16:08, Peter Devanney wrote: Chris The buffer input is a point the lat and long are Doubles. The buffer distance variable is a Double. Using EPSG 3857 for all. So your data is in lat/lon so in degrees? Or in EPSG:3857 units (more or less meters)? Can you show the coordinates of your point layer (also EPSG:3857 ?) What if you select/copy one point, does it look like (a point in NL) wkt_geom Point (542953.32029126526322216 6792876.35233329329639673) or wkt_geom Point (5.50943334180317645 52.15814766031191851) ? Not sure what the protocol on the list is or if it will accept a small 2 MB .mp4 but I can show what I am doing for workflow if that might help? Nope, I think attachments > 75kB are removed or held back Regards, Richard ___ 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] Buffer by Attribute Issue
Chris The buffer input is a point the lat and long are Doubles. The buffer distance variable is a Double. Using EPSG 3857 for all. Not sure what the protocol on the list is or if it will accept a small 2 MB .mp4 but I can show what I am doing for workflow if that might help? thanks Chris Peter On Wed, Dec 15, 2021 at 6:42 PM chris hermansen wrote: > Peter and list, > > On Wed, Dec 15, 2021 at 7:26 AM Peter Devanney wrote: > >> Hi Folks >> >> Have a table full of points that I want to buffer by a variable distance. >> The distance is an attribute in the input table in km. >> >> Using Vector>Geoprocessing>Buffer It works fine if I specify a fixed >> buffer. >> >> When I run it with the attribute selected it runs fine but it will not >> paint the buffers. At first I thought I had a unit issue so added an >> expression to multiply the attribute by 1000 to get to km from m as I >> wasn't sure if the default was m. >> >> The buffered output behaves totally normally so I can label, and zoom to >> features... All looks fine except no actual buffers draw. Symbology panel >> looks normal. >> >> Just wondering if anyone has seen this or knows of a workaround or >> thoughts on what I am doing wrong. >> >> What is the type of your buffer item? What are the typical values? > > What is your CRS? > > > -- > Chris Hermansen · clhermansen "at" gmail "dot" com > > C'est ma façon de parler. > ___ 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] 'developmet'
Hi everybody, Maybe you can do something with this... I already send an email to https://srtm.csi.cgiar.org/ Where: https://srtm.csi.cgiar.org/contact-us/ What: Sadir Mohideen CSI-CGIAR Chief GeoNetwork Technologist / Senior Web Applications Developmet Specialist ___ 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] errore nel collegamento di due algoritmi di processing nello stesso script
Ciao Andrea
questo è quello che viene mostrato alla fine dell'esecuzione dello script
(che fornisce comunque un risultato perfetto)
-
Versione di QGIS: 3.22.1-Białowieża
Revisione codice QGIS: 663dcf8fb9
Versione di Qt: 5.12.8
Versione Python: 3.8.10
Versione di GDAL: 3.0.4
Versione di GEOS: 3.8.0-CAPI-1.13.1
Versione di PROJ: Rel. 6.3.1, February 10th, 2020
versione di PDAL: 2.0.1 (git-version: Release)
Algoritmo iniziato alle: 2021-12-16T09:58:16
In avvio l'algoritmo 'Linear to dB' …
Parametri in ingresso:
{ 'INPUT' :
'/home/giacomo/Desktop/PP_esperimenti/4_PP_2020_I_r_stacks/I_HH_2020_stack.tif',
'OUTPUT' : 'TEMPORARY_OUTPUT' }
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/fc597f3178ca47e0b543c5a0936576a0/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/de653b67e79c43bf8589946c5ee972f0/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/8908d2eb383a4dba81bae9d61fba4887/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/f5dbf29e85ed4d61b73c417e84787653/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/59d7c1a8c19e405280b2384191248824/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/7a75cb2ae2ed46128826678140a94543/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/06ed438e78094c7c94a6e289715af4de/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/feebae37ea0d44389da6599c9d317759/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/519d926faa68436ab444e9b0faf302d8/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/471d544d7e4d401480c5baa5a30774ef/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/47657e7e6aee481692f119ba7d3fd995/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/81e912a8859742f998f8f54ea14a0ee1/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/730cd07bea554ab8ad3370f725afc92b/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/acf1afaf4f76438696c86eac2843aa15/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/c7c4e07db59f4d38bc9d2d06a4f64fda/OUTPUT.tif'}
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/2e1d47d229c64db793c9d5e40cedba6b/OUTPUT.tif'}
Comando GDAL:
gdal_merge.py -separate -ot Float32 -of GTiff -o
/tmp/processing_xWeKZC/3983ace422504502b50b4df7d55b2d28/OUTPUT.tif
--optfile
/tmp/processing_xWeKZC/cd92fe92f4ab411eae2322cb9ed5bbc7/mergeInputFiles.txt
Risultato comando GDAL:
0...10...20...30...40...50...60...70...80...90...100 - done.
Processo completato con successo.
Risultati: {'OUTPUT':
'/tmp/processing_xWeKZC/3983ace422504502b50b4df7d55b2d28/OUTPUT.tif'}
Execution completed in 2.78 secondi
Risultati:
{'OUTPUT':
'/tmp/processing_xWeKZC/3983ace422504502b50b4df7d55b2d28/OUTPUT.tif'}
Caricamento layer
I seguenti layer non sono stati generati correttamente
• /tmp/processing_xWeKZC/c39d842bacba4a1a824e685ea21c8b5c/OUTPUT.tif
Puoi verificare il "Pannello dei messaggi" nella finestra principale di
QGIS per trovare maggiori informazioni circa l'esecuzione dell'algoritmo
-
Nel "Pannello dei Messaggi" non viene scritto niente, ma guardando nel
pannello dei Log, più precisamente nel pannello OGR, appare questo messaggio
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/fc597f3178ca47e0b543c5a0936576a0/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/de653b67e79c43bf8589946c5ee972f0/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/8908d2eb383a4dba81bae9d61fba4887/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/f5dbf29e85ed4d61b73c417e84787653/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/59d7c1a8c19e405280b2384191248824/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/7a75cb2ae2ed46128826678140a94543/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/06ed438e78094c7c94a6e289715af4de/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/feebae37ea0d44389da6599c9d317759/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/519d926faa68436ab444e9b0faf302d8/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/471d544d7e4d401480c5baa5a30774ef/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
/tmp/processing_xWeKZC/47657e7e6aee481692f119ba7d3fd995/OUTPUT.tif ().()
2021-12-16T09:58:19 WARNINGImpossibile aprire
