Re: [Qgis-developer] QEP: QGIS Mapserver Python Plugins
2014-08-29 18:05 GMT+02:00 René-Luc Dhont rldh...@gmail.com: Le 29/08/2014 16:54, Alessandro Pasotti a écrit : 2014-08-29 16:39 GMT+02:00 René-Luc Dhont rldh...@gmail.com: Hi Alessandro Thanks for this interesting input. I'm happy to test it and to develope some use case. I thought it's a good feature and can help to enhance QGIS-Server easily : WPS, WMTS, Table Join Service, WFS2 or other that OGC does not already know. Regards, René-Luc Hello René-Luc, I'm happy to hear that you are going to test it, please let me know how it goes! Keep in mind that it's just a proof of concept, and yes, we need a RFC or QEP: the current implementation is the simplest, less obtrusive and quickest that I could think about. For example, I would consider adding real signals attached to plugins slots and cached parsed projects passed to plugin instances... I'm currently working on a WPS server plugin that bridges Processing and PyWPS (version 3.2.2 since the latest version 4 is tightly bound to werkzeug), now fighting with parameters but it basically works. Can I help ? I already done some works on it ! Regards Hello, I've got a first highly experimental Processing-PyWPS bridging plugin: https://github.com/elpaso/qgis-wps * I've only tested grass convex hull with a small shapefile * GetCapabilties and other requests work with GET calls ony * it needs Processing patches otherwise it hangs when reading pipes from shell process (see [1]) * Processing needs other patches as well to support concurrent requests (for example the grass temporary script storage should be done in tempfile instead of the current processing folder) I don't know Processing enough to say if there aren't any other big showstoppers for this plugin. Still a lot of work to do :) [1] https://github.com/elpaso/QGIS/commit/afbfb7f12b8f62731d40745035d919532ae5da1f -- 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] QEP: QGIS Mapserver Python Plugins
Another question could be the timeout. Infact. If a processing take too much time to end. It should go in timeout. So not only concurrency need, but also a timeout system to avoid the lock never ending of resources. A. Il 30/08/2014 13:21, Alessandro Pasotti ha scritto: 2014-08-29 18:05 GMT+02:00 René-Luc Dhont rldh...@gmail.com: Le 29/08/2014 16:54, Alessandro Pasotti a écrit : 2014-08-29 16:39 GMT+02:00 René-Luc Dhont rldh...@gmail.com: Hi Alessandro Thanks for this interesting input. I'm happy to test it and to develope some use case. I thought it's a good feature and can help to enhance QGIS-Server easily : WPS, WMTS, Table Join Service, WFS2 or other that OGC does not already know. Regards, René-Luc Hello René-Luc, I'm happy to hear that you are going to test it, please let me know how it goes! Keep in mind that it's just a proof of concept, and yes, we need a RFC or QEP: the current implementation is the simplest, less obtrusive and quickest that I could think about. For example, I would consider adding real signals attached to plugins slots and cached parsed projects passed to plugin instances... I'm currently working on a WPS server plugin that bridges Processing and PyWPS (version 3.2.2 since the latest version 4 is tightly bound to werkzeug), now fighting with parameters but it basically works. Can I help ? I already done some works on it ! Regards Hello, I've got a first highly experimental Processing-PyWPS bridging plugin: https://github.com/elpaso/qgis-wps * I've only tested grass convex hull with a small shapefile * GetCapabilties and other requests work with GET calls ony * it needs Processing patches otherwise it hangs when reading pipes from shell process (see [1]) * Processing needs other patches as well to support concurrent requests (for example the grass temporary script storage should be done in tempfile instead of the current processing folder) I don't know Processing enough to say if there aren't any other big showstoppers for this plugin. Still a lot of work to do :) [1] https://github.com/elpaso/QGIS/commit/afbfb7f12b8f62731d40745035d919532ae5da1f ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QEP: QGIS Mapserver Python Plugins
2014-08-30 13:28 GMT+02:00 aperi2007 aperi2...@gmail.com: Another question could be the timeout. Infact. If a processing take too much time to end. It should go in timeout. So not only concurrency need, but also a timeout system to avoid the lock never ending of resources. This is normally done at the webserver level: http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidbusytimeout ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] removing MetaSearch GetCapabilities checking
Devs: in QGIS' MetaSearch plugin, we have had various issues being reported which are all rooted in the following behaviour. When MetaSearch presents CSW results, records which have associated WMS/WMTS/WFS/WCS type links detected will have an Add to [WMS/WMTS|WFS|WCS] button enabled. When the user clicks the button [1], MetaSearch (among other things) uses OWSLib to do a quick GetCapabilities test/check [2] as a means of verifying things before it's passed to the appropriate provider [3]. The original intent was to prevent erroneously detected URLs from getting to the provider dialogs, but it is looking like ([4], [5], [6]) this is turning to be more of a burden that does not yield additional value to the logic/checking already baked in the existing WMS/WMTS/WFS/WCS providers proper. So then MetaSearch just passes the URL as-is. Alex/Richard/Angelos: I propose lifting this out of MetaSearch per above. Comments/objections/other ideas? ..Tom [1] https://github.com/geopython/MetaSearch/blob/master/plugin/MetaSearch/dialogs/maindialog.py#L644 [2] https://github.com/geopython/MetaSearch/blob/master/plugin/MetaSearch/dialogs/maindialog.py#L672 [3] https://github.com/geopython/MetaSearch/blob/master/plugin/MetaSearch/dialogs/maindialog.py#L721 [4] https://github.com/geopython/MetaSearch/issues/65 [5] https://github.com/geopython/MetaSearch/issues/64 [6] https://github.com/geopython/MetaSearch/issues/23 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] plugins: what's next?
hello devs! after the good job done with the plugin-repo, I was wondering if there is any idea about trying to optimize plugins through the merging of the similar ones. something like having a package of more plugins related to a single topic (i.e. qProf + ProfileTool + VogisProfilTool or all the CAD ones, etc). in this way would be easier to concentrate single devs' efforts on a single plugin instead of having more than one, and obviously it turns useful also for users not to be lost among the hundreds already present. does it make sense? may be hard to organise the working groups? or it may lead to a heavier loading of the software? sorry if it sounds as a silly question. all the best! Nic ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Getting the current QgsComposerView in an expression builder user function
On 29/08/2014 9:05 pm, Alexandre Neto senhor.n...@gmail.com wrote: It gives me a list of QgsComposerView, that I can select by the list index. But how can I know the position of the QgsComposerView in which I'm using the function (by using it in a label)? It's not currently possible -expressions have no way of knowing the context in which they are being used. See: http://hub.qgis.org/issues/9546 Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Getting the current QgsComposerView in an expression builder user function
Thanks Nyall, this way I will just stop looking for it. Alexandre Neto Em 30/08/2014 22:54, Nyall Dawson nyall.daw...@gmail.com escreveu: On 29/08/2014 9:05 pm, Alexandre Neto senhor.n...@gmail.com wrote: It gives me a list of QgsComposerView, that I can select by the list index. But how can I know the position of the QgsComposerView in which I'm using the function (by using it in a label)? It's not currently possible -expressions have no way of knowing the context in which they are being used. See: http://hub.qgis.org/issues/9546 Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
