alexvmt / animal-movement-summary-and-stationarity-analysis Goto Github PK

Hi @alexvmt & @mb-feldm,
it seems your app needs the data to be in a geographic coordinate system, i.e. EPSG:4326. Given that the error that it gives is not at all intuitive, I would recommend to include in the function checking if the incoming data is in lat/long (there are several packages that do that, I think), and if not to reprojected to EPSG:4326 and print a message (e.g. logger.info()) to let the user know that the data were reprojected. Maybe just implement it when transitioning the app to move2. Also make a note of this in the documentation.
Best, Anne

Hi @alexvmt
We had a message from Greer Smith, who is using your on a regular basis, but gets an error since we have updated the Movebank App to move2. Please, can you have a look into it? Might also be a good time to start with a transition to move2 for this App. Thanks! Details below. Best, Andrea

message from Greer: "When do you think the app "Animal Movement Summary and Stationarity Analysis" will be back operational? Since the updates, I have had this error message. "Error Replacement has 0 Rows, data has 8380." and of course the data number changes to however many data points i am trying to analyze." Screenshots from him below

Hi Alex,
Thanks so much for your contribution to MoveApps and EMAC23!

I have built your App so that you can test it on MoveApps. The App runs for me locally fine and looks very good, but there are three changes I would receommend:

1. The two lines 19-21 in ShinyModule.R are outside of the functions, which is not meant to be, but we are not sure if it could work. I would recomemend to move them e.g. to line 280, but try if/how it works in MoveApps. In case it does not work, the error message should be clear.
2. Locally the App did only work when I added the command "library(shiny)", might be worth to explicitly add it to the ShinyModule.R top and also the dependencies in the appspec.json. (even if it locally gets loaded as a dependency of shinybusy)
3. Please, indicate in the readme.md that the output data type is moveStack (UI is not really an output type any more), i.e. the input data so that the App can be integrated in a workflow.

All the best, Andrea
(@annescharf FYI)