Re: [Qgis-developer] QGIS and GRASS 7.0.0
On Tue, Feb 24, 2015 at 9:51 PM, Andrew wrote: > Hi Radim, > > I would be willing to volunteer to help maintain the qgm and qgc files. Great, I'll keep current config system also for GRASS 7. Radim > Andrew > > On Tue, Feb 24, 2015 at 12:28 AM, Radim Blazek > wrote: >> >> Olá todos, >> >> I'am already preparing crowdfunding campaign for GRASS plugin upgrade. >> It will include: >> >> - qgisgrasslib upgrade to GRASS 7 >> - single build with both GRASS 6 and 7 (GRASS version chosen by >> environmental variables on start up) >> - move plugin browser functionality to standard QGIS browser (meta >> info widget, delete and rename action) >> - implement raster and vector import via browser drag and drop >> (including reprojection) >> - new/open/close location tools upgrade to GRASS 7 >> - region editor upgrade to GRASS 7 >> - upgrade GRASS shell to the last qtermwidget >> - modules GUI - my idea is to throw away the qgm and qgc definitions >> and auto generate GUI for modules with all options based on >> --interface-description only, also the list of modules would be auto >> generated for all modules. The reason is my impression that there are >> no volunteers willing to maintain qgm and qgc. If there are volunteers >> to do that (no programming, xml editing only) let me know and I'll >> include keeping of current system in the proposal. >> - vector editing overall upgrade and enhancement more integrated with >> standard QGIS tools >> - standard editing tools (e.g. node tool) >> - snapping to other layers >> - undo/redo >> - attribute forms >> - possibility to change topological symbology via standard style >> dialog >> - standard rendering of not edited layers based on edited map >> (i.e. draw filled polygons on background during editing) >> >> I am currently coding proof of concept for vector editing to be sure >> that it is feasible at all. I hope to launch the campaign in about 2-3 >> weeks. >> >> Radim >> >> On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio >> wrote: >> > Olá Paolo, >> > >> > >> >> this will require a reasonable amount of work. I have raised the issue >> >> several times; sadly it seems nobody is willing to invest the necessary >> >> resources on this. >> > >> > >> > Despite the great advantages of GRASS commands in Processing, I think >> > that >> > the GRASS plugin still plays an important role and is an excellent >> > interface >> > for GRASS. For those who still like to use the paradigm of locations, >> > mapsets and the GRASS topological model, GRASS plugin is very important, >> > because then it allows to use all QGIS tools, for example, to create >> > layouts >> > using the Composer, etc. >> > >> > If no one is interested in making the port of the plugin for GRASS 7, we >> > could try through a crowdfounding initiative. Who was behind the initial >> > creation of GRASS plugin? >> > >> > >> > >> >> >> >> BTW, would you mind giving us a list of the missing modules in >> >> Processing? AFAIK these should be only obsolete and useless ones, but >> >> if >> >> there is some genuinely missing we should be able to fix this rather >> >> easily. >> > >> > >> > >> > I've been checking the differences and they are indeed few. Please see >> > the >> > spreadsheet attached. >> > >> > Some commands seem that were adaptations of other algorithms, made for >> > Processing, as they are not in the 6 manual, or in the 7: >> > r.cost.full.raster, r.drain.coordinate, r.terraflow.short, >> > v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. >> > >> > Others seem that have been removed from GRASS 7 (r.average, r.bilinear, >> > r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. >> > >> > There are five that seem important to me, which are in GRASS 7, in >> > Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, >> > r.spread, r.univar, v.kernel. >> > >> > Finally, there are two commands that are on GRASS 7 and were not in 6: >> > r.viewshed (which replace r.los) and r.relief (which replace >> > r.shaded.relief). >> > >> > >> > Thanks! >> > >> > Best regards, >> > Pedro Venâncio >> > >> > >> > ___ >> > 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] QGIS and GRASS 7.0.0
Hi, On Tue, Feb 24, 2015 at 7:11 PM, Vaclav Petras wrote: > > On Tue, Feb 24, 2015 at 3:28 AM, Radim Blazek > wrote: >> >> - modules GUI - my idea is to throw away the qgm and qgc definitions >> and auto generate GUI for modules with all options based on >> --interface-description only, also the list of modules would be auto >> generated for all modules. > > > Hi Radim, > > it would be good if you can include GRASS Addons, too. There is a lot of > requests for installing/running GRASS Addons from QGIS, e.g. at > gis.stackexchange.com. How can I get list of installed GRASS Addons? > Also, there are some files in GRASS GIS which might be quite useful [1]. > toolboxes.xml [2] The toolboxes.xml looks interesting, fortunately we have already volunteer to maintain qgc (tree configuration). Radim > contains GRASS GIS modules sorted into different tooboxes. > They are currently not part of the official API but it is just a matter of > declaring them as part of API I guess [3]. GRASS wxGUI is using these files > to create a menu and module tree in Search module tab. It is also a way to > customize wxGUI [4] but that's not related to QGIS use case. > > Loading Addons dynamically to menu or module tree including their > descriptions seems to be a bit challenging but if nothing else wxGUI can > always run a module installed using g.extension (or custom user script) if > it can run and give --interface-description. > > Best, > Vaclav > > [1] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml > [2] > http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml/toolboxes.xml > [3] > http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/docs/wxgui_sphinx/src/wxgui_toolboxes.rst > [4] http://grass.osgeo.org/grass70/manuals/wxGUI.toolboxes.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
Il 24/02/2015 22:46, Andrea Peri ha scritto: > I can confirm our goal was to have a per-layer option. > Because not all the layers in a wms service are good to have a > contextual legend. I see, thanks for clarifying. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Bookmarks can be imported/exported?
Il 24/02/2015 22:51, Salvatore Larosa ha scritto: > I just fixed both the issues. Thanks Salvatore. Will this go to 2.8.1? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
Il 24/02/2015 23:39, Pedro Venâncio ha scritto: > You are right Nyall, with the range widget, operations work both in the > attribute table cells and in forms fields! confirmed, thanks. this limitation is surprising for the user, and should be overcome, or at least documented. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Temporary memory layers: wrong dialog size
Il 25/02/2015 00:49, Nyall Dawson ha scritto: > See some discussion in https://hub.qgis.org/issues/10775 . However, I > think the form *should* be suppressed in this case, which > https://github.com/qgis/QGIS/pull/1925 implements. > > Thoughts? notes added. thanks. -- 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] MetaSearch 0.3.3 released
The MetaSearch team announces the release of MetaSearch 0.3.3. This is the initial release of MetaSearch directly from the QGIS codebase and as a result is considerably smaller in size given dependencies and internationalization are leveraged from QGIS and no longer bundled with the plugin. The result is a leaner and more stable plugin and user experience. The plugin can be found on the QGIS Plugins Repository at http://plugins.qgis.org/plugins/MetaSearch MetaSearch is a QGIS plugin to interact with metadata catalogue services (CSW). Version 0.3.3 (2015-02-24) -- - safeguard CSW connection names with '/' - fix help link URL opening - general fixes to support releasing from QGIS core Testers and developers are welcome. The MetaSearch team. https://hub.qgis.org/projects/MetaSearch ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Temporary memory layers: wrong dialog size
> The window for the creation of new memory layers appears wrong: ic can > be resized to zero width and reduced to only window header in height. > Should I open a ticket? > I confirm this on Xubuntu 12.04 (Xfce desktop environment) and Lubuntu 14.04 (LXDE desktop environment), but not on Windows (OSGeo4W). Best regards, Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Temporary memory layers: wrong dialog size
On 24 February 2015 at 23:07, Paolo Cavallini wrote: > Also, when adding an element the attribute popup appears, but since > field cannot be added during creation, the window is useless and > annoying: should the popup be suppressed, or better give the user to > opportunity to add fields? See some discussion in https://hub.qgis.org/issues/10775 . However, I think the form *should* be suppressed in this case, which https://github.com/qgis/QGIS/pull/1925 implements. Thoughts? Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
> > I see what's happening here - I suspect that your field is set to use > a "text edit" edit widget rather than a "range" widget (check the > layer properties->fields tab). QGIS only uses spin boxes for the edit > widget if it's set to a range widget, otherwise they are just standard > text boxes which don't accept expressions (yet -- I'll try and tackle > that at some stage). > > You are right Nyall, with the range widget, operations work both in the attribute table cells and in forms fields! Thanks! Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
On 25 February 2015 at 06:54, Pedro Venâncio wrote: > Hi Nyall, > >> Which spin boxes are you testing with? >> >> > > I was trying directly in the attribute table cells. I got the idea that it > worked directly in the cells, when I saw the changelog on the other day. At > this time it is not active to confirm: > http://changelog.qgis.org/qgis/version/2.8/ > > But am I wrong? I see what's happening here - I suspect that your field is set to use a "text edit" edit widget rather than a "range" widget (check the layer properties->fields tab). QGIS only uses spin boxes for the edit widget if it's set to a range widget, otherwise they are just standard text boxes which don't accept expressions (yet -- I'll try and tackle that at some stage). Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Bookmarks can be imported/exported?
Hi Paolo, On Tue, Feb 24, 2015 at 4:41 PM, Paolo Cavallini wrote: > Il 24/02/2015 16:39, Paolo Cavallini ha scritto: >> Hi all. >> Sorry for flooding, but while checking the changelog I'm finding a >> series of issues. Exporting a bookmark and reimporting it results in: >> * an empty name of the bookmark >> * a wrong extent. >> Is this confirmed, ora local issue? I just fixed both the issues. The first one was due to the lack of some translation string and the second one I mistakenly swapped xmax with ymin of the bookmark extent (as reported by Pedro, thanks). > > furthermore, the output dir is not remembered. also this has been fixed. Best regards, -SL -- Salvatore Larosa linkedIn: http://linkedin.com/in/larosasalvatore twitter: @lrssvt skype: s.larosa IRC: lrssvt on freenode ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
Hi, strk, and Paolo. I can confirm our goal was to have a per-layer option. Because not all the layers in a wms service are good to have a contextual legend. Actually the more layer don't need a contextual legend. Only few layer with really many layer are this need. Of course the proebl of a per-layer configuration is to have a web client capable to do a non standard call. Meanwhile a per-server configuration will work with every client. This is why we fund also the capability of qgis to set the wms provider to do a contextual-client call. With a per-server configuration this will not need. But another question about why we prefer a per-client configuration is that this is the same configuration used by mapserver in it contextual legend. nfact we originally use the contextual legend in mapserver and after see how good it was on some layer we decided to fund to have the same contextual legend call in qgis-server. This is a good question fo interoperability to have the same request in more then one wms server. This kind of request is surely not standard for ogc but is the same for mapserver and for qgis-server. This mean that a wms provider client that can call the contextual legend on mapserver can call also on qgis-server. Instead If qgis-server was working with a different kind of request for contextual legend, it will be incompatibile and this mean that every client that support the mapserver contextual call don't conseguentially support the qgis-server contextual call. The theird question is that a per-client configuration will allow t have the full legend and also the contextual legend. Instead aper-server configuration will allow to have always only one of both legends. This mean a lesser useful usage. Because not always is useful to have the contextual legend (also on a lyar with many domains). Regards, Andrea. 2015-02-24 17:35 GMT+01:00 Sandro Santilli : > On Tue, Feb 24, 2015 at 10:42:40PM +0700, Martin Dobias wrote: >> Hi Paolo >> >> On Tue, Feb 24, 2015 at 10:23 PM, Paolo Cavallini >> wrote: >> >> > Il 24/02/2015 16:18, Sandro Santilli ha scritto: >> > >> > > I wouldn't consider that one a bug. The default is for contextual >> > > WMS legend to be off (it's not a standard call). Eventually you >> > > might want a per-server default configuration, but would be >> > > an enhancement. >> > >> > sorry, I do not see your point: if an user chooses to display the legend >> > for a server, it is more than likely that he will expect further >> > connections to that server will remember his choice. >> > but OK, it can be an enhancement. >> >> I would even argue that such option should not exist. Most users will >> probably not understand its meaning. If necessary, such option should be in >> WMS server configuration dialog, not in the main WMS dialog. Anyway I think >> QGIS should try to figure it out itself whether the server supports >> contextual legend. > > Contextual legend is a non-standard feature, not sure how QGIS could > rely on capability info to figure out. Moreover the user might want > it enabled only for some of the layers. The per-layer option was explicitly > requested by the funding party (Regione Toscana). > > So I would see a per-server option to determine a per-layer default > (overridable) and eventually an "autodetect" choice for that option in > case there's a likely-to-work way to do that. > > --strk; > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer -- - Andrea Peri . . . . . . . . . qwerty àèìòù - ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
Hi On Tue, Feb 24, 2015 at 10:08 PM, Pedro Venâncio wrote: > > I'm not sure - I've never tried it in the attribute table. Try in a >> symbology dialog or in a composer item properties panel and see if it works >> OK... >> > Simple expressions (25 * 5) in the attribute table did work for me when I took that screenie in the changelog. Regards Tim -- -- Tim Sutton Visit http://kartoza.com to find out about open source: * Desktop GIS programming services * Geospatial web development * GIS Training * Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net Tim is a member of the QGIS Project Steering Committee --- Kartoza is a merger between Linfiniti and Afrispatial ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.02.2015 21:15, Pedro Venâncio wrote: >> >> >> I have completely missed option WITH_QWTPOLAR, so I have tried to >> set it to OFF and will see what it happens. >> >> > I think I set both (WITH_QWTPOLAR and WITH_INTERNAL_QWTPOLAR) to > ON, but I'm not sure. Thanks all for your help. When setting WITH_QWTPOLAR=OFF build went fine. - -- Ivan Minčík ivan.min...@gmail.com GPG: 0x79529A1E http://imincik.github.io/0x79529A1E.key ivan.min...@gista.sk GPG: 0xD714B02C http://imincik.github.io/0xD714B02C.key -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU7OTnAAoJEPfdLsR5Upoe5xwH/3VVUJtHZlDd5d0a+jTx+f2L j65oBqfRZYtZtaAcrgxDKu1nsVPWIy65wU99MTNxeRrVaKn6Dab/wapBvsSMSz2t J3Y9m6g47FagpiQXViSClS7fYRyCX8tGcQl6M093KFsNOzOaIKmDrVPIg+9FmSIi ddG8ariTJtWM/8dt0Ktwe+59fYHCV/aM+8IMcdBijVJaRAKL4yhLNKGVYrmFLSx5 yh2BAtdeUOuDBtU+IpIpdZZrF6bY84AnhAmvF/uyPrEfWoOEVVRav87HfYYnASKJ h0yUNQgojCSVouo514QQfaD1UYw2rWlNtMInAlei1GoxbVxw9yqiqGuqCPPLny8= =3SlK -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi Radim, I would be willing to volunteer to help maintain the qgm and qgc files. Andrew On Tue, Feb 24, 2015 at 12:28 AM, Radim Blazek wrote: > Olá todos, > > I'am already preparing crowdfunding campaign for GRASS plugin upgrade. > It will include: > > - qgisgrasslib upgrade to GRASS 7 > - single build with both GRASS 6 and 7 (GRASS version chosen by > environmental variables on start up) > - move plugin browser functionality to standard QGIS browser (meta > info widget, delete and rename action) > - implement raster and vector import via browser drag and drop > (including reprojection) > - new/open/close location tools upgrade to GRASS 7 > - region editor upgrade to GRASS 7 > - upgrade GRASS shell to the last qtermwidget > - modules GUI - my idea is to throw away the qgm and qgc definitions > and auto generate GUI for modules with all options based on > --interface-description only, also the list of modules would be auto > generated for all modules. The reason is my impression that there are > no volunteers willing to maintain qgm and qgc. If there are volunteers > to do that (no programming, xml editing only) let me know and I'll > include keeping of current system in the proposal. > - vector editing overall upgrade and enhancement more integrated with > standard QGIS tools > - standard editing tools (e.g. node tool) > - snapping to other layers > - undo/redo > - attribute forms > - possibility to change topological symbology via standard style > dialog > - standard rendering of not edited layers based on edited map > (i.e. draw filled polygons on background during editing) > > I am currently coding proof of concept for vector editing to be sure > that it is feasible at all. I hope to launch the campaign in about 2-3 > weeks. > > Radim > > On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio > wrote: > > Olá Paolo, > > > > > >> this will require a reasonable amount of work. I have raised the issue > >> several times; sadly it seems nobody is willing to invest the necessary > >> resources on this. > > > > > > Despite the great advantages of GRASS commands in Processing, I think > that > > the GRASS plugin still plays an important role and is an excellent > interface > > for GRASS. For those who still like to use the paradigm of locations, > > mapsets and the GRASS topological model, GRASS plugin is very important, > > because then it allows to use all QGIS tools, for example, to create > layouts > > using the Composer, etc. > > > > If no one is interested in making the port of the plugin for GRASS 7, we > > could try through a crowdfounding initiative. Who was behind the initial > > creation of GRASS plugin? > > > > > > > >> > >> BTW, would you mind giving us a list of the missing modules in > >> Processing? AFAIK these should be only obsolete and useless ones, but if > >> there is some genuinely missing we should be able to fix this rather > >> easily. > > > > > > > > I've been checking the differences and they are indeed few. Please see > the > > spreadsheet attached. > > > > Some commands seem that were adaptations of other algorithms, made for > > Processing, as they are not in the 6 manual, or in the 7: > > r.cost.full.raster, r.drain.coordinate, r.terraflow.short, > > v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. > > > > Others seem that have been removed from GRASS 7 (r.average, r.bilinear, > > r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. > > > > There are five that seem important to me, which are in GRASS 7, in > > Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, > > r.spread, r.univar, v.kernel. > > > > Finally, there are two commands that are on GRASS 7 and were not in 6: > > r.viewshed (which replace r.los) and r.relief (which replace > > r.shaded.relief). > > > > > > Thanks! > > > > Best regards, > > Pedro Venâncio > > > > > > ___ > > 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] error in compiling (QWTPOLAR_INCLUDE_DIR)
> > > I have completely missed option WITH_QWTPOLAR, so I have tried to set > it to OFF and will see what it happens. > > I think I set both (WITH_QWTPOLAR and WITH_INTERNAL_QWTPOLAR) to ON, but I'm not sure. Best regards, Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
> I'm not sure - I've never tried it in the attribute table. Try in a > symbology dialog or in a composer item properties panel and see if it works > OK... > > > Everything ok here, like in Field Calculator Bar. Maybe I have not really understood the changelog. Thanks Nyall! Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.02.2015 21:00, Pedro Venâncio wrote: > Hi, > > I compiled 2.8 last Sunday, on Xubuntu 12.04, and I came across the > same problem. > > I solved with this tip. > >> on Ubuntu you will probably have to set them both to TRUE I have completely missed option WITH_QWTPOLAR, so I have tried to set it to OFF and will see what it happens. - -- Ivan Min?ík ivan.min...@gmail.com GPG: 0x79529A1E http://imincik.github.io/0x79529A1E.key ivan.min...@gista.sk GPG: 0xD714B02C http://imincik.github.io/0xD714B02C.key -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU7Nm7AAoJEPfdLsR5UpoefV8H/i7fZrg3RTIo1g5xQ1G3Q+zX 9tEY2zVtW3dXvmi7OhfxPngI8Ki8nMyJEYOqEx8/0U8QEiG2p+Eh7+i8MHbVTbiD f7gZWvhWAg/+bfEOlaHJxuN3+auNlRVPpYZBM8XzQsCk60Te8mJ/leON0JjlK8Dk sTXmHYbSLj5fLe+KkWcEx1qjmi+lb2cgSTc3D6JNtzICGf5ljPeRgXsLnE42UbgH BloWp+4+vFOBLSub2cFCrO4RUlWUvZMeolWa1ei6LONAeyFvaH2plRNHdy3EYHfq hyTWBJYcmEe4j8ByJsdIOpd3sbckPJXHZniYRrTZGzlGH2pCeCRXSgR8FGqdFww= =6VfU -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
Hi, I compiled 2.8 last Sunday, on Xubuntu 12.04, and I came across the same problem. I solved with this tip. > on Ubuntu you will probably have to set them both to TRUE ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
On 25 Feb 2015 6:54 am, "Pedro Venâncio" wrote: > > Hi Nyall, > >> Which spin boxes are you testing with? >> >> > > I was trying directly in the attribute table cells. I got the idea that it worked directly in the cells, when I saw the changelog on the other day. At this time it is not active to confirm: http://changelog.qgis.org/qgis/version/2.8/ > > But am I wrong? > > I'm not sure - I've never tried it in the attribute table. Try in a symbology dialog or in a composer item properties panel and see if it works OK... Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
Hi Nyall, Which spin boxes are you testing with? > > > I was trying directly in the attribute table cells. I got the idea that it worked directly in the cells, when I saw the changelog on the other day. At this time it is not active to confirm: http://changelog.qgis.org/qgis/version/2.8/ But am I wrong? Thanks Nyall! Best regards, Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
On 25 Feb 2015 6:31 am, "Ivan Mincik" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 24.02.2015 20:25, Nyall Dawson wrote: > > On 25 Feb 2015 6:15 am, "Ivan Mincik" > > wrote: > >> > >> > >> Nyall, could be this fix backported to release_2_8 branch ? > >> > > > > It's already included in the 2.8 release. with ext Nyall > > > > I am trying to build release_2_8 on Ubuntu 14.04 and I am failing with > exactly same symptoms. What is the ID of commit where this problem was > fixed ? > 2589b1a Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Bookmarks can be imported/exported?
I also confirm here. I think what it is doing is exchanging yMin by xMax. Please see the images - https://dl.dropboxusercontent.com/u/5772257/qgis/1_bookmarks_before_export.png - https://dl.dropboxusercontent.com/u/5772257/qgis/2_bookmarks_after_import.png and this query in qgis.db: select * from tbl_bookmarks - Before export the result is: "bookmark_id", "name", "project_name", "xmin", "ymin", "xmax", "ymax", "projection_srid" "1", "north", "", "-55027.0163934426", "122440.672131148", "138610.344262295", "274711.672131148", "1721" "2", "center", "", "24699.6035052022", "68084.4791722655", "124465.925154528", "146537.921795216", "1721" "3", "south", "", "-64823.6749913617", "-278157.939148463", "-14940.5141666986", "-238931.217836987", "1721" - After import: "bookmark_id", "name", "project_name", "xmin", "ymin", "xmax", "ymax", "projection_srid" "1", "north", "", "-55027.0163934426", "138610.344262295", "122440.672131148", "274711.672131148", "1721" "2", "center", "", "24699.6035052022", "124465.925154528", "68084.4791722655", "146537.921795216", "1721" "3", "south", "", "-64823.6749913617", "-14940.5141666986", "-278157. 939148463", "-238931.217836987", "1721" Randal, The SRID represents the srs_id field in srs.db database, not the AuthorityID. For example, if you query in srs.db select * from tbl_srs where srs_id = 222 you will see that this is your EPSG: 2240 "srs_id", "description", "projection_acronym", "ellipsoid_acronym", "parameters", "srid", "auth_name", "auth_id", "is_geo", "deprecated", "noupdate" "222", "NAD83 / Georgia West (ftUS)", "tmerc", "GRS80", "+proj=tmerc +lat_0=30 +lon_0=-84.17 +k=0. +x_0=69.9998983998 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=us-ft +no_defs", "2240", "EPSG", "2240", "0", "0", "0" So, I think this is a bug and the problem is the exchange of yMin by xMax. Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24.02.2015 20:25, Nyall Dawson wrote: > On 25 Feb 2015 6:15 am, "Ivan Mincik" > wrote: >> >> >> Nyall, could be this fix backported to release_2_8 branch ? >> > > It's already included in the 2.8 release. with ext Nyall > I am trying to build release_2_8 on Ubuntu 14.04 and I am failing with exactly same symptoms. What is the ID of commit where this problem was fixed ? - -- Ivan Minčík ivan.min...@gmail.com GPG: 0x79529A1E http://imincik.github.io/0x79529A1E.key ivan.min...@gista.sk GPG: 0xD714B02C http://imincik.github.io/0xD714B02C.key -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU7NGDAAoJEPfdLsR5UpoefDoH/0tCNOYW8EjuCppXgM07ga/o +5rapngAmhElmgrPlJ+fN/XSURK7/RXRYotZ2JHyx/kLcN/3Rb2qPEUxDGlCgM89 +jbz6T9RzrG3V1zuRM4yewruUIjyK6vXiZr7jBNXR2LZOiJvRVlnGRrOajMBqAsE g4jq8SnP6oXriJfD3rXYded7uV3x72dwEuQJIm94T4VQDmmolmoFkEbXhLSMNUyr YznELNxdDXON3TjPYi32YAhDcHnRiWGvYD4isBsLQTjjrbs0kHJ28Nm3IIf0VwG5 T+3eyFqRxmuKrfTcW/gAdVuv3Dei+yl2PCpceKD95MGWEm1/hPN41xfkouW9flY= =srrs -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
On 25 Feb 2015 6:15 am, "Ivan Mincik" wrote: > > > Nyall, could be this fix backported to release_2_8 branch ? > It's already included in the 2.8 release. Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
On 25 Feb 2015 5:47 am, "Pedro Venâncio" wrote: > > Confirmed here. > > I also can not insert operators in numerical fields. > > Which spin boxes are you testing with? Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] error in compiling (QWTPOLAR_INCLUDE_DIR)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08.02.2015 10:42, Nyall Dawson wrote: > On 8 Feb 2015 8:04 pm, "Matthias Kuhn" > wrote: >> >> Hi Matteo, >> >> What is the status of WITH_QWTPOLAR and WITH_INTERNAL_QWTPOLAR >> >> on Ubuntu you will probably have to set them both to TRUE or set > WITH_QWTPOLAR to FALSE (in which case, if you still experience > troubles you may have to delete the variables QWTPOLAR_INCLUDE_DIR > and QWTPOLAR_LIBRARY. Deleting these is not the same as setting > them to OFF.) >> > > That should be fixed in master now - try an updated build. > > Nyall Nyall, could be this fix backported to release_2_8 branch ? - -- Ivan Min?ík ivan.min...@gmail.com GPG: 0x79529A1E http://imincik.github.io/0x79529A1E.key ivan.min...@gista.sk GPG: 0xD714B02C http://imincik.github.io/0xD714B02C.key -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJU7M3cAAoJEPfdLsR5UpoeBnQH/R7gQtUuKgc6kVSODvsf1VjK HLn3yw/FwyTAgZEz1c4OLEhM4AbvarxKOcDBuqlcls/Z2gOuRp4FE7urll+Vjqwm SJSunfK3NzWf142RZgtW1CS9KqQmuIkK+pqEHeFICmX7CcM2zjZ2JMu65dF380CF jsOBFGGa6ZqvEiBqlSZbKQecLhDN29J+vfF16VbEX2GHnHiowJb+mR0pRruplh4w CSf+B1EPvUw7iv2IqyJFWQFh8qahA5muFRjSKNk183i1gnEslEfLBN/YSDbhzY6d NZImXetc2Ze78xP2gFMnHcn+rrY1pcmsgwP4+0UI5rEG2LNVVU9kD1WlTOHG7v8= =9jef -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Enter expressions into spin boxes?
Confirmed here. I also can not insert operators in numerical fields. Best regards, Pedro 2015-02-24 15:34 GMT+00:00 Paolo Cavallini : > Hi all. > I'm trying to insert simple expressions, but operators (* + etc.) are > not entered. > A local problem or a bug? > 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] QGIS and GRASS 7.0.0
On Tue, Feb 24, 2015 at 3:28 AM, Radim Blazek wrote: > - modules GUI - my idea is to throw away the qgm and qgc definitions > and auto generate GUI for modules with all options based on > --interface-description only, also the list of modules would be auto > generated for all modules. > Hi Radim, it would be good if you can include GRASS Addons, too. There is a lot of requests for installing/running GRASS Addons from QGIS, e.g. at gis.stackexchange.com. Also, there are some files in GRASS GIS which might be quite useful [1]. toolboxes.xml [2] contains GRASS GIS modules sorted into different tooboxes. They are currently not part of the official API but it is just a matter of declaring them as part of API I guess [3]. GRASS wxGUI is using these files to create a menu and module tree in Search module tab. It is also a way to customize wxGUI [4] but that's not related to QGIS use case. Loading Addons dynamically to menu or module tree including their descriptions seems to be a bit challenging but if nothing else wxGUI can always run a module installed using g.extension (or custom user script) if it can run and give --interface-description. Best, Vaclav [1] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml [2] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml/toolboxes.xml [3] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/docs/wxgui_sphinx/src/wxgui_toolboxes.rst [4] http://grass.osgeo.org/grass70/manuals/wxGUI.toolboxes.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Fwd: Re: Re: QGIS and GRASS 7.0.0
On Tue, Feb 24, 2015 at 6:19 AM, Paolo Cavallini wrote: > > Messaggio Inoltrato > > Oggetto: Re: [Qgis-developer] QGIS and GRASS 7.0.0 > > Data: Tue, 24 Feb 2015 08:08:18 +0100 > > Mittente: Paolo Cavallini > > Organizzazione: Faunalia > > A: Pedro Venâncio > > CC: qgis-developer > > > > Olá Pedro, > > > > Il 23/02/2015 22:06, Pedro Venâncio ha scritto: > > > >> Despite the great advantages of GRASS commands in Processing, I think > >> that the GRASS plugin still plays an important role and is an excellent > >> interface for GRASS. For those who still like to use the paradigm of > >> locations, mapsets and the GRASS topological model, GRASS plugin is very > >> important, because then it allows to use all QGIS tools, for example, to > >> create layouts using the Composer, etc. > > > > Agreed. Moreover, the overhead of importing/exporting data for each step > > of a complex analysis puts GRASS algs to a disadvantage for Processing > > users. > > The overhead is not necessarily needed in case of raster maps: > > Workflow example: > # register GeoTIFF file in GRASS GIS database (no import but direct link): > r.external input=tempmap1.tif output=modis_celsius > > # define output directory for files resulting from GRASS calculation: > # i.e. GRASS GIS writes directly a GeoTIFF file here, no GRASS DB storage > r.external.out directory=$HOME/gisoutput/ format="GTiff" > > # perform calculation (here: extract pixels > 20 deg C) and > # write output directly as GeoTIFF: > r.mapcalc "warm.tif = if(modis_celsius > 20.0, modis_celsius, null() )" > > # cease GDAL output connection and turn back to write GRASS raster files: > r.external.out -r > > # use the result elsewhere > qgis $HOME/gisoutput/warm.tif > END Workflow example: > > This approach could be used in "Processing" as well. Or in a WPS context > etc. > Hi, see also GRASS GIS (+QGIS?) GSoC 2015 idea for further discussion on that topic: http://trac.osgeo.org/grass/wiki/GSoC/2015#Neweasy-to-usecommandlineinterfaceforGRASSGIS >From the QGIS Processing source code, I actually got an impression that this approach is already used for rasters. Vaclav ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] pyqgis dxf
I changed the code without lucky
fitxer="/tmp/prova.dxf"
uri = QgsDataSourceURI()
uri.setDatabase(fitxer)
uri.setDataSource('', 'entities', 'OGR_GEOMETRY', "OGR_GEOMETRY='POINT'",
'fid')
layer = QgsVectorLayer(uri.uri(), 'prova', 'ogr')
print 'isValid:', layer.isValid()
2015-02-24 16:12 GMT+01:00 Alexandre Busquets :
> Hi,
>
> can somebody help me with load a dxf file as a vector layer?
>
> Is QgsDataSourceURI an option? I tried with this code, but I haven't been
> lucky.
>
> fitxer="/tmp/prova.dxf"
> uri = QgsDataSourceURI()
> uri.setDatabase(fitxer)
> uri.setDataSource('', 'entities', None, "OGR_GEOMETRY='POINT'",
> 'EntityHandle')
>
> layer = QgsVectorLayer(uri.uri(), 'prova', 'ogr')
>
> print 'source:', layer.source()
> print 'isValid:', layer.isValid()
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
On Tue, Feb 24, 2015 at 10:42:40PM +0700, Martin Dobias wrote: > Hi Paolo > > On Tue, Feb 24, 2015 at 10:23 PM, Paolo Cavallini > wrote: > > > Il 24/02/2015 16:18, Sandro Santilli ha scritto: > > > > > I wouldn't consider that one a bug. The default is for contextual > > > WMS legend to be off (it's not a standard call). Eventually you > > > might want a per-server default configuration, but would be > > > an enhancement. > > > > sorry, I do not see your point: if an user chooses to display the legend > > for a server, it is more than likely that he will expect further > > connections to that server will remember his choice. > > but OK, it can be an enhancement. > > I would even argue that such option should not exist. Most users will > probably not understand its meaning. If necessary, such option should be in > WMS server configuration dialog, not in the main WMS dialog. Anyway I think > QGIS should try to figure it out itself whether the server supports > contextual legend. Contextual legend is a non-standard feature, not sure how QGIS could rely on capability info to figure out. Moreover the user might want it enabled only for some of the layers. The per-layer option was explicitly requested by the funding party (Regione Toscana). So I would see a per-server option to determine a per-layer default (overridable) and eventually an "autodetect" choice for that option in case there's a likely-to-work way to do that. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Bookmarks can be imported/exported?
Mine imported with the propers names but wrong extent. Although the extent saved with the bookmark appears correct. Also my SRID is not saving correctly - it shoudl be 2240 1 Stadium 2536428.56329485 1437239.38093017 2538453.53270209 1438274.10899181 222 On 02/24/2015 10:41 AM, Paolo Cavallini wrote: Il 24/02/2015 16:39, Paolo Cavallini ha scritto: Hi all. Sorry for flooding, but while checking the changelog I'm finding a series of issues. Exporting a bookmark and reimporting it results in: * an empty name of the bookmark * a wrong extent. Is this confirmed, ora local issue? furthermore, the output dir is not remembered. All the best. -- - Randal Hale North River Geographic Systems, Inc http://www.northrivergeographic.com 423.653.3611 rjh...@northrivergeographic.com twitter:rjhale http://about.me/rjhale http://www.northrivergeographic.com/introduction-to-quantum-gis ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
Hi Paolo On Tue, Feb 24, 2015 at 10:23 PM, Paolo Cavallini wrote: > Il 24/02/2015 16:18, Sandro Santilli ha scritto: > > > I wouldn't consider that one a bug. The default is for contextual > > WMS legend to be off (it's not a standard call). Eventually you > > might want a per-server default configuration, but would be > > an enhancement. > > sorry, I do not see your point: if an user chooses to display the legend > for a server, it is more than likely that he will expect further > connections to that server will remember his choice. > but OK, it can be an enhancement. > I would even argue that such option should not exist. Most users will probably not understand its meaning. If necessary, such option should be in WMS server configuration dialog, not in the main WMS dialog. Anyway I think QGIS should try to figure it out itself whether the server supports contextual legend. Cheers Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Bookmarks can be imported/exported?
Hi all. Sorry for flooding, but while checking the changelog I'm finding a series of issues. Exporting a bookmark and reimporting it results in: * an empty name of the bookmark * a wrong extent. Is this confirmed, ora local issue? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Bookmarks can be imported/exported?
Il 24/02/2015 16:39, Paolo Cavallini ha scritto: > Hi all. > Sorry for flooding, but while checking the changelog I'm finding a > series of issues. Exporting a bookmark and reimporting it results in: > * an empty name of the bookmark > * a wrong extent. > Is this confirmed, ora local issue? furthermore, the output dir is not remembered. 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] Enter expressions into spin boxes?
Hi all. I'm trying to insert simple expressions, but operators (* + etc.) are not entered. A local problem or a bug? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
Il 24/02/2015 16:18, Sandro Santilli ha scritto: > I wouldn't consider that one a bug. The default is for contextual > WMS legend to be off (it's not a standard call). Eventually you > might want a per-server default configuration, but would be > an enhancement. sorry, I do not see your point: if an user chooses to display the legend for a server, it is more than likely that he will expect further connections to that server will remember his choice. but OK, it can be an enhancement. all the best, and thanks. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
On Tue, Feb 24, 2015 at 02:40:11PM +0100, Paolo Cavallini wrote: > Il 24/02/2015 13:22, Sandro Santilli ha scritto: > > > Each time you open the project after saving it ? > > Or each time you add a new WMS layer ? > > the second event I wouldn't consider that one a bug. The default is for contextual WMS legend to be off (it's not a standard call). Eventually you might want a per-server default configuration, but would be an enhancement. --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] pyqgis dxf
Hi,
can somebody help me with load a dxf file as a vector layer?
Is QgsDataSourceURI an option? I tried with this code, but I haven't been
lucky.
fitxer="/tmp/prova.dxf"
uri = QgsDataSourceURI()
uri.setDatabase(fitxer)
uri.setDataSource('', 'entities', None, "OGR_GEOMETRY='POINT'",
'EntityHandle')
layer = QgsVectorLayer(uri.uri(), 'prova', 'ogr')
print 'source:', layer.source()
print 'isValid:', layer.isValid()
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Issues with new measuring dialog
Hi Paolo, * the tool is always in the foreground, covering all others (also from > other applications) > * when clicking on Help, the help window stays in the background > I confirm these two in Windows > * more seriously, the tool fails to detect the measure unit and all > other info (ellipsoid, etc.) of my layer and project, unclear why. > but not this one. Apparently the calculations and units are working well, both with OTF on or off. Best regards, Pedro ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
Il 24/02/2015 13:22, Sandro Santilli ha scritto: > Each time you open the project after saving it ? > Or each time you add a new WMS layer ? the second event cheers -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Contextual WMS legend graphics forgets option
On Tue, Feb 24, 2015 at 12:59:42PM +0100, Paolo Cavallini wrote: > Hi all. > When adding a WMS layer, the choice to display the contextual legend is > forgotten each time. To me this seems a small bug, am I wrong? Each time you open the project after saving it ? Or each time you add a new WMS layer ? --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] The new simplify feature - settings stored in *.qgs-file ?
Hi Larissa, usally settings are saved in the settings managed by QSetting. I remember this info is already available in the manuals. this is extracted from: http://docs.qgis.org/2.6/en/docs/user_manual/introduction/qgis_configuration.html#network-menu Settings are saved in a text file: $HOME/.config/QGIS/QGIS2.conf You can find your settings in: $HOME/Library/Preferences/org.qgis.qgis.plist Settings are stored in the registry under: HKEY\CURRENT_USER\Software\QGIS\qgis regards, Luigi Pirelli On 24 February 2015 at 11:27, Larissa Junek wrote: > Dear all, > I'm describing the new simply feature tool in the user manual 2.8. > Martin Dobias mentioned the possibility to save the simplify settings > in settings. I know that there are severel possibilities to save QGIS > settings in files. For the readers of the user manual I think it's > sufficient to describe that the settings are stored in the *.qgs-file. > Am I barking up the wrong tree with this? > > Thanks! > > Kind 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
[Qgis-developer] Temporary memory layers: wrong dialog size
Hi all. The window for the creation of new memory layers appears wrong: ic can be resized to zero width and reduced to only window header in height. Should I open a ticket? Also, when adding an element the attribute popup appears, but since field cannot be added during creation, the window is useless and annoying: should the popup be suppressed, or better give the user to opportunity to add fields? Other ticket? 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] Contextual WMS legend graphics forgets option
Hi all. When adding a WMS layer, the choice to display the contextual legend is forgotten each time. To me this seems a small bug, am I wrong? 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] Issues with new measuring dialog
Hi all. I'm finding several annoying issue with the new measurement dialog (Debian Sig, Gnome 3, QGIS 2.8): * the tool is always in the foreground, covering all others (also from other applications) * when clicking on Help, the help window stays in the background * more seriously, the tool fails to detect the measure unit and all other info (ellipsoid, etc.) of my layer and project, unclear why. Any suggestion? Thanks. -- 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] Attribute names and Strings are not displayed correctly
Hi,
I guess this is not a bug but some problem with external libraries. In
my qgis (using Ubuntu 14.10) and have the problem since a few weeks. I
don't know when it started exactly,but I guess it was some update.
Whenever I look at the attribute table or at the attribute dialog for a
shape, the attribute names are shown as _1,_2,_3, ... In the attributes,
Strings are generally displayed as "NULL". Numbers are fine.
Since the Problem occurs, I have reinstalled qgis several times and also
tried out several versions (2.2,2.6,2.8) but nothing changed.
In the message window, I found one warning by python:
warning:/usr/lib/python2.7/dist-packages/PyQt4/uic/uiparser.py:890:
PendingDeprecationWarning: This method will be removed in future
versions. Use 'elem.iter()' or 'list(elem.iter())' instead.
for include in elem.getiterator("include"):
traceback: File "", line 1, in
File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 219, in
startPlugin
plugins[packageName] = package.classFactory(iface)
File "/usr/share/qgis/python/plugins/MetaSearch/__init__.py", line 28,
in classFactory
from MetaSearch.plugin import MetaSearchPlugin
File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 478, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
File "/usr/share/qgis/python/plugins/MetaSearch/plugin.py", line 31, in
from MetaSearch.dialogs.maindialog import MetaSearchDialog
File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 478, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
File "/usr/share/qgis/python/plugins/MetaSearch/dialogs/maindialog.py",
line 49, in
from MetaSearch.dialogs.manageconnectionsdialog import
ManageConnectionsDialog
File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 478, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
File
"/usr/share/qgis/python/plugins/MetaSearch/dialogs/manageconnectionsdialog.py",
line 39, in
BASE_CLASS = get_ui_class('manageconnectionsdialog.ui')
File "/usr/share/qgis/python/plugins/MetaSearch/util.py", line 59, in
get_ui_class
return loadUiType(ui_file_full)[0]
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/__init__.py", line 210,
in loadUiType
winfo = compiler.UICompiler().compileUi(uifile, code_string,
from_imports, resource_suffix)
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/Compiler/compiler.py",
line 139, in compileUi
w = self.parse(input_stream, resource_suffix)
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/uiparser.py", line 992,
in parse
actor(elem)
File "/usr/lib/python2.7/dist-packages/PyQt4/uic/uiparser.py", line 890,
in readResources
for include in elem.getiterator("include"):
I don't think that this causes the problem, but I don't know. Any
developer with any suggestion? :)
Thanks!
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Fwd: Re: Re: QGIS and GRASS 7.0.0
I'm forwarding here comments from Markus Neteler. All the best. > Messaggio Inoltrato > Oggetto: Re: [Qgis-developer] QGIS and GRASS 7.0.0 > Data: Tue, 24 Feb 2015 08:08:18 +0100 > Mittente: Paolo Cavallini > Organizzazione: Faunalia > A: Pedro Venâncio > CC: qgis-developer > > Olá Pedro, > > Il 23/02/2015 22:06, Pedro Venâncio ha scritto: > >> Despite the great advantages of GRASS commands in Processing, I think >> that the GRASS plugin still plays an important role and is an excellent >> interface for GRASS. For those who still like to use the paradigm of >> locations, mapsets and the GRASS topological model, GRASS plugin is very >> important, because then it allows to use all QGIS tools, for example, to >> create layouts using the Composer, etc. > > Agreed. Moreover, the overhead of importing/exporting data for each step > of a complex analysis puts GRASS algs to a disadvantage for Processing > users. The overhead is not necessarily needed in case of raster maps: Workflow example: # register GeoTIFF file in GRASS GIS database (no import but direct link): r.external input=tempmap1.tif output=modis_celsius # define output directory for files resulting from GRASS calculation: # i.e. GRASS GIS writes directly a GeoTIFF file here, no GRASS DB storage r.external.out directory=$HOME/gisoutput/ format="GTiff" # perform calculation (here: extract pixels > 20 deg C) and # write output directly as GeoTIFF: r.mapcalc "warm.tif = if(modis_celsius > 20.0, modis_celsius, null() )" # cease GDAL output connection and turn back to write GRASS raster files: r.external.out -r # use the result elsewhere qgis $HOME/gisoutput/warm.tif END Workflow example: This approach could be used in "Processing" as well. Or in a WPS context etc. > BTW, I'm unsure about the G7 support in the Browser: could someone check > thoroughly? > >> If no one is interested in making the port of the plugin for GRASS 7, we >> could try through a crowdfounding initiative. Who was behind the initial >> creation of GRASS plugin? > > Yes, I have been talking about that. Radim did most of the work on the > plugin. If he (or eventually others) are available, a crowdfounding > initiative could be appropriate. Yes, it would be great to get the plugin updated as well. >> I've been checking the differences and they are indeed few. Please see >> the spreadsheet attached. > > Obrigado for this. > >> Some commands seem that were adaptations of other algorithms, made for >> Processing, as they are not in the 6 manual, or in the 7: >> r.cost.full.raster, r.drain.coordinate, r.terraflow.short, >> v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. > > Yes, these are adaptations of the original commands, in order to make > them more usable from QGIS. Update to GRASS GIS 7 should not be a lot of work, see below. >> Others seem that have been removed from GRASS 7 (r.average, r.bilinear, >> r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. It is all documented in the release notes: http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Replacedandremovedmodules [...] raster: - r.average: merged into G7:r.statistics, G7:r.stats.zonal, G7:r.stats.quantile - r.bilinear: merged into G7:r.resamp.interp - r.bitpattern: G7:r.mapcalc (&&& and | | | operators) + G7:i.modis.qa offer the same and more functionality [...] - r.surf.idw2: moved to Addons (install with G7:g.extension) - r.terraflow.short (merged into FP version G7:r.terraflow is sufficient) [...] >> There are five that seem important to me, which are in GRASS 7, in >> Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, >> r.spread, r.univar, v.kernel. >> >> Finally, there are two commands that are on GRASS 7 and were not in 6: >> r.viewshed (which replace r.los) and r.relief (which replace >> r.shaded.relief). > > Overall, I think these are minor issues. If someone really miss them, > they can ask, and we can add them. I updated "Processing" accordingly, so you can see the needed changes from the changelog. Or simply here: http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Optionschanges Best regards, Markus -- http://courses.neteler.org http://gis.cri.fmach.it/neteler/ Next GRASS GIS 7 courses: Berlin, 16 +17 March 2015 http://courses.neteler.org/next-training/ > All the best, and thanks again. > -- > 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
[Qgis-developer] The new simplify feature - settings stored in *.qgs-file ?
Dear all, I'm describing the new simply feature tool in the user manual 2.8. Martin Dobias mentioned the possibility to save the simplify settings in settings. I know that there are severel possibilities to save QGIS settings in files. For the readers of the user manual I think it's sufficient to describe that the settings are stored in the *.qgs-file. Am I barking up the wrong tree with this? Thanks! Kind regards, Larissa ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi Radim, thanks a lot for this. Il 24/02/2015 09:28, Radim Blazek ha scritto: > - modules GUI - my idea is to throw away the qgm and qgc definitions > and auto generate GUI for modules with all options based on > --interface-description only, also the list of modules would be auto > generated for all modules. The reason is my impression that there are > no volunteers willing to maintain qgm and qgc. If there are volunteers > to do that (no programming, xml editing only) let me know and I'll > include keeping of current system in the proposal. IMHO having the possibility of making simplified modules is a bi plus, and would better not be missed. Thanks again. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Olá todos, I'am already preparing crowdfunding campaign for GRASS plugin upgrade. It will include: - qgisgrasslib upgrade to GRASS 7 - single build with both GRASS 6 and 7 (GRASS version chosen by environmental variables on start up) - move plugin browser functionality to standard QGIS browser (meta info widget, delete and rename action) - implement raster and vector import via browser drag and drop (including reprojection) - new/open/close location tools upgrade to GRASS 7 - region editor upgrade to GRASS 7 - upgrade GRASS shell to the last qtermwidget - modules GUI - my idea is to throw away the qgm and qgc definitions and auto generate GUI for modules with all options based on --interface-description only, also the list of modules would be auto generated for all modules. The reason is my impression that there are no volunteers willing to maintain qgm and qgc. If there are volunteers to do that (no programming, xml editing only) let me know and I'll include keeping of current system in the proposal. - vector editing overall upgrade and enhancement more integrated with standard QGIS tools - standard editing tools (e.g. node tool) - snapping to other layers - undo/redo - attribute forms - possibility to change topological symbology via standard style dialog - standard rendering of not edited layers based on edited map (i.e. draw filled polygons on background during editing) I am currently coding proof of concept for vector editing to be sure that it is feasible at all. I hope to launch the campaign in about 2-3 weeks. Radim On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio wrote: > Olá Paolo, > > >> this will require a reasonable amount of work. I have raised the issue >> several times; sadly it seems nobody is willing to invest the necessary >> resources on this. > > > Despite the great advantages of GRASS commands in Processing, I think that > the GRASS plugin still plays an important role and is an excellent interface > for GRASS. For those who still like to use the paradigm of locations, > mapsets and the GRASS topological model, GRASS plugin is very important, > because then it allows to use all QGIS tools, for example, to create layouts > using the Composer, etc. > > If no one is interested in making the port of the plugin for GRASS 7, we > could try through a crowdfounding initiative. Who was behind the initial > creation of GRASS plugin? > > > >> >> BTW, would you mind giving us a list of the missing modules in >> Processing? AFAIK these should be only obsolete and useless ones, but if >> there is some genuinely missing we should be able to fix this rather >> easily. > > > > I've been checking the differences and they are indeed few. Please see the > spreadsheet attached. > > Some commands seem that were adaptations of other algorithms, made for > Processing, as they are not in the 6 manual, or in the 7: > r.cost.full.raster, r.drain.coordinate, r.terraflow.short, > v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. > > Others seem that have been removed from GRASS 7 (r.average, r.bilinear, > r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. > > There are five that seem important to me, which are in GRASS 7, in > Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, > r.spread, r.univar, v.kernel. > > Finally, there are two commands that are on GRASS 7 and were not in 6: > r.viewshed (which replace r.los) and r.relief (which replace > r.shaded.relief). > > > Thanks! > > Best regards, > Pedro Venâncio > > > ___ > 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 GRASS 7.0.0
Il 24/02/2015 09:02, PIERRE Sylvain ha scritto: > Hi GRASS plugin users ;-) > > > > +1 Pedro > > > > GRASS plugin is definitely the most convenient way to access GRASS > functionalities… > > With plugin you have GRASS embedded in QGIS, you get the best of both worlds Merci Pierre. Unfortunately, +1 is not enough here: we need someone to either coding, or sponsoring a developer. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS and GRASS 7.0.0
Hi GRASS plugin users ;-) +1 Pedro GRASS plugin is definitely the most convenient way to access GRASS functionalities… With plugin you have GRASS embedded in QGIS, you get the best of both worlds Sylvain De : qgis-developer-boun...@lists.osgeo.org [mailto:qgis-developer-boun...@lists.osgeo.org] De la part de Pedro Venâncio Envoyé : lundi 23 février 2015 22:07 À : Paolo Cavallini Cc : qgis-developer Objet : Re: [Qgis-developer] QGIS and GRASS 7.0.0 Olá Paolo, this will require a reasonable amount of work. I have raised the issue several times; sadly it seems nobody is willing to invest the necessary resources on this. Despite the great advantages of GRASS commands in Processing, I think that the GRASS plugin still plays an important role and is an excellent interface for GRASS. For those who still like to use the paradigm of locations, mapsets and the GRASS topological model, GRASS plugin is very important, because then it allows to use all QGIS tools, for example, to create layouts using the Composer, etc. If no one is interested in making the port of the plugin for GRASS 7, we could try through a crowdfounding initiative. Who was behind the initial creation of GRASS plugin? BTW, would you mind giving us a list of the missing modules in Processing? AFAIK these should be only obsolete and useless ones, but if there is some genuinely missing we should be able to fix this rather easily. I've been checking the differences and they are indeed few. Please see the spreadsheet attached. Some commands seem that were adaptations of other algorithms, made for Processing, as they are not in the 6 manual, or in the 7: r.cost.full.raster, r.drain.coordinate, r.terraflow.short, v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. Others seem that have been removed from GRASS 7 (r.average, r.bilinear, r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. There are five that seem important to me, which are in GRASS 7, in Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, r.spread, r.univar, v.kernel. Finally, there are two commands that are on GRASS 7 and were not in 6: r.viewshed (which replace r.los) and r.relief (which replace r.shaded.relief). Thanks! Best regards, Pedro Venâncio ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
