Skip to content

Moving a singlepart point should adopt Z/M of snapped position#7214

Merged
nirvn merged 1 commit intomasterfrom
move_z_m_fix
Mar 28, 2026
Merged

Moving a singlepart point should adopt Z/M of snapped position#7214
nirvn merged 1 commit intomasterfrom
move_z_m_fix

Conversation

@nirvn
Copy link
Copy Markdown
Member

@nirvn nirvn commented Mar 27, 2026

Fixes #7190

Background on this: since QField 4.1, in order to offer a less intimidating interface, we removed the geometry editor button for singlepart points because they only thing that could do is doing a one-vertex movement operation, which is the same thing as moving a feature.

That being said, the move feature would not transfer Z/M the same way a vertex movement did. This PR fixes that.

@qfield-fairy
Copy link
Copy Markdown
Collaborator

qfield-fairy commented Mar 27, 2026

🍎 MacOS DMG universal builds

Download a MacOS DMG universal build of this PR for testing.
(Built from commit 6957ef5)

📱 Android builds

Download an Android arm64 build of this PR for testing.
(Built from commit 6957ef5)

Other Android architectures

🪟 Windows builds

Download a Windows build of this PR for testing.
(Built from commit 6957ef5)

🐧 Linux AppImage builds

Download a Linux AppImage build of this PR for testing.
(Built from commit 6957ef5)

@pbourges-lahocy
Copy link
Copy Markdown

Hi,

I confirm that moving a point now correctly updates the Z value. This fixes the issue on our side.

Thanks for the fix

Best regards,

@nirvn nirvn merged commit b8e2925 into master Mar 28, 2026
28 checks passed
@nirvn nirvn deleted the move_z_m_fix branch March 28, 2026 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Moving point features does not seem to update Z value when using GNSS

4 participants