Re: [Qgis-developer] QGIS server docs
Hi Marco, I also wanted to add some Python Plugin related stuff. I kindly as the documentation people to create the skeleton to hold server docs in the main QGIS documentation. 2015-02-23 11:13 GMT+01:00 Marco Hugentobler marco.hugentob...@sourcepole.ch: Hi I'd like to update the QGIS server documentation (tolerance parameters for GetFeatureInfo). What is the right place to do so? In the https://github.com/qgis/QGIS-Documentation repo, I can't find anything related to the server. Thanks, Marco On 18.12.2014 10:23, Marco Hugentobler wrote: Hi all Ok from me to move the server documentation to the doc. Could someone from the documentation team import the current content? Regards, Marco On 18.12.2014 09:39, Richard Duivenvoorde wrote: On 18-12-14 09:20, Yves Jacolin wrote: hello, Don't we need to move this wiki page to the doc also? IF Marco is OK with it (as he creates the most updated info I think), I would also prefer to move all info from the wiki page into documentation (and update the wikipage to link to the docs then). I think QGIS server deserves a thorough Chapter in the docs nowadays. Regards, Richard Duivenvoorde -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, Switzerland marco.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 -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS server docs
Hi all, not sure if this is correct place, but there is a section in QGIS User Guide about QGIS Server [0]. For developer-related stuff maybe it is better to create chapter in PyQGIS CookBook. [0] https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manual/working_with_ogc/ogc_server_support.rst 2015-02-23 12:18 GMT+02:00 Alessandro Pasotti apaso...@gmail.com: Hi Marco, I also wanted to add some Python Plugin related stuff. I kindly as the documentation people to create the skeleton to hold server docs in the main QGIS documentation. 2015-02-23 11:13 GMT+01:00 Marco Hugentobler marco.hugentob...@sourcepole.ch: Hi I'd like to update the QGIS server documentation (tolerance parameters for GetFeatureInfo). What is the right place to do so? In the https://github.com/qgis/QGIS-Documentation repo, I can't find anything related to the server. Thanks, Marco On 18.12.2014 10:23, Marco Hugentobler wrote: Hi all Ok from me to move the server documentation to the doc. Could someone from the documentation team import the current content? Regards, Marco On 18.12.2014 09:39, Richard Duivenvoorde wrote: On 18-12-14 09:20, Yves Jacolin wrote: hello, Don't we need to move this wiki page to the doc also? IF Marco is OK with it (as he creates the most updated info I think), I would also prefer to move all info from the wiki page into documentation (and update the wikipage to link to the docs then). I think QGIS server deserves a thorough Chapter in the docs nowadays. Regards, Richard Duivenvoorde -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, Switzerland marco.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 -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-user] Better tags for plugins
Hi Paulo, Surely this can be enforced by having requirements for acceptance on the official plugin repository. If a plugin doesn't fulfil all the requirements, it doesn't get included. Possible requirements (to give an idea): - Brief description of plugin, - Detailed explanation of plugin. - How to use documentation. - Useful, consistent tags. - Homepage/tracker/repository links (that work and go somewhere relevant). - Author - Changelog - Date of last plugin release - Supported QGIS Versions This may (will) mean fewer plugins, however the plugins that don't get included would be ones with poor user documentation. Most plugins fail quite badly at making it clear what they do, let alone how to use them. That lot wouldn't take much more than half an hour to do for any given plugin (with only a few very-complex exceptions) and would make plugins much more useable. Cheers, Jonathan -Original Message- From: qgis-developer-boun...@lists.osgeo.org [mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf Of Paolo Cavallini Sent: Friday, February 20, 2015 1:12 PM To: Lynton Cox Cc: qgis-user; qgis-developer Subject: Re: [Qgis-developer] [Qgis-user] Better tags for plugins Hi Lynton, Il 19/02/2015 19:21, Lynton Cox ha scritto: Please don't forget the newbies need to know exactly what plugins might be used for - some have hardly any description. Once out of the basic QGIS manual finding one's way around isnt that easy. Many amateurs in areas such as local studies realise how useful GIS but see that jargon and acronyms can fog the path. Yes, the About is often neglected. I invite plugin authors to add a reasonable description, but I cannot enforce this. A very good idea would be for the user to write a short note and add it to a feature request, through the plugin bugtracker; even better, this could be added as a Pull Request on the plugin repository. All the best, and thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html *New course* QGIS for naturalists: http://www.faunalia.eu/en/nat_course.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer This message has been scanned for viruses by MailControl - www.mailcontrol.com Click https://www.mailcontrol.com/sr/SVGcvJSn6gnGX2PQPOmvUizKrmxxhcEGGlzw3ci4oH!oYUmIc3YrHGSGHzny8KZlOXtgio1tB25zr!jqbv!p6A== to report this email as spam. HR Wallingford and its subsidiaries uses faxes and emails for confidential and legally privileged business communications. They do not of themselves create legal commitments. Disclosure to parties other than addressees requires our specific consent. We are not liable for unauthorised disclosures nor reliance upon them. If you have received this message in error please advise us immediately and destroy all copies of it. HR Wallingford Limited Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom Registered in England No. 02562099 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Error in new Metasearch
On Mon, 23 Feb 2015, Paolo Cavallini wrote: Date: Mon, 23 Feb 2015 08:45:42 +0100 From: Paolo Cavallini cavall...@faunalia.it To: Tom Kralidis tomkrali...@gmail.com Cc: Richard Duivenvoorde rich...@duif.net, qgis-developer qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Error in new Metasearch Il 20/02/2015 19:11, Tom Kralidis ha scritto: This works for me with both a fresh 2.8.0 via OSGeo4W with MetaSearch 0.3.2 default (i.e. not fetched from plugins.qgis.org) as well as a fresh 2.8.0 via OSGeo4W with fetching the plugin from plugins.qgis.org. I'm able to work with the UNEP server at http://metadata.grid.unep.ch:8080/geonetwork/srv/eng/csw as well as http://services.grid.unep.ch:8080/geonetwork/srv/eng/csw , tested via English and Italian locale. Are these the servers you are working with? Hi Tom, checked again, on a fresh install (2.8 on Debian Sid). I think I found the problem: editing the connection shows that the URL is empty. Adding the address you mention fixes it. Unclear why the default server URL it is empty, however. All the best, and thanks. Hi Paolo: I was able to reproduce this. In loading the default CSW connections, if a CSW server name contains '/', this causes issue in the saved settings/registry values. I've since fixed this in master, 2.6 and 2.8 branch. Having said this, we should add a check to prevent users adding new CSW connection names containing a '/'. Filed in http://hub.qgis.org/issues/12239 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Filter layer after join, error/impossible
Thank's Hugo Will the patch be include in next release (2.8.1)? And what about the small function to convert layer to virtual layer? By the way, I've found a workaround: 1 begin first by filtering the wanna be joined table 2 perform join 3 Display only needed features by setting NoSymbol to other features in a rule-rendering style... Sylvain -Message d'origine- De : qgis-developer-boun...@lists.osgeo.org [mailto:qgis-developer-boun...@lists.osgeo.org] De la part de Hugo Mercier Envoyé : vendredi 20 février 2015 17:56 À : qgis-developer@lists.osgeo.org Objet : Re: [Qgis-developer] Filter layer after join, error/impossible Hi Pierre, Le 20/02/2015 16:31, PIERRE Sylvain a écrit : Hi, I've same behaviour with different case : I want to filter a layer (Oracle/Postgis) after performing join with tabular data (Excel, MSSQL tested). First Filtering by Layer properties Ui is disabled (greyed button) Filtering possible by Menu Layer-Filter Joined fields appears, and Sample values do so. But when I want to test filter I got an error message box: (sorry in French) Une erreur a été rencontrée lors de l'exécution de la requête. Le prestataire de donné a dit : ORA-00904: V_SIG_SITE_Site_Nature : identificateur non valide Impossible d'exécuter cette déclaration » The filtering of a layer is done at the provider level, where nothing is known about the joined fields (they only exist QGIS side). I've submitted a patch (1) to fix the UI issues: we will be able to filter on layers with joined fields, but only on fields of the primary table. If you need to filter on joined fields, I am working on a virtual layer provider where you could use any SQL joins. A small function would allow to convert a layer with joins to a virtual layer and apply filtering on it. More on this next week, hopefully ... (1) https://github.com/qgis/QGIS/pull/1911 ___ 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] Better tags for plugins
In my experience Paulo has been doing good job of encouraging developers to do just that. If we want to formalize it further it might be a good idea to set the requirements lower for experimental plugins as it happens to be a helpful means of facilitating testing plugins on different platforms. TSW On Feb 23, 2015 4:26 AM, Jonathan Moules j.mou...@hrwallingford.com wrote: Hi Paulo, Surely this can be enforced by having requirements for acceptance on the official plugin repository. If a plugin doesn't fulfil all the requirements, it doesn't get included. Possible requirements (to give an idea): - Brief description of plugin, - Detailed explanation of plugin. - How to use documentation. - Useful, consistent tags. - Homepage/tracker/repository links (that work and go somewhere relevant). - Author - Changelog - Date of last plugin release - Supported QGIS Versions This may (will) mean fewer plugins, however the plugins that don't get included would be ones with poor user documentation. Most plugins fail quite badly at making it clear what they do, let alone how to use them. That lot wouldn't take much more than half an hour to do for any given plugin (with only a few very-complex exceptions) and would make plugins much more useable. Cheers, Jonathan -Original Message- From: qgis-developer-boun...@lists.osgeo.org [mailto: qgis-developer-boun...@lists.osgeo.org] On Behalf Of Paolo Cavallini Sent: Friday, February 20, 2015 1:12 PM To: Lynton Cox Cc: qgis-user; qgis-developer Subject: Re: [Qgis-developer] [Qgis-user] Better tags for plugins Hi Lynton, Il 19/02/2015 19:21, Lynton Cox ha scritto: Please don't forget the newbies need to know exactly what plugins might be used for - some have hardly any description. Once out of the basic QGIS manual finding one's way around isnt that easy. Many amateurs in areas such as local studies realise how useful GIS but see that jargon and acronyms can fog the path. Yes, the About is often neglected. I invite plugin authors to add a reasonable description, but I cannot enforce this. A very good idea would be for the user to write a short note and add it to a feature request, through the plugin bugtracker; even better, this could be added as a Pull Request on the plugin repository. All the best, and thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html *New course* QGIS for naturalists: http://www.faunalia.eu/en/nat_course.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer This message has been scanned for viruses by MailControl - www.mailcontrol.com Click https://www.mailcontrol.com/sr/SVGcvJSn6gnGX2PQPOmvUizKrmxxhcEGGlzw3ci4oH!oYUmIc3YrHGSGHzny8KZlOXtgio1tB25zr!jqbv!p6A== to report this email as spam. HR Wallingford and its subsidiaries uses faxes and emails for confidential and legally privileged business communications. They do not of themselves create legal commitments. Disclosure to parties other than addressees requires our specific consent. We are not liable for unauthorised disclosures nor reliance upon them. If you have received this message in error please advise us immediately and destroy all copies of it. HR Wallingford Limited Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom Registered in England No. 02562099 ___ 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] Upgrading qgis
I upgraded ubuntu 14.04 to qgis 2.8 yesterday from 2.6. I ended up with the python-qgis at 2.8 - but (i have no clue if this is right or wrong) I have several other libraries still at 2.6 like libqgispython and a few others. On 02/23/2015 03:01 AM, Alex Mandel wrote: On 02/22/2015 11:42 PM, Paolo Cavallini wrote: Hi all, when upgrading qgis from 2.7 to 2.8 on Debian sid, python-qgis is not upgraded automatically, so python support is disabled. All the best. This seems to be a perpetually unresolved bug. Had this same issue upgrading to 2.6 on ubuntu systems. I'm not sure what needs to change in the Debian control file to do this right. Thanks, Alex ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- - 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
[Qgis-developer] [PyQGIS] QgsComposerItem.dataDefinedProperty doesn't return anything
I'm trying to obtain the data defined expression for an HTML item but myitem.dataDefinedProperty(QgsComposerObject.SourceUrl) doesn't return anything. What's wrong? I'm working on latest master (built half an hour ago). giovanni -- Giovanni Allegri http://about.me/giovanniallegri Twitter: https://twitter.com/_giohappy_ 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
Re: [Qgis-developer] [PyQGIS] QgsComposerItem.dataDefinedProperty doesn't return anything
Solved. It must be called on QgsCompomerHtml instead of (a child) QgsComposerFrame. giovanni 2015-02-23 13:40 GMT+01:00 G. Allegri gioha...@gmail.com: I'm trying to obtain the data defined expression for an HTML item but myitem.dataDefinedProperty(QgsComposerObject.SourceUrl) doesn't return anything. What's wrong? I'm working on latest master (built half an hour ago). giovanni -- Giovanni Allegri http://about.me/giovanniallegri Twitter: https://twitter.com/_giohappy_ blog: http://blog.spaziogis.it GEO+ geomatica in Italia http://bit.ly/GEOplus -- Giovanni Allegri http://about.me/giovanniallegri Twitter: https://twitter.com/_giohappy_ 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
Re: [Qgis-developer] Error in new Metasearch
Il 23/02/2015 14:06, Tom Kralidis ha scritto: Hi Paolo: I was able to reproduce this. In loading the default CSW connections, if a CSW server name contains '/', this causes issue in the saved settings/registry values. I've since fixed this in master, 2.6 and 2.8 branch. Thanks Tom. Will this be included in 2.8.1? All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html *New course* QGIS for naturalists: http://www.faunalia.eu/en/nat_course.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-user] Better tags for plugins
I was referring to manual vetting. TSW On Feb 23, 2015 7:49 AM, Alessandro Pasotti apaso...@gmail.com wrote: 2015-02-23 15:41 GMT+01:00 Trevor Wiens tsw@gmail.com: In my experience Paulo has been doing good job of encouraging developers to do just that. If we want to formalize it further it might be a good idea to set the requirements lower for experimental plugins as it happens to be a helpful means of facilitating testing plugins on different platforms. Hi, speaking as the Plugin's repository developer, I would say that implementing different validation rules for experimental/stable plugins would require some not trivial refactoring. But if is there anybody out there willing to help, why not? The code is here: https://github.com/qgis/QGIS-Django/tree/master/qgis-app/plugins and the validator: https://github.com/qgis/QGIS-Django/blob/master/qgis-app/plugins/validator.py#L19 -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Filter layer after join, error/impossible
Hi Pierre, Le 23/02/2015 14:54, PIERRE Sylvain a écrit : Thank's Hugo Will the patch be include in next release (2.8.1)? And what about the small function to convert layer to virtual layer? I think the patch could be included in the next release without harm. It is not strictly speaking a (critical) bug fix, however. So, if a core commiter reads this: what's your opinion ? The virtual layer and conversion function are still under development as a separate plugin and are still to be discussed in order to be integrated. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-user] Better tags for plugins
2015-02-23 16:18 GMT+01:00 Frank M. Howell frankmhow...@gmail.com: My two cents...I understand the validation requirements. But I think the fundamental problem is those plugin authors who submit a plugin for X and then describe it thusly: This is a plugin for X where X is the same name as the plugin. The problem is that this one word or very brief phrase isn't very clear. X may be called Y in another field. There may be several methods to do X (or Y) so the user doesn't really know what's being computed and how. X may do something in one field but may also be an undiscovered solution to a problem in another field so just saying This is a plugin for X just doesn't say much useful stuff. Description is already a required metadata field, of course we have not an AI in place to determine the meaningfulness of the description. This is the list of required metadata fields: 'name', 'description', 'version', 'qgisMinimumVersion', 'author', 'email' Note: I'm always speaking about the official plugins repository. -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Error in new Metasearch
On Mon, 23 Feb 2015, Paolo Cavallini wrote: Date: Mon, 23 Feb 2015 15:22:05 +0100 From: Paolo Cavallini cavall...@faunalia.it To: Tom Kralidis tomkrali...@gmail.com Cc: Richard Duivenvoorde rich...@duif.net, qgis-developer qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Error in new Metasearch Il 23/02/2015 14:06, Tom Kralidis ha scritto: Hi Paolo: I was able to reproduce this. In loading the default CSW connections, if a CSW server name contains '/', this causes issue in the saved settings/registry values. I've since fixed this in master, 2.6 and 2.8 branch. Thanks Tom. Will this be included in 2.8.1? All the best. -- Yes, assuming 2.8.1 gets built off 2.8 branch. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Finalising the changelog for 2.8
We've added one entry and altered another to reflect our contributions on processing. Regards Arnaud Le 21/02/2015 09:19, Tim Sutton a écrit : Hi all We have finished our edits to the visual changelog, the working copy is here: http://changelog.qgis.org/qgis/version/2.8/ Please note that you should not blog / tweet / link to this URL yet, Richard will move it onto the main QGIS.org web site from where it can be translated and where it is statically rendered. Before I give Richard the green light to do that, I would like to mention that at a recent PSC meeting we agreed to allow feature funders and developers to be included in an acknowledgement in the changelog. Thus I would request anyone who funded or developed a feature listed in the change log to please submit to me a change request by email (t...@kartoza.com mailto:t...@kartoza.com) with the following specific format: For funders: **This features was funded by:** [name of your organisation](http://website/of/your/organisation) For developers: **This feature was developed by:** John Doe, Polly Gone, Sim Boll Finally, if there is a key feature that you think should be on the list, at the above web site, please let me know and I will endeavour to add it over the weekend. Please provide clear details about what the new feature does etc. Many thanks Tim -- -- Tim Sutton Visit http://kartoza.com 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 http://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 -- Arnaud Morvan Ingénieur logiciel Tél: +33 (0)4 79 26 57 95 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] pyqgis add postgres table
try:
uri.setDataSource('public', 'persones', None, '', 'id')
Bernhard
Am 23.02.2015 16:18, schrieb Alexandre Busquets:
Hi,
I can't add non geometry tables from postgres with pyqgis, this is my code
uri = QgsDataSourceURI()
uri.setConnection(bd_host, bd_port, bd_db, bd_user, bd_pass)
uri.setDataSource('public', 'persones', '', '', 'id')
taula = QgsVectorLayer(uri.uri(), 'persones', 'postgres')
print taula.isValid()
What is the problem?
Thanks
__ Information from ESET Mail Security, version of virus signature
database 11219 (20150223) __
The message was checked by ESET Mail Security.
http://www.eset.com
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-user] Better tags for plugins
2015-02-23 15:41 GMT+01:00 Trevor Wiens tsw@gmail.com: In my experience Paulo has been doing good job of encouraging developers to do just that. If we want to formalize it further it might be a good idea to set the requirements lower for experimental plugins as it happens to be a helpful means of facilitating testing plugins on different platforms. Hi, speaking as the Plugin's repository developer, I would say that implementing different validation rules for experimental/stable plugins would require some not trivial refactoring. But if is there anybody out there willing to help, why not? The code is here: https://github.com/qgis/QGIS-Django/tree/master/qgis-app/plugins and the validator: https://github.com/qgis/QGIS-Django/blob/master/qgis-app/plugins/validator.py#L19 -- 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] pyqgis add postgres table
Hi,
I can't add non geometry tables from postgres with pyqgis, this is my code
uri = QgsDataSourceURI()
uri.setConnection(bd_host, bd_port, bd_db, bd_user, bd_pass)
uri.setDataSource('public', 'persones', '', '', 'id')
taula = QgsVectorLayer(uri.uri(), 'persones', 'postgres')
print taula.isValid()
What is the problem?
Thanks
___
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á 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_Processing_GRASS_6_vs_7.ods Description: application/vnd.oasis.opendocument.spreadsheet ___ 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
Paolo Cavallini wrote Il 23/02/2015 00:06, Pedro Venâncio ha scritto: QGIS GRASS plugin (qgis-plugin-grass) still depends on the 6.4.4, so it will no longer be available for those who upgrade to GRASS 7.0.0. GRASS 6.4 in Processing has 168 algorithms, GRASS 7 has 153, are a few less, but it will be easier to solve. So how can the issue of GRASS plugin be overcome with the GRASS 7? Ola Pedro, 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. 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. Thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html *New course* QGIS for naturalists: http://www.faunalia.eu/en/nat_course.html ___ Qgis-developer mailing list Qgis-developer@.osgeo http://lists.osgeo.org/mailman/listinfo/qgis-developer the grass 7 command list in qgis processing should be uptodate. see: https://github.com/qgis/QGIS/commit/b7dcd67f3eb2e330742c2dd30f035ea6c31a9973 - best regards Helmut -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-and-GRASS-7-0-0-tp5189299p5189554.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
Re: [Qgis-developer] Print composer font pickers are broken
On 22-02-15 22:33, Nyall Dawson wrote: ... however... making this change meant we got hit with a Qt bug [1] which causes font dialogs with a parent window set to effectively discard their results. Arghh! The worst part is that Jürgen had actually fixed this issue 3 years ago - I should have checked the git history on the effected files to see if there was an explicit reason the parent wasn't correctly set for these dialogs. Checking git is one thing (I'm not blaming you for not doing this for every change...), but maybe also add a comment about this above the line of code, as more and more people are hacking or trying to clean up in QGIS, and this knowledge should be IN the code instead of heads and githubs? Regards, Richard ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Print composer font pickers are broken
On 23 February 2015 at 19:09, Richard Duivenvoorde rdmaili...@duif.net wrote: On 22-02-15 22:33, Nyall Dawson wrote: ... however... making this change meant we got hit with a Qt bug [1] which causes font dialogs with a parent window set to effectively discard their results. Arghh! The worst part is that Jürgen had actually fixed this issue 3 years ago - I should have checked the git history on the effected files to see if there was an explicit reason the parent wasn't correctly set for these dialogs. Checking git is one thing (I'm not blaming you for not doing this for every change...), but maybe also add a comment about this above the line of code, as more and more people are hacking or trying to clean up in QGIS, and this knowledge should be IN the code instead of heads and githubs? Already done (by Jürgen): https://github.com/qgis/QGIS/commit/57ba28c344ed03cd555c31b0301311a93f988e83 Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Upgrading qgis
On 02/22/2015 11:42 PM, Paolo Cavallini wrote: Hi all, when upgrading qgis from 2.7 to 2.8 on Debian sid, python-qgis is not upgraded automatically, so python support is disabled. All the best. This seems to be a perpetually unresolved bug. Had this same issue upgrading to 2.6 on ubuntu systems. I'm not sure what needs to change in the Debian control file to do this right. Thanks, Alex ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Finalising the changelog for 2.8
Hi On Feb 23, 2015 4:56 PM, Arnaud Morvan arnaud.mor...@camptocamp.com wrote: We've added one entry and altered another to reflect our contributions on processing. Thanks! Regards Tim Regards Arnaud Le 21/02/2015 09:19, Tim Sutton a écrit : Hi all We have finished our edits to the visual changelog, the working copy is here: http://changelog.qgis.org/qgis/version/2.8/ Please note that you should not blog / tweet / link to this URL yet, Richard will move it onto the main QGIS.org web site from where it can be translated and where it is statically rendered. Before I give Richard the green light to do that, I would like to mention that at a recent PSC meeting we agreed to allow feature funders and developers to be included in an acknowledgement in the changelog. Thus I would request anyone who funded or developed a feature listed in the change log to please submit to me a change request by email (t...@kartoza.com) with the following specific format: For funders: **This features was funded by:** [name of your organisation]( http://website/of/your/organisation) For developers: **This feature was developed by:** John Doe, Polly Gone, Sim Boll Finally, if there is a key feature that you think should be on the list, at the above web site, please let me know and I will endeavour to add it over the weekend. Please provide clear details about what the new feature does etc. Many thanks 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 -- Arnaud Morvan Ingénieur logiciel Tél: +33 (0)4 79 26 57 95 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex http://www.camptocamp.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] QGIS and GRASS 7.0.0
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. 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. 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. 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). Overall, I think these are minor issues. If someone really miss them, they can ask, and we can add them. 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
Re: [Qgis-developer] QGIS server docs
On 23.02.2015 11:23, Alexander Bruy wrote: Hi all, not sure if this is correct place, but there is a section in QGIS User Guide about QGIS Server [0]. For developer-related stuff maybe it is better to create chapter in PyQGIS CookBook. [0] https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manual/working_with_ogc/ogc_server_support.rst Hi Alex Thank you, this seems the right place for the server (user) documentation. I'll add to that and move the rest of the wiki content over to ogc_server_support.rst Regards, Marco 2015-02-23 12:18 GMT+02:00 Alessandro Pasotti apaso...@gmail.com: Hi Marco, I also wanted to add some Python Plugin related stuff. I kindly as the documentation people to create the skeleton to hold server docs in the main QGIS documentation. 2015-02-23 11:13 GMT+01:00 Marco Hugentobler marco.hugentob...@sourcepole.ch: Hi I'd like to update the QGIS server documentation (tolerance parameters for GetFeatureInfo). What is the right place to do so? In the https://github.com/qgis/QGIS-Documentation repo, I can't find anything related to the server. Thanks, Marco On 18.12.2014 10:23, Marco Hugentobler wrote: Hi all Ok from me to move the server documentation to the doc. Could someone from the documentation team import the current content? Regards, Marco On 18.12.2014 09:39, Richard Duivenvoorde wrote: On 18-12-14 09:20, Yves Jacolin wrote: hello, Don't we need to move this wiki page to the doc also? IF Marco is OK with it (as he creates the most updated info I think), I would also prefer to move all info from the wiki page into documentation (and update the wikipage to link to the docs then). I think QGIS server deserves a thorough Chapter in the docs nowadays. Regards, Richard Duivenvoorde -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, Switzerland marco.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 -- Alessandro Pasotti w3: www.itopen.it ___ 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, Switzerland marco.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
