Is there a way to keep the form open after saving a feature?

Ask the Community
1

Hi,

Is there a method to keep the attribute form open after saving a feature in QField? I’d like to avoid having to save and reopen the form repeatedly, as I need to input data quickly.

Thanks!

Imported from GitHub discussion by @paul-carteron on 2025-02-26T11:46:35Z

2

It seems weird not to choose a location before filling a form, doesn’t it ?

Imported from GitHub comment by @VxTedxV on 2025-02-27T19:15:43Z

3

Yes, of course, and that’s not my intention. I was hoping that coordinates are only stored when you save a feature, allowing you to keep the feature open continuously.

However, as you pointed out, the geometry is saved as soon as the feature is opened, correct?

Imported from GitHub comment by @paul-carteron on 2025-02-28T07:49:57Z

4

Maybe this QField plugin helps you. Which allows you to add a feature without Geometry and then you can modify the feature and add the location geometry.

Imported from GitHub comment by @SeqLaz on 2025-02-28T19:08:17Z

5

May be you could develop a customized plugin for feature attribute editing, in which you could control the ui logic on your own.

Imported from GitHub comment by @gitpydev on 2025-03-01T08:02:40Z

6

I believe that when you fill a form to create a feature without knowing yet its location or knowing its numeric coordinates only, it’s not a field work and rather a QGis work but I may be wrong depending the specific case…

Imported from GitHub comment by @VxTedxV on 2025-03-01T15:23:55Z

7

Thanks for answer, I will probably go with the plugin solution !

Imported from GitHub comment by @paul-carteron on 2025-03-03T17:23:02Z

8

In my case, multiple people will be shouting values at me, so I need to enter data quickly. To improve efficiency, I’d like to avoid clicking “Add Feature” each time. Instead, I want the form to automatically reopen after each submission, allowing continuous input without interruption.

Of course, the feature isn’t created where people are shouting the values, but for my use case, this approach works just fine.

Imported from GitHub comment by @paul-carteron on 2025-03-03T17:28:31Z