Direct upload of final submission to OSM, attributed to user

hotosm / fmtm

Field Mapping Tasking Manager - coordinated field mapping.

https://fmtm.hotosm.org/

GNU Affero General Public License v3.0

40 stars 44 forks source link

Direct upload of final submission to OSM, attributed to user #1550

Open spwoodcock opened 1 month ago

spwoodcock commented 1 month ago

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

Following on from https://github.com/hotosm/fmtm/issues/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 commented 3 weeks ago

@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 commented 3 weeks ago

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 commented 3 weeks ago

In the latest form from osm-fieldwork, included in this PR https://github.com/hotosm/fmtm/pull/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.