[Export job data] Allow data to be exported as GeoJSON

[jo-spek]

Currently, the data export "Download job data" delivers a CSV. It would be great to also have the option to download the job data as GeoJSONs.

Users that want to display their recorded geodata in a GIS need to do extra steps to draw the WKT notation from the CSV, whereas a GeoJSON can simply be dragged and dropped into any GIS. Also, regarding the EUDR aspect, the EU Information System is set to accept only GeoJSONs containing the geometries, the ISO2 country code and a few optional columns.

Thanks for considering.

[jo-spek]

Hi @kenstershiro, connecting to yesterday's chat, we have consensus that this needs doing. We could push this to P1 or even P0, or what do you suggest @rfontanarosa?

[jo-spek]

While we're at it, we could automatically add the columns required for upload in the EU Information System, i.e.:
"ProducerName" (can be left empty), "ProducerCountry" (mandatory ISO2 country code), "ProductionPlace" (can be filled with the name given to the geometry), and "Area" (hectares for polygons, empty for points). --> This is a nice to have, no high priority.

Split off into this FR: #2123

[kenstershiro]

@jo-spek to set the priority and whether to pull it into the current or next sprint, it would be good to understand better the use cases for geojson data, and how important and urgent they are. It doesn't sound like a P0 which usually means a blocking issue or bug or something essential with a tight deadline. Let's chat tomorrow on our call.

[kenstershiro]

After internal discussion agreed on the high priority and usefulness of this new feature. Dev can kick off as soon as we have capacity. Small UX input needed in parallel on nav links and terms to use for the additional download option. e.g.
"Download full survey results"
"Download geodata"
OR
Download survey results (CSV)
Download geodata only (GeoJSON)

[kenstershiro]

@jo-spek to split into two tasks:

1. geojson export - Must have (P0.5)
2. creation of properties needed for EU Information System compatibility: "ProducerName" (can be left empty), "ProducerCountry" (mandatory ISO2 country code), "ProductionPlace" (can be filled with the name given to the geometry), and "Area" (hectares for polygons, empty for points).
3. Second point needs further discussion offline @rfontanarosa @gino-m @jo-spek

[gino-m]

@vittorino for how to allow user to select between CSV vs GeoJSON

[jo-spek]

@jo-spek to split into two tasks:

2. creation of properties needed for EU Information System compatibility: "ProducerName" (can be left empty), "ProducerCountry" (mandatory ISO2 country code), "ProductionPlace" (can be filled with the name given to the geometry), and "Area" (hectares for polygons, empty for points).

Done. 2 to be found here: #2123

[jo-spek]

@vittorino for how to allow user to select between CSV vs GeoJSON

Low quality suggestion since it's already been created:

Could probably look a lot nicer still.

[vittorino]

@gino-m here's my recommendation:

[gino-m]

Thanks! They will both download the same job data, just in different formats. In that case would it make sense to just have one menu option and prompt in a dialog?

[kenstershiro]

For implementation there's a dependency on completing the PR for streaming data #2091

[gino-m]

@vittorino @rfontanarosa Updated based on our discussion: