Add kml selection exports

[alesan99]

Fixes #3589

Adds the ability to export a KML file from a query using only the selected query results.

Checklist

• Self-review the PR after opening it to make sure the changes look good
  and self-explanatory (or properly documented)
• Add automated tests
• Add relevant issue to release milestone

Testing instructions

• In query builder, create a locality query with coordinate data (like Latitude1 and Longitude1).
• Run the query and "Create KML"
• Make sure the KML was exported correctly. The result should be the exact same as one created on production.
• Select any rows of the query results.
• Make sure the KML includes ONLY the rows that were selected. (Also keep in mind that any rows without valid coordinate data will not be exported.)
• Make sure CSV exports still work.

[realVinayak]

While I'm sure that this is done to mimic CSV on frontend, I think a better implementation would be just to make an API call, but this time adding an extra filter to just select the ids that the user chose. Benefits:

1. Much simpler to implement
2. If in future we find a bug in KML on backend, we don't need to waste time fixing on frontend.
3. No need to reimplement the wheel
4. Most importantly (/s), I'll need to be doing something similar for batch-edit BUT I plan on making it a backnd way (snding filtrs). So, if you implement it right, I can reuse it! If you want, you can use wb_improvements to implement it straight-away (I'm not sure where it lies in priority, so ask @CarolineDenis too).

@maxpatiiuk thoughts? I think, even for CSV, it would have been better to directly use backend.

[maxpatiiuk]

Good use of the utility functions that we have available!

Nevertheless, I agree with Vinny that if it would reduce duplication, we should do this work on the back-end.

---

Aside from that, better communication about who is working on what is always nice to avoid redundant effort

[alesan99]

While I'm sure that this is done to mimic CSV on frontend, I think a better implementation would be just to make an API call, but this time adding an extra filter to just select the ids that the user chose. Benefits:

I agree. I already came across issues myself having to implement the same feature twice on my last CSV export PR.

I think the only downside is we'd lose the instant downloads from the frontend exports.
But I'd like to take a look into it and see if I'm able to do that.

[realVinayak]

I don't think it necessarily matters, especially for KML exports. For CSV, it is quite handy to do it within a few clicks, so don't change that (or users wouldn't like extra clicks needed now). For KML, definitely go the backend route. You'd learn about the query builder API quite a bit in the process!

[maxpatiiuk]

👍

[emenslin]

Testing instructions

• In query builder, create a locality query with coordinate data (like Latitude1 and Longitude1).
• Run the query and "Create KML"
• Make sure the KML was exported correctly. The result should be the exact same as one created on production.
• Select any rows of the query results.
• Make sure the KML includes ONLY the rows that were selected. (Also keep in mind that any rows without valid coordinate data will not be exported.)
• Make sure CSV exports still work.

If you try to create KML without selecting any rows nothing happens. Creating a KML and selecting rows does work along with creating a CSV with or without selecting rows.

[pashiav]

• In query builder, create a locality query with coordinate data (like Latitude1 and Longitude1).
• Run the query and "Create KML"
• Make sure the KML was exported correctly. The result should be the exact same as one created on production.
• Select any rows of the query results.
• Make sure the KML includes ONLY the rows that were selected. (Also keep in mind that any rows without valid coordinate data will not be exported.)
• Make sure CSV exports still work.

---

Looks great! Everything works as expected.

[emenslin]

Testing instructions

• In query builder, create a locality query with coordinate data (like Latitude1 and Longitude1).
• Run the query and "Create KML"
• Make sure the KML was exported correctly. The result should be the exact same as one created on production.
• Select any rows of the query results.
• Make sure the KML includes ONLY the rows that were selected. (Also keep in mind that any rows without valid coordinate data will not be exported.)
• Make sure CSV exports still work.

Looks good!!