Timeline for Creating and updating a field from calculation
Current License: CC BY-SA 4.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2022 at 10:19 | comment | added | Ben W | @Louis Cottereau, sure. Thanks for bringing it to my attention. Cheers. | |
| Dec 8, 2022 at 7:10 | comment | added | Kalak | @BenW Same here, that is why when I see something that is not quite right on an answer I comment even if it might be old. It still might help someone else | |
| Dec 7, 2022 at 23:16 | history | edited | Ben W | CC BY-SA 4.0 |
deleted 1 character in body
|
| Dec 7, 2022 at 22:06 | comment | added | Ben W | @Louis Cottereau, yep you're right- I changed it. This was quite an old answer for me. I have learnt a lot trying to answer questions on here over the years and no doubt made a few mistakes along the way. | |
| Dec 7, 2022 at 22:03 | history | edited | Ben W | CC BY-SA 4.0 |
deleted 15 characters in body
|
| Dec 7, 2022 at 14:42 | comment | added | Kalak |
QgsVectorLayer.dataProvider().changeAttributeValues shouldn't be used within an edit session of the QgsVectorlayer (startEditing -> commitChanges) since it bypasses the edit block by accessing directly the underlying data source
|
|
| Jan 28, 2019 at 7:22 | comment | added | lhowarth | That is useful to know! Well spotted! | |
| Jan 26, 2019 at 11:21 | history | edited | Ben W | CC BY-SA 4.0 |
added 7 characters in body
|
| Jan 26, 2019 at 7:20 | history | edited | Ben W | CC BY-SA 4.0 |
added 2 characters in body
|
| Jan 26, 2019 at 6:15 | history | edited | Ben W | CC BY-SA 4.0 |
added 411 characters in body
|
| Jan 26, 2019 at 4:42 | comment | added | Ben W | @lhowarth, I did some testing and experienced a similar issue to you if the join layer was another shapefile (join fields from a csv worked fine). Looks like just an issue with how expressions are parsed. See my edit to my answer above. | |
| Jan 26, 2019 at 4:37 | history | edited | Ben W | CC BY-SA 4.0 |
added 485 characters in body
|
| Jan 24, 2019 at 18:50 | comment | added | lhowarth | Yeah, I think i'll try and post that question later tomorrow - not being able to calculate from joined fields is a definately à pain... | |
| Jan 24, 2019 at 18:47 | vote | accept | lhowarth | ||
| Jan 24, 2019 at 14:49 | comment | added | Ben W | That's disappointing. Not sure what's going on there. May be worth asking a new question. | |
| Jan 24, 2019 at 14:37 | comment | added | lhowarth | Ok, well same problem - works fine on 'native' fields but not on joined fields... no idea why - the script obviously works differently than the field calculater in the attribute table - would be good to know why! | |
| Jan 24, 2019 at 13:58 | comment | added | Ben W | Bummer...does it work on the "native" fields? I tested it summing two integer fields & it was working fine. | |
| Jan 24, 2019 at 13:40 | comment | added | lhowarth | I'm testing the code now - for the minute it creates the field ok but doesn't update the values - perhaps due to the joined fields - I'll keep trying and let you know | |
| Jan 24, 2019 at 13:13 | history | edited | Ben W | CC BY-SA 4.0 |
added 393 characters in body
|
| Jan 24, 2019 at 12:52 | history | answered | Ben W | CC BY-SA 4.0 |