Re: [Qgis-developer] QGIS TMS provider?
There is already a simple TMS driver in GDAL [1], it would be easiest to make a wrapper/plugin that uses this wms mini-driver instead of writing from scratch, as was done for the following plugins. If you are talking about my Load TMS layer plugin [2] that I discussed a few weeks ago, I have not released it because some TMS services cannot be used legally, so it is not as useful as I thought initially. There is also the TileMapScaleLevels plugin [3] which was not approved for similar reasons, but it seems that the offending code has been removed from the github repos. Perhaps you could check both out and give your feedback. regards, Etienne [1] http://www.gdal.org/frmt_wms.html [2] https://github.com/etiennesky/loadtmslayer [3] https://github.com/datalyze-solutions/TileMapScaleLevels On Mon, Jul 7, 2014 at 10:14 AM, Alexander Bruy alexander.b...@gmail.com wrote: Hi all, TMS (Tile Map Service) is an easy way to work with different tiled maps. It can be used to access local or remote maps. We already have great OpenLayers plugin that provides access to some popular maps like Google or OSM. There is also Load TMS Layer plugin that allows to load some TMS maps in QGIS. But both this plugins are limited only to predefined servers/maps, users can't add new services without some handwork. For OpenLayers plugin it is necessary to create corresponding HTML/CSS files, for Load TMS Layer — write service definition in XML format. Does it makes sense to develop TMS provider for QGIS (native or GDAL-based) to allow users create connections to different services and/or local tilesets? Comments and opinions are welcome. -- Alexander Bruy ___ 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] Openlayers plugin support in QGIS 2.4
You cannot use the google maps TMS service, it is not allowed under the Google Maps TOS. On Mon, Jul 7, 2014 at 4:54 AM, René-Luc Dhont rldh...@gmail.com wrote: Hi Ali, You'll find examples here : http://www.gdal.org/frmt_wms.html Remember that using Google Maps needs to accept the Google licence. Regards René-Luc Le 07/07/2014 09:42, Aamir Ali a écrit : Thanks for your prompt response I need to call google maps, how can I use TMS service to call the tiles from Google Map. Regards Ali On Mon, Jul 7, 2014 at 11:53 AM, René-Luc Dhont rldh...@gmail.com wrote: Hi Ali, You can use this method instead of OpenLayers Plugin : Using Map Tile Servers in QGIS 2.4 http://www.konstantingreger.net/using-map-tile-servers-in-qgis-2-4/ Based on : How to display OpenStreetMap data tiles with no plugin inside Qgis http://www.3liz.com/blog/rldhont/index.php?post/2012/ 07/17/OpenStreetMap-Tiles-in-QGIS Regards, René-Luc D'Hont Le 07/07/2014 07:38, Aamir Ali a écrit : Dear All I am using QGIS 2.4 built using qgis source code and qt creator in ubuntu. I am unable to find openlayers plugin in the list of plugin repository. I have a two questions 1. Whether it is not compatible with this version or my build has some problems? 2. If its not compatible then how long it will take the community to release the compatible version? Aamir Ali ___ 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 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] lack of zip_decoder in PIL with Windows 64bits installer
It would be useful if you can file a bug report for this problem. On Tue, Jul 1, 2014 at 5:23 AM, Arnaud Morvan arnaud.mor...@camptocamp.com wrote: I've meet problems to open PNG files with PIL from plugin on with windows 64 bits version of QGIS standalone installer I don't have zip_decoder in binary _image.pyd (same problem on 2.2 and 2.4) A workaround is to overwrite PIL in QGIS folder with files from PIL standalone installer I've printed methods PIL.Image.core.*_decoder on QGIS 2.4 64bits: bit_decoder fli_decoder gif_decoder hex_decoder msp_decoder packbits_decoder pcd_decoder pcx_decoder raw_decoder sun_rle_decoder tga_rle_decoder tiff_lzw_decoder xbm_decoder on QGIS 2.2 32bits: bit_decoder fli_decoder gif_decoder hex_decoder jpeg_decoder msp_decoder packbits_decoder pcd_decoder pcx_decoder raw_decoder sun_rle_decoder tga_rle_decoder tiff_lzw_decoder xbm_decoder zip_decoder Arnaud ___ 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] lack of zip_decoder in PIL with Windows 64bits installer
Hi, is the standalone installer based on osgeo4w? On Tue, Jul 1, 2014 at 5:46 PM, Jürgen E. j...@norbit.de wrote: Hi Etienne, On Tue, 01. Jul 2014 at 17:32:25 -0300, Etienne Tourigny wrote: It would be useful if you can file a bug report for this problem. if anywhere on OSGeo4W. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS PSC member (RM) Germany IRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ 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] SOSI support in QGIS
If SOSI is available in the Raster file open dialog, it is because gdal has support for SOSI. If a particular SOSI file cannot be opened, then it is a GDAL bug, not a QGIS one, and should be reported in the GDAL bugtracker. On Fri, Jun 27, 2014 at 11:18 AM, Blumentrath, Stefan stefan.blumentr...@nina.no wrote: Hi Larry, Thanks for your efforts. I understand that you are especially busy right now… I checked GDAL_DRIVER_PATH and it was - just as you suspected for OSGeo4W – set properly to “C:\OSGeo4W\bin\gdalplugins”. Just like in James case, SOSI is listed in the combo-box in QGIS and I get the dialog for selecting among the three layers in the file. When I try to load one of them I get the “Invalid data source” error message. GDAL in the same OSGeo4W installation reads and converts the SOSI file without any issues. However, I noticed that GDAL was also less picky with the versions. While the SOSI plugin compiled against GDAL 1.10 does not show up in QGIS 2.3 (build against GDAL 1.11), GDAL 1.11 itself has no problems with that plugin either. Maybe some subtle differences in compiler settings between Jürgens build of GDAL and my build of the SOSI-plugin may cause the problems here? I assume you use same compiler for GDAL and QGIS on Mac (like I do on Ubuntu)… When I built the SOSI plugin I tried to follow packaging instructions closely. I used MS Visual Studio Express 2010 (compiler toolset v100) for the 32bit build (SDK 7.1 for the 64bit build), set MSVC_VER=1600 in GDALs nmake.opt, added SOSI support and kept default settings in the other cases. Cheers Stefan *From:* la...@shafferinteractive.com [mailto:la...@shafferinteractive.com] *On Behalf Of *Larry Shaffer *Sent:* 27. juni 2014 13:02 *To:* Blumentrath, Stefan *Cc:* Stott, James; qgis-developer@lists.osgeo.org *Subject:* Re: [Qgis-developer] SOSI support in QGIS Hi, Hmm. I had no issues opening that file up on Mac [0]. The only other thing I can think of is to ensure the GDAL_DRIVER_PATH is set in the environment, so the plugins can be found at run-time by QGIS/GDAL. I don't think that should be an issue for an OSGeo4W install, though. To be sure, you can try setting it in Options - System - Environment and see if that helps. If the plugin wasn't found by GDAL, then the file filter for SOSI would not show up in QGIS's file browse dialog's combobox for opening a vector layer. If you choose *.* (all files) and try to load a .sos file, then it will throw the invalid source error in the message bar, because GDAL never loaded the plugin. Sorry, won't have time to test on any other platforms for a couple of days. [0] http://drive.dakotacarto.com/qgis/sosi-file-load.png Regards, Larry On Fri, Jun 27, 2014 at 3:50 AM, Blumentrath, Stefan stefan.blumentr...@nina.no wrote: Hi Larry, Tanks for having a look at this. I shall send you the file off-list… Cheers Stefan *From:* la...@shafferinteractive.com [mailto:la...@shafferinteractive.com] *On Behalf Of *Larry Shaffer *Sent:* 27. juni 2014 11:37 *To:* Blumentrath, Stefan *Cc:* Stott, James; qgis-developer@lists.osgeo.org *Subject:* Re: [Qgis-developer] SOSI support in QGIS Hi James, Can you share the dataset from Miljødirektoratet that you are testing? I can't get Google to translate the pages to English. Regards, Larry On Fri, Jun 27, 2014 at 2:43 AM, Blumentrath, Stefan stefan.blumentr...@nina.no wrote: So it Works for Mac and Linux users? Yes, seems to work there. Does this work with the installer download of QGIS for Windows? I havent actually tried that. I doubt it, since the installer is also built based on OSGeo4W, if I am not mistaken. Is it possible to drop it for just Windows users? No idea. Any developer / packager who would be willing to help us tracing down the problem on Win? Since a fix would be the best solution... I just think we will end up with a lot of users (especially as Windows will possbily be the most used platform) who will get frustrated that they cant open these files despite it looking like they should be able to. Better to wait until 2.6 in my opinion. This is a shame as we now have a nearly complete Norwegian translation in place for 2.4, so SOSI support and a translation are two very good arguements for adopting QGIS here. I see your point... Cheers Stefan ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Value Tool disabled when another tool selected
I have implemented this to be able to identify on a mouse click instead of whenever you move the mouse (this is an optional behaviour). This requires the tool being a map tool, and you cannot have more than one active map tool. However, when the mouse click option is not enabled, it is NOT used as a map tool therefore it should not be deactivate when another map tool is used. If you uncheck that option (first in the Options dialog) and you still get that behavior it is a bug, and you should file a bug report (I can't reproduce with qgis 2.2). Default is this option turned off, so if you didn't change the option yourself that would be a bug also. Etienne On Fri, Jun 6, 2014 at 1:47 PM, Jamie Adams jaad...@gmail.com wrote: I've noticed the new version of the Value Tool plugin (0.8.4) automatically have the Enable button unchecked when another tool is selected. What is the rationale for this change? I draw polygons on top of raster files to be used during post processing and need the raster values for reference. This change breaks that functionality. I'm running QGIS 2.2 on Ubuntu 14.04. Thanks, Jamie ___ 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] Value Tool disabled when another tool selected
I actually fixed this last month, and forgot to upload a new version. I've been busy finishing my PhD the last few months which explains this! I have just uploaded version 0.8.5 to the plugin repos. Etienne On Fri, Jun 6, 2014 at 5:15 PM, Jamie Adams jaad...@gmail.com wrote: Ok, thanks. I filed a bug for this: http://hub.qgis.org/issues/10490 On Fri, Jun 6, 2014 at 11:27 AM, Etienne Tourigny etourigny@gmail.com wrote: I have implemented this to be able to identify on a mouse click instead of whenever you move the mouse (this is an optional behaviour). This requires the tool being a map tool, and you cannot have more than one active map tool. However, when the mouse click option is not enabled, it is NOT used as a map tool therefore it should not be deactivate when another map tool is used. If you uncheck that option (first in the Options dialog) and you still get that behavior it is a bug, and you should file a bug report (I can't reproduce with qgis 2.2). Default is this option turned off, so if you didn't change the option yourself that would be a bug also. Etienne On Fri, Jun 6, 2014 at 1:47 PM, Jamie Adams jaad...@gmail.com wrote: I've noticed the new version of the Value Tool plugin (0.8.4) automatically have the Enable button unchecked when another tool is selected. What is the rationale for this change? I draw polygons on top of raster files to be used during post processing and need the raster values for reference. This change breaks that functionality. I'm running QGIS 2.2 on Ubuntu 14.04. Thanks, Jamie ___ 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] Legend refactoring branch merged
On Wed, May 21, 2014 at 3:46 PM, Etienne Tourigny etourigny@gmail.comwrote: A quick test revealed that layer actions added via QgsLegendInterface::addLegendLayerAction() and addLegendLayerActionForLayer() do not show up in the context menu any more. Should the corresponding members be added to QgsLayerTreeLayer class? I mean QgsLayerTreeRegistryBridge class and adding the menus in QgsAppLayerTreeViewMenuProvider::createContextMenu() cheers Etienne On Wed, May 21, 2014 at 3:03 PM, Rouzaud Denis denis.rouz...@gmail.comwrote: Congratulations for this big cleanup! I am really glad we (SIGE) could help this project to come true. On 21 May 2014, at 19:11, Martin Dobias wonder...@gmail.com wrote: Hi everyone I have just merged the first part of the legend refactoring work to master [1]. It does not really bring any new features for the end user, the changes are mainly under the hood. Things should ideally work as before, if not then probably it is a bug. There will be second part of the work related mainly around improved layer symbology display in legend, more interactive legend and more options for customization. At Lutra Consulting we are still looking for funders willing to co-fund the work. At this point let me thank SIGE and Swiss QGIS User Group for supporting the project. Please test thoroughly - the legend has received quite a lot of features over time, so there could be still some minor features I have missed to port to new implementation. The format of the project file has changed, but there is backward compatibility with older projects which should allow seamless transition. Once saved with 2.4, the older versions of QGIS will loose the information about grouping. If you are interested in studying the new code, there are two new folders of interest: - src/core/layertree - src/gui/layertree There is basic doxygen documentation for the new core classes, I plan to add more, add python bindings and unit tests. Regards Martin [1] https://github.com/qgis/QGIS/commit/b2a4c765b4e8a3fa00385a56a358952f46a1957a ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Legend refactoring branch merged
On Wed, May 21, 2014 at 3:46 PM, Etienne Tourigny etourigny@gmail.comwrote: A quick test revealed that layer actions added via QgsLegendInterface::addLegendLayerAction() and addLegendLayerActionForLayer() do not show up in the context menu any more. Should the corresponding members be added to QgsLayerTreeLayer class? cheers Etienne On Wed, May 21, 2014 at 3:03 PM, Rouzaud Denis denis.rouz...@gmail.comwrote: Congratulations for this big cleanup! I am really glad we (SIGE) could help this project to come true. On 21 May 2014, at 19:11, Martin Dobias wonder...@gmail.com wrote: Hi everyone I have just merged the first part of the legend refactoring work to master [1]. It does not really bring any new features for the end user, the changes are mainly under the hood. Things should ideally work as before, if not then probably it is a bug. There will be second part of the work related mainly around improved layer symbology display in legend, more interactive legend and more options for customization. At Lutra Consulting we are still looking for funders willing to co-fund the work. At this point let me thank SIGE and Swiss QGIS User Group for supporting the project. Please test thoroughly - the legend has received quite a lot of features over time, so there could be still some minor features I have missed to port to new implementation. The format of the project file has changed, but there is backward compatibility with older projects which should allow seamless transition. Once saved with 2.4, the older versions of QGIS will loose the information about grouping. If you are interested in studying the new code, there are two new folders of interest: - src/core/layertree - src/gui/layertree There is basic doxygen documentation for the new core classes, I plan to add more, add python bindings and unit tests. Regards Martin [1] https://github.com/qgis/QGIS/commit/b2a4c765b4e8a3fa00385a56a358952f46a1957a ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Legend refactoring branch merged
On Wed, May 21, 2014 at 3:46 PM, Etienne Tourigny etourigny@gmail.comwrote: A quick test revealed that layer actions added via QgsLegendInterface::addLegendLayerAction() and addLegendLayerActionForLayer() do not show up in the context menu any more. Should the corresponding members be added to QgsLayerTreeLayer class? I mean QgsLayerTreeRegistryBridge class and adding the menus in QgsAppLayerTreeViewMenuProvider::createContextMenu() sorry about so many email, my gmail is flaky. Etienne cheers Etienne On Wed, May 21, 2014 at 3:03 PM, Rouzaud Denis denis.rouz...@gmail.comwrote: Congratulations for this big cleanup! I am really glad we (SIGE) could help this project to come true. On 21 May 2014, at 19:11, Martin Dobias wonder...@gmail.com wrote: Hi everyone I have just merged the first part of the legend refactoring work to master [1]. It does not really bring any new features for the end user, the changes are mainly under the hood. Things should ideally work as before, if not then probably it is a bug. There will be second part of the work related mainly around improved layer symbology display in legend, more interactive legend and more options for customization. At Lutra Consulting we are still looking for funders willing to co-fund the work. At this point let me thank SIGE and Swiss QGIS User Group for supporting the project. Please test thoroughly - the legend has received quite a lot of features over time, so there could be still some minor features I have missed to port to new implementation. The format of the project file has changed, but there is backward compatibility with older projects which should allow seamless transition. Once saved with 2.4, the older versions of QGIS will loose the information about grouping. If you are interested in studying the new code, there are two new folders of interest: - src/core/layertree - src/gui/layertree There is basic doxygen documentation for the new core classes, I plan to add more, add python bindings and unit tests. Regards Martin [1] https://github.com/qgis/QGIS/commit/b2a4c765b4e8a3fa00385a56a358952f46a1957a ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Legend refactoring branch merged
A quick test revealed that layer actions added via QgsLegendInterface::addLegendLayerAction() and addLegendLayerActionForLayer() do not show up in the context menu any more. Should the corresponding members be added to QgsLayerTreeLayer class? cheers Etienne On Wed, May 21, 2014 at 3:03 PM, Rouzaud Denis denis.rouz...@gmail.comwrote: Congratulations for this big cleanup! I am really glad we (SIGE) could help this project to come true. On 21 May 2014, at 19:11, Martin Dobias wonder...@gmail.com wrote: Hi everyone I have just merged the first part of the legend refactoring work to master [1]. It does not really bring any new features for the end user, the changes are mainly under the hood. Things should ideally work as before, if not then probably it is a bug. There will be second part of the work related mainly around improved layer symbology display in legend, more interactive legend and more options for customization. At Lutra Consulting we are still looking for funders willing to co-fund the work. At this point let me thank SIGE and Swiss QGIS User Group for supporting the project. Please test thoroughly - the legend has received quite a lot of features over time, so there could be still some minor features I have missed to port to new implementation. The format of the project file has changed, but there is backward compatibility with older projects which should allow seamless transition. Once saved with 2.4, the older versions of QGIS will loose the information about grouping. If you are interested in studying the new code, there are two new folders of interest: - src/core/layertree - src/gui/layertree There is basic doxygen documentation for the new core classes, I plan to add more, add python bindings and unit tests. Regards Martin [1] https://github.com/qgis/QGIS/commit/b2a4c765b4e8a3fa00385a56a358952f46a1957a ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Cannot install libqgis_customwidgets.so
It should probably be disabled by default when CMAKE_INSTALL_PREFIX is set (to avoid this error), but it would make sense to make it default if CMAKE_INSTALL_PREFIX is not set (which requires to install as root). Don't know if it's easy to do that in cmake though. cheers Etienne On Mon, May 19, 2014 at 1:16 PM, Rouzaud Denis denis.rouz...@gmail.comwrote: Hi, The libqgis_customwidgets is a new library which allow using specific QGIS widgets directly in Qt Designer (if compiled with Qt4). Now, this lib needs to be in Qt plugin’s directory to work properly. So this will require to run make as install as root. You can disable this by running cmake with -DWITH_CUSTOM_WIDGETS=FALSE Regarding the second problem described by Richard it should be fixed. pyuic will not bug anymore, even if QGIS is not installed. I don’t know what’s the best default value for this library installation. But it might be better to reset it to false, if one wants that the default install can be run not being root. Cheers, Denis On 19 May 2014, at 18:08, Richard Duivenvoorde rdmaili...@duif.net wrote: On 19-05-14 17:08, Radim Blazek wrote: I am getting: CMake Error at src/customwidgets/cmake_install.cmake:68 (FILE): file INSTALL cannot copy file /home/radim/devel/qgis/build/output/lib/libqgis_customwidgets.so.2.3.0 to /usr/lib/x86_64-linux-gnu/qt4/plugins/designer/libqgis_customwidgets.so.2.3.0. it seems to ignore CMAKE_INSTALL_PREFIX. Hi Radim, I had the same problem. It has something to do with the customwidgets from QGIS. Actually making them available for designer. It is just changed from default not install to default install it. But (as you) I install only locally, so am not allowed to install .so files into the directory. So I ran 'sudo make install', BUT then you get another problem: there is a new dependecy now on qgis.gui module (which I do not have globally) so this breaks your pyqt. So I would not do this. Denis is aware of the problem, and looking for a solution. (For me part of the solution would be to NOT default do this installation into my global system.) Regards, Richard Duivenvoorde ___ 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] changes to file filters in GDAL and OGR file open dialogs
It can be done but requires a really long filter string (with all possible file extensions) shown in the dialog - not very practical. See attached screenshot which occupies the whole screen. To do this properly (without showing the long filter string) would require a custom widget, I think. Etienne On Mon, May 12, 2014 at 11:17 AM, AntonioLocandro antoniolocan...@hotmail.com wrote: +1, would there be a way to show all supported files as an option? That would work to show all supported by default files without showing extra files like all files (*) would do, All files still would be an option All files (*) All supported files () -- View this message in context: http://osgeo-org.1560.x6.nabble.com/changes-to-file-filters-in-GDAL-and-OGR-file-open-dialogs-tp5139506p5139778.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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] GDAL 1.11 new formats
There is also one new raster format (KRO). To whoever adds support for these, it would be nice to test that they it works in file open dialogs as well as the browser dock and app. Should work automatically once the ogr and gdal drivers are updated. Looks like there is no support for network-based gdal/ogr drivers in the browser - that would be nice to have. It could take the form of a new top-level item, and a New connection dialog similar to the one used in the new vector database widget. Etienne On Wed, May 7, 2014 at 4:21 PM, Even Rouault even.roua...@mines-paris.orgwrote: Le mercredi 07 mai 2014 20:51:53, Larry Shaffer a écrit : Hi, GDAL/OGR 1.11 offers several new OGR formats [0] that need support added in QGIS's source. I have added the OpenFileGDB format (because it was simple to do) [1], but don't have enough experience with the other database formats to add their support. * CartoDB : read/write support -- Not file based, but remote database. Should be dealt like others myDatabaseDrivers cases * GME (Google Map Engine) : read/write support -- Remote database too. * GPKG (GeoPackage): read-write support (vector part of the spec.) -- File-based (similar to CSV) Extension is .gpkg * SXF: read-only support -- File-based. Extension is SXF * WALK : read-only support -- Similar to PGEO. It is a MDB database * WAsP .map : read-write support -- File-based. Extension is .map Would anyone be willing to help add support for those? Looks like in addition to qgsogrprovider.cpp's createFilters( QString type ) that QgsVectorFileWriter::initMetaData() also needs updated. IMO, it would be good to then backport these to release-2.2 branch as well, so current users may benefit from the new formats. I could add my commit, but seems like it would be better to add full GDAL/OGR 1.11 support at once to that branch, excepting some formats if they will need more extensive support added first. [0] http://trac.osgeo.org/gdal/wiki/Release/1.11.0-News [1] https://github.com/qgis/QGIS/commit/a096cf4 Regards, Larry -- Geospatial professional services http://even.rouault.free.fr/services.html ___ 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] SciPy in osgeo4w @64 bit
Probably better off asking elsewhere, this topic is specific to osgeo4w not QGIS. There is a bugtraker and mailing list for osgeo4w. cheers Etienne On Mon, Apr 14, 2014 at 4:36 PM, Luca Congedo semiautomatic.blog...@gmail.com wrote: Hello everybody, SciPy (a very useful python library) is used by several plugin for QGIS, and it is already included in osgeo4w @32 bit. I would like to ask if it is possible to include SciPy in osgeo4w @64 bit too. I am also available for testing the package, if you need. Thank you, Luca Congedo ___ 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] new plugin Load TMS Layer
Hi Thanks for the thumbs up. Can you explain if using Google Maps with the OpenLayers plugin respects their TOS? Do you have any links for Google TOS using both tiles and web view (used in OpenLayers)? thanks Etienne On Wed, Apr 9, 2014 at 7:59 PM, Pirmin Kalberer pi...@sourcepole.comwrote: Hi Etienne, Am Montag, 7. April 2014, 18.45:05 schrieb Etienne Tourigny: I have put together a simple plugin to load a number of TMS layers using the GDAL TMS mini-driver [1]. I see it as a simple alternative to the more complete OpenLayers plugin. Code is at github for now [2]. Any suggestions are welcome (including plugin name). Also if you have any other working examples please let me know. Supported layers are OSM, Google, and other examples given in [1] (except those that don't work). Using Google Maps via TMS URL's is against their TOS. That's also the reason, why I didn't approve the similar Tile Map Scale Plugin [1] yet. [1] https://github.com/datalyze-solutions/TileMapScaleLevels Regards Pirmin -- Pirmin Kalberer@PirminKalberer Sourcepole - Linux Open Source Solutions Weberstrasse 5, 8004 Zürich, Switzerland Tel: 044 440 77 11 Direkt: 044 51 567 77 p...@sourcepole.ch http://www.sourcepole.ch ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] new plugin Load TMS Layer
I meant heads up... not thumbs up On Wed, Apr 9, 2014 at 9:28 PM, Etienne Tourigny etourigny@gmail.comwrote: Hi Thanks for the thumbs up. Can you explain if using Google Maps with the OpenLayers plugin respects their TOS? Do you have any links for Google TOS using both tiles and web view (used in OpenLayers)? thanks Etienne On Wed, Apr 9, 2014 at 7:59 PM, Pirmin Kalberer pi...@sourcepole.comwrote: Hi Etienne, Am Montag, 7. April 2014, 18.45:05 schrieb Etienne Tourigny: I have put together a simple plugin to load a number of TMS layers using the GDAL TMS mini-driver [1]. I see it as a simple alternative to the more complete OpenLayers plugin. Code is at github for now [2]. Any suggestions are welcome (including plugin name). Also if you have any other working examples please let me know. Supported layers are OSM, Google, and other examples given in [1] (except those that don't work). Using Google Maps via TMS URL's is against their TOS. That's also the reason, why I didn't approve the similar Tile Map Scale Plugin [1] yet. [1] https://github.com/datalyze-solutions/TileMapScaleLevels Regards Pirmin -- Pirmin Kalberer@PirminKalberer Sourcepole - Linux Open Source Solutions Weberstrasse 5, 8004 Zürich, Switzerland Tel: 044 440 77 11 Direkt: 044 51 567 77 p...@sourcepole.ch http://www.sourcepole.ch ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Adding plugins to core?
Since the OpenLayers plugin does not (currently) work with master, perhaps we can replace it with TMS-based layers, wither through a plugin or as a native (GDAL-based) provider? Is there anything in OpenLayers that could not work with GDAL TMS mini-driver [1] ? On Mon, Apr 7, 2014 at 7:22 AM, Vincent Picavet vincent...@oslandia.comwrote: Hello, Le lundi 7 avril 2014 12:05:05, Nyall Dawson a écrit : On 7 April 2014 18:15, Vincent Picavet vincent...@oslandia.com wrote: A good solution though would be to remove google layers and only use OSM and mapbox layers, which begin to be on par in terms of quality. I'm pretty sure this is against MapBox's terms of service too, unless users were made to sign up for a MapBox account and had to add their individual API key to QGIS to unlock MapBox layers: You must have a Mapbox account to use Mapbox. You are required to register for an account before using the Service. Each request to the API must include your account's unique API identifier. Unauthorized use of any API identifier is prohibited. [1] Right, I had not read this through. It would probably be much easier to get a specific authorization from MapBox than from Google though, given their open- source orientation. Or let the user a deliberate way to add google layers (indicating a URL or something like this), warning him about the licence. Hmm... while this may be a workable solution to the licensing issue, wouldn't it be a step back in functionality anyway? We'd be trading having a good, working off-the-shelf third-party plugin for a crippled core version which takes user intervention to unlock the same features. In any case, there are quite a lot of OSM based layers which can be used (HOT, OSM.fr, OpenCycleMap...). We can still enhance the plugin with those. It would lack an aerial imagery layer though. I'm totally for adding essential plugins to core (or merging the functionality with reimplemented c++ versions), but I honestly don't know if it's workable to do this for the OpenLayers plugin. Right, if we remove everything from the plugin except the TMS YXZ layers, we could also just have a better ergonomy for opening this kind of layers through GDAL, and have a predefined list of layers accessible on internet (even auto- updatable by downloading the list). Vincent ___ 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] Adding plugins to core?
Since the OpenLayers plugin does not (currently) work with master, perhaps we can replace it with TMS-based layers, either through a plugin or as a native (GDAL-based) provider? Is there anything in OpenLayers plugin that could not work with GDAL TMS mini-driver [1] ? [1] http://www.gdal.org/frmt_wms.html On Mon, Apr 7, 2014 at 11:42 AM, Etienne Tourigny etourigny@gmail.comwrote: Since the OpenLayers plugin does not (currently) work with master, perhaps we can replace it with TMS-based layers, wither through a plugin or as a native (GDAL-based) provider? Is there anything in OpenLayers that could not work with GDAL TMS mini-driver [1] ? On Mon, Apr 7, 2014 at 7:22 AM, Vincent Picavet vincent...@oslandia.comwrote: Hello, Le lundi 7 avril 2014 12:05:05, Nyall Dawson a écrit : On 7 April 2014 18:15, Vincent Picavet vincent...@oslandia.com wrote: A good solution though would be to remove google layers and only use OSM and mapbox layers, which begin to be on par in terms of quality. I'm pretty sure this is against MapBox's terms of service too, unless users were made to sign up for a MapBox account and had to add their individual API key to QGIS to unlock MapBox layers: You must have a Mapbox account to use Mapbox. You are required to register for an account before using the Service. Each request to the API must include your account's unique API identifier. Unauthorized use of any API identifier is prohibited. [1] Right, I had not read this through. It would probably be much easier to get a specific authorization from MapBox than from Google though, given their open- source orientation. Or let the user a deliberate way to add google layers (indicating a URL or something like this), warning him about the licence. Hmm... while this may be a workable solution to the licensing issue, wouldn't it be a step back in functionality anyway? We'd be trading having a good, working off-the-shelf third-party plugin for a crippled core version which takes user intervention to unlock the same features. In any case, there are quite a lot of OSM based layers which can be used (HOT, OSM.fr, OpenCycleMap...). We can still enhance the plugin with those. It would lack an aerial imagery layer though. I'm totally for adding essential plugins to core (or merging the functionality with reimplemented c++ versions), but I honestly don't know if it's workable to do this for the OpenLayers plugin. Right, if we remove everything from the plugin except the TMS YXZ layers, we could also just have a better ergonomy for opening this kind of layers through GDAL, and have a predefined list of layers accessible on internet (even auto- updatable by downloading the list). Vincent ___ 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] Adding plugins to core?
Thanks for the links. Most of this information is also available at [1]. I am preparing a simple plugin to load these layers as raster layers, will keep you updated on this. [1] http://www.gdal.org/frmt_wms.html On Mon, Apr 7, 2014 at 2:32 PM, kimaidou kimai...@gmail.com wrote: Hi List For the record, here is an old blog post about using gdal driver to use external layers such as OSM http://www.3liz.com/blog/rldhont/index.php?post/2012/07/17/OpenStreetMap-Tiles-in-QGIS The problem is that with this method, it seems GDAL does not alway use the right tiles for the rigth scale. There must be an additionnal parameter wich can control this behaviour. I totally agree with the concerns about licence violation. Easing the use of Google layers is kind of encouraging people to use it, for example for digitization purpose. Users must be warned about the terms of service. Michael PS : someone has gathered a list of XML for GDAL for some providers : http://libreavous.teledetection.fr/geomatique/28-sig/58-afficher-des-couches-issues-de-services-en-ligne-dans-un-sig Click on the button called Fichiers de configuration Michael 2014-04-07 16:48 UTC+02:00, Etienne Tourigny etourigny@gmail.com: Since the OpenLayers plugin does not (currently) work with master, perhaps we can replace it with TMS-based layers, either through a plugin or as a native (GDAL-based) provider? Is there anything in OpenLayers plugin that could not work with GDAL TMS mini-driver [1] ? [1] http://www.gdal.org/frmt_wms.html On Mon, Apr 7, 2014 at 11:42 AM, Etienne Tourigny etourigny@gmail.comwrote: Since the OpenLayers plugin does not (currently) work with master, perhaps we can replace it with TMS-based layers, wither through a plugin or as a native (GDAL-based) provider? Is there anything in OpenLayers that could not work with GDAL TMS mini-driver [1] ? On Mon, Apr 7, 2014 at 7:22 AM, Vincent Picavet vincent...@oslandia.comwrote: Hello, Le lundi 7 avril 2014 12:05:05, Nyall Dawson a écrit : On 7 April 2014 18:15, Vincent Picavet vincent...@oslandia.com wrote: A good solution though would be to remove google layers and only use OSM and mapbox layers, which begin to be on par in terms of quality. I'm pretty sure this is against MapBox's terms of service too, unless users were made to sign up for a MapBox account and had to add their individual API key to QGIS to unlock MapBox layers: You must have a Mapbox account to use Mapbox. You are required to register for an account before using the Service. Each request to the API must include your account's unique API identifier. Unauthorized use of any API identifier is prohibited. [1] Right, I had not read this through. It would probably be much easier to get a specific authorization from MapBox than from Google though, given their open- source orientation. Or let the user a deliberate way to add google layers (indicating a URL or something like this), warning him about the licence. Hmm... while this may be a workable solution to the licensing issue, wouldn't it be a step back in functionality anyway? We'd be trading having a good, working off-the-shelf third-party plugin for a crippled core version which takes user intervention to unlock the same features. In any case, there are quite a lot of OSM based layers which can be used (HOT, OSM.fr, OpenCycleMap...). We can still enhance the plugin with those. It would lack an aerial imagery layer though. I'm totally for adding essential plugins to core (or merging the functionality with reimplemented c++ versions), but I honestly don't know if it's workable to do this for the OpenLayers plugin. Right, if we remove everything from the plugin except the TMS YXZ layers, we could also just have a better ergonomy for opening this kind of layers through GDAL, and have a predefined list of layers accessible on internet (even auto- updatable by downloading the list). Vincent ___ 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] new plugin Load TMS Layer
I have put together a simple plugin to load a number of TMS layers using the GDAL TMS mini-driver [1]. I see it as a simple alternative to the more complete OpenLayers plugin. Code is at github for now [2]. Any suggestions are welcome (including plugin name). Also if you have any other working examples please let me know. Supported layers are OSM, Google, and other examples given in [1] (except those that don't work). Tested with QGIS 2.2 and master. Rendering of labels is not the best but it seems better with master. [1] http://www.gdal.org/frmt_wms.html [2] https://github.com/etiennesky/loadtmslayer cheers Etienne ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] new plugin Load TMS Layer
Matthieu, Thanks for your input! I will change the project CRS by default but make it optional. Do you have a xml file for the TMS of the Global Forest Change, or any info on what server it uses or at least the path? While working on it I realized the power of the caching - I am taking advantage of that and setting the proper cache directory. cheers Etienne On Mon, Apr 7, 2014 at 11:00 PM, Mathieu Pellerin nirvn.a...@gmail.comwrote: Nice, few comments (based on my previous uses of the GDAL TMS mini-driver): - your plugin should make sure the loaded layer is assigned the proper projection (mostly pseudo-mercator); failing to do so will leave must users unable to understand why the TMS rendering fails - that would also switch OTF reprojection on when needed - consider adding TMS of the Global Forest Change (see http://www.earthenginepartners.appspot.com/science-2013-global-forest for data source, and https://www.flickr.com/photos/60284107@N00/11096344994/in/pool-qgis-screenshotsfor in-QGIS example) The GDAL TMS driver is in many ways a superior solution to OpenLayers; it works perfectly fine with the multi-thread rendering, can be exported via qgis composer, caches the tiles, etc. Math On Tue, Apr 8, 2014 at 4:45 AM, Etienne Tourigny etourigny@gmail.comwrote: I have put together a simple plugin to load a number of TMS layers using the GDAL TMS mini-driver [1]. I see it as a simple alternative to the more complete OpenLayers plugin. Code is at github for now [2]. Any suggestions are welcome (including plugin name). Also if you have any other working examples please let me know. Supported layers are OSM, Google, and other examples given in [1] (except those that don't work). Tested with QGIS 2.2 and master. Rendering of labels is not the best but it seems better with master. [1] http://www.gdal.org/frmt_wms.html [2] https://github.com/etiennesky/loadtmslayer cheers Etienne ___ 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] Adding plugins to core?
On Sat, Apr 5, 2014 at 1:00 AM, Nathan Woodrow madman...@gmail.com wrote: I agree that adding the plugins to core would be a good idea however I don't feel that we should just add them in their current state. The plugin repository has the benefit of of being able to update things faster then the release of QGIS itself if you find bugs, etc, you can also add features for older QGIS versions. the processing/sextante plugin is both in core and also can be updated. Same thing for ftools and gdaltools. I think these features in the plugins are great but we should really integrate them into the core project itself as new features rather then just a plugin. Having Python plugins in core can also raise issue for users because they still look like normal plugins but you can't update them because they are no longer in the repository. Having to enable handy features also feels a bit hap hazard to me. Something like the value tool could easily be integrated into the identify tool for instance. I agree, more or less - I thought about integrating it into the main identify tool, but as it works with raster layers only, how would you display raster and vector layers? There are also some other concepts floating around the idea of bring CAD functions into core so I think it's best to just focus on making those stronger. So +1 for adding the functions but -1 for just bringing the plugins into core. Not sure they would make it into core then, as development cost fof integrating into core is much higher than adding them as core python modules. For instance, the openlayer plugin would probably need quite a lot of work to be ported to c++. On the other hand, anything that relies on qwt would be better handled. Butanthing that uses python plotting libraries would obviously not work. cheers Etienne - Nathan On Sat, Apr 5, 2014 at 1:22 PM, AntonioLocandro antoniolocan...@hotmail.com wrote: I think it's a great idea, I was actually thinking about this the other day and glad you brought the topic. Although we can install plugins certainly it becomes evident when a plugin should really become a core feature, example the Openlayers Plugin, I bet almost all people using QGIS downloads it before doing anything with QGIS. Plugins extend QGIS functionality beyond what initially was thought but in many cases plugins become a must to be able to work efficiently If the plugins are added to core I would vote for blending the functions coherently with the rest of the interface in the appropriate menus. A good example would be CAD tools which I would say be called Advanced Editing or something. I would add http://plugins.qgis.org/plugins/zoomtocoordinates/ http://plugins.qgis.org/plugins/numericalDigitize/ - needs to add case for geographic coordinates -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Adding-plugins-to-core-tp5133202p5133245.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Adding plugins to core?
On Sat, Apr 5, 2014 at 1:13 PM, Etienne Tourigny etourigny@gmail.comwrote: On Sat, Apr 5, 2014 at 1:00 AM, Nathan Woodrow madman...@gmail.comwrote: I agree that adding the plugins to core would be a good idea however I don't feel that we should just add them in their current state. The plugin repository has the benefit of of being able to update things faster then the release of QGIS itself if you find bugs, etc, you can also add features for older QGIS versions. the processing/sextante plugin is both in core and also can be updated. Same thing for ftools and gdaltools. I think these features in the plugins are great but we should really integrate them into the core project itself as new features rather then just a plugin. Having Python plugins in core can also raise issue for users because they still look like normal plugins but you can't update them because they are no longer in the repository. Having to enable handy features also feels a bit hap hazard to me. Something like the value tool could easily be integrated into the identify tool for instance. I agree, more or less - I thought about integrating it into the main identify tool, but as it works with raster layers only, how would you display raster and vector layers? I have implemented most features of the Identify Tool plugin to the main identify map tool in master, here is the pull request. https://github.com/qgis/QGIS/pull/1293 There are also some other concepts floating around the idea of bring CAD functions into core so I think it's best to just focus on making those stronger. So +1 for adding the functions but -1 for just bringing the plugins into core. Not sure they would make it into core then, as development cost fof integrating into core is much higher than adding them as core python modules. For instance, the openlayer plugin would probably need quite a lot of work to be ported to c++. On the other hand, anything that relies on qwt would be better handled. Butanthing that uses python plotting libraries would obviously not work. cheers Etienne - Nathan On Sat, Apr 5, 2014 at 1:22 PM, AntonioLocandro antoniolocan...@hotmail.com wrote: I think it's a great idea, I was actually thinking about this the other day and glad you brought the topic. Although we can install plugins certainly it becomes evident when a plugin should really become a core feature, example the Openlayers Plugin, I bet almost all people using QGIS downloads it before doing anything with QGIS. Plugins extend QGIS functionality beyond what initially was thought but in many cases plugins become a must to be able to work efficiently If the plugins are added to core I would vote for blending the functions coherently with the rest of the interface in the appropriate menus. A good example would be CAD tools which I would say be called Advanced Editing or something. I would add http://plugins.qgis.org/plugins/zoomtocoordinates/ http://plugins.qgis.org/plugins/numericalDigitize/ - needs to add case for geographic coordinates -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Adding-plugins-to-core-tp5133202p5133245.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Adding plugins to core?
I think it's a great idea. +1 for openlayers, once it works with master (I don't use the others) how about adding value tool? http://plugins.qgis.org/plugins/valuetool/ But we need to fix the pyqwt bug with debian before including it in main QGIS. http://hub.qgis.org/issues/7450 On Fri, Apr 4, 2014 at 2:26 PM, Paolo Cavallini cavall...@faunalia.itwrote: Hi all. How about adding some popular, well tested plugin of general usage to main QGIS? We have done this in the past, e.g. for fTools, GDALTools, DB Manager etc., and they were good additions to QGIS. Currently the most downloaded (DESC) are: http://plugins.qgis.org/plugins/openlayers_plugin/ http://plugins.qgis.org/plugins/tablemanager/ http://plugins.qgis.org/plugins/mmqgis/ http://plugins.qgis.org/plugins/GeoCoding/ http://plugins.qgis.org/plugins/cadtools/ http://plugins.qgis.org/plugins/xytools/ I believe they are all good candidates, plus possibly more. Opinions? 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] ValueTool error
This has been reported a few times: on the bug tracker and on the qgis-user mailing list just yesterday. Version 0.8.4, released a week ago, fixes this bug. I was able to install that version with qgis-2.2.0 but on linux - do you not see the latest version (0.8.4) in the plugin manager? Regards, Etienne On Thu, Apr 3, 2014 at 9:45 AM, Casper Børgesen (CABO) c...@niras.dkwrote: Hi! I get the following error massage from time to time when using the ValueTool plugin. It seems like it happens when I add or remove a layer: An error has occured while executing Python code: Traceback (most recent call last): File C:/Users/my_user/.qgis2/python/plugins\valuetool\valuewidget.py, line 500, in invalidatePlot if self.mplLine is not None: AttributeError: 'ValueWidget' object has no attribute 'mplLine' Python version: 2.7.5 (default, May 15 2013, 22:44:16) [MSC v.1500 64 bit (AMD64)] QGIS version: 2.2.0-Valmiera Valmiera, c3a2817 What is this about and has it been reported? Regards, Casper ___ 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] [GRASS-dev] GRASS QGIS: the future
On Fri, Mar 28, 2014 at 11:16 AM, Paolo Cavallini cavall...@faunalia.itwrote: Il 28/03/2014 15:04, Martin Dobias ha scritto: On Fri, Mar 28, 2014 at 11:48 AM, Paolo Cavallini cavall...@faunalia.it wrote: * to add GRASS browsing capabilities in QGIS file browser The support for GRASS is already in the browser - if you enter a directory that is a GRASS database, it will detect it and show locations/mapsets/maps/layers. That's great news, never tried. Works beautifully, thanks. In the GRASS plugin there are a few more features, i.e.: * showing history (important) * copy/rename/delete. The browser does not support these operations, but it would be cool. If we can add these, I think the corresponding section of the plugin would be rather useless. Am I missing something? 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] new plugin website metadata.txt requirements for plugins
I just uploaded a new version of the plugin qith about field and it works - new site looks great too! i just filed a bug about experimental end approved checkboxes not being respected when I add a new version. On Fri, Mar 28, 2014 at 10:52 AM, Alessandro Pasotti apaso...@gmail.comwrote: 2014-03-28 14:45 GMT+01:00 Tom Kralidis tomkrali...@gmail.com: What should the optional about field attribute contain? Is this documented anywhere? Not yet, AFAIK. The ticket request is here: http://hub.qgis.org/issues/5236 -- Alessandro Pasotti w3: www.itopen.it ___ 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] OL plugin crashes QGIS
and there is a bug report for it in the openlayers tracker On Thu, Mar 20, 2014 at 2:29 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Anyone confirms? yes it is a known problem since the first hours after MTR was merged. ___ 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] Crash when activating Value Tool plugin
what OS are you running? my bet is debian... might be related to this bug - a conflict between qwt5 and qwt6. Please add info to this bug report... http://hub.qgis.org/issues/7450 On Wed, Mar 19, 2014 at 1:04 PM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. I have Value tool installed; when I activate it from the plugin manager, I get a crash. Master, just recompliled. Anyone confirms? All the best. === [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7c34c000 0x7f54a3814cf9 in __libc_waitpid (pid=24744, stat_loc=0x7c2ff93c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 40 ../sysdeps/unix/sysv/linux/waitpid.c: File o directory non esistente. [Current thread is 1 (Thread 0x7f54ab07d7c0 (LWP 24648))] #0 0x7f54a3814cf9 in __libc_waitpid (pid=24744, stat_loc=0x7c2ff93c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 resultvar = 0 oldtype = 0 #1 0x004f7f17 in qgisCrash(int) () No symbol table info available. #2 signal handler called No locals. #3 0x7f54a5e1f15f in QPen::operator=(QPen const) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 No symbol table info available. #4 0x7f5461791998 in QwtSymbol::clone() const () from /usr/lib/libqwt-qt4.so.5 No symbol table info available. #5 0x7f5461a66220 in ?? () from /usr/lib/python2.7/dist-packages/PyQt4/Qwt5/Qwt.so No symbol table info available. #6 0x7f546179b8fa in QwtPlotCurve::setSymbol(QwtSymbol const) () from /usr/lib/libqwt-qt4.so.5 No symbol table info available. #7 0x7f5461aa5011 in ?? () from /usr/lib/python2.7/dist-packages/PyQt4/Qwt5/Qwt.so No symbol table info available. #8 0x7f547bec6854 in PyEval_EvalFrameEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #9 0x7f547bec67d9 in PyEval_EvalFrameEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #10 0x7f547bec88fd in PyEval_EvalCodeEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #11 0x7f547bec8a90 in ?? () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #12 0x7f547bea86b3 in PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #13 0x7f547be3311d in ?? () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #14 0x7f547bea86b3 in PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #15 0x7f547beacf1f in ?? () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #16 0x7f547beaaf2f in ?? () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #17 0x7f547bea86b3 in PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #18 0x7f547bec3f96 in PyEval_EvalFrameEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #19 0x7f547bec67d9 in PyEval_EvalFrameEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #20 0x7f547bec67d9 in PyEval_EvalFrameEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #21 0x7f547bec88fd in PyEval_EvalCodeEx () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #22 0x7f547bec8be2 in PyEval_EvalCode () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #23 0x7f547bdf3ce9 in PyRun_StringFlags () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #24 0x7f547c2f1018 in QgsPythonUtilsImpl::evalString(QString const, QString) () from /usr/lib/libqgispython.so.2.3.0 No symbol table info available. #25 0x7f547c2ee291 in QgsPythonUtilsImpl::startPlugin(QString) () from /usr/lib/libqgispython.so.2.3.0 No symbol table info available. #26 0x006a080a in QgsPluginRegistry::loadPythonPlugin(QString) () No symbol table info available. #27 0x007bd8b2 in QgsPluginManager::loadPlugin(QString) () No symbol table info available. #28 0x007cafb3 in QgsPluginManager::pluginItemChanged(QStandardItem*) () No symbol table info available. #29 0x007fc46c in ?? () No symbol table info available. #30 0x7f54a692077a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 No symbol table info available. #31 0x7f54a622be2f in QStandardItemModel::itemChanged(QStandardItem*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 No symbol table info available. #32
Re: [Qgis-developer] Crash when activating Value Tool plugin
Definitely a qwt5/qwt6 conflict issue in debian. Jurgen - can you have a look at the bug report and help out? regards, Etienne On Wed, Mar 19, 2014 at 2:54 PM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 19/03/2014 18:48, Etienne Tourigny ha scritto: what OS are you running? my bet is debian... might be related to this bug - a conflict between qwt5 and qwt6. Please add info to this bug report... http://hub.qgis.org/issues/7450 right: done, thanks. - -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlMp2b0ACgkQ/NedwLUzIr7xvwCgk6s31aBQgyyC3kut69oG9aZC SRAAoIUQLjF/e/dmNgX+kxcH9VfsBxUE =7CQb -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QgsMapCanvas.mapRenderer() deprecated since 2.4, use mapRendererSettings()
use iface.mapCanvas().mapSettings() On Sat, Mar 15, 2014 at 7:15 AM, Radim Blazek radim.bla...@gmail.comwrote: Python plugins are now printing deprecation traceback. Hhow to fix that. I dont see any mapRendererSettings() implemented. Radim ___ 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] [gdal-dev] Fix for QGIS 2.2+ Projection issue with OSGB36 NTv2
On Fri, Mar 14, 2014 at 10:44 AM, Marco Hugentobler marco.hugentob...@sourcepole.ch wrote: Hi The info for OSGB36 NTv2 is in srs.db now. Makes me think - could QGIS ship with the freely available gsb grids, in an optional package (say qgis-datum-grids)? It would be rather convenient, especially as QGIS now supports them (but does not ship with any grids yet, unless mistaken). I'm receiving frequent suggestions of bundling .gsb files with QGIS. The problems I see with this are: - It adds the extra MB for QGIS too. it should be an extra package, not part of main QGIS packages (for osgeo4w and linux) - They come with various licences. that would require a bit of time to make sure all added packages are ok to distribute, but it's a one-time process. - .gsb files are usefull for all tools working with proj. So a logical choice would be to have an optional package for proj4. Yes, but that would be up to others not QGIS, so adding them to the QGIS packages would have more chances of actually happening. It would be nice to have a point of view from those responsible for packaging QGIS. cheers, Etienne Regards, Marco On 13.03.2014 18:20, Etienne Tourigny wrote: On Thu, Mar 13, 2014 at 4:27 AM, Marco Hugentobler marco.hugentob...@sourcepole.ch wrote: Hi I'm adding the entries for OSGB36 NTv2 to srs.db. For the .gsb file, you could probably contact the proj4 project if they want it to distribute it togethere with the library (if the license allows that). I guess that's unlikely they would add it to the binary packages, as it would add a few MB to the base install. But they might add it to proj-datumgrid-1.5.zip (which contains many free datum files), as the licence for the grid is BSD. Makes me think - could QGIS ship with the freely available gsb grids, in an optional package (say qgis-datum-grids)? It would be rather convenient, especially as QGIS now supports them (but does not ship with any grids yet, unless mistaken). cheers, Etienne Regards, Marco On 11.03.2014 18:23, Etienne Tourigny wrote: You email should be sent to the qgis-developer list (this is the gdal-dev list), which I am forwarding this to. On Tue, Mar 11, 2014 at 7:44 AM, Nicholas Duggan dragons8my...@live.co.uk wrote: Hi all, I'm trying to get my fix for the OSGB36 to WGS84 using Ordnance Surveys OSTN02 (NTv2) transformation into the QGIS master. Nathan Woodrow recommended I bring it up with you guys who might be able to implement it. Essentially I've updated the QGIS srs.db and put the OSTN02_NTv2.gsb in the Share/Proj folder, full description and files are here: http://dragons8mycat.wordpress.com/2014/03/03/gis-tips-getting-ostn02-to-work-with-qgis-2-2/ Is this something which can be implemented by yourselves or can you point me in the right direction for getting it put in the master/future releases? Thanks, Nick D (@dragons8mycat) ___ gdal-dev mailing list gdal-...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev ___ Qgis-developer mailing listQgis-developer@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, switzerlandmarco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, switzerlandmarco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ 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] [gdal-dev] Fix for QGIS 2.2+ Projection issue with OSGB36 NTv2
On Thu, Mar 13, 2014 at 4:27 AM, Marco Hugentobler marco.hugentob...@sourcepole.ch wrote: Hi I'm adding the entries for OSGB36 NTv2 to srs.db. For the .gsb file, you could probably contact the proj4 project if they want it to distribute it togethere with the library (if the license allows that). I guess that's unlikely they would add it to the binary packages, as it would add a few MB to the base install. But they might add it to proj-datumgrid-1.5.zip (which contains many free datum files), as the licence for the grid is BSD. Makes me think - could QGIS ship with the freely available gsb grids, in an optional package (say qgis-datum-grids)? It would be rather convenient, especially as QGIS now supports them (but does not ship with any grids yet, unless mistaken). cheers, Etienne Regards, Marco On 11.03.2014 18:23, Etienne Tourigny wrote: You email should be sent to the qgis-developer list (this is the gdal-dev list), which I am forwarding this to. On Tue, Mar 11, 2014 at 7:44 AM, Nicholas Duggan dragons8my...@live.co.uk wrote: Hi all, I'm trying to get my fix for the OSGB36 to WGS84 using Ordnance Surveys OSTN02 (NTv2) transformation into the QGIS master. Nathan Woodrow recommended I bring it up with you guys who might be able to implement it. Essentially I've updated the QGIS srs.db and put the OSTN02_NTv2.gsb in the Share/Proj folder, full description and files are here: http://dragons8mycat.wordpress.com/2014/03/03/gis-tips-getting-ostn02-to-work-with-qgis-2-2/ Is this something which can be implemented by yourselves or can you point me in the right direction for getting it put in the master/future releases? Thanks, Nick D (@dragons8mycat) ___ gdal-dev mailing list gdal-...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev ___ Qgis-developer mailing listQgis-developer@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, switzerlandmarco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ 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] [gdal-dev] Fix for QGIS 2.2+ Projection issue with OSGB36 NTv2
You email should be sent to the qgis-developer list (this is the gdal-dev list), which I am forwarding this to. On Tue, Mar 11, 2014 at 7:44 AM, Nicholas Duggan dragons8my...@live.co.ukwrote: Hi all, I'm trying to get my fix for the OSGB36 to WGS84 using Ordnance Surveys OSTN02 (NTv2) transformation into the QGIS master. Nathan Woodrow recommended I bring it up with you guys who might be able to implement it. Essentially I've updated the QGIS srs.db and put the OSTN02_NTv2.gsb in the Share/Proj folder, full description and files are here: http://dragons8mycat.wordpress.com/2014/03/03/gis-tips-getting-ostn02-to-work-with-qgis-2-2/ Is this something which can be implemented by yourselves or can you point me in the right direction for getting it put in the master/future releases? Thanks, Nick D (@dragons8mycat) ___ gdal-dev mailing list gdal-...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error building qgis debian package for 2.2
You are right - so sorry! I got it to build ok following the steps Just a remark: dch requires the devscripts package but that is not explained in INSTALL. Is that required for ubuntu only? If not this dependency be added to INSTALL $ dch -l ~raring --force-distribution --distribution raring raring build The program 'dch' is currently not installed. You can install it by typing: sudo apt-get install devscripts regards, Etienne On Thu, Mar 6, 2014 at 5:04 AM, Jürgen E. j...@norbit.de wrote: Hi Etienne, On Wed, 05. Mar 2014 at 22:05:49 -0300, Etienne Tourigny wrote: I am trying to build debian packages for 2.2 in Ubuntu Raring (12.04) but there seems to be a problem with libspatialindex, although I do have libspatialindex1 and libspatialindex-dev installed The build process complains about missing /libspatialindex.so which is in /usr/lib/ You didn't add the changelog entry for raring (INSTALL 3.8), right? Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS PSC member (RM) Germany IRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ 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] error building qgis debian package for 2.2
I am trying to build debian packages for 2.2 in Ubuntu Raring (12.04) but there seems to be a problem with libspatialindex, although I do have libspatialindex1 and libspatialindex-dev installed The build process complains about missing /libspatialindex.so which is in /usr/lib/ $ dpkg-buildpackage [...] [ 12%] Building CXX object src/core/CMakeFiles/qgis_core.dir/gps/qextserialport/moc_qextserialenumerator.cxx.o cd /data/src/qgis/qgis-master/debian/build/src/core /usr/bin/c++ -DEXTERNAL_SPATIALITE -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_TEST_LIB -DQT_WEBKIT_LIB -DQT_XML_LIB -D_HAVE_PTHREAD_ -D_TTY_POSIX_ -Dqgis_core_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -Wall -Wextra -Wno-long-long -Wformat-security -Wno-strict-aliasing -fPIC -I/usr/include/qt4 -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/data/src/qgis/qgis-master/debian/build -I/data/src/qgis/qgis-master/src/core -I/data/src/qgis/qgis-master/src/core/composer -I/data/src/qgis/qgis-master/src/core/dxf -I/data/src/qgis/qgis-master/src/core/pal -I/data/src/qgis/qgis-master/src/core/raster -I/data/src/qgis/qgis-master/src/core/renderer -I/data/src/qgis/qgis-master/src/core/symbology-ng -I/data/src/qgis/qgis-master/src/core/gps/qextserialport -I/usr/include/spatialindex -I/usr/include/gdal-DCORE_EXPORT= -DGUI_EXPORT= -DPYTHON_EXPORT= -DANALYSIS_EXPORT= -DAPP_EXPORT= -DTEST_DATA_DIR=\/data/src/qgis/qgis-master/tests/testdata\ -o CMakeFiles/qgis_core.dir/gps/qextserialport/moc_qextserialenumerator.cxx.o -c /data/src/qgis/qgis-master/debian/build/src/core/gps/qextserialport/moc_qextserialenumerator.cxx make[3]: *** No rule to make target `/usr/lib/x86_64-linux-gnu/libspatialindex.so', needed by `output/lib/libqgis_core.so.2.2.0'. Stop. make[3]: Leaving directory `/data/src/qgis/qgis-master/debian/build' make[2]: *** [src/core/CMakeFiles/qgis_core.dir/all] Error 2 make[2]: Leaving directory `/data/src/qgis/qgis-master/debian/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/data/src/qgis/qgis-master/debian/build' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Spatial index - what about having it automatically created and updated ?
That's a python plugin (ftools), so it may not be available to everyone. Better to do it natively (in the data provider) doing something like OGR_DS_ExecuteSQL(CREATE SPATIAL INDEX ON tablename [DEPTH N]) - untested I think it's a great idea to do this automatically with large ogr data sources as you said you should probably ask the gdal-dev list about which drivers support spatial index creation an automatic update. cheers Etienne On Thu, Feb 27, 2014 at 7:51 AM, kimaidou kimai...@gmail.com wrote: Hi 2014-02-27 11:14 GMT+01:00 Andrea Peri aperi2...@gmail.com: I guess more better is to use this extremely simple batch and create all the index in one step only. sing the gdal/ogr from osgeo4w. http://trac.osgeo.org/gdal/wiki/BatchCreationIndexesForShapefilesOnDOS Regards, As I said, I am thinking of non power users. They surely won't create nor use such a batch file, even if it is simple. I know there is also the great tool Vector / Data management tools / Create Spatial Index, which can create one for all layers in one step. But users do not use it : they do no know it exists, or they know but forget to use it. ___ 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] Spatial index - what about having it automatically created and updated ?
On Thu, Feb 27, 2014 at 10:56 AM, Etienne Tourigny etourigny@gmail.comwrote: That's a python plugin (ftools), so it may not be available to everyone. Better to do it natively (in the data provider) doing something like OGR_DS_ExecuteSQL(CREATE SPATIAL INDEX ON tablename [DEPTH N]) - untested there is already a function QgsOgrProvider::createSpatialIndex() (for shapefiles only) which is called by QgsOgrProvider::syncToDisc() if the spatial index already exists. I think it's a great idea to do this automatically with large ogr data sources as you said you should probably ask the gdal-dev list about which drivers support spatial index creation an automatic update. cheers Etienne On Thu, Feb 27, 2014 at 7:51 AM, kimaidou kimai...@gmail.com wrote: Hi 2014-02-27 11:14 GMT+01:00 Andrea Peri aperi2...@gmail.com: I guess more better is to use this extremely simple batch and create all the index in one step only. sing the gdal/ogr from osgeo4w. http://trac.osgeo.org/gdal/wiki/BatchCreationIndexesForShapefilesOnDOS Regards, As I said, I am thinking of non power users. They surely won't create nor use such a batch file, even if it is simple. I know there is also the great tool Vector / Data management tools / Create Spatial Index, which can create one for all layers in one step. But users do not use it : they do no know it exists, or they know but forget to use it. ___ 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] Identify with Feature Form on QGIS 2.2
There are going to be a few other bugs, hopefully fixed in 2.2, so eventually a point release will be worthwhile. With (semi-)automated builds it's not *that* much trouble I think. On Tue, Feb 25, 2014 at 9:40 AM, Sandro Santilli s...@keybit.net wrote: On Tue, Feb 25, 2014 at 12:09:30PM +1000, Nathan Woodrow wrote: hmmm that is a real bugger. Yeah I think kind of thing warrants a bug fix release. This will kill QGIS for most users who do data entry, which is most of the people I know. +1 A 2.2.1 could come out after 1 week of no activity in the stable branch after any activity. If it takes 4 months to get to that state (ie: nobody pushes a fix for that or more than one fix a week gets committed weekly) then no 2.2.1 would ever come out. --strk; ___ 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] Identify with Feature Form on QGIS 2.2
shouldn't there be a tag 'backport' tag in the tracker to identify critical tickets that warrant a backport to stable branch, so if someone has the time can backport those fixes? On Tue, Feb 25, 2014 at 12:48 PM, Anita Graser anitagra...@gmx.at wrote: We also have this blocker issue in 2.2.0 because it wasn't completely fixed after all: http://hub.qgis.org/issues/9396 Best wishes, Anita On Tue, Feb 25, 2014 at 1:44 PM, Etienne Tourigny etourigny@gmail.com wrote: There are going to be a few other bugs, hopefully fixed in 2.2, so eventually a point release will be worthwhile. With (semi-)automated builds it's not *that* much trouble I think. On Tue, Feb 25, 2014 at 9:40 AM, Sandro Santilli s...@keybit.net wrote: On Tue, Feb 25, 2014 at 12:09:30PM +1000, Nathan Woodrow wrote: hmmm that is a real bugger. Yeah I think kind of thing warrants a bug fix release. This will kill QGIS for most users who do data entry, which is most of the people I know. +1 A 2.2.1 could come out after 1 week of no activity in the stable branch after any activity. If it takes 4 months to get to that state (ie: nobody pushes a fix for that or more than one fix a week gets committed weekly) then no 2.2.1 would ever come out. --strk; ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Master doesn't compile
Just a remark, there are quite a few new warnings (mostly about deprecated functions, but also some unused or variables or parameters) using gcc 4.7.3 Here are some, in no particular order, there might be more /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaplayer.cxx: In static member function 'static void QgsMapLayer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)': /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaplayer.cxx:102:38: warning: 'void QgsMapLayer::clearCacheImage()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaplayer.h:386) [-Wdeprecated-declarations] In file included from /home/softdev/include/ogr_api.h:43:0, from /data/src/qgis/qgis-etiennesky/src/core/qgsvectorfilewriter.h:25, from /data/src/qgis/qgis-etiennesky/src/core/qgsvectorfilewriter.cpp:26: /home/softdev/include/ogr_core.h:72:32: warning: missing option after '#pragma GCC diagnostic' kind [-Wpragmas] /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaprenderer.cxx: In static member function 'static void QgsMapRenderer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)': /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaprenderer.cxx:69:80: warning: 'void QgsMapRenderer::hasCrsTransformEnabled(bool)' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaprenderer.h:327) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaprenderer.cxx:77:110: warning: 'void QgsMapRenderer::onDrawingProgress(int, int)' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaprenderer.h:355) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaplayer.cxx: In static member function 'static void QgsMapLayer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)': /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaplayer.cxx:102:38: warning: 'void QgsMapLayer::clearCacheImage()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaplayer.h:386) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaprenderer.cxx: In static member function 'static void QgsMapRenderer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)': /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaprenderer.cxx:69:80: warning: 'void QgsMapRenderer::hasCrsTransformEnabled(bool)' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaprenderer.h:327) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaprenderer.cxx:77:110: warning: 'void QgsMapRenderer::onDrawingProgress(int, int)' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaprenderer.h:355) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/gui/moc_qgsmapcanvas.cxx: In static member function 'static void QgsMapCanvas::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)': /data/src/qgis/qgis-etiennesky/build-debug/src/gui/moc_qgsmapcanvas.cxx:116:104: warning: 'void QgsMapCanvas::setProgress(int, int)' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/gui/../../../src/gui/qgsmapcanvas.h:391) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/gui/moc_qgsmapcanvas.cxx:121:40: warning: 'void QgsMapCanvas::mapCanvasRefreshed()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/gui/../../../src/gui/qgsmapcanvas.h:419) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/gui/moc_qgsmapcanvas.cxx:122:36: warning: 'void QgsMapCanvas::renderStarting()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/gui/../../../src/gui/qgsmapcanvas.h:424) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/gui/moc_qgsmapcanvas.cxx:144:32: warning: 'void QgsMapCanvas::updateMap()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/gui/../../../src/gui/qgsmapcanvas.h:356) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/build-debug/src/gui/moc_qgsmapcanvas.cxx:146:76: warning: 'void QgsMapCanvas::showError(QgsMapLayer*)' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/gui/../../../src/gui/qgsmapcanvas.h:363) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/src/gui/qgshighlight.cpp: In member function 'void QgsHighlight::init()': /data/src/qgis/qgis-etiennesky/src/gui/qgshighlight.cpp:72:64: warning: 'QgsMapRenderer* QgsMapCanvas::mapRenderer()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/src/gui/qgsmapcanvas.h:177) [-Wdeprecated-declarations] /data/src/qgis/qgis-etiennesky/src/gui/qgshighlight.cpp: In member function
Re: [Qgis-developer] Master doesn't compile
I see, sorry I didn't check the actual code... I tried changing the function to an inline one, but the moc file still triggers the deprecated warning. Unless there is an argument against it, I think Martin's suggestion to disable deprecated warnings for moc files. Etienne On Sun, Feb 23, 2014 at 1:47 PM, Martin Dobias wonder...@gmail.com wrote: Hi Etienne On Sun, Feb 23, 2014 at 11:33 PM, Etienne Tourigny etourigny@gmail.com wrote: Just a remark, there are quite a few new warnings (mostly about deprecated functions, but also some unused or variables or parameters) using gcc 4.7.3 Here are some, in no particular order, there might be more /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaplayer.cxx: In static member function 'static void QgsMapLayer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)': /data/src/qgis/qgis-etiennesky/build-debug/src/core/moc_qgsmaplayer.cxx:102:38: warning: 'void QgsMapLayer::clearCacheImage()' is deprecated (declared at /data/src/qgis/qgis-etiennesky/build-debug/src/core/../../../src/core/qgsmaplayer.h:386) [-Wdeprecated-declarations] Most of them are in files generated by MOC - maybe we could disable the deprecation warnings for those files. For the actual QGIS source code that triggers deprecation warnings, these should get sorted out. Regards Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Opening KML files.
If that's the case, you should file a bug report as kml should be supported everywhere. Did you install using the osgeo4w or standalone package? On Fri, Feb 14, 2014 at 4:33 AM, hubbatov hubba...@mail.ru wrote: libgdal was built without exif support Closed. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Opening-KML-files-tp5102244p5103735.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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] Failing tests consider blockers
Probably better to relax this for 2.2, but enforce it after release... On Fri, Feb 14, 2014 at 2:00 PM, Jürgen E. j...@norbit.de wrote: Hi Radim, On Fri, 14. Feb 2014 at 14:10:25 +0100, Radim Blazek wrote: I am suggesting to consider all failing tests as blockers. Suddenly? The tests have been broken for ages (see [1]) and nobody seems to really care. Jürgen [1] see http://dash.orfeo-toolbox.org/index.php?project=QGIS -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS PSC member (RM) Germany IRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ 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] How to display the cursor Z info in the QGis staus bar ?
you need to install the value tool plugin On Thu, Feb 13, 2014 at 5:13 AM, Geo DrinX geodr...@gmail.com wrote: Hello all, as in object, I need to display the current cursor Z info into the QGis staus bar. Of course, I have a DTM layer in QGis list:) It just exists something that does something similar ? Thank you in advance for any info about this. Regards Roberto ___ 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] New feature: RFC saving style and ui in Spatialite
Saving style as spatialite files would probably cause a significant file size overhead - don't all spatialite files take at least 3MB for the SRS tables? On Wed, Feb 5, 2014 at 10:18 AM, Gino Pirelli lui...@gmail.com wrote: Hi, I'm developing a new feature to save SLD and ui in Spatialite provider in the same way this function is available for postgres. this function developed for Faunalia is funded by ARPA Piemonte fork is available at: https://github.com/luipir/QGIS/tree/spatialite-savestyle and actual modification are localized in this commit: f058bea1fe51116b8231eb5c1ca4faee485c38b2 there are some question about how to develop it and are related how to manage XML in a sqlite/spatialite table. this code derive by the postgres provider code where QML and UI xmls are recorded in a XML column. XML is a postgres type. This type is not available in SQlite but it's available in SL 4.1 (called XmlBlob [1]) In this preliminary commit XML is saved in a text column, but saving XML as a blog (blob type in sqlite or XmlBlob in SL) have the advantage to avoid all encoding problems. so the question is... sqlite blob or spatialite xmlbob? Blob type can't allow XML parsing using SQL queries XmlBlob allows this (using libxml2) Blob type is sqlite native type XmlBlob can be used only with SL 4.1 My preference is to use native data type Blob. What's you opinion about blob/ xmlblob or whatever regards, Luigi Pirelli (luigi.pire...@faunalia.it - lui...@gmail.com) [1] https://www.gaia-gis.it/fossil/libspatialite/wiki?name=XmlBlob-intro ___ 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] QGIS SZIP.DLL Licensing?
What is the problem with distributing the szip.dll ? There is no agreement between qgis (or gdal) with szip/hdf group. My understanding of the info in this page http://www.hdfgroup.org/doc_resource/SZIP/ is: - In no circumstances a user can create hdf5 files with szip encoding within qgis. So far, only gtiff files are created within qgis. - you are correct in stating that commercial products can use szip for decoding only, so it is OK for qgis to distribute the szip library. - as qgis is not a commercial product and does not allow to create szip-encoded hdf5 files, there is no need for any commercial licence. - if someone were to write software, based on qgis (and gdal), which sould create an szip-encoded hdf5 file, that entity would require a commercial licence There is no GPL szip library, AFAIK. On Mon, Feb 3, 2014 at 3:15 PM, Moriarty, Mark F mark.f.moria...@lmco.comwrote: Does QGIS have any license agreement related to SZIP use? I'd like to use QGIS on a project, but we're stuck on whether/how the szip.dll is licensed for use. For example HDF specifically has a license page asserting permission to use szip in their distribution, so long as it is used within the context of their overall app. For a commercial firm, the permission is just to decode, not to encode, but that is fine. I tried just deleting/renaming the szip.dll, since we do not actually need the functionality for our use, but it appears to be tightly bound to the build - qgis errors-out if it does not detect a proper, functioning, szip.dll on startup. If there isn't a license statement from the intellectual property owner allowing its use/distribution to decode with qgis, is it possible to include a user-controllable switch to allow not including it, or to perhaps include a true GPL zip package, albeit losing the lossless functionality? Thanks. Mark ___ 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] EXTERNAL: Re: QGIS SZIP.DLL Licensing?
lose the SZip Rice lossless functionality, but for a lot of basic bulk unpacking 7zip is fine. *From:* Etienne Tourigny [mailto:etourigny@gmail.com] *Sent:* Monday, February 03, 2014 2:00 PM *To:* Moriarty, Mark F *Cc:* *Subject:* EXTERNAL: Re: [Qgis-developer] QGIS SZIP.DLL Licensing? What is the problem with distributing the szip.dll ? There is no agreement between qgis (or gdal) with szip/hdf group. My understanding of the info in this page http://www.hdfgroup.org/doc_resource/SZIP/ is: - In no circumstances a user can create hdf5 files with szip encoding within qgis. So far, only gtiff files are created within qgis. - you are correct in stating that commercial products can use szip for decoding only, so it is OK for qgis to distribute the szip library. - as qgis is not a commercial product and does not allow to create szip-encoded hdf5 files, there is no need for any commercial licence. - if someone were to write software, based on qgis (and gdal), which sould create an szip-encoded hdf5 file, that entity would require a commercial licence There is no GPL szip library, AFAIK. On Mon, Feb 3, 2014 at 3:15 PM, Moriarty, Mark F mark.f.moria...@lmco.com wrote: Does QGIS have any license agreement related to SZIP use? I'd like to use QGIS on a project, but we're stuck on whether/how the szip.dll is licensed for use. For example HDF specifically has a license page asserting permission to use szip in their distribution, so long as it is used within the context of their overall app. For a commercial firm, the permission is just to decode, not to encode, but that is fine. I tried just deleting/renaming the szip.dll, since we do not actually need the functionality for our use, but it appears to be tightly bound to the build - qgis errors-out if it does not detect a proper, functioning, szip.dll on startup. If there isn't a license statement from the intellectual property owner allowing its use/distribution to decode with qgis, is it possible to include a user-controllable switch to allow not including it, or to perhaps include a true GPL zip package, albeit losing the lossless functionality? Thanks. Mark ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lidar data into QGIS
There was some discussion about LAS format and PDAL on the GDAL mailing list a few weeks ago, there is probably some interesting info there. cheers Etienne On Tue, Jan 28, 2014 at 5:13 PM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. Lidar data in LAS format are increasingly widespread. Leaving aside all 3D frenzy, we would be interested in simply displaying them in QGIS, with their useful attributes (classification and intensity), either with a native driver or through an available library. All the licensing issues around libLAS/LSTools are a bit obscure to me, so I wonder if someone has already dealt with this. Any hint would be appreciated. Thanks in advance. All the best. - -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlLoAUQACgkQ/NedwLUzIr4zpgCePUoYkVf+xtWE5n0GNskWL256 0S4An34ARAD3dTfyktHatc9UuQeCb/sm =3Pbv -END PGP SIGNATURE- ___ 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] QGIS and 3D
How about using matplotlib's mplot3d ? There are already a number of plugins using matplotlib. http://matplotlib.org/mpl_toolkits/mplot3d/tutorial.html On Sat, Jan 25, 2014 at 9:30 AM, G. Allegri gioha...@gmail.com wrote: Thanks for remembering us of it. I couldn't retrieve it from the ML! Visvis seems a good approach to the visualization of 3D data in QGIS. I imagine it won't be as performant as native implementations (like osg, used by Horao) but it would be probably more portable and easy to mantain... giovanni 2014/1/25 gene martin.lal...@gmail.com You can also use Python in the Python console, look at Using/visualizing 3D data (Z values) http://osgeo-org.1560.x6.nabble.com/Using-visualizing-3D-data-Z-values-td4126375.html#a5009086 -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-and-3D-tp5099845p5099985.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Giovanni Allegri http://about.me/giovanniallegri blog: http://blog.spaziogis.it GEO+ geomatica in Italia http://bit.ly/GEOplus ___ 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] QGIS and 3D
I guess you are referring to this (French) tutorial? http://www.portailsig.org/content/qgis-representation-3d-des-couches-vectorielles-shapefiles-dits-3d-ou-shapefiles-avec-attrib On Mon, Jan 27, 2014 at 2:20 PM, gene martin.lal...@gmail.com wrote: The solution in Python reported uses matplotlib/mplot3d, Visvis and even mayavi http://code.enthought.com/projects/mayavi/ . -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-and-3D-tp5099845p5100260.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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] [RASTER][Feature] Applying scale and offset to raster data - funded Ifremer
I have made some comments and will test it with some netcdf files. It would be great to add this before feature freeze, but it is imperative that a test is in place, at least to make sure that it does not break anything with normal files. On Fri, Jan 24, 2014 at 1:30 PM, rldhont rldh...@gmail.com wrote: Hi dev, I would like my pull-request be merged before code freeze. Radim Blazek helped me to finalize it, but he would like someone else does the merge. https://github.com/rldhont/Quantum-GIS/commit/ 916f2cd6fb3de6f46c8f0fd8b0f5ae4ccbaff8ff This pull-request is also a BUGFIX #8417 incorrect value loaded from netcdf file http://hub.qgis.org/issues/8417 Who do I assign the pull-request ? Regards, René-Luc D'Hont 3Liz ___ 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] Difference for transform reference system between QGIS and GDAL
Hi, you should probably raise this on the gdal-dev mailing list... On Fri, Jan 17, 2014 at 8:56 AM, Luiz Motta motta.l...@gmail.com wrote: Andre, Thank for quickly response. The question is exact this, why the QGIS read the PRJ and understands the 'towgs84', otherwise, the GDAL don't understands, where , the QGIS use the GDAL/OGR provider ? File PRJ: PROJCS[SAD69_UTM_zone_21S,GEOGCS[GCS_SAD69,DATUM[D_South_American_1969,SPHEROID[GRS_1967_Truncated,6378160,298.2496]],PRIMEM[Greenwich,0],UNIT[Degree,0.017453292519943295]],PROJECTION[Transverse_Mercator],PARAMETER[latitude_of_origin,0],PARAMETER[central_meridian,-57],PARAMETER[scale_factor,0.9996],PARAMETER[false_easting,50],PARAMETER[false_northing,1000],UNIT[Meter,1]] Proj4 for QGIS: +proj=utm +zone=21 +south +ellps=aust_SA +towgs84=-57,1,-41,0,0,0,0 +units=m +no_defs Proj4 for GDAL: +proj=utm +zone=21 +south +ellps=aust_SA +units=m +no_defs Regards, Luiz Motta 2014/1/17 Andre Joost andre+jo...@nurfuerspam.de Am 17.01.2014 03:01, schrieb Luiz Motta: Hi all, I had differences for transform the reference system of geometries between GDAL and QGIS. I made the transform using GDAL into geometry with reference system SAD 69 UTM (EPSG 29191) to WGS 84 (EPSG 4326) . When i add in QGIS the geometries with WGS84 and SAD 69 using 'on the fly' (WGS84), has diferences positions of coordinate (see picture). The QGIS reads the reference system of shapefile different than GDAL (see layer property). I would like understand how using GDAL for transform geometries this reference system of this shapefile ? How can difference reading shapefile by QGIS and GDAL ? The shapefiles .prj file has no +towgs84 parameters, so GDAL sets them to zero. QGIS assigns the EPSG:29191 to the file, which has +towgs84 parameters. HTH, André Joost ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Luiz Motta Analista Ambiental - IBAMA/COTIG Instituto Brasileiro do Meio Ambiente dos Recursos Naturais - IBAMA IBAMA - SCEN Trecho 2 - Ed. Sede - Cx. Postal nº 09566 CEP 70818-900 - Brasília-DF Tel: 61.3316-1807 Skype: ibama_luiz-motta ___ 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] please help me :(
also, why would you build qgis 1.7 which is an old release? On Thu, Jan 9, 2014 at 10:08 PM, otmane yazidi alaoui yazidiotm...@gmail.com wrote: i have this problem [ 0%] Built target svnversion [ 1%] Built target t2tdoc [ 17%] Built target qgis_core [ 24%] Built target ui [ 34%] Built target qgis_gui [ 37%] Built target qgis_analysis [ 63%] Built target qgis [ 66%] Built target translations [ 66%] Built target compile_python_files [ 67%] Built target python_module_qgis_analysis [ 67%] Building CXX object python/CMakeFiles/python_module_qgis_core.dir/core/sipcorepart0.cpp.o [ 67%] Building CXX object python/CMakeFiles/python_module_qgis_core.dir/core/sipcorepart1.cpp.o /home/alaoui/dev/cpp/qtcreator-build-qgis/python/core/sipcorepart1.cpp: In function ‘PyObject* meth_QgsSymbolV2_renderHints(PyObject*, PyObject*)’: /home/alaoui/dev/cpp/qtcreator-build-qgis/python/core/sipcorepart1.cpp:6719:42: error: passing ‘const QgsSymbolV2’ as ‘this’ argument of ‘int QgsSymbolV2::renderHints()’ discards qualifiers [-fpermissive] /home/alaoui/dev/cpp/qtcreator-build-qgis/python/core/sipcorepart1.cpp: In function ‘PyObject* meth_QgsSymbolV2RenderContext_setSelected(PyObject*, PyObject*)’: /home/alaoui/dev/cpp/qtcreator-build-qgis/python/core/sipcorepart1.cpp:7121:35: error: passing ‘const QgsSymbolV2RenderContext’ as ‘this’ argument of ‘void QgsSymbolV2RenderContext::setSelected(bool)’ discards qualifiers [-fpermissive] make[2]: *** [python/CMakeFiles/python_module_qgis_core.dir/core/sipcorepart1.cpp.o] Error 1 make[1]: *** [python/CMakeFiles/python_module_qgis_core.dir/all] Error 2 make: *** [all] Error 2 00:03:40: Le processus /usr/bin/make s'est terminé avec le code 2. Erreur à la compilation du projet qgis1.7.0 (cible : Desktop) Lors de l'exécution de l'étape Make --- -- YAZIDI ALAOUI OTMANE Ingénieur d'état en Géomatique Tel:+212652538743 @ :yazidiotm...@gmail.com http://www.doyoubuzz.com/otmane-yazidi-alaoui // ___ 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] Master segfault on close
I have the same problem, see the bug report (closed as invalid) and add any information It is somehow related to the gdal build, because if I used libgdal-dev from ubuntugis my qgis build is ok. http://hub.qgis.org/issues/8932 On Thu, Nov 28, 2013 at 5:50 PM, rldhont rldh...@gmail.com wrote: Hi dev, I'm on Ubuntu 13.04 (raring) and my QGIS master segfault on close. No need to open a layer to have this. *** Error in `/***/***/***/build/bin/qgis': corrupted double-linked list: 0x024b4830 *** Am I the only one ? René-Luc D'Hont 3Liz ___ 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] Multi threading and background processing
My personal experience with numpy/scipy is that it is very slow for generic computation (aside from matrix operations) compared to c/c++/fortran, so I'm not sure it would be good for an efficient fire spread algorithm, with non-trivial number crunching. On Fri, Nov 22, 2013 at 5:33 AM, Martin Dobias wonder...@gmail.com wrote: On Thu, Nov 21, 2013 at 6:00 AM, Tom Moore moor...@gmail.com wrote: As you can imagine from my newbie questions I'm not a python guy. While I really like a lot of the modern mechanisms in python I have never been able to look at a python script without being puzzled by the retro/hipster nature of using whitespace as syntax. As someone who once lined up fortran statements on punch cards you will have to pry whitespace indifferent languages from my cold hunt-n-peck fingers. Anyway, I'm expecting to use python for the ui and glue code, and do all of the number crunching in a C module. Horses for courses eh? Let me note one more thing here: if you think of writing number crunching in C, things will get more complicated: you will need to compile and ship the binaries somehow - the plugin repository does not accept plugins with architecture dependent binaries. Maybe try to have a look at numpy module, it's fairly common for fast array/matrix operations in python. Martin ___ 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] VTerrain plugin - version 1.0 ( QGis 1.5 - 2.0.1 )
You need to provide your osgeo user id and password. To recover your lost password go to the osgeo page at https://www.osgeo.org/user On Mon, Oct 14, 2013 at 12:52 PM, Geo DrinX geodr...@gmail.com wrote: Hello all, I have problems to upload my new version of VTerrain plugin for QGis, because I lost the passw for http://plugins.qgis.org/plugins/VTerrain/ :( could you please contact me ? Thank you Roberto ___ 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] Reliable way to determine a groupIndex in the legend tree
On Fri, Oct 11, 2013 at 8:35 AM, Vincent Schut sc...@sarvision.nl wrote: On 10/11/13 11:48, Sandro Santilli wrote: On Fri, Oct 11, 2013 at 09:33:05AM +, Andreas Neumann wrote: Am 11.10.2013 09:22, schrieb Sandro Santilli: On Fri, Oct 11, 2013 at 09:13:03AM +, Duarte Carreira wrote: The group checkbox, imho, should *not always* switch children on/off. You should have a modifier to get this as a secondary behavior, like pressing the ctrl key when (un)checking the group checkbox. The primary behavior of the group switch should be to make the children invisible or visible, regardless of the children's visibility being on or off. In the primary behavior when the parent is turned OFF, the children are not drawn but retain their checked or uncheck status. If you use the secondary behavior then unchecking the parent will uncheck the children. Same would apply when checking the parent on. Agreed, sounds like a sensible behavior to me. Yes, a sensible behavior. But there is still use-case for the radio-button like behaviour. Imagine having a group with a series of orthoimages of different years and you quickly want to see each year. In this case, the radio-button behaviour would save you one click. So I don't think that this contradicts the other proposal listed above here. Maybe this could be obtained with secondary behavior (SHIFT-click) on layers, but it sounds like something that easily becomes confusing (conflicting with radio-on-groups, undefined behavior for unchecking etc.). switching between several raster layers is exactly the main (only) use I have for this, and as we are mainly doing remote sensing stuff here, including lots of time series, it is something I really frequently miss. (Practical example: you have several Landsat rasters from different times for the same area, all of them have clouds but not in the same place. By switching between layers, you can easily get a 'cloudfree' view of the entire area.) I have made the Loop Visible Layers plugin for just that. Add the reaster layers you want to see in a group, then select that group in the Loop Visible Layers dock and click play. You will see those raster layers one at a time. IMHO 'undefined behavior for unchecking' should not be a problem; usually unchecking simply is disabled for radio groups. I do not know any UI with radio groups where you can uncheck a selected item by clicking it again... I think having it as a secondary behaviour is just confusing. I'd rather see groups have a 'selection type' property, which defines the selection behaviour within that group (and on that level only). Could you explain what you mean with 'conflicting with radio-on-groups' (what are 'radio-on-groups')? Vincent. --strk; __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://lists.osgeo.org/mailman/listinfo/qgis-developer __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://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] test new android package
Installed on my Nexus 7 without any issues. However, cannot install any python plugins dues to lack of python. Cheers Etienne On Fri, Oct 11, 2013 at 5:42 AM, Roel Vanhout roel.vanh...@gmail.comwrote: Tried on a Nexus 10 tablet, install worked OK. Only 'issue' is cosmetic; after the message that I need to install the 'necessitas' runtime, I'm redirected to the play store. When I return from that, I get the message (in qgis) 'necessitas not found' and I need to restart to resume the in-app installation procedure to continue. Apart from that, is this meant to be more than a proof of concept / pre-alpha? Does it make sense for me to report bugs yet? cheers, roel On Thu, Oct 10, 2013 at 6:55 PM, Marco Bernasocchi ma...@bernawebdesign.ch wrote: Hi all, I've been working on creating an android packae that is smaller than 50mb to fit the playstore. the pakage now includes only a small subset of the needed libs, all other libs are downloaded on the first run by ministro. all in all you will be downloding about 30mb for the apk plus 200mb dependencies plus 40mb qt, so do it on a wifi, i know it got bigger (used to be 150mb apk), but the adventage is that now qgis is small enough for the market (thus update notification will be available) and for each update you will have to rownload only what actually changed. To achieve this, I created a reporitory at http://android.qgis.org/** repository/ http://android.qgis.org/repository/ that can actually be used by any android qt app that needs any of the available libs. so please, help me test this package and just report if the installation worked and you could start QGIS. thanks a lot Marco https://db.tt/sBa0e2Pu -- Marco Bernasocchi http://opengis.ch __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] install instructions
On Fri, Sep 27, 2013 at 4:11 PM, stevenhorner ste...@stevenhorner.comwrote: I had similar problems installing on raring, like you I had both listed, but now use these instructions disable any other source you may have added: sudo apt-get install python-software-properties sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable sudo apt-get update sudo apt-get install qgis python-qgis qgis-plugin-grass This installs but you may get an error when starting QGIS on Ubuntu which is normally because the owner of the .QGIS2 folder is Root rather than your logon user. You may need to change this. I experienced the same problem (.qgis2 folder created by root). Is that folder created by qgis installation? Probably, but very odd. This is a BIG bug and should be fixed, is there a bug report on this? Etienne Once QGIS successfully opens you are likely to still have problems with the Processing Toolbox (formerly SEXTANTE) if you want to use its GRASS commands or GDAL. I have been trying for several weeks now to get the GRASS commands in Processing to work on either Windows or Ubuntu (raring or precis) without any success, most recently GDAL isn't configured correctly for the processing Toolbox. I have tried various releases from 1.80, 1.9, 2.0.1 and 2.1.0-master. If you don't need the Processing Toolbox you should find most other things are a great improvement over 1.8. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/install-instructions-tp5080617p5080629.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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] install instructions
On Fri, Sep 27, 2013 at 4:25 PM, stevenhorner ste...@stevenhorner.comwrote: Etienne Tourigny-3 wrote On Fri, Sep 27, 2013 at 4:11 PM, stevenhorner lt; steven@ gt;wrote: I had similar problems installing on raring, like you I had both listed, but now use these instructions disable any other source you may have added: sudo apt-get install python-software-properties sudo add-apt-repository ppa:ubuntugis/ubuntugis-unstable sudo apt-get update sudo apt-get install qgis python-qgis qgis-plugin-grass This installs but you may get an error when starting QGIS on Ubuntu which is normally because the owner of the .QGIS2 folder is Root rather than your logon user. You may need to change this. I experienced the same problem (.qgis2 folder created by root). Is that folder created by qgis installation? Probably, but very odd. This is a BIG bug and should be fixed, is there a bug report on this? Etienne Yes it's on the issue list here: http://hub.qgis.org/issues/8613 http://hub.qgis.org/issues/8613 sorry just saw that a few minutes ago! -- View this message in context: http://osgeo-org.1560.x6.nabble.com/install-instructions-tp5080617p5080633.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ 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] Add yourself to the QGIS Contributor Map
where can we see the actual, updated map? The source is in the master tree, but I have not seen in in the QGIS about dialogs. cheers On Fri, Sep 20, 2013 at 4:54 AM, Tim Sutton li...@linfiniti.com wrote: Hi On Fri, Sep 20, 2013 at 1:55 AM, Etienne Tourigny etourigny@gmail.com wrote: I get a blank document It should be back now Regards Tim On Thu, Sep 19, 2013 at 6:35 PM, Tim Sutton li...@linfiniti.com wrote: Hi On Thu, Sep 19, 2013 at 3:12 PM, Gino Pirelli lui...@gmail.com wrote: I can change to Unknow... that date was related to my repo. I presented code in Brighton but I can't do pull request until some burocratic problems are resolved. But it's ok leaving with unknow (as pcav)... but I prefer to stay in this list because my last tree month of work in the communtiy it it's not a problem, obviously. thanks, Luigi Pirelli (luigi.pire...@faunalia.it) Just put the date of your first contribution if you know it. Regards Tim On 19 September 2013 14:38, Borys Jurgiel li...@borysjurgiel.plwrote: Please everybody check your first commit date. By setting JEF's first contribution to 2013 we seriously mess the Earth history :) Gino's date looks suspicious too. I haven't check others. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Infrastructure for plugin settings
Denis, I like the idea of having a dictionnary for the values a settings can have. Do you think that my work on a tree view for all settings [1] can be merged with yours into core c++? There could be 2 ways to open a settings dialog, one for all settings like I have done, and one for just a particular plugin (by limiting which settings are shown in the tree). [1] https://github.com/qgis/QGIS/pull/878 cheers Etienne On Wed, Sep 11, 2013 at 9:17 AM, Denis Rouzaud denis.rouz...@gmail.comwrote: On 09/11/2013 02:12 PM, Borys Jurgiel wrote: Dnia czwartek, 5 września 2013 15:00:31 Denis Rouzaud pisze: I have made some publicity before for a library which handles plugin settings. http://3nids.github.io/**qgissettingmanager/http://3nids.github.io/qgissettingmanager/ Basically, the idea is that it you create once the settings somewhere in your plugin and then it handles type validation, defaut values, etc. The most interesting part is that you have a SettingDialog class, which automatically read/write widgets if you name them accordingly to the settings (it handles several widgets for all the different types of settings). This small lib is very time saving for the few plugins I have. It looks great! Especially with setValueOnWidgetUpdate=True, as I understand, I'm able to make interactive settings (reading values in the runtime, setting one widget depending on other widget value), without any need of direct access to widgets, I mean staying purely within this layer of abstraction. It's really nice. Of course, I understand graying out widgets and changing list of combobox' items still needs direct access. Maybe an idea would be to translate this to a QgsPluginSetting class which would then list all the settings to be edited in the main plugin setting window. Similarly to Alex, I prefer interactive and aesthetically hand-polished gui ;) So for my plugins I only can imagine the common settings tree as something additional, an 'advanced' mode. Anyway, let's talk about it on the HF! So do I. But you could use this library to create the settings, and it would automatically add them to the infrastructure. Then, fell free to set your own UI or not. See you tomorrow! __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://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] Add yourself to the QGIS Contributor Map
That's pretty cool! If we can include this page in a new tab in the about dialog that would be nice. cheers Etienne On Sat, Sep 21, 2013 at 8:44 PM, Tim Sutton li...@linfiniti.com wrote: Hi On Sat, Sep 21, 2013 at 8:43 PM, Etienne Tourigny etourigny@gmail.com wrote: where can we see the actual, updated map? The source is in the master tree, but I have not seen in in the QGIS about dialogs. If you go here https://github.com/qgis/QGIS/blob/master/doc/contributors.json you will see it on a map. I used the map in the keynote speech at foss4g2013. In future versions of QGIS, sure we could include it somewhere in a dialog of you thought that would be a useful thing to do. Regards Tim cheers On Fri, Sep 20, 2013 at 4:54 AM, Tim Sutton li...@linfiniti.com wrote: Hi On Fri, Sep 20, 2013 at 1:55 AM, Etienne Tourigny etourigny@gmail.com wrote: I get a blank document It should be back now Regards Tim On Thu, Sep 19, 2013 at 6:35 PM, Tim Sutton li...@linfiniti.comwrote: Hi On Thu, Sep 19, 2013 at 3:12 PM, Gino Pirelli lui...@gmail.comwrote: I can change to Unknow... that date was related to my repo. I presented code in Brighton but I can't do pull request until some burocratic problems are resolved. But it's ok leaving with unknow (as pcav)... but I prefer to stay in this list because my last tree month of work in the communtiy it it's not a problem, obviously. thanks, Luigi Pirelli (luigi.pire...@faunalia.it) Just put the date of your first contribution if you know it. Regards Tim On 19 September 2013 14:38, Borys Jurgiel li...@borysjurgiel.plwrote: Please everybody check your first commit date. By setting JEF's first contribution to 2013 we seriously mess the Earth history :) Gino's date looks suspicious too. I haven't check others. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Irc: timlinux on #qgis at freenode.net == -- Tim Sutton - QGIS Project Steering Committee Member == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] cpt-city missing colour ramps?
Jurgen has just fixed this in the osgeo4w scripts in both master and release_2_0 branches - thanks. I have also commited to master a fix to show all ramps by default when opening cpt-city dialog, instead of an empty screen. cheers Etienne On Fri, Sep 20, 2013 at 3:15 AM, Paolo Cavallini cavall...@faunalia.itwrote: On 2013-09-20 02:54, Etienne Tourigny wrote: I have tried both local install and install from ubuntugis-unstable (2.0.1 in Linux Mint 15-raring) and the color ramps seem ok. we spotted this on Windows machines. UNfortuynately this was during a short workshop, and could not test further. Perhaps the problem is that no ramps appear, until you click on one of the categories? tried. Merci. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/**calendariohttp://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] cpt-city missing colour ramps?
I will look into this today. which package(s)/platform(s) does this problem appear? On Wed, Sep 18, 2013 at 6:17 AM, Paolo Cavallini cavall...@faunalia.itwrote: Hi Etienne, Juergen, any chance for a last minute fix to this? Looks simple, maybe just a packaging bug. Thanks. Original Message Subject: Re: [Qgis-developer] cpt-city missing colour ramps? Date: 2013-09-17 14:42 From: skampus stefano.campus@regione.**piemonte.itstefano.cam...@regione.piemonte.it To: qgis-developer@lists.osgeo.org yes it happens to me too. first i have updated the cpt version to 2.09 but the problem was still there. it seems that firstly the path of installation directory has not been written in dialogue window. now it works... -- View this message in context: http://osgeo-org.1560.x6.** nabble.com/cpt-city-missing-**colour-ramps-**tp5078247p5078255.htmlhttp://osgeo-org.1560.x6.nabble.com/cpt-city-missing-colour-ramps-tp5078247p5078255.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://lists.osgeo.org/mailman/listinfo/qgis-developer -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/**calendariohttp://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] cpt-city missing colour ramps?
I have tried both local install and install from ubuntugis-unstable (2.0.1 in Linux Mint 15-raring) and the color ramps seem ok. Perhaps the problem is that no ramps appear, until you click on one of the categories? Can someone confirm that this is the issue (not that ramps are not available). regards, Etienne On Thu, Sep 19, 2013 at 8:51 PM, Etienne Tourigny etourigny@gmail.comwrote: I will look into this today. which package(s)/platform(s) does this problem appear? On Wed, Sep 18, 2013 at 6:17 AM, Paolo Cavallini cavall...@faunalia.itwrote: Hi Etienne, Juergen, any chance for a last minute fix to this? Looks simple, maybe just a packaging bug. Thanks. Original Message Subject: Re: [Qgis-developer] cpt-city missing colour ramps? Date: 2013-09-17 14:42 From: skampus stefano.campus@regione.**piemonte.itstefano.cam...@regione.piemonte.it To: qgis-developer@lists.osgeo.org yes it happens to me too. first i have updated the cpt version to 2.09 but the problem was still there. it seems that firstly the path of installation directory has not been written in dialogue window. now it works... -- View this message in context: http://osgeo-org.1560.x6.** nabble.com/cpt-city-missing-**colour-ramps-**tp5078247p5078255.htmlhttp://osgeo-org.1560.x6.nabble.com/cpt-city-missing-colour-ramps-tp5078247p5078255.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://lists.osgeo.org/mailman/listinfo/qgis-developer -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/**calendariohttp://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Infrastructure for plugin settings
I have implemented something like this some time ago, based on a gui from QT - Settings Editor. I am not sure if I never commited it or if someone removed it. I will try to find the code and submit a pull request. Etienne On Thu, Sep 5, 2013 at 5:12 AM, Victor Olaya vola...@gmail.com wrote: The idea is to have that common place for all settings. The bad thing that I see (and some people have told me), is that it might be difficult to find for a user that searches for a configuration panel for a given plugin, since he might look for it in the menu of that plugin. A solution to that would be to make it easy to call the settigns dialog, but open in the tab (or panel, or whatever), corresponding to a given plugin. So there would be a plugin options menu, with all options, but a plugin author could add a shortcut to that and add a setting of my plugin menu entry which would go straight to those settings. The thing is to avoid developers creating their own panels and dialogs for settings, which is time consuming and each one looks differently. I would suggest a design similar to the eclipse one, with a tree in the left hand side where you have all plugins, and once you select one, you see all its parameters in the right-hand side panel. If anyone is interested, we can discuss this in the HF. It looks to me like a nice thing to work on, and we can also adapt some existing plugins to use it, once it is done. cheers Víctor 2013/9/5 Matthias Kuhn matthias.k...@gmx.ch: Hi, Other applications have unified setting centers like firefox when you enter about:config in the URL bar. But this is in addition to the settings dialog(s) which is/are still offered. Are you thinking about something like this? A simple config value editor, like regedit? Or is the aim of this project a unified config dialog, where plugins register their own tab (or list entry or whatsoever)? In this case, would it be a new dialog Plugin Options which would act as container for all options? Or opening up the Options dialog for registering additional tabs? IMO the first one has the drawback of brandmarking plugins as 3rd-party, not fully integrated, while the second one has the drawback/risk of cluttering this dialog. Talking about this, I recently did a similar thing for the vector layer properties (add the possibility to add a new tab for plugins. POC implemented in form of layer specific globe settings, not yet merged) Cheers Matthias ___ 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] Infrastructure for plugin settings
the work I have is a dialog in core, in src/gui folder. It is opened via a new menu item in the Settings menu. Preliminary support for custom settings and description. Perhaps both could be merged into a single gui class which would be available to core and plugins? code and screenshot in this pull request: https://github.com/qgis/Quantum-GIS/pull/878 On Thu, Sep 5, 2013 at 10:14 AM, Victor Olaya vola...@gmail.com wrote: So it seems that at least two people had worked on this previously... I am glad that I asked :-) Let's see if we can put all that together and make it more visible, so people can use it easily Cheers Victor 2013/9/5 Denis Rouzaud denis.rouz...@gmail.com: I have made some publicity before for a library which handles plugin settings. http://3nids.github.io/qgissettingmanager/ Basically, the idea is that it you create once the settings somewhere in your plugin and then it handles type validation, defaut values, etc. The most interesting part is that you have a SettingDialog class, which automatically read/write widgets if you name them accordingly to the settings (it handles several widgets for all the different types of settings). This small lib is very time saving for the few plugins I have. Maybe an idea would be to translate this to a QgsPluginSetting class which would then list all the settings to be edited in the main plugin setting window. Cheers, Denis On 09/05/2013 02:47 PM, Etienne Tourigny wrote: I have implemented something like this some time ago, based on a gui from QT - Settings Editor. I am not sure if I never commited it or if someone removed it. I will try to find the code and submit a pull request. Etienne On Thu, Sep 5, 2013 at 5:12 AM, Victor Olaya vola...@gmail.com wrote: The idea is to have that common place for all settings. The bad thing that I see (and some people have told me), is that it might be difficult to find for a user that searches for a configuration panel for a given plugin, since he might look for it in the menu of that plugin. A solution to that would be to make it easy to call the settigns dialog, but open in the tab (or panel, or whatever), corresponding to a given plugin. So there would be a plugin options menu, with all options, but a plugin author could add a shortcut to that and add a setting of my plugin menu entry which would go straight to those settings. The thing is to avoid developers creating their own panels and dialogs for settings, which is time consuming and each one looks differently. I would suggest a design similar to the eclipse one, with a tree in the left hand side where you have all plugins, and once you select one, you see all its parameters in the right-hand side panel. If anyone is interested, we can discuss this in the HF. It looks to me like a nice thing to work on, and we can also adapt some existing plugins to use it, once it is done. cheers Víctor 2013/9/5 Matthias Kuhn matthias.k...@gmx.ch: Hi, Other applications have unified setting centers like firefox when you enter about:config in the URL bar. But this is in addition to the settings dialog(s) which is/are still offered. Are you thinking about something like this? A simple config value editor, like regedit? Or is the aim of this project a unified config dialog, where plugins register their own tab (or list entry or whatsoever)? In this case, would it be a new dialog Plugin Options which would act as container for all options? Or opening up the Options dialog for registering additional tabs? IMO the first one has the drawback of brandmarking plugins as 3rd-party, not fully integrated, while the second one has the drawback/risk of cluttering this dialog. Talking about this, I recently did a similar thing for the vector layer properties (add the possibility to add a new tab for plugins. POC implemented in form of layer specific globe settings, not yet merged) Cheers Matthias ___ 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Pull request responsibility
On Thu, Sep 5, 2013 at 1:44 PM, Sandro Santilli s...@keybit.net wrote: On Thu, Sep 05, 2013 at 06:15:18PM +0200, Matthias Kuhn wrote: Marco is looking for an option to enable these notifications. In case there's nothing I think we should open a ticket on github's github page (I just guess there is one :-) ) I shortly checked, the information would be present in the github API, but honestly, we got enough issues to solve in our software. Remember github is not free software... How about disabling pull requests from github as a whole and rely on the existing bug tracker for that ? It's just a matter of including someone's repository url and branch name to make a pull request, and there's even a convenience `git request-pull` command to generate the text for you. or attach a link to the pull request in the bug report... --strk; ___ 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] ImportError: No module named Qsci
sorry for sending the message too early. I have installed python-qscintilla2 and qgis loads without error. It seems to me it would be better to detect for Qsci ? cheers Etienne On Wed, Sep 4, 2013 at 11:33 AM, Etienne Tourigny etourigny@gmail.comwrote: I have just pulled recent code from master, built and compiled and I have an error from sextant (R) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] ImportError: No module named Qsci
I have just pulled recent code from master, built and compiled and I have an error from sextant (R) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] FIX BUG #8473 Cannot rename layers in composer legend
you should create a pull request On Mon, Aug 19, 2013 at 9:31 AM, rldhont rldh...@gmail.com wrote: Hi all, The bug 8473 'Cannot rename layers in composer legend' is marked as Blocker. http://hub.qgis.org/issues/**8473 http://hub.qgis.org/issues/8473 I have created a branch to supply a patch : https://github.com/rldhont/**Quantum-GIS/tree/8473https://github.com/rldhont/Quantum-GIS/tree/8473 You can see the diff : https://github.com/rldhont/**Quantum-GIS/commit/** f3edd5445520030c75880109677fb1**751cc9d7e1https://github.com/rldhont/Quantum-GIS/commit/f3edd5445520030c75880109677fb1751cc9d7e1 If you validate this patch I can push it. Regards, René-Luc D'Hont 3Liz __**_ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/**mailman/listinfo/qgis-**developerhttp://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] Ubuntu QGIS Master package
then you should be using the qgis builds that link to ubuntugis-unstable http://hub.qgis.org/projects/quantum-gis/wiki/Download#263-Master see section 2.6.3.2 ubuntugis On Tue, Aug 6, 2013 at 4:12 PM, Jeremy Palmer jpal...@linz.govt.nz wrote: Hi Jürgen, Right. Is there anything wrong with our ubuntugis nightly builds? The only problem is the nightly build links to the gdal 1.7 lib which is very old now. When I test the latest QGIS master build I also want to see it in the context of a much newer gdal. A newer gdal such as 1.9 or 1.10 provides FileGDB support, much better UTF-8 fixes and a large number bug fixes. Cheers, Jeremy This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or i...@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank You. ___ 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] update plugin to QGIS 2.0
from the api http://www.qgis.org/api/classQgsRasterIdentifyResult.html#a8537d25fdff215e7e9650b71a0a16783 results() returns a QMapint, QVariant (one item for each band), it does not return a tuple, so you should actually call ident = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() and then test that ident is not empty (i,e. ident is not None and ident.iterkeys() is not None) for each band, if the point is outside of the raster extent or is nodata, the value will be a null QVariant (i.e. QVariant()) which in python is None. cheers Etienne On Fri, Aug 2, 2013 at 7:13 AM, Otto Dassau das...@gbd-consult.de wrote: Hi, thanks for your hints, I think I am on the right track now. I had a look at the value tool plugin and tried to adapt the method accordingly: def sampleRaster20(self, layer, x, y): #success, data = layer.dataProvider().identify(QgsPoint(x,y)) success, data = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() for band, value in data.items(): return value But now I get another error message File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 448, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 454, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 526, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 300, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 285, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y), QgsRaster.IdentifyFormatValue ).results() ValueError: need more than 1 value to unpack Do you have an idea for this, too? Thanks Otto Am Thu, 1 Aug 2013 16:00:08 -0300 schrieb Etienne Tourigny etourigny@gmail.com: Have a look at the source of the value tool plugin, it calls the identify() method and has been updated to 2.0 api. Etienne On Thu, Aug 1, 2013 at 1:58 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, I want to update a plugin from 1.8 to QGIS 2.0 and it throws following error: Traceback (most recent call last): File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 447, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 453, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 514, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 299, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 284, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y)) TypeError: QgsRasterDataProvider.identify(QgsPoint, QgsRaster.IdentifyFormat, QgsRectangle theExtent=QgsRectangle(), int theWidth=0, int theHeight=0): not enough arguments I found at http://hub.qgis.org/wiki/quantum-gis/API_changes_for_version_20 the section QgsRasterDataProvider which should fit. And the Method, where I assume the error occurs should be this # get value at mouse position QGIS = 1.8 (working for 1.8) def sampleRaster18(self, layer, x, y): success, data = layer.identify(QgsPoint(x,y)) for band, value in data.items(): return value now what I tried but doesn't work (see error above) # get value at mouse position QGIS = 2.0 (not working yet :() def sampleRaster20(self, layer, x, y): success, data = layer.dataProvider().identify(QgsPoint(x,y)) for band, value in data.items(): return value my problem is, that I don't understand how to implement in sampleRaster20 the new method from the API_changes_for_version_20 website which says: QMapint, QVariant identify( const QgsPoint thePoint, IdentifyFormat theFormat, const QgsRectangle theExtent = QgsRectangle(), int theWidth = 0, int theHeight = 0 ) can anybody help? Thanks Otto ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Geoinformatik Büro Dassau - http://www.gbd-consult.de FOSSGIS consulting , training , support and analysis Ackerstrasse 144c , D - 40233 Düsseldorf , Germany Tel: +49-(0)211-47468178 , Mobil: +49-(0)171-4687540 -- Community Advisor - QGIS Project
Re: [Qgis-developer] update plugin to QGIS 2.0
On Fri, Aug 2, 2013 at 9:37 AM, Matthias Kuhn matthias.k...@gmx.ch wrote: Hi On Fre 02 Aug 2013 13:50:08 CEST, Etienne Tourigny wrote: for each band, if the point is outside of the raster extent or is nodata, the value will be a null QVariant (i.e. QVariant()) which in python is None. It will be a QPyNullVariant so doing value = QPyNullVariant( int ) if not value: print 'Is NULL' else: print 'Is not NULL' if value is None: print 'Is None' else: print 'Is NOT None' will print: Is NULL Is NOT None Hi, I was not referring to the value of QPyNullVariant( int ), but the value that results() would return in the case of nodata (which is QVariant() in the c++ code) unless mistaken, that would be converted to None by Sip - or am I wrong? Sorry for the smart-arsing ;) -- Matthias cheers Etienne On Fri, Aug 2, 2013 at 7:13 AM, Otto Dassau das...@gbd-consult.de wrote: Hi, thanks for your hints, I think I am on the right track now. I had a look at the value tool plugin and tried to adapt the method accordingly: def sampleRaster20(self, layer, x, y): #success, data = layer.dataProvider().identify(QgsPoint(x,y)) success, data = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() for band, value in data.items(): return value But now I get another error message File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 448, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 454, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 526, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 300, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 285, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y), QgsRaster.IdentifyFormatValue ).results() ValueError: need more than 1 value to unpack Do you have an idea for this, too? Thanks Otto Am Thu, 1 Aug 2013 16:00:08 -0300 schrieb Etienne Tourigny etourigny@gmail.com: Have a look at the source of the value tool plugin, it calls the identify() method and has been updated to 2.0 api. Etienne On Thu, Aug 1, 2013 at 1:58 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, I want to update a plugin from 1.8 to QGIS 2.0 and it throws following error: Traceback (most recent call last): File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 447, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 453, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 514, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 299, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 284, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y)) TypeError: QgsRasterDataProvider.identify(QgsPoint, QgsRaster.IdentifyFormat, QgsRectangle theExtent=QgsRectangle(), int theWidth=0, int theHeight=0): not enough arguments I found at http://hub.qgis.org/wiki/quantum-gis/API_changes_for_version_20 the section QgsRasterDataProvider which should fit. And the Method, where I assume the error occurs should be this # get value at mouse position QGIS = 1.8 (working for 1.8) def sampleRaster18(self, layer, x, y): success, data = layer.identify(QgsPoint(x,y)) for band, value in data.items(): return value now what I tried but doesn't work (see error above) # get value at mouse position QGIS = 2.0 (not working yet :() def sampleRaster20(self, layer, x, y): success, data = layer.dataProvider().identify(QgsPoint(x,y)) for band, value in data.items(): return value my problem is, that I don't understand how to implement in sampleRaster20 the new method from the API_changes_for_version_20 website which says: QMapint, QVariant identify( const QgsPoint thePoint, IdentifyFormat theFormat, const QgsRectangle theExtent = QgsRectangle(), int theWidth = 0, int theHeight = 0 ) can anybody help? Thanks Otto ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Geoinformatik Büro Dassau - http://www.gbd-consult.de FOSSGIS consulting , training , support and analysis Ackerstrasse 144c , D
Re: [Qgis-developer] update plugin to QGIS 2.0
On Fri, Aug 2, 2013 at 10:22 AM, Matthias Kuhn matthias.k...@gmx.ch wrote: On Fre 02 Aug 2013 15:13:04 CEST, Etienne Tourigny wrote: On Fri, Aug 2, 2013 at 9:37 AM, Matthias Kuhn matthias.k...@gmx.ch wrote: Hi On Fre 02 Aug 2013 13:50:08 CEST, Etienne Tourigny wrote: for each band, if the point is outside of the raster extent or is nodata, the value will be a null QVariant (i.e. QVariant()) which in python is None. It will be a QPyNullVariant so doing value = QPyNullVariant( int ) if not value: print 'Is NULL' else: print 'Is not NULL' if value is None: print 'Is None' else: print 'Is NOT None' will print: Is NULL Is NOT None Hi, I was not referring to the value of QPyNullVariant( int ), but the value that results() would return in the case of nodata (which is QVariant() in the c++ code) unless mistaken, that would be converted to None by Sip - or am I wrong? The SIP API v2 for QVariant defines: An Invalid QVariant will be represented as None A Null QVariant will be represented as QPyNullVariant [1] Except for feature attributes (e.g. for a vectorlayer: feature['attr']) which is patched by QGIS to become None in case of a Null value. thanks for the clarification Although it seems that testing for None does the trick,,. In the case of nodata pixels this test does seem to work: bandvalue = ident[iband] if bandvalue is None: bandvalue = no data and in c++ nodata pixels are defined as QVariant() (i.e. a null QVariant) Matthias [1] http://pyqt.sourceforge.net/Docs/PyQt4/python_v3.html#qvariant Sorry for the smart-arsing ;) -- Matthias cheers Etienne On Fri, Aug 2, 2013 at 7:13 AM, Otto Dassau das...@gbd-consult.de wrote: Hi, thanks for your hints, I think I am on the right track now. I had a look at the value tool plugin and tried to adapt the method accordingly: def sampleRaster20(self, layer, x, y): #success, data = layer.dataProvider().identify(QgsPoint(x,y)) success, data = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() for band, value in data.items(): return value But now I get another error message File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 448, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 454, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 526, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 300, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 285, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y), QgsRaster.IdentifyFormatValue ).results() ValueError: need more than 1 value to unpack Do you have an idea for this, too? Thanks Otto Am Thu, 1 Aug 2013 16:00:08 -0300 schrieb Etienne Tourigny etourigny@gmail.com: Have a look at the source of the value tool plugin, it calls the identify() method and has been updated to 2.0 api. Etienne On Thu, Aug 1, 2013 at 1:58 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, I want to update a plugin from 1.8 to QGIS 2.0 and it throws following error: Traceback (most recent call last): File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 447, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 453, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 514, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 299, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 284, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y)) TypeError: QgsRasterDataProvider.identify(QgsPoint, QgsRaster.IdentifyFormat, QgsRectangle theExtent=QgsRectangle(), int theWidth=0, int theHeight=0): not enough arguments I found at http://hub.qgis.org/wiki/quantum-gis/API_changes_for_version_20 the section QgsRasterDataProvider which should fit. And the Method, where I assume the error occurs should be this # get value at mouse position QGIS = 1.8 (working for 1.8) def sampleRaster18(self, layer, x, y): success, data = layer.identify(QgsPoint(x,y)) for band, value in data.items(): return value now what I tried but doesn't work (see error above) # get value at mouse
Re: [Qgis-developer] update plugin to QGIS 2.0
On Fri, Aug 2, 2013 at 11:58 AM, Otto Dassau das...@gbd-consult.de wrote: Hi, thanks for the hint. And if I need the value of the raster? If I understand correctly, ident will always be 1, if I have a 1 band raster layer. But how can I get the value at QgsPoint(x,y) of the raster? I don't understand that from the value tool plugin. no, ident will be a dict with an element of key 1 you get exactly the fist band's value at the point with ident[1] . the key of the map is the band number, and the value is the value (or None if nodata/out of bounds) so without any error checking you would do ident = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() return ident[1] cheers Etienne In QGIS 1.8 I use : success, data = layer.identify(QgsPoint(x,y)) for band, value in data.items(): return value and in QGIS 2.0: ident = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() ? Thanks again Otto Am Fri, 2 Aug 2013 08:50:08 -0300 schrieb Etienne Tourigny etourigny@gmail.com: from the api http://www.qgis.org/api/classQgsRasterIdentifyResult.html#a8537d25fdff215e7e9650b71a0a16783 results() returns a QMapint, QVariant (one item for each band), it does not return a tuple, so you should actually call ident = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() and then test that ident is not empty (i,e. ident is not None and ident.iterkeys() is not None) for each band, if the point is outside of the raster extent or is nodata, the value will be a null QVariant (i.e. QVariant()) which in python is None. cheers Etienne On Fri, Aug 2, 2013 at 7:13 AM, Otto Dassau das...@gbd-consult.de wrote: Hi, thanks for your hints, I think I am on the right track now. I had a look at the value tool plugin and tried to adapt the method accordingly: def sampleRaster20(self, layer, x, y): #success, data = layer.dataProvider().identify(QgsPoint(x,y)) success, data = layer.dataProvider().identify(QgsPoint(x,y),QgsRaster.IdentifyFormatValue).results() for band, value in data.items(): return value But now I get another error message File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 448, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 454, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 526, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 300, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 285, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y), QgsRaster.IdentifyFormatValue ).results() ValueError: need more than 1 value to unpack Do you have an idea for this, too? Thanks Otto Am Thu, 1 Aug 2013 16:00:08 -0300 schrieb Etienne Tourigny etourigny@gmail.com: Have a look at the source of the value tool plugin, it calls the identify() method and has been updated to 2.0 api. Etienne On Thu, Aug 1, 2013 at 1:58 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, I want to update a plugin from 1.8 to QGIS 2.0 and it throws following error: Traceback (most recent call last): File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 447, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 453, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 514, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 299, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 284, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y)) TypeError: QgsRasterDataProvider.identify(QgsPoint, QgsRaster.IdentifyFormat, QgsRectangle theExtent=QgsRectangle(), int theWidth=0, int theHeight=0): not enough arguments I found at http://hub.qgis.org/wiki/quantum-gis/API_changes_for_version_20 the section QgsRasterDataProvider which should fit. And the Method, where I assume the error occurs should be this # get value at mouse position QGIS = 1.8 (working for 1.8) def sampleRaster18(self, layer, x, y): success, data = layer.identify
Re: [Qgis-developer] update plugin to QGIS 2.0
Have a look at the source of the value tool plugin, it calls the identify() method and has been updated to 2.0 api. Etienne On Thu, Aug 1, 2013 at 1:58 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, I want to update a plugin from 1.8 to QGIS 2.0 and it throws following error: Traceback (most recent call last): File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 447, in printValue self.showValues() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 453, in showValues self.plot() File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 514, in plot w = float(self.sampleRaster(self.InRastW.currentText(), self.xCoord, self.yCoord))/10 File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 299, in sampleRaster return self.sampleRaster20(layer, x, y) File /home/dassau/.qgis2/python/plugins/weibullanalyse/weibullanalysedialog.py, line 284, in sampleRaster20 success, data = layer.dataProvider().identify(QgsPoint(x,y)) TypeError: QgsRasterDataProvider.identify(QgsPoint, QgsRaster.IdentifyFormat, QgsRectangle theExtent=QgsRectangle(), int theWidth=0, int theHeight=0): not enough arguments I found at http://hub.qgis.org/wiki/quantum-gis/API_changes_for_version_20 the section QgsRasterDataProvider which should fit. And the Method, where I assume the error occurs should be this # get value at mouse position QGIS = 1.8 (working for 1.8) def sampleRaster18(self, layer, x, y): success, data = layer.identify(QgsPoint(x,y)) for band, value in data.items(): return value now what I tried but doesn't work (see error above) # get value at mouse position QGIS = 2.0 (not working yet :() def sampleRaster20(self, layer, x, y): success, data = layer.dataProvider().identify(QgsPoint(x,y)) for band, value in data.items(): return value my problem is, that I don't understand how to implement in sampleRaster20 the new method from the API_changes_for_version_20 website which says: QMapint, QVariant identify( const QgsPoint thePoint, IdentifyFormat theFormat, const QgsRectangle theExtent = QgsRectangle(), int theWidth = 0, int theHeight = 0 ) can anybody help? Thanks Otto ___ 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] QGIS compilation in Linux
On Thu, Jul 25, 2013 at 1:44 AM, agadisugan...@bel.co.in wrote: Hi All, Im compiling the Qgis1.8 in RHEL 5, all the dependencies I have compiled, so now compiling the source code of QGIS, while doing that as per compilation instruction when I gave ccmake .., everything went properly but when I gave option 'g', it is showing some WARNING messages like: WARNING: Target qgis_core requests linking to directory /usr/local/lib. Targets may link only to libraries. CMake is dropping the item. WARNING: Target qgis_analysis requests linking to directory /usr/local/lib. Targets may link only to libraries. CMake is dropping the item. WARNING: Target qgis_networkanalysis requests linking to directory /usr/local/lib. Targets may link only to libraries. CMake is dropping the item. ETC Along with the WARNINGS I gave make, at that time its giving an error like this: src/core/qgsexpression.h: In member function ˜virtual QStringList QgsExpression::NodeInOperator::referencedColumns() const: /root/Desktop/qgis/final_qgis/qgis-1.8.0-9_0.el6.src.rpm_FILES/qgis-1.8.0/src/core/qgsexpression.h:335: error: no matching function for call to ˜QStringList::append(QStringList)™ /usr/local/Trolltech/Qt-4.4.0/include/QtCore/qlist.h:420: note: candidates are: void QListT::append(const T) [with T = QString] I have no idea why you get these errors, but you should NEVER run as root user, unless installing important things. Try again as a normal user, you will probably have better success. Etienne Please guide me. Thanks Sugandha Every 3000 Sheets of paper costs us a tree.. Save trees... Conserve Trees. Don't print this email or any Files unless you really need to Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Bharat Electronics or supp...@bel.co.in immediately and destroy all copies of this message and any attachments. ___ 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] Bugs in QGIS Master
On Thu, Jul 25, 2013 at 3:28 AM, Oscar van Vliet ovv...@gmail.com wrote: Dear QGIS developers, Thanks for all the hard work, I have been using the almost 2.0 builds with some satisfaction. Unfortunately, all is not well. I am using yesterday's Master build, and there seems to be a few bugs still. First of all, the dialog window for Raster|Analysis|DEM is too tall for my Macbook, which only has 800 pixels vertically. You might consider rearranging it a little. I can still use it by starting the analysis by hitting Enter, but I cannot actually see the bottom row of buttons or the resize widget. Admittedly the vertical size of that dialog is a bit large. If you close the Creation Options section, can you resize the window and see the bottom buttons? Second, I have some errors in the Raster|Conversion|Rasterise dialog that make it unusable for me. I am trying to rasterise a vector layer that I saved as a selection from a layer that I had previously vectorised. I understand this dialog is just a front for GDAL tools, but the bridge seems to be broken: I get the following python error when I try to select a filename for the rasterised output layer: Traceback (most recent call last): File /Applications/GIS/QGIS_2.0-dev_SnoLeo.app/Contents/MacOS/../Resources/python/plugins/GdalTools/tools/doRasterize.py, line 102, in fillOutputFileEdit outputFile = fileDialogFunc(self, self.tr( Select the raster file to save the results to ), Utils.FileFilter.allRastersFilter(), lastUsedFilter) File /Applications/GIS/QGIS_2.0-dev_SnoLeo.app/Contents/MacOS/../Resources/python/plugins/GdalTools/tools/GdalTools_utils.py, line 413, in getSaveFileName return self.getDialog(parent, caption, QFileDialog.AcceptSave, QFileDialog.AnyFile, filter, selectedFilter, useEncoding) File /Applications/GIS/QGIS_2.0-dev_SnoLeo.app/Contents/MacOS/../Resources/python/plugins/GdalTools/tools/GdalTools_utils.py, line 362, in getDialog dialog.selectNameFilter(selectedFilter) TypeError: QFileDialog.selectNameFilter(QString): argument 1 has unexpected type 'QPyNullVariant' Python versie: 2.6.1 (r261:67515, Jun 24 2010, 21:47:49) [GCC 4.2.1 (Apple Inc. build 5646)] QGIS versie: 1.9.0-Master Master, 5c2e3f3 Python pad: ['/Applications/GIS/QGIS_2.0-dev_SnoLeo.app/Contents/MacOS/../Resources/python', '/Users/XX/.qgis2/python', '/Users/XX/.qgis2/python/plugins', '/Applications/GIS/QGIS_2.0-dev_SnoLeo.app/Contents/MacOS/../Resources/python/plugins', '/Library/Frameworks/SQLite3.framework/Versions/B/Python/2.6', '/Library/Python/2.6/site-packages/numpy-override', '/Library/Frameworks/GDAL.framework/Versions/1.10/Python/2.6/site-packages', '/Library/Frameworks/cairo.framework/Versions/1/Python/2.6', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python26.zip', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/plat-darwin', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/plat-mac', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/plat-mac/lib-scriptpackages', '/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-tk', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-old', '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload', '/Library/Python/2.6/site-packages', '/Library/Python/2.6/site-packages/PIL', '/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/PyObjC', '/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/wx-2.8-mac-unicode', '/Applications/GIS/QGIS_2.0-dev_SnoLeo.app/Contents/Resources/python/plugins/fTools/tools', '/Users/XX/YY/ZZ'] Then if I try to run it with the existing size, I get another python error. If I choose the option with pixel size, the action just seems to hang without resolving or any error message. I cannot reproduce these 2 problems in linux, perhaps only a Mac bug? Consider filing a bug report here: http://hub.qgis.org/projects/quantum-gis/issues I hope this makes sense. I have installed all of the required packages from kyngchaos, AFAIK. Feel free to contact me for additional data. Best wishes, Oscar ___ 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] OpenLayers plugin
There is a working version (thanks to Richard Duivenvoorde) available at http://www.qgis.nl/2013/06/30/english-temporary-fix-for-openlayers-plugin/?lang=en Why not upload it now on plugins.qgis.org (for qgis 1.9 only), and then upload the new (improved) plugin when ready? cheers Etienne On Thu, Jul 18, 2013 at 8:27 AM, Werner Macho werner.ma...@gmail.comwrote: *lol* ok yeah .. you are right .. I should not mix up terms when it comes to a release .. On Thu, Jul 18, 2013 at 1:25 PM, Matthias Kuhn matthias.k...@gmx.ch wrote: Based on Tim's expected release date (before Brighton) this will be fixed it for 2.0 and not for master there ;-) Cheers Matthias On Don 18 Jul 2013 13:13:36 CEST, Werner Macho wrote: Hi I remember Pirmin said something about they are going to fix it for master during the HF in Brighton.. regards Werner On Thu, Jul 18, 2013 at 12:10 PM, Paolo Cavallini cavall...@faunalia.it wrote: * *BEGIN ENCRYPTED or SIGNED PART* * Hi all. The plugin is currently broken for master. I remember Richard fixed it, but it is not available from the repo: could this please be added, so we can keep on working in the meantime? Thanks. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ** *END ENCRYPTED or SIGNED PART* ** ___ 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 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] Raster tools support for GDAL 1.10 in QGIS 2?
There are probably a number of options that are not recognized due tho this bug, which has been partially fixed. Can you please file a generic bug report and add any other missing elements? cheers Etienne On Thu, Jul 18, 2013 at 1:45 PM, Cline, Royce L. rcl...@nd.gov wrote: Is the intent to have the GDAL tools in the Raster menu support using GDAL 1.10 with the release of QGIS 2. With QGIS 2 built with GDAL 1.10, the Mask layer radio button does not display in the Clipper dialog. GDAL 1.10 is failing the the version test in doClipper.py as it thinks 1.10 is older than 1.7. I would assume other tools may also be effected. Should I file a bug report? Priority? Royce ___ 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] get mean of pixel values within defined area around current mouse position
probably A would be slow because of the external call to gdalwarp On Wed, Jul 3, 2013 at 8:58 AM, Fred Lehodey leho...@gmail.com wrote: Hi, I have no idea in terms of performance but I would bet on B option in your case. Thanks to give feedback. Regards. On Wed, Jul 3, 2013 at 8:36 AM, Otto Dassau das...@gbd-consult.de wrote: Hi Fred, thanks for the hints, A and B sound interesting - PostGIS is not an option here. One more question, because you already used these workarounds. What solution A or B should be more usable (faster) from your opinion, if I need to calculate the mean while moving the mouse over the map canvas? Regards Otto Am Tue, 2 Jul 2013 18:05:10 +0100 schrieb Fred Lehodey leho...@gmail.com: Hi, Not sure it's the best way but I did something similar with these workarounds: A - with gdal: 1 - the user click and you get your buffer. (already done) 2 - use gdalwarp with -cutline and *-*crop_to_cutline options to extract a new raster. (python subprocess) 3 - read the created raster in a numpy array to do all the statistics you need. B - with matplotlib: 1 - with the buffer: create an array of the vertices 2 - read the raster into another numpy array 3 - use the points_inside_poly function of matplotlib lib to create a numpy mask. Not tried but postgis raster should do the job. Hth, Fred On Tue, Jul 2, 2013 at 1:12 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, for a qgis 1.8 plugin I would like to query the mean of pixel values of a raster layer within a defined buffer for the current mouse position (not for an existing point layer). For the buffer it works: ... feat.geometry().asPoint() (3.5176e+06,5.4062e+06) buff_geom = feat.geometry().buffer(1000, 5) buff_geom.asPolygon() [[(3.5186e+06,5.4062e+06), (3.51855e+06,5.4059e+06), (3.51841e+06,5.40562e+06), (3.51819e+06,5.4054e+06), (3.51791e+06,5.40525e+06), (3.5176e+06,5.4052e+06), (3.51729e+06,5.40525e+06), (3.51701e+06,5.4054e+06),...]] but now I try to find a solution to query the raster pixels within the buffer zone and calculate the mean, but I don't know how and if this is possible in QGIS 1.8 at all. I found QgsZonalStatistics, but that doesn't work for my task. Does anybody have a solution for this or a better idea, how to solve this? Thanks Otto ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Geoinformatik Büro Dassau - http://www.gbd-consult.de FOSSGIS consulting , training , support and analysis Ackerstrasse 144c , D - 40233 Düsseldorf , Germany Tel: +49-(0)211-47468178 , Mobil: +49-(0)171-4687540 -- Community Advisor - QGIS Project Steering Committee ___ 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] QGIS browser: filter files
Do you mean the standalone browser application or the browser dock in QGIS? On Wed, Jun 19, 2013 at 10:01 AM, Larissa Junek ju...@gbd-consult.dewrote: Hello, I test the new QGIS features for the user manual 2.0.0. Working with the QGIS browser I found that the 'Filter Files' feature either doesn't work or that I don't use it properly. Is it possible that the function still is in development? Can someone please explain? Regards Larissa ___ 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] SIP API Update
I have done some more fixing of GdalTools. What remains are the algorithms in the Conversion and Analysis menus - most work left is tedious work changing QString-str and QStringList-list help and testing would be appreciated. Any volunteers? Etienne On Mon, Jun 3, 2013 at 6:14 PM, Etienne Tourigny etourigny@gmail.comwrote: The following core plugins do not load properly: plugin_installer GdalTools Do the respective devs plan to fix this? I could help out a bit with GdalTools, but I don't know anything about the plugin_installer plugin to really help. Cheers Etienne On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.comwrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] SIP API Update
On Thu, Jun 6, 2013 at 9:46 AM, Nathan Woodrow madman...@gmail.com wrote: Hey all, Would I be able to get an update on where everyone is at with updating the core plugins. I have started updating the plugin installer and should have that done tomorrow. I have fixed a few of the GdalTools algorithms (and most of the generic code that is used by all algos), but quite a few remain. Most of the work left is rather simple, i.e. argument processing and string comparison. But I don't have much time until next week. If someone can step in it would be great. Etienne - Nathan On Wed, Jun 5, 2013 at 7:09 AM, Etienne Tourigny etourigny@gmail.comwrote: On Tue, Jun 4, 2013 at 3:40 PM, Etienne Tourigny etourigny@gmail.com wrote: I just ran into another problem... how do you pass a list (of strings) to a QT function which requires a QStringList (which is not available anymore). File /home/softdev/share/qgis/python/plugins/GdalTools/tools/GdalTools_utils.py, line 208, in getRasterFiles workDir.setNameFilters( filter ) TypeError: QDir.setNameFilters(QStringList): argument 1 has unexpected type 'list' never mind... it works now. On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.comwrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] SIP API Update
I just ran into another problem... how do you pass a list (of strings) to a QT function which requires a QStringList (which is not available anymore). File /home/softdev/share/qgis/python/plugins/GdalTools/tools/GdalTools_utils.py, line 208, in getRasterFiles workDir.setNameFilters( filter ) TypeError: QDir.setNameFilters(QStringList): argument 1 has unexpected type 'list' On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.com wrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] SIP API Update
How do we handle translated strings with arguments? QString::arg() is not available. Not sure if the following would work? The string syntax is slightly different and would require re-translation, but at least works in English before: self.tr( %1 not created. ).arg( outFn ) after: self.tr( %s not created. ) % outFn Traceback (most recent call last): File /home/softdev/share/qgis/python/plugins/GdalTools/tools/widgetPluginBase.py, line 120, in finished QMessageBox.warning(self, self.tr( Warning ), self.tr( %1 not created. ).arg( outFn ) ) AttributeError: 'unicode' object has no attribute 'arg' On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.com wrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] SIP API Update
On Tue, Jun 4, 2013 at 3:40 PM, Etienne Tourigny etourigny@gmail.comwrote: I just ran into another problem... how do you pass a list (of strings) to a QT function which requires a QStringList (which is not available anymore). File /home/softdev/share/qgis/python/plugins/GdalTools/tools/GdalTools_utils.py, line 208, in getRasterFiles workDir.setNameFilters( filter ) TypeError: QDir.setNameFilters(QStringList): argument 1 has unexpected type 'list' never mind... it works now. On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.comwrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] [Qgis-user] Another compiling error at 48 percent
On Sat, Jun 1, 2013 at 7:08 AM, Pedro Venâncio pedrongvenan...@yahoo.comwrote: Hi Etienne, Thank you very much for your help! I usually do not compile directly, I use the alternative of creating .deb packages with dpkg-buildpackage -us -uc -b -d -j4 In fact, it can be a local problem, maybe with some update, because it began to happen in the past weekend. To test, I did a clean install on a virtual machine and it passes the 48%, even after applying all updates, but gives error at 83%... [ 83%] Building CXX object src/python/CMakeFiles/qgispython.dir/qgispython.cpp.o cd /home/pedro/sextante_github/Quantum-GIS-master/debian/build/src/python /usr/bin/c++ -Dqgispython_EXPORTS -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SVG_LIB -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_TEST_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_NO_CAST_TO_ASCII -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -Wall -Wextra -Wno-long-long -Wformat-security -Wno-strict-aliasing -fPIC -I/usr/include/qt4 -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/home/pedro/sextante_github/Quantum-GIS-master/debian/build -I/home/pedro/sextante_github/Quantum-GIS-master/src/python/../core -I/home/pedro/sextante_github/Quantum-GIS-master/src/python/../core/raster -I/home/pedro/sextante_github/Quantum-GIS-master/src/python/../gui -I/usr/include/python2.7-DCORE_EXPORT= -DGUI_EXPORT= -DPYTHON_EXPORT= -DANALYSIS_EXPORT= -DPYTHON_EXPORT= -o CMakeFiles/qgispython.dir/qgispython.cpp.o -c /home/pedro/sextante_github/Quantum-GIS-master/src/python/qgispython.cpp /usr/bin/cmake -E cmake_progress_report /home/pedro/sextante_github/Quantum-GIS-master/debian/build/CMakeFiles [ 83%] Building CXX object src/python/CMakeFiles/qgispython.dir/qgspythonutilsimpl.cpp.o cd /home/pedro/sextante_github/Quantum-GIS-master/debian/build/src/python /usr/bin/c++ -Dqgispython_EXPORTS -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SVG_LIB -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_TEST_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_NO_CAST_TO_ASCII -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -Wall -Wextra -Wno-long-long -Wformat-security -Wno-strict-aliasing -fPIC -I/usr/include/qt4 -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtCore -I/home/pedro/sextante_github/Quantum-GIS-master/debian/build -I/home/pedro/sextante_github/Quantum-GIS-master/src/python/../core -I/home/pedro/sextante_github/Quantum-GIS-master/src/python/../core/raster -I/home/pedro/sextante_github/Quantum-GIS-master/src/python/../gui -I/usr/include/python2.7-DCORE_EXPORT= -DGUI_EXPORT= -DPYTHON_EXPORT= -DANALYSIS_EXPORT= -DPYTHON_EXPORT= -o CMakeFiles/qgispython.dir/qgspythonutilsimpl.cpp.o -c /home/pedro/sextante_github/Quantum-GIS-master/src/python/qgspythonutilsimpl.cpp make[3]: *** Sem regra para processar o alvo `/usr/lib/i386-linux-gnu/ libpython2.7.so', necessário por `output/lib/libqgispython.so.1.9.0'. Pare. make[3]: Saindo do diretório `/home/pedro/sextante_github/Quantum-GIS-master/debian/build' make[2]: ** [src/python/CMakeFiles/qgispython.dir/all] Erro 2 make[2]: Saindo do diretório `/home/pedro/sextante_github/Quantum-GIS-master/debian/build' make[1]: ** [all] Erro 2 make[1]: Saindo do diretório `/home/pedro/sextante_github/Quantum-GIS-master/debian/build' make: ** [build-stamp] Erro 2 dpkg-buildpackage: erro: debian/rules build deu erro de saída estado 2 pedro@pedro-vbox:~/sextante_github/Quantum-GIS-master$ What could be the reason? I know these problems are also happening to other people who use the creation of .debs packages. sorry, I don't build .deb packages. looks like your are missing the python-devel package or similar, or there is a version mismatch in your python packages... (missing /usr/lib/i386-linux-gnu/libpython2.7.so) Thank you very much! Best regards, Pedro From: Etienne Tourigny most probably a local problem... I can build latest master without problem. Try getting latest code, do a make clean, remove CMakeCache.txt, run cmake again and build ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SIP API Update
The following core plugins do not load properly: plugin_installer GdalTools Do the respective devs plan to fix this? I could help out a bit with GdalTools, but I don't know anything about the plugin_installer plugin to really help. Cheers Etienne On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.com wrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] SIP API Update
On Mon, Jun 3, 2013 at 7:51 PM, Nathan Woodrow madman...@gmail.com wrote: Yeah Borys or myself will take care of the plugin installer. Marco is going to review the C++ part of the installer and merge that into master. Once that is done I will merge SIP v2 into master and update the plugin installer. Matthias has a patch that he started for gdal tools. I'm going to merge that into sip update now and we can go from there. I can lend a hand in testing gdaltools as well as ftools. I had forgotten about the old plugin installer, no need to update it of course... Thanks to everyone for lending a hand. The next task is handling this from a PR point of view. As soon as we have the update in master I'll put out a blog post on how to update plugins, if you have a blog please do the same. I know Victor was thinking of putting together an update guide. If we could coordinate this effort it would be good, so we can have one place to look for how to update a plugin. great! It would be nice to have all information in one spot regarding upgrade to qgis api 2.0 as well as sip api v2. There is already a wiki page for qgis api 2.0, perhaps it could all go there and be linked from your blog(s). Regards, Nathan On Tue, Jun 4, 2013 at 8:42 AM, Borys Jurgiel li...@borysjurgiel.plwrote: Dnia poniedziałek, 3 czerwca 2013 o 23:14:26 Etienne Tourigny napisał(a): The following core plugins do not load properly: plugin_installer GdalTools Do the respective devs plan to fix this? I could help out a bit with GdalTools, but I don't know anything about the plugin_installer plugin to really help. Cheers Etienne Either Nathan or me will care about the plugin installer (strictly speaking: about the new pyplugin_installer module, as the old plugin_installer plugin will be removed as soon as the new manager is reviewed by Marco and merged to master) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SIP API Update
I've pushed some fixes for info and clipper. the raster file dialog filters needs fixing On Mon, Jun 3, 2013 at 8:31 PM, Nathan Woodrow madman...@gmail.com wrote: Ok patch for gdaltools applied. Thanks Matthias. Can I get some testing on that. Regards, Nathan On Tue, Jun 4, 2013 at 9:24 AM, Etienne Tourigny etourigny@gmail.comwrote: On Mon, Jun 3, 2013 at 7:51 PM, Nathan Woodrow madman...@gmail.comwrote: Yeah Borys or myself will take care of the plugin installer. Marco is going to review the C++ part of the installer and merge that into master. Once that is done I will merge SIP v2 into master and update the plugin installer. Matthias has a patch that he started for gdal tools. I'm going to merge that into sip update now and we can go from there. I can lend a hand in testing gdaltools as well as ftools. I had forgotten about the old plugin installer, no need to update it of course... Thanks to everyone for lending a hand. The next task is handling this from a PR point of view. As soon as we have the update in master I'll put out a blog post on how to update plugins, if you have a blog please do the same. I know Victor was thinking of putting together an update guide. If we could coordinate this effort it would be good, so we can have one place to look for how to update a plugin. great! It would be nice to have all information in one spot regarding upgrade to qgis api 2.0 as well as sip api v2. There is already a wiki page for qgis api 2.0, perhaps it could all go there and be linked from your blog(s). Regards, Nathan On Tue, Jun 4, 2013 at 8:42 AM, Borys Jurgiel li...@borysjurgiel.plwrote: Dnia poniedziałek, 3 czerwca 2013 o 23:14:26 Etienne Tourigny napisał(a): The following core plugins do not load properly: plugin_installer GdalTools Do the respective devs plan to fix this? I could help out a bit with GdalTools, but I don't know anything about the plugin_installer plugin to really help. Cheers Etienne Either Nathan or me will care about the plugin installer (strictly speaking: about the new pyplugin_installer module, as the old plugin_installer plugin will be removed as soon as the new manager is reviewed by Marco and merged to master) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SIP API Update
so plugin authors would potentially need to maintain 2 versions of their plugins, on for qgis = 1.8 and one for qgis =2.0. This is probably easier than adding a bunch of if statements where sip1 and spi2 need different syntax I guess, cheers Etienne On Thu, May 30, 2013 at 6:07 AM, Nathan Woodrow madman...@gmail.com wrote: On Thu, May 30, 2013 at 7:04 PM, Sandro Santilli s...@keybit.net wrote: Plugin authors want to maintain support for multiple qgis versions, so changing an API is really only _more_ work, not _less_. Is there any facility to deal with that ? The new plugin manager can handle different versions of the same plugin. With the new vector API this is already the case so changing SIP isn't going to hurt much more. - Nathan ___ 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] SIP API Update
On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.com wrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 I am trying to update a plugin (tileindex) using your branch and I get the following an error fileName = feature[self.attrStr] TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be instantiated It seems that feature[], as well as feature.attribute() return a QVariant (defined in qgsfeature.sip), which is incompatible with SIP API v2. How can this be fixed in the plugin or qgis? It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] SIP API Update
On Thu, May 30, 2013 at 11:41 PM, Nathan Woodrow madman...@gmail.comwrote: Etienne, If self.attrStr() is something like QVariant(value) then you need to remove the QVariant() bit call. that probably was the problem, it works now, many thanks. - Nathan On Fri, May 31, 2013 at 12:39 PM, Nathan Woodrow madman...@gmail.comwrote: Yeah they both return QVariant but that is auto converted to a Python object by SIP. Not sure what is going on there I'll look into it. I get the right return result if I called feature.attribute(). Which platform are you on? - Nathan On Fri, May 31, 2013 at 12:30 PM, Etienne Tourigny etourigny@gmail.com wrote: On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow madman...@gmail.comwrote: Hey all, I have decided to manage the SIP API update process so that we can have it done by 2.0. This is an important update as leaving it for later will break every plugin yet again at later date which just leaves a really bad taste for people to deal with. A few plugin authors have already expressed that they would not be impressed having to do another major update again in the future. And I agree. So having said that this is the current plan: - I have created a branch with the SIP API v2 update - Update all the core plugins in the sipapi-udate[0] branch over the next couple of days - Merge into master I couldn't update all the core plugins myself BUT it would be a lot easier if I could call on the plugin authors to run though their own code and do the quick update. The risk of me doing it is that I might break something and not know it. You know your code best so the help would be greatly appreciated. I updated most of the console code and Salvatore has already cleaned the rest up for me so that is one thing out of the way. And here comes the kicker: I would like to do this as quickly as we can so to reduce the gap between master and the branch. The sooner we merge it to master the sooner we can open it to wider testing, but I don't expect to run into any major issues when we do. If you are not aware of what benefits the SIP API update will bring here is a quick example: Before: str(yourlineedit.text().toString()) 'Hello World' feature[column].toInt()[0] 100 After yourlineedit.text() 'Hello World' feature[column] 1000 I am trying to update a plugin (tileindex) using your branch and I get the following an error fileName = feature[self.attrStr] TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be instantiated It seems that feature[], as well as feature.attribute() return a QVariant (defined in qgsfeature.sip), which is incompatible with SIP API v2. How can this be fixed in the plugin or qgis? It will make life for us and plugin authors a hell of a lot easier. I have put together a quick guide[1] with some examples. It is open edit so feel free to add any notes you have. It might be good to turn it into a plugin translate guide for future plugin authors moving to 2.0. Regards, Nathan [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update [1] https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing ___ 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] changes to raster and vector file loading for files with sublayers
Hi, I have just pushed a commit to fix the loading of raster and vector files with sublayers. I have also added 2 files to test this in the testdata folder. This may cause some bug(s) that I have not tested for, especially regarding non-file based data sources. cheers Etienne ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] State of Spatialite 4.0 and GDAL 1.10 for QGIS 2.0?
IMHO it would be great to make sure latest spatialite and GDAL are tested and packaged with 2.0 in Mac, osgeo4w and ubuntugis-unstable I personally use gdal-1.10 with qgis master without any problems (Linux Mint 14) Etienne On Tue, May 21, 2013 at 4:14 PM, Larry Shaffer lar...@dakotacarto.comwrote: Hi, Recently William upgraded his Mac support frameworks to GDAL 1.10 and Spatialite 4.0 [0]. However, it appears that QGIS core code may not be ready for Spatialite 4.0 [1]. Is anyone using QGIS master branch with Spatialite 4.0 successfully? If Spatialite 4.0 is still not supported yet, is anyone working on it? I can get a vector layer to Save as... to a Spatialite 4.0 db, but can't create a new one. Same questions for GDAL 1.10. Are there issues within the QGIS codebase concerning its use that would cause it not to be recommended for 2.0? These are two major new FOSSGeo releases that seem a shame to not include support for in QGIS 2.0. [0] http://www.kyngchaos.com/blog/2013/20130501_gdal_1.10 [1] http://hub.qgis.org/issues/7664 Regards, Larry ___ 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
