Re: [Qgis-developer] Topology for PGD
On 08/27/2014 10:17 PM, thiruvikrama...@cognizant.com wrote: Hi, Is it possible to run topology for personal geodatabase instead of shapefiles like in ArcGIS? Regards, S. Thiruvikraman(449668) It might be possible with Spatialite, Postgis or GRASS layers. Thanks, Alex ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Topology for PGD
Yeah it is possible.. But instead of converting feature class to shapefile and executing topology is time consuming. Is it possible to create a plugin for that? If so please help me.. Regards, S. Thiruvikraman(449668) Programmer Analyst Cognizant - Mangalore Hand Ph: +91 8792574660 From: Alex Mandel [tech_...@wildintellect.com] Sent: Thursday, August 28, 2014 11:34 AM To: S, Thiruvikraman (Cognizant); qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] Topology for PGD On 08/27/2014 10:17 PM, thiruvikrama...@cognizant.com wrote: Hi, Is it possible to run topology for personal geodatabase instead of shapefiles like in ArcGIS? Regards, S. Thiruvikraman(449668) It might be possible with Spatialite, Postgis or GRASS layers. Thanks, Alex This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Legend refactoring - part II - ready for merge
Something to be addressed - these features are not supported out of the box by QgsLegendRenderer. Btw. are these custom options documented / used anywhere? The additional wms legend parameters are documented here: http://hub.qgis.org/projects/quantum-gis/wiki/QGIS_Server_Tutorial#GetLegendGraphics Regards, Marco On 27.08.2014 05:40, Martin Dobias wrote: Hi Marco thanks for you comments. On Tue, Aug 26, 2014 at 3:38 PM, Marco Hugentobler marco.hugentob...@sourcepole.ch wrote: Hi Martin Thanks for your efforts to unify the legends. Few comments from my side: - API break: is there a list of breaks inside the 2.x series? I recently came accross one in the provider API, and it would be good to provide some guidance for people porting code to newer versions. Regarding 'not used according to plugin analysis tool': most plugins are probably not in the plugin repo. I am not aware of such list - but it is the right time to start one. Do you have any preferences where to put it - doxygen page / wiki page / qgis-documentation repo / somewhere else? - For the legend graphics options layertitlespace and layerfontcolor, it says 'TODO'. Something to be addressed - these features are not supported out of the box by QgsLegendRenderer. Btw. are these custom options documented / used anywhere? - qgswmsserver.cpp:671 : it seems a bit strange to iterate over all nodes to set the property. Can this be done inside some legend class (maybe legend renderer)? This looks OK to me - I don't think we do not need another mechanism to skip legend node labels... and other classes like legend renderer are not supposed to alter the input model. Moreover this functionality is special to WMS and it's just two lines of code, so I did not feel a need to generalize it somehow. Regards Martin -- 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
Re: [Qgis-developer] Legend refactoring - part II - ready for merge
Hi Marco, On Thu, 28. Aug 2014 at 09:03:49 +0200, Marco Hugentobler wrote: On 27.08.2014 09:27, Paolo Cavallini wrote: Il 27/08/2014 05:40, Martin Dobias ha scritto: Do you have any preferences where to put it - doxygen page / wiki page / qgis-documentation repo / somewhere else? -1 for wiki thanks What place do you recommend then? Seems to me there is no developer documentation in the qgis-documentation repo. That leaves doxygen. Why not document API breakages where the API is documented? Sounds like the best fit ;) Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] nightly repos for debian testing
-BEGIN PGP MESSAGE- Charset: ISO-8859-1 Version: GnuPG v1 hQEMA8LIYu4K9k41AQf+NvYLgPocDWK6tdCsq6iKwhDoeoDp2W+70Qo9UucsI+XU ni4aLvmRUuFW2Jig0tnvrdWi6LLHLYN9w7Im5TZll9AFs8gmAqiO4aOWZrSUhb5W 2XRmDrgnstiD3J0pGRLoKe66LXdvdg50I6QQwNRm/E590ckvfALwvSIP7wn8OUMf 0l+jWMCi0034Uh7e3fruYdZEvQ+BqzoziIu4UZ7a8+HAAfC2TkrPx9EiaosOXx0X aWjAa9m8kvhAeXGhyPWmUOlrGNnAPXmZpSc2UnyEXVxZLha/e23lMdrqFv9/6+cC zn3TPuJT7ts/3X1y8boYeFZ9hix15U/OXczBtrzDd4UBDAOkmt8owvtBKAEIAKd3 jKABmg1xMPzt/Y0Bx+Dwmc6A9d+kPbeTby6/rkEhGKTpn9Gv4exof+/IV7vi3E6N p6D5ojRHtFX6JZq/vt5Uv5crADDhDNh+QjyfMG/mSFuTX9eop2viICgm07AL1q/i RFfII/PELsiZndnhWQEjbTsVJg8ULfmcjQYqdIArFUedqerEKc4ET4N1gcIY9fZc 75cPEZSexHMkG3KwDIhu5XSanRx6+01h+0365JF10snx6dh4QGvl9b/Yb3w4ArUN LlFtV7B0riFaKwYif/MZ58KqolAdpZooLcnX22N+q76930c9JTjIgqOHoBut8xBq uYBseqvZStz6P4fGfmTS6QFcTmVyyqJeE/OWwyH0MhLRxxFzRJ7pa/TTPFrMWw3a 9kfduQviU8cYu+Aoe8g+Pbs70RRpePZzZ6c9OtzyFPnvo+S/9WcBnkKtlQNKBXME bOZotPWSmPyDGBm40Q1vPU9+T61pdZY2lgv6ySVG3pV6ReqzcEdwgjF6Wb8gayiS wxtX1LoSypausCvJeCWt8upmr+kJG3QLle+tKAjXpCxzYmanIf86wojGnLuwQoXA 7+BQACcI2lcO7dUnGURA402xIdidzZbYJ59FEKzfEC3DxusULFTSz7yArKQT+EhG bsEkxCcK43YTgqoZ8PjoekxtE4rUcEp6kGFhFexyYeAEKKErD/mwNO/e2qFKZEPN bQ60hcl5FHNURmgXfpYU+4+eRicqzpaataHbT0ePtWFS4Yu7Q2hmPqgs9CuH8hzr GLZout4dZllrLSSnLMxYIQUgeu2z9gVLnFb62WBowojvjr1j4OHj9duVD237F1yc xzxnF/11IRbU02+pR/GLz8UNRlP9kDWkS51KSECp+UUbF2BwD0Q+DsJopznRWUys A9py6Uaw5NM7f0z46qWnMLDwSL8x+3JLYZFCpOO/NtS31m6aEd3602DeshYlRRR5 9tT3wcim0Ft/Q2Tycr2I55zhnKe/JixFVTPxsY8YWLqhxEeY7FpzhUGC852SeuBd wAZlB3DDLtEFaT0X3bGoWOEDflJQz2Te0wSj4/S2N95HSiEdRxaa2xsrKjS72W7l 4PrpnGdny/Zd9AaZcQ9LrhNBKBXxPe6VVV9YFVWlod759u39Je1aKaB/ONQN0NVk HH3G7qHhaRApFMhZuizdqpLg36AgesfZKoMb4e0w4g7O/N8/32TyUb7aQIRycGDG UVLOzbF8Y+LKuXbkep2hq6V2QKyI7R/nBlH7tijnATjvcZHpbNAeqOJrUsNucRfw q9AIxpC77JM= =IMLC -END PGP MESSAGE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] nightly repos for debian testing
Hi, um, perhaps I shouldn't have used qgis-developer@lists.osgeo.org for the archive key... Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Legend refactoring - part II - ready for merge
On 28/08/2014 5:29 pm, Jürgen E. j...@norbit.de wrote: That leaves doxygen. Why not document API breakages where the API is documented? Sounds like the best fit ;) That's fine, until those deprecated methods are removed. Then the api break documentation will be removed as well... Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Fwd: Caching GetProjectSettings with Qgis server
Alessandro, Thanks for answering, yes I have fcgid enabled and I meant configuration stuff especially getprojectsetting request which is taking very long on certain project. So that is cached, in memory I assume? Are there any settings, I would to keep the cache unless I saved the project or restart server, which are obvious cases to remove cache. From the code example I see that if the project is changed it is removed from cache, I don't see any other cases. Can I use apache cache modules to save the cache to disk? How are anyone dealing with this on production servers? regards, Uros 2014-08-26 19:33 GMT+02:00 Alessandro Pasotti apaso...@gmail.com: 2014-08-26 19:05 GMT+02:00 Uros Preloznik uro...@gmail.com: Hi, I would like to have more information regarding Qgis server caching certain requests and how to control that. I didn't find any documentation regarding this, so I ask. Example: On my environment (ubuntu 12.04, apache 2.2.22, qgis 2.4) I do GetProjectSettings request on certain project. If I restart Apache or save the project the request is not cached (I assume) and it takes from 20 - 65 seconds. In order to avoid Server Error after 40second I added this line to Apache configuration FcgidIOTimeout 80 So, after this long request, next same request is immediately so it must be cached, right? I tested with different clients and must be on server. But I do not control this, because after unknown amount of time the cache is removed. Can anyone explain this and should I explore basic Apache caching tehniques like this: http://httpd.apache.org/docs/2.2/caching.html Right now I don't have any caching modules enabled in Apache. Another question is why is it taking so long, but I will ask that extra. thanks Uros Hi Uros, I might be wrong but I think that request are not cached in the standard sense, the startup delay is due to the application startup time ant to the first time parsing of the project file that also needs to instanciate many objects. What is cached are project configurations (parsed project files) for the available services, layers, getcapabilities and getprojectsettings requests, but the caches are invalidate whenever the project file changes on disk, for instance see: https://github.com/elpaso/QGIS/blob/master/src/mapserver/qgsconfigcache.cpp#L36 The end of the story is that there at the first request there is the application startup time + the configuration parsing for the particular service and project tuple, the next requests for the same service and project is considerably faster because it doesn't have to start the application nor to parse the project file and instanciate all the stuff. Of course, all this goodies come only with FCGI, if you run the server in CGI mode, then all requests are treated as the first one. -- 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 can't enable logging
Hi, Thanks Alessandro, this is working now. I was trying only with SetEnv. I also had to set QGIS_SERVER_LOG_LEVEL, otherwise the file was empty. So this is my setting now which is working (Apache+Fcgid): FcgidInitialEnv QGIS_SERVER_LOG_FILE /var/tmp/qgislog.txt FcgidInitialEnv QGIS_SERVER_LOG_LEVEL 0 LogLevel 0 means that everything is logged, for debugging only. Is someone working on documentation? This could be included for others. regards, Uros 2014-08-27 8:46 GMT+02:00 Alessandro Pasotti apaso...@gmail.com: 2014-08-26 23:19 GMT+02:00 Uros Preloznik uro...@gmail.com: Hi, I know this was already discused, but I still cannot enable logging for qgis server. My configuration is this: -Ubuntu 12.04 -Apache 2.22 -Qgis 2.4 (standard install) I added this line to apache configuration: SetEnv QGIS_SERVER_LOG_FILE /var/log/qgislog.txt Nothing happens, I also manualy created empty file and set chown as wwwdata, but still nothing is logged. Am i missing something? Any ideas? If you are on apache and mod_fcgid you'd better try with http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidinitialenv -- 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] Legend refactoring - part II - ready for merge
Hi Nyall On Thu, Aug 28, 2014 at 5:33 PM, Nyall Dawson nyall.daw...@gmail.com wrote: On 28/08/2014 5:29 pm, Jürgen E. j...@norbit.de wrote: That leaves doxygen. Why not document API breakages where the API is documented? Sounds like the best fit ;) That's fine, until those deprecated methods are removed. Then the api break documentation will be removed as well... The idea is to have an explicit list (a doxygen page) with the incompatible changes - so nothing should get lost if stuff it removed. Cheers Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] QEP1 - Proposal for QEP
Hey all, So I think all (most) agree that the QEP idea is good for the future of the project. So in order to move this forward Richard has created a new github repo for us to store the QEPs. The plan is to use a git repo to store the QEPs and new QEPs MUST be added via a pull request.The pull request will allow discussion around the QEP until voting stage, then once it's committed into the repository it is accepted. So the short hand of that is, if it in pull request state, it's in draft/review stage. Using the pull requests will allow for comments on the sections inside the QEP and allow tracking of commits made while in draft/review. In order to kick this off I have created the first QEP which is a proposal for using QEPs. How meta is that! QEP 1 should include the details on how future QEPs will work. You can find the first pull request here: https://github.com/qgis/QGIS-Enhancement-Proposals/pull/1. This QEP is still in draft mode and I'm happy to take feedback on the sections so we can build it out how we need. Please leave comments on the pull request. You will notice that I have created two types of QEPs, process and standard. Standard is application focused and will be managed by a group of developers. Process QEPs are related to how we do the other stuff in the project and are managed by the PSC. I got this idea from PEPs which have three types but I don't think we will need to go to that level. Regards, Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] DBManager Oracle implementation
Hello, I've been working on the Oracle implementation of DBManager. The code can be downloaded at this repository: https://github.com/medspx/dbmanager-oracle In order to work, it needs cx_Oracle (development done with latest version 5.1.3). See the README.md for further details. It's a DBA-API 2.0 implementation for Oracle and this eased development a lot by not dealing with low-level Oracle Database connections problems. I have started from the postgis code of DBManager and tried to implement all of its features under Oracle. Some tasks can't been done under Oracle like renaming a schema or changing the schema of a table, etc. From what I have tested so far, eveything is working but you can expect bugs just because my test environment is quite restrictive (Oracle 10g, Spatial 12, no DBA rights, no raster data). I am not a professionnal Python developper nor an Oracle DBA but I've tested the plugin on a production environment with good results. I think it needs code and internal queries review. My main objective is to have this code (and its modifications) incorporated in the official QGis repository. One of the prerequisites is to have cx_Oracle Python library incorporated in the official QGis build. But I don't know how to achieve this and I think it is a little bit complicated, especially for GNU/Linux distros (at least there is already an Oracle SDK incorporated into QGis repository). Other prerequisite will be, of course, the code quality. Feel free to report bugs in the Github issues tool of the repository. You can also send me patches. Best regards, -- Médéric RIBREUX http://medspx.homenet.org ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] QEP: QGIS Mapserver Python Plugins
Hello, as anticipated to some of you during the last HF, I've started to add Python plugins support for the server side. The rationale behind server plugins is doublefold: first they could provide additional services without the need to touch the C++ codebase, second they allow for GUI-based configuration since the server plugins are not separated from the desktop plugins (of course the environment and permissions should be carefully configured to allow information sharing from the desktop user to the webserver user ). I've already coded a first working implementation and a few proof-of-concept plugins. The current implementation is based on the following ideas: QGIS Python plugins can have additional metatags to specify what SERVICE and REQUEST they expose, for example: service=HELLO methods=GetCapabilities,GetOutput,RemoteConsole This plugin will respond to calls like /cgi-bin/qgis_mapserv.fcgi?SERVICE=HELLOREQUEST=RemoteConsole The current implementation is pretty simple and CGI-style, whatever the plugin prints to sdtout is captured and sent back to the client, the return value from the method is the (optional) content type. I would like to discuss this ideas during the next HF (or sooner), in particular: * I'm not happy with the current request handling and I think we need a mehod to pass cached parsed project instances to the plugins when needed and a better handling of HTTP headers * I 'd like to see signals/slots implementation instead of static function calls, but maybe it's just syntactic sugar * from the python side, we don't have an iface to pass to the plugins, so I'm currently stuck to @staticmethod The code is in a branch: https://github.com/elpaso/QGIS/tree/serverplugins HelloServer demo plugin: https://github.com/elpaso/qgis-helloserver It is a test plugin and it provides a remote console (web shell), insanely insecure DO NOT USE IN PRODUCTION!! and arbitrary python code execution configurable through the QGIS desktop plugin GUI. Here is a short demo of the HelloServer plugin: http://youtu.be/ys9VVxQ8uac Have fun !! -- 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 can't enable logging
Il 28/08/2014 12:47, Uros Preloznik ha scritto: Hi, Thanks Alessandro, this is working now. I was trying only with SetEnv. I also had to set QGIS_SERVER_LOG_LEVEL, otherwise the file was empty. So this is my setting now which is working (Apache+Fcgid): FcgidInitialEnv QGIS_SERVER_LOG_FILE /var/tmp/qgislog.txt FcgidInitialEnv QGIS_SERVER_LOG_LEVEL 0 LogLevel 0 means that everything is logged, for debugging only. Is someone working on documentation? This could be included for others. Hi Uros, would you mind making a pull request on https://github.com/qgis/QGIS-Documentation Thanks. -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: 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] collapse and expand all actions in legend
Hi Martin, On Thu, Aug 28, 2014 at 1:20 PM, Martin Dobias wonder...@gmail.com wrote: Hi Salvatore On Thu, Aug 28, 2014 at 6:01 PM, Salvatore Larosa lrssv...@gmail.com wrote: I don't see anymore those actions in legend contextual menu, could we re-enable them? Now they still show up only if you click to empty area. I have excluded it from the ordinary context menu because it is getting really long for layers - and expand/collapse all items are not really contextual actions anyway. I think we could have a small toolbar like in browser dock widget and have those actions there (either directly or in advanced menu) - together with actions like new group. no problem to scroll down a lot of layers to find an empty area :) but couldn't we think to some submenu action here? I think it is useful to add they in context menu for groups only as well. Also, wouldn't be useful to have a check all and uncheck all actions? We already have such thing in Layer menu Show / Hide All Layers. yeah, I know, sorry badly explained, I was referring to move them in the context (sub)menu as well. Having all in legend should be helpful to the end user imo. Regards, -SL I did not test the legend refactoring part II branch yet, so I don't know if this has already been done there. The second part of legend refactoring contains no changes in this area. Regards Martin -- 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] Processing causes major slowness at QGIS startup
I am away until Sept 5th, but will work on that once i am back. Didn't know about the init() and initGUI() separation, so thanks for the info. A large part of the time it takes to start Processing is probably spent in reading the description files for SAGA, GRASS and OTB algorithms, so i will try to find a way of making that faster, or avoiding it if not needed at first 2014-08-27 10:55 GMT+02:00 Luca Manganelli luc...@gmail.com: On Wed, Aug 27, 2014 at 10:24 AM, Bo Victor Thomsen bo.victor.thom...@gmail.com wrote: When and how will the creation of menu items and push buttons for the plugins be done? It can be done inside initGUI() function. ___ 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] Possible issue with QgsRubberBand
Hi all, I'm struggling to understand the rationale behind some logic in QgsRubberBand::addPoint. At line 163 (https://github.com/qgis/QGIS/blob/master/src/gui/qgsrubberband.cpp#L163), if a new geometry index is required then it is added and the specified point added to this new geometry index. That's fair enough, but the very next code block will then re-add that same point to the new index. The result is that the first point will always be added TWICE to the rubber band. Is this deliberate? Or a bug in the code? Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Possible issue with QgsRubberBand
Hi Nyall, IIR the rubber band adds two points because the second one will be used to track the mouse moves. Basically addPoint is synonym of add point to line. It shall not be used if you want to have single points. Cheers, Denis On 28.08.2014 23:17, Nyall Dawson wrote: Hi all, I'm struggling to understand the rationale behind some logic in QgsRubberBand::addPoint. At line 163 (https://github.com/qgis/QGIS/blob/master/src/gui/qgsrubberband.cpp#L163), if a new geometry index is required then it is added and the specified point added to this new geometry index. That's fair enough, but the very next code block will then re-add that same point to the new index. The result is that the first point will always be added TWICE to the rubber band. Is this deliberate? Or a bug in the code? Nyall ___ 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
