Open jkburges opened 9 years ago
Email Enquiry, Thursday 21 May 2015: Hello,
I’m trying to access the visualisation tools within the AATAMS database to visualise my passive acoustic animal tracks in Google Earth as documented at https://www.youtube.com/watch?v=ukFFCxAULvs
While I’ve tried running the on both Google Chrome and Firefox browsers, it appears that this functionality is not currently available and I am only able to download a CSV containing the tag detections.
Can you please let me know when this functionality will come back online - it’s very useful when we have data spanning several years and across various receiver arrangements.
Kind regards,
Ross
Dr Ross Dwyer
Hi Ross,
Thanks again for contacting us.
You are correct, the KML export functionality is no longer available it has been disabled for a number of reasons.
I can advise that it certainly has not been forgotten and sits in a backlog of issues and feature requests that have been prioritised in importance accordingly by management (both at eMII and AATAMS).
As such I cannot advise when this feature will be re-introduced.
Please do not hesitate to contact us if you have any further questions.
Warm Regards, Kate
Hi Kate,
Thanks for letting me know and sorry to hear this functionality is no longer available in AATAMS. It was a big carrot for those looking to upload their data to the database, even those concerned about data security.
I’ll look to develop some code to do something similar in the R programming language.
Best wishes, Ross
Dr Ross Dwyer
... or at least it will be, when https://github.com/aodn/aatams/pull/169 is released.
The decision was made to disable KML export for detections - it was proving too difficult to get this working in the context of the new protected species feature.
The current "pipeline" for extracting detections from the database, applying security restrictions and then rendering as either HTML, CSV or KML is a bit of a tangled web and could really do with some cleaning up - then, in theory, doing the KML stuff would be much easier.
I'd like to see something like the following three distinct stage:
As a side note, a lot of the tests are implemented as grails integration tests - it would be desirable to move most, if not all, of these to unit tests (for speed, ease of development) when addressing this bug.