You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2022. It is now read-only.
Add function to get deployment metadata in the Movebank standard reference data format. Goal is that the output (csv) can be uploaded as is to Movebank to import/update reference data there (i.e. it contains all the columns Movebank expects).
All the required mapping for this function is already written in this SQL file. The remaining work is validating input arguments, connecting to the DB and running the SQL with glue().
All parameters are expected by glue() SQL template, but defaults should be used if not provided by user.
project is the literal project key. It's existence should be looked up in UvA-BiTS DB
Most other parameters are controlled values: an error should be returned for wrong values.
Output
csv or dataframe: not sure what best approach is. Most often, you'll want this data as a csv file that you can upload to Movebank, but it might be nice if you can just get it as a dataframe too. If we offer csv file option, then path parameter should be included.
The text was updated successfully, but these errors were encountered:
Add function to get deployment metadata in the Movebank standard reference data format. Goal is that the output (csv) can be uploaded as is to Movebank to import/update reference data there (i.e. it contains all the columns Movebank expects).
All the required mapping for this function is already written in this SQL file. The remaining work is validating input arguments, connecting to the DB and running the SQL with
glue()
.Input
Input parameters (see this code).
project
MH_WATERLAND
animal_life_stage
NA
attachment_type
"harness"
manipulation_type
"none"
bird_remarks_is_nickname
FALSE
path
Notes:
glue()
SQL template, but defaults should be used if not provided by user.project
is the literal project key. It's existence should be looked up in UvA-BiTS DBOutput
csv or dataframe: not sure what best approach is. Most often, you'll want this data as a csv file that you can upload to Movebank, but it might be nice if you can just get it as a dataframe too. If we offer csv file option, then
path
parameter should be included.The text was updated successfully, but these errors were encountered: