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

No easy way to get geojson submissions from FMTM/ODK #1452

Open
spwoodcock opened this issue Apr 17, 2024 · 0 comments
Open

No easy way to get geojson submissions from FMTM/ODK #1452

spwoodcock opened this issue Apr 17, 2024 · 0 comments
Assignees
Labels
backend enhancement New feature or request frontend QA ready Any issues that is fixed

Comments

@spwoodcock
Copy link
Member

Is your feature request related to a problem? Please describe.

@manjitapandey related to E2E feedback.

  • There is no easy way to get submission data in GeoJSON format.

Describe the solution you'd like

Backend:

  • Following on from Frontend buttons to load Entities in ODK Collect by intent #1449 we should get the submission data via OData endpoint, using osm-fieldwork OdkCentralAsync.OdkEntity.getEntityData().
  • This data should be parsed and then passed through the same logic that currently sits in /helper/convert-odk-submission-json-to-geojson.
  • The result should be GeoJSON format submission data from a submission router endpoint.

Frontend:

  • There should be a new button added in the download section:
  • image
  • The button should say 'Submissions' and download the data in GeoJSON format from the new endpoint.

Additional context

  • OData / Entities significantly improve this workflow, as in the past we had to cache the submissions in S3.
@spwoodcock spwoodcock added enhancement New feature or request frontend backend labels Apr 17, 2024
@spwoodcock spwoodcock added this to the FMTM 2024.03 Release milestone Apr 17, 2024
@spwoodcock spwoodcock assigned spwoodcock and Sujanadh and unassigned spwoodcock Apr 29, 2024
@spwoodcock spwoodcock added the QA ready Any issues that is fixed label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend enhancement New feature or request frontend QA ready Any issues that is fixed
Projects
Status: In Progress
Development

No branches or pull requests

3 participants