Re: [Qgis-developer] master slow reading rasters?
Il 22/03/2014 13:59, Luca Lanteri ha scritto: I had the same problem on a old version od qgis using large raster with rotation parameter into the tfw file. May be the same issue? Il 21/mar/2014 09:30 Paolo Cavallini cavall...@faunalia.it mailto:cavall...@faunalia.it ha scritto: Il 20/03/2014 18:28, Giovanni Manghi ha scritto: yes, apparently it depends on the size of the raster (I'm trying with pretty large ones) how much large? I'm testing with 9gb rasters and it is lighting fast (just fast wothout overviews). 3Gb Perhaps this has something to do with colour table? This is what I use for testing: http://rmgsc.cr.usgs.gov/outgoing/ecosystems/AfricaData/ 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
[Qgis-developer] Code Sprint agenda
Hi all. This is my agenda for the just started Code Sprint (AKA HackFest): * better management of sponsor and donor lists * translation of lizmap * setup a procedure for a more reliable and timely plugin approval * help implementing the repository for symbols * help improving course material: manual, data, Python examples. Anyone willing to collaborate on this, either in presence or remotely, is welcome. 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
[Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers
Hi QGIS-Processing (former Sextante) has open tickets on two bugtrackers: - the plugin bug tracker, built when it was a plugin, but with a lot of active tickets - http://hub.qgis.org/projects/sextante/activity - the main bug tracker with a few open tickets - http://hub.qgis.org/projects/quantum-gis/issues I understand those two can't be merged in one go, because the plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing GRASS GIS etc) that don't fit in the main bug tracker. But this should be solved ASAP, because the current situation is quite confusing Regards F. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers
Hi, I raised this issue twice some time ago, see [0, 1]. Also if I'm not wrong same issue was raised by Paolo too. [0] http://lists.osgeo.org/pipermail/qgis-developer/2013-August/027973.html [1] http://lists.osgeo.org/pipermail/qgis-developer/2013-September/028585.html 2014-03-24 14:10 GMT+02:00 Filipe Dias filipesd...@gmail.com: Hi QGIS-Processing (former Sextante) has open tickets on two bugtrackers: - the plugin bug tracker, built when it was a plugin, but with a lot of active tickets - http://hub.qgis.org/projects/sextante/activity - the main bug tracker with a few open tickets - http://hub.qgis.org/projects/quantum-gis/issues I understand those two can't be merged in one go, because the plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing GRASS GIS etc) that don't fit in the main bug tracker. But this should be solved ASAP, because the current situation is quite confusing Regards F. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] missing setColorShadingAlgorithm for QgsRasterLayer
Hello to everyone, i'm new to this mailinglist!
I've ha question about QGIS 2.2.0 API.
I've developed a qgis plugin in python for version 1.8 and now i'm
rewriting it for 2.2.0 version; i've encountered a problem:
i've defined a raster layer with QgsRasterLayer, eg.
rasterLayer = QgsRasterLayer(fileName, fileBaseName)
and i've defined a drawing style (with new rules of 2.2.0 APIs)
rasterLayer.setDrawingStyle('SingleBandPseudoColor')
So i need to define a color shading algorithm, in the same way that i used
with 1.8 version
rasterLayer.setColorShadingAlgorithm(QgsRasterLayer.PseudoColorShader)
but i see there's not
setColorShadingAlgorithm()
in new API
Someone can help me to find a way to define it?
Thanks in advance
Nicola
--
*http://www.nicolastella.it
http://www.nicolastella.iti...@nicolastella.it i...@nicolastella.it*
*nicolastel...@gmail.com* nicolastel...@gmail.com
..Innovation has nothing to do with how many RD dollars you have.It's not
about money. It's about the people you have, how you're led, and how much
you get it...
Steve Jobs
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers
On 03/24/2014 05:10 AM, Filipe Dias wrote: Hi QGIS-Processing (former Sextante) has open tickets on two bugtrackers: - the plugin bug tracker, built when it was a plugin, but with a lot of active tickets - http://hub.qgis.org/projects/sextante/activity - the main bug tracker with a few open tickets - http://hub.qgis.org/projects/quantum-gis/issues I understand those two can't be merged in one go, because the plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing GRASS GIS etc) that don't fit in the main bug tracker. But this should be solved ASAP, because the current situation is quite confusing Regards F. I'm of the opinion that the tracker should continue to be the Plugin tracker, not the main QGIS tracker. So I'd propse moving any Sextante/Processing tickets from the main or linking them into the Plugin tracker. To me it's still a plugin, just a core plugin but big enough that it's really a subproject. If we wanted to move the Plugin tracker as a sub-project of QGIS that would also make sense. Also Processing bugs aside from Processing not loading aren't showstoppers for release. Thanks, Alex ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Problems editing WFS in QGIS
Hi Scott, I have discovered this issue next week and I'm working on a bugfix. I hope to propose a patch or a pull request tomorrow. I'd like to see this fix backported. Regards Le 24 mars 2014 14:58, Scott Clark sct...@gmail.com a écrit : Upon further investigation it appears that WFS authentication is broken. Further testing shows that the Add WFS dialog does not display layers that require basic auth - even when the login is supplied. It will only show the public layers. Note that the WMS auth works great for me. When you try to edit a WFS-T, I believe it is also failing to use the supplied login info. Which results in the error I'm seeing below. I've added the additional details to the existing bug at http://hub.qgis.org/issues/9234 Since this makes WFS of very limited use, is this planned to be fixed in an up-coming release? I'll happily be a tester for this! Scott Scott Clark wrote: I've been having no success using the digitizing toolbar with WFS-T. I'm using QGIS 2.2.0 with a GeoServer 2.4. The layers are displaying fine when added through the Add WFS dialog, and the editing UI is functional. However, on save, it fails (after freezing up QGIS for a minute or so) with the following message: Could not commit changes to layer geonode:incidentes_copeco Errors: ERROR: 1 feature(s) not added. Provider errors: unhandled response: html It's not specific to these layers and it fails on all of the layers I pick. I've successfully tested editing using WFS-T on this particular server using both our OL3 and our mobile client. Any ideas on workarounds or what might be going wrong? Thanks, Scott ___ 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] Problems editing WFS in QGIS
Excellent news and many thanks! René-Luc D'Hont wrote: Hi Scott, I have discovered this issue next week and I'm working on a bugfix. I hope to propose a patch or a pull request tomorrow. I'd like to see this fix backported. Regards Le 24 mars 2014 14:58, Scott Clark sct...@gmail.com mailto:sct...@gmail.com a écrit : Upon further investigation it appears that WFS authentication is broken. Further testing shows that the Add WFS dialog does not display layers that require basic auth - even when the login is supplied. It will only show the public layers. Note that the WMS auth works great for me. When you try to edit a WFS-T, I believe it is also failing to use the supplied login info. Which results in the error I'm seeing below. I've added the additional details to the existing bug at http://hub.qgis.org/issues/9234 Since this makes WFS of very limited use, is this planned to be fixed in an up-coming release? I'll happily be a tester for this! Scott Scott Clark wrote: I've been having no success using the digitizing toolbar with WFS-T. I'm using QGIS 2.2.0 with a GeoServer 2.4. The layers are displaying fine when added through the Add WFS dialog, and the editing UI is functional. However, on save, it fails (after freezing up QGIS for a minute or so) with the following message: Could not commit changes to layer geonode:incidentes_copeco Errors: ERROR: 1 feature(s) not added. Provider errors: unhandled response: html It's not specific to these layers and it fails on all of the layers I pick. I've successfully tested editing using WFS-T on this particular server using both our OL3 and our mobile client. Any ideas on workarounds or what might be going wrong? Thanks, Scott ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org mailto: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-Processing (former Sextante) has two bug trackers
Hi I think Processing tickets should be in the main bug tracker, since GDAL tools, fTools and Grass plugin tickets are also there. Also, Qgis-Processing is a really big (and great) feature, that interests a lot of users, so it makes sense to keep its tickets in the main tracker. Regards F. On Mon, Mar 24, 2014 at 6:02 PM, Alex Mandel tech_...@wildintellect.comwrote: On 03/24/2014 05:10 AM, Filipe Dias wrote: Hi QGIS-Processing (former Sextante) has open tickets on two bugtrackers: - the plugin bug tracker, built when it was a plugin, but with a lot of active tickets - http://hub.qgis.org/projects/sextante/activity - the main bug tracker with a few open tickets - http://hub.qgis.org/projects/quantum-gis/issues I understand those two can't be merged in one go, because the plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing GRASS GIS etc) that don't fit in the main bug tracker. But this should be solved ASAP, because the current situation is quite confusing Regards F. I'm of the opinion that the tracker should continue to be the Plugin tracker, not the main QGIS tracker. So I'd propse moving any Sextante/Processing tickets from the main or linking them into the Plugin tracker. To me it's still a plugin, just a core plugin but big enough that it's really a subproject. If we wanted to move the Plugin tracker as a sub-project of QGIS that would also make sense. Also Processing bugs aside from Processing not loading aren't showstoppers for release. Thanks, Alex ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-Processing (former Sextante) has two bug trackers
As a sub-project, it would show up in queries of the main QGIS ticket system, but at the same time be able to have it's own internal categories. This to me seems the best compromise. It's really a big plugin with a myriad of backends. That complexity is what makes it a little different from the others mentioned. The others mentioned could be sub-projects of the main QGIS too. In reality all of them are core plugins, but they are still plugins. None of them are required to make QGIS work (boot). Hence they each have their own category. The challenge here is Processing/Sextante(I always call it by both since I do the the possibility of Processing stuff that isn't sextante) needs it's own categories/sub-categories. Also it's really easy for use to try moving it to be a subproject and then reassess (Takes about 30 seconds to move it). If it's still not right then we can talk about how to move tickets. Thanks, Alex On 03/24/2014 12:05 PM, Filipe Dias wrote: Hi I think Processing tickets should be in the main bug tracker, since GDAL tools, fTools and Grass plugin tickets are also there. Also, Qgis-Processing is a really big (and great) feature, that interests a lot of users, so it makes sense to keep its tickets in the main tracker. Regards F. On Mon, Mar 24, 2014 at 6:02 PM, Alex Mandel tech_...@wildintellect.comwrote: On 03/24/2014 05:10 AM, Filipe Dias wrote: Hi QGIS-Processing (former Sextante) has open tickets on two bugtrackers: - the plugin bug tracker, built when it was a plugin, but with a lot of active tickets - http://hub.qgis.org/projects/sextante/activity - the main bug tracker with a few open tickets - http://hub.qgis.org/projects/quantum-gis/issues I understand those two can't be merged in one go, because the plugin-bugtracker has categories (QGIS-Processing SAGA GIS, QGIS-Processing GRASS GIS etc) that don't fit in the main bug tracker. But this should be solved ASAP, because the current situation is quite confusing Regards F. I'm of the opinion that the tracker should continue to be the Plugin tracker, not the main QGIS tracker. So I'd propse moving any Sextante/Processing tickets from the main or linking them into the Plugin tracker. To me it's still a plugin, just a core plugin but big enough that it's really a subproject. If we wanted to move the Plugin tracker as a sub-project of QGIS that would also make sense. Also Processing bugs aside from Processing not loading aren't showstoppers for release. Thanks, Alex ___ 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] Plugin [399] Digital Number 2 NBR approval notification.
Plugin Digital Number 2 NBR approval by pcav. The plugin version [399] Digital Number 2 NBR 0.1 Experimental is now approved Link: http://plugins.qgis.org/plugins/Dn2Nbr/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [47] QSpatiaLite approval notification.
Plugin QSpatiaLite approval by pcav. The plugin version [47] QSpatiaLite 7.0.1 is now approved Link: http://plugins.qgis.org/plugins/QspatiaLite/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [398] Vertices Counter approval notification.
Plugin Vertices Counter approval by pcav. The plugin version [398] Vertices Counter 1.1 is now approved Link: http://plugins.qgis.org/plugins/Vertices_Counter/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [420] Video UAV Tracker approval notification.
Plugin Video UAV Tracker approval by pcav. The plugin version [420] Video UAV Tracker 1.2.2 is now approved Link: http://plugins.qgis.org/plugins/Video_UAV_Tracker/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [420] Video UAV Tracker approval notification.
Plugin Video UAV Tracker approval by pcav. The plugin version [420] Video UAV Tracker 1.2.1 is now approved Link: http://plugins.qgis.org/plugins/Video_UAV_Tracker/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [420] Video UAV Tracker approval notification.
Plugin Video UAV Tracker approval by pcav. The plugin version [420] Video UAV Tracker 1.2.2.1 is now approved Link: http://plugins.qgis.org/plugins/Video_UAV_Tracker/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [420] Video UAV Tracker approval notification.
Plugin Video UAV Tracker approval by pcav. The plugin version [420] Video UAV Tracker 1.2.3 is now approved Link: http://plugins.qgis.org/plugins/Video_UAV_Tracker/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [440] Viewshed Analysis approval notification.
Plugin Viewshed Analysis approval by pcav. The plugin version [440] Viewshed Analysis 0.1 Experimental is now approved Link: http://plugins.qgis.org/plugins/ViewshedAnalysis/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Cleaning up the plugin queue
Hi all. After a short talk with Richard, I feel it is important to clean up the unapproved plugin queue: we had about 40 plugins, some from 2012. I'm writing the authors to ask for missing info, then I approve/unapprove as I believe it is best for the project. Of course I may be wrong, please forgive me: I think it is better to approve a less than perfect plugin than leave dozens of potentially good ones in the shade, and frustrate their authors and potential users. Any suggestion and feedback welcome. -- 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
[Qgis-developer] Plugin [387] Processing approval notification.
Plugin Processing approval by pcav. The plugin version [387] Processing 2.-20131120 Experimental is now approved Link: http://plugins.qgis.org/plugins/processing/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [416] SelectPlusFR approval notification.
Plugin SelectPlusFR approval by pcav. The plugin version [416] SelectPlusFR 2.0.4 Experimental is now approved Link: http://plugins.qgis.org/plugins/selectplus/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [416] SelectPlusFR approval notification.
Plugin SelectPlusFR approval by pcav. The plugin version [416] SelectPlusFR 2.0.5 is now approved Link: http://plugins.qgis.org/plugins/selectplus/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [416] SelectPlusFR approval notification.
Plugin SelectPlusFR approval by pcav. The plugin version [416] SelectPlusFR 2.0.6 is now approved Link: http://plugins.qgis.org/plugins/selectplus/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [437] Toporobot Importer approval notification.
Plugin Toporobot Importer approval by pcav. The plugin version [437] Toporobot Importer 0.2.3 is now approved Link: http://plugins.qgis.org/plugins/ToporobotImporter/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [437] Toporobot Importer approval notification.
Plugin Toporobot Importer approval by pcav. The plugin version [437] Toporobot Importer 0.2.4 is now approved Link: http://plugins.qgis.org/plugins/ToporobotImporter/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [408] shptoobs approval notification.
Plugin shptoobs approval by pcav. The plugin version [408] shptoobs 0.1.1 Experimental is now approved Link: http://plugins.qgis.org/plugins/shp_to_obs/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [408] shptoobs approval notification.
Plugin shptoobs approval by pcav. The plugin version [408] shptoobs 0.1.2 Experimental is now approved Link: http://plugins.qgis.org/plugins/shp_to_obs/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [474] Drone Planner approval notification.
Plugin Drone Planner approval by pcav. The plugin version [474] Drone Planner 0.1 is now approved Link: http://plugins.qgis.org/plugins/DronePlanner/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Plugin [422] teamqgis approval notification.
Plugin teamqgis approval by pcav. The plugin version [422] teamqgis 0.1 is now approved Link: http://plugins.qgis.org/plugins/teamqgis/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Cleaning up the plugin queue
Il 24/03/2014 22:34, Alex Mandel ha scritto: I understood the intent of approval process was to prevent distribution of malicious code, spam and other nefarious purposes. yes, this is also the spirit with which I am revising them now. You'll notice a spur of new plugins: please install and test them, and promptly report any issues. 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] processing.runalg() issue with grass algorithms
Oops, my mistake. I have ##lrm=output raster in the header, but lpf = ... Is the only line in my code. I don't get the error message after changing lrm to lpf in the header. I do get another error message, but I think I broke my processing by trying to force an update. I'll test it tomorrow. Sorry about the confusion! Eric On Mar 22, 2014 5:06 PM, Eric Goddard egoddard1...@gmail.com wrote: Ah, I didn't know a file could he specified without a path. Thanks for the clarification! On Mar 22, 2014 4:37 PM, Victor Olaya vola...@gmail.com wrote: If I run the same line in the python console, it works correctly: radius = 4 lpf = processing.runalg(saga:simplefilter, SR_50M_alaska_nad, 0, 0, radius, None) processing.load(lpf['RESULT']) Results in the map being loaded. Not sure why this is happening. I will try to reproduce the error and see if it can be fixed Thanks for the report Also, if I change the output folder in the processing settings to a different location (in this case, tmp/processing in my home folder) and run another algorithm in the python console, the RESULT key still points to /tmp/processing/... This is not a bug. If you do not enter a filename, the output will always go to a temporary file. The output folder that yu can set in the settings is the folder to be used when you enter a filename without a path (like myfile.shp, but not /home/myuser/myfile.shp), not the folder to use for temporary files. Thanks again! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
