Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tokha discussion additonal requirements #1915

Open
spwoodcock opened this issue Nov 25, 2024 · 3 comments
Open

Tokha discussion additonal requirements #1915

spwoodcock opened this issue Nov 25, 2024 · 3 comments
Labels
backend Related to backend code effort:high Broader scope task with unclear timeline (consider splitting) enhancement New feature or request frontend Related to frontend code priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

4 Requirements

High Priority

Multiple Feature Selection At Once

  • Ability to select two geometries as part of a form.
  • This requires creating a second entity list (done).
  • One option is via ODK (the current setup):
    • Extra question injected into XLSForm.
    • User selects one geometry in one question.
    • Selects associated geometry in another question.
  • However, a more ideal scenario would be to solve this via the FMTM map UI:
    • User selects one geometry.
    • Popup appears to 'Map Feature', with an extra button to 'select associated geometry'.
    • User selects second geom.
    • User clicks button to 'Map Feature'.
    • ODK form is opened with both geometries pre-selected (via URL params).
    • To facilitate this perhaps we need a flag / db record that the user opted for multiple geometries?

Adding New Geometries Via FMTM

  • We added a geopoint capability.
  • This needs to be more advanced.
  • We need building polygon and road polyline addition too.
  • Probably possible in ODK via form.
  • Ideally also solved via FMTM mapping library.
    • Create new geom, then open in ODK.
    • Send the new geometry as javarosa string to to the form as intent field.

Low Priority

Submission Download Filtering

  • Filtering by date is useful.
  • Particularly in workflow that require validation on a daily basis (as new data comes in).

Displaying Recently Digitised Buildings

  • Show recently digitised buildings to the enumerator.
  • In ODK:
    • We could achieve this by updating the create_if logic for the entity and adding the new geom to the entities list.
    • It would display the next time the user views the geometries in a question.
  • In FMTM:
    • This is harder as we rely on the flatgeobuf geometry!
    • Needs more thought it going this route.
@spwoodcock spwoodcock added backend Related to backend code effort:high Broader scope task with unclear timeline (consider splitting) enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority labels Nov 25, 2024
@manjitapandey manjitapandey added priority:low Backlog of tasks that will be addressed in time and removed priority:high Should be addressed as a priority labels Nov 28, 2024
@manjitapandey
Copy link
Contributor

The addition of New Geometries can be done through odk using geoshape and geotrace. So this is not the priority to integrate this feature on FMTM especially for tokha.
The Multiple Feature Selection At Once: This feature is also already addressed on odk. We are able to select two features from the same geojson file on two different questions. But selecting two features on the same questions seem very difficult technically and not sure will beof high priority.

@spwoodcock
Copy link
Member Author

The addition of New Geometries can be done through odk using geoshape and geotrace. So this is not the priority to integrate this feature on FMTM especially for tokha.
The Multiple Feature Selection At Once: This feature is also already addressed on odk. We are able to select two features from the same geojson file on two different questions. But selecting two features on the same questions seem very difficult technically and not sure will beof high priority.

Amazing if they will be happy with that!

They seemed pretty adamant they want the features to be more user friendly though!

I would suggest we first:

  • Test adding a geotrace.
  • Update our form injection so we can select between an add geopoint, or add geotrace question (or both?). I assume most users actually want geotrace!
  • If we decide it's not nice to work with, we could consider the approach via FMTM as discussed (but not preferred!). In the long term we could improve this via the map we make available on Web Forms anyway.

@spwoodcock
Copy link
Member Author

The linked PR has solved 'Adding New Geometries Via FMTM'

I agree we shouldn't look into 'Multiple Feature Selection At Once', as it's quite specific to this project and is a bit of work.
Maybe in the future 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Related to backend code effort:high Broader scope task with unclear timeline (consider splitting) enhancement New feature or request frontend Related to frontend code priority:low Backlog of tasks that will be addressed in time
Projects
Development

No branches or pull requests

2 participants