Re: [Qgis-developer] more advanced editing tools
Hi Angelos, I agree that some 2 to 5 tools should go into cadTools. What we have until now: - parallel move of polygon side (IMHO CAD-like function) - split feature with selected feature from another theme (general digitizing function) - cut out from feature with selected polygon from another theme (general digitizing function) - continue editing an exisitng line (general digitizing function) - save all layers being in editing mode in one go (general digitizing function) - fill hole(s) in polygon feature (general digitizing function) - fill spaces between polygons (general digitizing function) - avoid intersection when copying/pasting polygons (reported bug) - split lines with points (IMHO fTools) - prolong a line, i.e. move its endpoint in the direction of the last segment (CAD-like function) from a users point of view it would be nice to have everything related to digitizing in one plugin on the other hand users probably do not expect the functions I marked as general digitizing in a plugin called cadTools. Bernhard Am 29.11.2012 19:48, schrieb Angelos Tzotsos: Hi Bernhard, I agree that some editing ideas are not strictly CAD but we have to think the end user and where the tools are expected to be found more easily. Also the number of new tools are important. For 2-5 new tools, extending cadTools would be more appropriate than a new plugin. Angelos On 11/29/2012 06:36 PM, Bernhard Ströbl wrote: Angelos, would you see this functionality rather in cadTools or in a new plugin? Bernhard Am 29.11.2012 17:28, schrieb Angelos Tzotsos: On 11/29/2012 02:35 PM, Bernhard Ströbl wrote: Dear list, during a course I realized that my institution needs some more editing tools for advanced editing tasks e.g. - prolong a line - cut polygon with feature (line or polygon) from another layer - save all layers being in editing mode in one go - some more A little background: when digitizing data we are not starting from scratch but are digitzing on existing data in many different layers (parcels, restricted areas ...). A new polygon normally needs to fit into these existing boundaries. Trying to digitize along existing boundaries of several layers and snapping to them is cumbersome and you are very likely missing snapping nodes (even when using trace digitize plugin). Is any of you aware of similar functions in a plugin (I know cadTools)? Is anyone interested in joining me to create such tools as a Python plugin? Which functions would you like to have? regards Bernhard __ Information from ESET Mail Security, version of virus signature database 7744 (20121129) __ 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 Hi Bernhard, Excellent timing, I was thinking about creating a new functionality that I need for a parcel digitization project. One tool I have in mind is parallel moving of a side of a polygon in order to achieve a specific area for the polygon (and at the same time maintain topological integrity with near polygons. Cheers, Angelos __ Information from ESET Mail Security, version of virus signature database 7747 (20121129) __ 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
[Qgis-developer] QGIS-Server WFS Transaction demo
Hi all, With the Faunalia'help, the QGIS Server WFS implementation is more interoperable. You can use QGIS-Server to publish vector data throw WFS and use it in QGIS, ArcGIS, gvSIG, and OpenLayers. To demonstrate the ability to update Spatialite data stored on a server with QGIS-Server, I've created a demo : http://demo.3liz.com/wfst/wfs-transaction-polygon.html I will add demo for point and linestring : http://demo.3liz.com/wfst/ Yan can also test the QGS-Server WFS-Transaction implementation with your favorite (or less) Desktop GIS. Feedbacks are welcome. René-Luc D'Hont 3Liz ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Settings - Panels vs. Settings - Customization - Docks
On Wed, Nov 28, 2012 at 5:17 PM, Otto Dassau das...@gbd-consult.de wrote: Hi, in QGIS 1.8 you can (de)activate panels under Settings - Panels. Under settings Customization the panels are described as Docks. Would it be possible to have only one name for it? Or is there a reason, why we have two names for it? Hi Otto as far as I know, there's no reason for two names, it's the same thing... I guess panel is a term that users are more familiar with. Regards Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] more advanced editing tools
* the tool should be able to fill all holes and/or spaces (with polygons) in one go that is similar but different from what I had in mind. I was thinking about the user clicking in a hole or space and just this one is filled. The algorithm however would be the same. a plugin that works this way (just for holes, not for spaces) already exist, but it does not asks for attributes, so right now it is not that useful. anyway an option to fill in one go all the holes/spaces would be very appreciated by many. cheers! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] more advanced editing tools
Hi Giovanni, You're probably talking about Ringer plugin. This was one of my first plugin and it was wrote for issue #3187 http://hub.qgis.org/issues/3187 . Some time ago I have short e-mail talk with Carson Farmer to include this functionality into fTools. Because of that I don't move it to new repository. What do you mean about asking for attributes? To copy them from parent polygon or popup form for each new polygon? Regards, Peter -- View this message in context: http://osgeo-org.1560.n6.nabble.com/more-advanced-editing-tools-tp5019552p5019884.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] Get list of dirty features and their attributes
Hi Ivan On Thu, Nov 29, 2012 at 2:15 PM, Ivan Mincik ivan.min...@gmail.com wrote: Hi, sure you know this - when editing/adding multiple features to layer and pressing 'save' button an error message appears because of some database constraint violation or invalid data type in attribute table. There is very hard to find out a problematic features when many of them where changed or added. We wrote a small Python console script to print all dirty features with their attributes and WKT geometry: # QGIS 1.7, 1.8, author: Marcel Dancak, Gista s.r.o. layer = qgis.utils.iface.activeLayer() map = qgis.utils.iface.mapCanvas() layer.select(map.fullExtent(), False) fields = layer.dataProvider().fields() features = layer.selectedFeatures() # filter only new features features = [f for f in features if f.id() 0] for f in features: attribs = dict([(unicode(fields[k].name().toUtf8()), unicode(v.toString().toUtf8())) for k, v in f.attributeMap().iteritems()]) print f.id(), attribs, f.geometry().type(), f.geometry().exportToWkt() Are you interested just in newly added features or any dirty features, i.e. also changed features and removed features? Because the above would work just for new features. Currently it's not possible to access uncommitted changes... but in theory you could still iterate over vector layer and then iterate through its data provider and compare the results to detect all changes. If you decide to create a plugin, you could listen to signals from QgsVectorLayer (featureAdded, featureDeleted and others) to immediately detect any changes. In general, any tools that would lead to easier detection of problems would be welcome. Regards Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Get list of dirty features and their attributes
Couldn't we just expose to the API the collection of changed features via QgsVectorLayer? - Nathan On Sat, Dec 1, 2012 at 12:45 AM, Martin Dobias wonder...@gmail.com wrote: Hi Ivan On Thu, Nov 29, 2012 at 2:15 PM, Ivan Mincik ivan.min...@gmail.comwrote: Hi, sure you know this - when editing/adding multiple features to layer and pressing 'save' button an error message appears because of some database constraint violation or invalid data type in attribute table. There is very hard to find out a problematic features when many of them where changed or added. We wrote a small Python console script to print all dirty features with their attributes and WKT geometry: # QGIS 1.7, 1.8, author: Marcel Dancak, Gista s.r.o. layer = qgis.utils.iface.activeLayer() map = qgis.utils.iface.mapCanvas() layer.select(map.fullExtent(), False) fields = layer.dataProvider().fields() features = layer.selectedFeatures() # filter only new features features = [f for f in features if f.id() 0] for f in features: attribs = dict([(unicode(fields[k].name().toUtf8()), unicode(v.toString().toUtf8())) for k, v in f.attributeMap().iteritems()]) print f.id(), attribs, f.geometry().type(), f.geometry().exportToWkt() Are you interested just in newly added features or any dirty features, i.e. also changed features and removed features? Because the above would work just for new features. Currently it's not possible to access uncommitted changes... but in theory you could still iterate over vector layer and then iterate through its data provider and compare the results to detect all changes. If you decide to create a plugin, you could listen to signals from QgsVectorLayer (featureAdded, featureDeleted and others) to immediately detect any changes. In general, any tools that would lead to easier detection of problems would be welcome. Regards Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Multiple geometry columns per layer
Hi Matthias On Thu, Nov 29, 2012 at 3:32 PM, Matthias Kuhn matthias.k...@gmx.ch wrote: I think rendering one at a time is enough (as in my first mail: one as the default to display), with time one could include fun stuff like LOD, subitems in the layer legend, or whatever somebody might come up with ( intersection etc). More interesting for me is the possibility to access additional geometry columns from a plugin, and therefore having the dataProvider ready for this. The idea of having multiple layers, pointing to the same table sounds interesting as well. This would probably mean separating the pretty strong linkage between layer (as representation) = table (as data), we've got now. So right now we have QgsFeature that contains ID, attributes and a geometry. I think we should keep that as-is because this is what is usually expected from a layer. In order to support multiple geometries per feature, we could possibly allow QgsGeometry class as another attribute type (next to int, double and QString). So providers like postgis that support multiple geometry columns could return additional geometries wrapped as attributes in QVariant. Would that work for you? Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] more advanced editing tools
On 30/11/2012, at 15:38 , Bernhard Ströbl wrote: The simplest snapping approach I've seen is a keyboard shortcut (S), and then watch as the programme tries to snap to anything in sight (not so good if you have many layers). not neccessarily because you can define your snap layers and snapping should only occur with one of those (though if you choose to snap to segments there would be an abundance of potential snap points) But, I wonder, would it be possible to pop the snapping menu out into a panel (or similar) so that when you're furiously digitising it was easily accessible? I think this would smoothen the workflow. We could file a ticket for this. I my case I have many line and point layers to which I can snap but I have to scroll a lot to get to a certain polygon layer that I want to tick for avoid intersections. Maybe we could have another column in the snapping options dialog with the geometry type in it so we could sort on that to have all polygon layers together? As usual with QGIS, I think wouldn't that be cool and lo, it's already there. It appears that you can leave the snapping dialogue open, go do some editing and come back change your snapping. So it is effectively already a panel. Well, I failed to guess that, although the apply button should have been a hint. Just as well I had a decent rummage in the issues db before filing! #5152 linking to #660 was a good hint :) -ramon. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Get list of dirty features and their attributes
On Fri, Nov 30, 2012 at 3:47 PM, Nathan Woodrow madman...@gmail.com wrote: Couldn't we just expose to the API the collection of changed features via QgsVectorLayer? We could (and it's a right thing to do), but that wouldn't really help people that use 1.x releases :-) Martin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Update to the SpatiaLite provider
Hi devs, hi all, Alessandro Furieri has sent to me a patch to support the features available from the newest SpatiaLite v4 into the provider, mostly the intensive use of statistics to improve performaces. @Alessandro: please, could you tell us what's new in the provider? I know some details, but I'm sure devs would like to know more. The patch doesn't break API, but could break the provider functionalities (worst). Alessandro and I have tested it and everything seems to work fine. Before merging it I've opened a pull request [1], further tests are welcome. Regards. [1] https://github.com/qgis/Quantum-GIS/pull/346 -- Giuseppe Sucameli - Faunalia ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Multiple geometry columns per layer
So right now we have QgsFeature that contains ID, attributes and a geometry. I think we should keep that as-is because this is what is usually expected from a layer. And the users would be forced to deal with yet another pretty strong API change besides the API changes you plan to commit. In order to support multiple geometries per feature, we could possibly allow QgsGeometry class as another attribute type (next to int, double and QString). So providers like postgis that support multiple geometry columns could return additional geometries wrapped as attributes in QVariant. Would that work for you? This would work perfectly well. I'm wondering how much work it would mean to get this. Matthias ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Update to the SpatiaLite provider
On Fri, 30 Nov 2012 16:58:44 +0100, Giuseppe Sucameli wrote: Hi devs, hi all, Alessandro Furieri has sent to me a patch to support the features available from the newest SpatiaLite v4 into the provider, mostly the intensive use of statistics to improve performaces. Giuseppe, thanks a lot for your precious collaboration. @Alessandro: please, could you tell us what's new in the provider? I know some details, but I'm sure devs would like to know more. surely yes: a) spatialite v4 is now strictly conformant to the most recent OGC-SFS and ISO SQL/MM standard requirements. unhappily this necessarily implies few compatibility breakages. b) any recent version of libspatialite starting since 4.0.0 has the capability to handle any DB created using any possible previous version of the library. this happens in a completely transparent way, and the user is not required to apply any special precaution at all. the full library support is available both on reading and writing, and obviously covers the Spatial Index capabilities as well. (see below for further details). c) the opposite isn't true; it's absolutely impossible connecting any new DB created using the most recent libspatialite 4.0.0 if the underlying library is obsolete (any version 4.0.0) the revised QGIS data-provider will emit an appropriate error message in this case (when linked against an obsolete library version and attempting to open a DB-file created by a recenter version). d) a new CLI tool is make available in spatialite-tools-4.0.0: spatialite_convert makes possible safely converting any DB-file back and forward between v.2.3.x, v.3.0.x and v.4.0.x it doesn't requires a full DB conversions, simply the metadata tables are affected, so converting from a version to the the other is a really fast process just requiring few seconds even when the DB-file is a really huge and complex one. e) the most recent DB layout supported by v.4.0.0 now supports a full set of statistic infos; this is specially useful for QGIS, because now the data provider can avoid at all to loose time by sniffing each layer before connecting. and this is obviously useful while connecting to some layer containing many million feature; the time required by any previous version of the QGIS data-provider could require several minutes in this case. now, when full v.4.0.0 support is available, just few seconds are enough to connect such huge layers. f) last but not least: libspatialite v.4.0.0 now supports several API methods taking full care to internally handle any metadata table (e.g. the ones supporting the internal statistics). such abstract methods are mainly intended to avoid any direct physical access from the data-provider itself. so the data-provider can now completely ignore any fine-grained detail about the version-dependent DB layout; these abstract API methods will always implement the most appropriate access strategy to the metadata tables for any possible DB layout. a strong commitment exist to fully preserve all these abstract API methods: so any future major change affecting the DB layout will be completely transparent to the QGIS data-provider, and simply upgrading the underlaying libspatialite will be enough to keep anything correctly aligned. g) just a final note: a further abstract API method will now support full deletion of any Geometry table, taking care to remove any possible metadata reference and any Spatial Index eventually defined. as a rule-of-the-thumb, the revised data-provider will continue to work exactly as before when linked against any libspatialite prior to 4.0.0 but will take full profit of the new abstract methods if linked to libspatialite v.4.0.0 (or any subsequent). if you are interested to learn more about these topics, here you can find the appropriate documentation: https://www.gaia-gis.it/fossil/libspatialite/wiki?name=switching-to-4.0 bye Sandro -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS Engine development
On Tue, Nov 27, 2012 at 9:42 PM, Martin Dobias wonder...@gmail.com wrote: I have been measuring the performance of vector layer rendering some time ago and it varies greatly on three levels: - data source type (shapefile / database layer / ...) - layer type (geometry type, number of vertices per geometry, number of attributes, ...) - renderer type (using attributes? antialiasing? thick lines?) I have run my benchmarks with latest master: http://bench.qgis.cz However it seems that we achieved significant slowdown over 100% there may exist a different explanation in benchmarking itself. Running benchmarks on all commits since April would help. I have free computer I would like to dedicate to real time benchmarks I just need to find time to configure it. Radim ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Defining the SEXTANTE roadmap
Hi all As you might know, the SEXTANTE project started some time ago at the University of Extremadura (Spain), where I was working. I started creating the QGIS version at the beginning of this year, and now I do not work for the University, but I am still mantaining it. The University has some money that they would like to invest on improving SEXTANTE for QGIS, as this is the version they (and I personally share that) consider more relevant. I am not available for that task, as I have another job, but I would help coordinate the development in my spare time, as I do now. There are some priorities, which involve developing certain new analysis algorithms that are of interest, mostly for academic purposes, and creating good documentation about how to develop new SEXTANTE algorithms, so as to bring more developers in and ensure that SEXTANTE will keep on growing. But apart from that, we would like to hear from the community, to know what is better for SEXTANTE. So, in short: - The University has some money (not much...but some) and wants to invest it wisely - It is looking for ideas to define the work to do (apart from its particular interest), in order to turn SEXTANTE into a really powerful tool. - We are looking for someone to do this work. Let's start with the second point How do you think we should spend this money on SEXTANTE? Please, comment on this and help us push SEXTANTE forward. Many thanks in advance. Victor ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] more advanced editing tools
Hi, Yes it is a real dilemma. I would like to hear more opinions on this... Angelos On 11/30/2012 11:23 AM, Bernhard Ströbl wrote: Hi Angelos, I agree that some 2 to 5 tools should go into cadTools. What we have until now: - parallel move of polygon side (IMHO CAD-like function) - split feature with selected feature from another theme (general digitizing function) - cut out from feature with selected polygon from another theme (general digitizing function) - continue editing an exisitng line (general digitizing function) - save all layers being in editing mode in one go (general digitizing function) - fill hole(s) in polygon feature (general digitizing function) - fill spaces between polygons (general digitizing function) - avoid intersection when copying/pasting polygons (reported bug) - split lines with points (IMHO fTools) - prolong a line, i.e. move its endpoint in the direction of the last segment (CAD-like function) from a users point of view it would be nice to have everything related to digitizing in one plugin on the other hand users probably do not expect the functions I marked as general digitizing in a plugin called cadTools. Bernhard Am 29.11.2012 19:48, schrieb Angelos Tzotsos: Hi Bernhard, I agree that some editing ideas are not strictly CAD but we have to think the end user and where the tools are expected to be found more easily. Also the number of new tools are important. For 2-5 new tools, extending cadTools would be more appropriate than a new plugin. Angelos On 11/29/2012 06:36 PM, Bernhard Ströbl wrote: Angelos, would you see this functionality rather in cadTools or in a new plugin? Bernhard Am 29.11.2012 17:28, schrieb Angelos Tzotsos: On 11/29/2012 02:35 PM, Bernhard Ströbl wrote: Dear list, during a course I realized that my institution needs some more editing tools for advanced editing tasks e.g. - prolong a line - cut polygon with feature (line or polygon) from another layer - save all layers being in editing mode in one go - some more A little background: when digitizing data we are not starting from scratch but are digitzing on existing data in many different layers (parcels, restricted areas ...). A new polygon normally needs to fit into these existing boundaries. Trying to digitize along existing boundaries of several layers and snapping to them is cumbersome and you are very likely missing snapping nodes (even when using trace digitize plugin). Is any of you aware of similar functions in a plugin (I know cadTools)? Is anyone interested in joining me to create such tools as a Python plugin? Which functions would you like to have? regards Bernhard __ Information from ESET Mail Security, version of virus signature database 7744 (20121129) __ 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 Hi Bernhard, Excellent timing, I was thinking about creating a new functionality that I need for a parcel digitization project. One tool I have in mind is parallel moving of a side of a polygon in order to achieve a specific area for the polygon (and at the same time maintain topological integrity with near polygons. Cheers, Angelos __ Information from ESET Mail Security, version of virus signature database 7747 (20121129) __ 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 -- Angelos Tzotsos Remote Sensing Laboratory National Technical University of Athens http://users.ntua.gr/tzotsos ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
