Hello,
Following the latest update, I noticed that the “edit entity” button, directly accessible from an feature’s form, has disappeared for point only. In my form, I have “horizontal accuracy” and “Z” fields that used to update when using this button (by retrieving GNSS data). Now, if I move the feature using the “move features” tool, these fields no longer update.
I would like to know if the disappearance of the button is normal and, if so, if there is a way to resolve this issue of the fields no longer updating?
Thanks,
@Nicolas , I believe we discussed this over github? In any case, for our broader community, this has been fixed in QField 4.1.4. The "move feature’ tool now captures the Z value (of snapped vertices or GNSS position) when moving.
Thank’s for your reply. I think it wasn’t me on github.
I have download the latest update and i capture the z now but not the horizontal accuracy (not all the time). When i edit feature i capture the horizontal accuracy but when i move the feature i lose it. In my form i’ve tried with @position_horizontal_accuracy or @gnss_horizontal_accuracy and check “apply the default value on the update”. And it’s the accuracy at the moment i edit and not at the moment i move.
is there a way to capture the accuracy associated to the move action and not the edit one ?
I have the same problem as Nicolas: I remember the accuracy was updated when moving a feature. Now I have to edit the feature after moving to store the accuracy (and it can have changed in a few seconds).
I move features when connected to RTK. I want to store the accuracy at this moment.
I edit features without being at the real place, and the current QField app replaces the accuracy associated with the RTK-measured position with another one that does not make sense.
This seems to be a regression.
“Apply default value on update” could be replaced by:
“Apply default value on position update” + “Apply default value on feature field update”