[FF] Support .geojson exports on Case Export page

[Charl1996]

Product Description

Demo video

A new export file type has been added to the case export page (sitting behind a FF), exporting case data to a .geojson file. The export file structure follows the standard geojson file structure. This exported file is intended to be imported into any GIS tool, for example ArcGIS.

The geojson file consists of features where each feature has a "geometry" section and a "properties" section. HQ will thus need to know which exported properties will define this "geometry" section (the rest will be assumed to be the "properties" of the geometry feature). The geo-property is determined by looking through the Data dictionary for the specific case type that is being exported and searching for the property with data type set to GPS (this feature depends on the CASE_IMPORT_DATA_DICTIONARY_VALIDATION feature flag).

Example of geo json export configuration:

If multiple geo-properties are detected, the user can use the Select geo property select input to specify which geo-property's coordinates will be used in the .geojson file to define the GPS point.

Example

Cases on HQ with "person" case type:

Imported "person" cases as visualized using ArcGIS Online.

Technical Summary

Ticket

A new export writer has been created, GeoJSONWriter, which writes to a .geojson file. The writer looks at the configured selected_geo_property value (a new field on the ExportWriter class) to determine which property should define the geometry section of each feature in the geojson file (see example of geojson file). All other export columns is considered to be properties of the feature(s).

Note: the exported .geojson file contains one feature collection which corresponds to one exported table, although this loop iterates over potentially multiple tables; I'm not 100% sure in what context multiple tables would be configured, so any input there might be helpful.

Feature Flag

New feature flag (SUPPORT_GEO_JSON_EXPORT)

Safety Assurance

Safety story

Tested locally and used the HQ generated .geojson file to import it into ArcGIS Online successfully.

Automated test coverage

Added some unit tests for the new export writer.

QA Plan

QA planned. Ticket to be linked.

Migrations

There's no migrations, but a new field is added to the ExportWriter class. No data migration necessary as this feature is completely new ground.

Rollback instructions

• This PR can be reverted after deploy with no further considerations

Labels & Review

• Risk label is set correctly
• The set of people pinged as reviewers is appropriate for the level of risk of the change

[zandre-eng]

Overall looks good, I've left a few comments.

I'm curious to hear if you did any testing around case exports containing repeat groups?

[zandre-eng]

We loop through each table in the export, however a few lines below we only grab the first table's features. Do we require this loop if we're only interested in the first table?

[SmittieC]

Looks good to me once Zandre's comments have been addressed

[kaapstorm]

This is great. Just the one super nitpicky spelling thing.

[mkangia]

@Charl1996
thanks for tagging me on this. I see you already have a solid review from Zandre and Norman.
Considering this is a big one, I will skip going through it, let me know if you suggest I should take a pass.

[zandre-eng]

Looks good. No blocking feedback from my side.

[SmittieC]

A test is failing. Otherwise looks good

[Charl1996]

The IndexError will occur if the row[geo_data_index] value is not correct (not in a form like "lat lng ..."), hence safe to ignore. Also, ValueErrors are not expected anymore.