-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beeper tag registrations #95
Comments
Yeah, this needs some work. The TODO is in these issues: jbrzusto/motusServer#80 I'm still giving some thought as to how to do those things. I think I'll work on the processing first, |
So should I be creating a project for these tags/receivers or keeping this off Motus entirely? The tags should fall off the bats before they leave so likely won't be picked up anywhere else and they don't expect their receivers will get anyone elses tags either |
I'd say create a project for it. All this kind of processing should go
through motus anyway, even if it permissions on the data are very strict.
And that way, whatever beeper support we try to implement gets tested
in the framework other projects will need to use.
…On Tue, Jun 6, 2017, at 15:14, zcrysler wrote:
So should I be creating a project for these tags/receivers or keeping this off Motus entirely? The tags should fall off the bats before they leave so likely won't be picked up anywhere else and they don't expect their receivers will get anyone elses tags either
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#95 (comment)
--
#-----------------------------------
# John Brzustowski
# Wolfville, NS Canada
|
Ok, it'll be project 157. Bioenergetics of WNS in western bat species. Can you register the tags from the file she sent or do you need to wait for detection data to come in? |
I received an email from Katie Haase who is working on a bat project with Liam McGuire, they've put out a bunch of beeper tags but didn't register them. They said they had previously sent you a list of frequency information, I'm not sure if that was for this year or a previous year. I've attached the spreadsheet she sent me for this years deployed tags.
What would be the best way to deal with this/future beeper tag projects? Do you deal with these separately or should we be getting those tags into motus and requesting metadata for tags/receivers. This one might be a bit unique since they can't disclose publicly any location information, and their receivers likely won't pick up any other tags so it may not affect other projects.
Telemetry_tag_list (3).xlsx
The text was updated successfully, but these errors were encountered: