[Qgis-user] Editing processes broken from 2.6.1 to 2.8.2

Tue May 19 08:20:12 PDT 2015

Hi Ross,

you might want to update to 0.6.0 although I doubt this improves the 
plugin's behaviour but it makes sure you use the version I have here.

Could you provide (at least) the two polygons causing the runtime error 
in a PM, so I can see if this problem is reproducible?

Bernhard

Am 19.05.2015 um 17:04 schrieb McDonaldR:
> Hi Bernhard
>
> 1) version 0.5.3
> 2) No. everything is in EPSG:27700 (British National Grid)
> 3) QGIS Brighton 2.6.1 (32 and 64bit) and QGIS Wien 2.8.2 (32 and 64bit)
>
> Thanks
>
> Ross
>
> -----Original Message-----
> From: qgis-user-bounces at lists.osgeo.org [mailto:qgis-user-bounces at lists.osgeo.org] On Behalf Of Bernhard Ströbl
> Sent: 19 May 2015 13:49
> To: qgis-user at lists.osgeo.org
> Subject: Re: [Qgis-user] Editing processes broken from 2.6.1 to 2.8.2
>
> Hi Ross,
>
> I am addressing the second error as it comes from the DigitizingTools plugin.
> Questions to make this reproducible for me:
> 1) Are you using the most current version of the plugin?
> 2) Is there any differences between the CRS of the layer(s) and/or the project?
> 3) Which QGIS version are you using on which platform?
>
> Bernhard
>
> Am 19.05.2015 um 12:42 schrieb McDonaldR:
>> Hello List
>>
>> I have a process that works perfectly in Brighton 2.6.1 but is broken
>> in Wien 2.8.2.
>>
>> I have two Postgis polygon layers loaded in QGIS - MR and RC.
>>
>> I copy some polygons from Ordnance Survey MasterMap Topography layer
>> and paste into a memory layer.  In the memory layer the polygons are
>> merged and edited until correct.  Then this new polygon is copied into
>> MR (there are three mandatory fields which have to be filled at this
>> point).  When I save my MR edits a series of triggers in the database
>> update various fields (area, x, y, centroids, etc).  Then I copy the
>> new
>> feature(s) in MR and paste into RC.  Polygons are merged if required.
>> Again, a series of triggers on the RC table update some fields.
>>
>> There are three processes that throw errors in 2.8.2
>>
>> 1.Selecting a polygon in MR and using the node tool to edit and move
>> nodes fails with a "could not snap to feature in current layer" error.
>> QGIS will crash with data written to a minidump file after selecting
>> node tool, selecting a node and dragging it. Crash on release.
>>
>> 2.Selecting overlapping polygons in MR and RC and using the "cut with
>> polygon from another layer" tool to cut RC with MR. That returns the
>> error below:
>>
>> An error has occured while executing Python code:
>>
>> Traceback (most recent call last):
>>     File
>> "C:\Users\me\.qgis2\python\plugins\DigitizingTools\tools\dtcutter.py",
>> line 94, in process
>>       bbox = cutterGeom.boundingBox()
>> AttributeError: 'NoneType' object has no attribute 'boundingBox'
>>
>>
>> Python version:
>> 2.7.4 (default, Apr  6 2013, 19:54:46) [MSC v.1500 32 bit (Intel)]
>>
>> QGIS version:
>> 2.8.2-Wien Wien, 1b929ef
>>
>> 3.Pasting from MR into RC does not carry over attributes (the field
>> names are the same) and the triggers don't run on the RC table.
>>
>> While this is very probably user specific we'd appreciate any suggestions.
>>
>> Thanks in advance
>>
>> Ross
>>
>> *Ross McDonald *|**GIS Data Coordinator | Resources Department, IT
>> Division | Angus Council, Angus House, Orchardbank Business Park,
>> Forfar, DD8 1AT
>>
>> T: *01307 476419* | F: 01307 476401 | E: mcdonaldr at angus.gov.uk
>> <mailto:mcdonaldr at angus.gov.uk> **
>>
>> This message is strictly confidential. If you have received this in
>> error, please inform the sender and remove it from your system. If
>> received in error you may not copy, print, forward or use it or any
>> attachment in any way. This message is not capable of creating a legal
>> contract or a binding representation and does not represent the views
>> of Angus Council. Emails may be monitored for security and network
>> management reasons.Messages containing inappropriate content may be
>> intercepted. Angus Council does not accept any liability for any harm
>> that may be caused to the recipient system or data on it by this
>> message or any attachment.
>>
>>
>>
>> __________ Information from ESET Mail Security, version of virus
>> signature database 11649 (20150519) __________
>>
>> The message was checked by ESET Mail Security.
>> http://www.eset.com
>>
>>
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>> __________ Information from ESET Mail Security, version of virus
>> signature database 11649 (20150519) __________
>>
>> The message was checked by ESET Mail Security.
>> http://www.eset.com
>>
>
>
>
> __________ Information from ESET Mail Security, version of virus signature database 11650 (20150519) __________
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>
> This message is strictly confidential. If you have received this in error, please inform the sender and remove it from your system. If received in error you may not copy, print, forward or use it or any attachment in any way. This message is not capable of creating a legal contract or a binding representation and does not represent the views of Angus Council. Emails may be monitored for security and network management reasons. Messages containing inappropriate content may be intercepted. Angus Council does not accept any liability for any harm that may be caused to the recipient system or data on it by this message or any attachment.
>
>
> __________ Information from ESET Mail Security, version of virus signature database 11651 (20150519) __________
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>

__________ Information from ESET Mail Security, version of virus signature database 11651 (20150519) __________

The message was checked by ESET Mail Security.
http://www.eset.com