MerginMaps / MerginMaps/mobile
suggestion/idea: allow initialize digitizing a feature/asset not from geometry first
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
When surveying assets/feature in the field there is a pretty common use case, one where there are some information/attribute that need/must be taken from a distance from the asset/feature, sometimes at 10/20 or more meters from it. Think about the need to measure the height of a building or a tower with a digital hypsometer and/or the need to take a picture of that asset/feature so that the whole of it is pictured in the photo.
As it is now the workflow is:
- you go by the asset/feature (frequently with your mobile phone/tablet stick to a pole with an RTK antenna on top of it)
- add the feature/point, fill the attributes that the form needs
- move away (10/20 sometimes even more meters) from the digitized point so to take a measurement that can only be taken from a few meters away
- go back to the feature, all the above by carrying with you some "heavy" equipment
When a technician has to repeat that tens/hundreds times a day it adds up to a lot unnecessary steps each day.
Yes, I know that with Mergin one can digitize away from the feature and then when the antenna is close to the feature click again in "edit geometry" and the position gets corrected automatically with the antenna position, but this leads frequently to the operator forgiving that he/she needs to do it.
A nice addition (and solution for the above scenario) would be an option that would allow to start editing the form without entering the geometry as first step of the workflow, and allowing to enter/digitize it further down in the form filling.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the mobile app's feature-creation and form-filling workflow, then review the existing edit-geometry behavior described in the issue. Done means a user can begin entering the form without first setting geometry and add or capture the geometry later in the workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100