Direct upload of final submission to OSM, attributed to user

[spwoodcock]

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

• Following on from Manual validation UI for final (conflated) data submission #1549
• The user should be able to submit their data once they have manually verified the submission.

Describe the solution you'd like

• An endpoint should be made for uploading the final submission GeoJSON directly to OSM.
• The GeoJSOn must be converted to OSM format, using osm-fieldwork json2osm.
• The conversion should also include the associated OSM usernames of the mapper for each geometry, if provided.

Describe alternatives you've considered

• Is an endpoint required at all? Can this be done via the frontend and the OSM API instead?

[manjitapandey]

@spwoodcock , Is there any chance we can make this section of verification compulsory during form or we can convince project creator to add this section while uploading custom form too, since it can be the important part on data conflation.

[spwoodcock]

Yes we certainly can! I can make the digitisation verification required in the XLSForm.

I think the only flow we should suggest to project creators is to either use our forms, or extend from our forms. We can hide rows that are important for FMTM functionality so that users don't accidentally edit them.

[spwoodcock]

In the latest form from osm-fieldwork, included in this PR #1555
the XLSForm now looks like this:

With the verification fields in the essential section and hidden by default.

I just made the digitization_correct yes/no question compulsory for the next release too.

[manjitapandey]

Decided on injecting those fields as mandatory. Ref: #1722

[spwoodcock]

Kind of! We still need to 'assess', but I'm hopefull it's feasible 🙏

[spwoodcock]

More context for this here: #1548 (comment)