Add a fixed endpoint for retrieving a KML file via the API

[grantfitzsimmons]

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

Our request via the API is desired to be to GET the KML and not to initiate the generation of a KML file that we can obtain some other way.

Describe the solution you'd like

This is cool and it would be even cooler if we could have a fixed endpoint to be able to access this kml file.... The goal is to configure ArcGIS to hit a url to obtain the KML. If we have to hit one endpoint to first generate it and then a second endpoint to retrieve, we are then writing an application middleware to work between the two APIS [Specify's and ArcGIS]. My suspicion is that even if we manually push the buttons in Specify to create the KML file, that every time we hit the endpoint to generate the KML file it will create a NEW file to download instead of overwriting the previously generated one. Therefore I suspect that we cannot have a fixed file endpoint for obtaining the KML.

Describe alternatives you've considered

Use the token to make a request to the appropriate Specify 7 API endpoint to generate the KML file for the desired data (this is not documented unfortunately, but the endpoint is at /stored_query/exportkml/. The body of the request should be the serialized query you wish to perform the export on. While it will return a ‘200 OK’ response, it should generate a notification for the current user. You can either open Specify and download the KML file from the notification sent to the current user, determine the structure of the static file URL that is generated by the application (e.g. deduce the structure used in this URL https://sp7demofish.specifycloud.org/static/depository/Collection%20Objects%20in%20Fiji%20-%20Mon%20Jul%2015%202024.kml and construct this URL), or you can access the Docker container / mount the ‘static/depository/‘ location on the host machine so the file is made immediately accessible to you.

Reported By
University of Michigan and Ohio State Mollusks