-
Notifications
You must be signed in to change notification settings - Fork 9
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
Determine the logic behind the Vectronic data ID #24
Comments
By data point ID, do you mean the first column in a vectronic text file? Eg. the "2674" in the following snippet:
Just curious if I can help answer your question. I have lots of these to look at. At first glance, they appear to just increment with each position record for a collar. Not unique to collars or accounts. |
Yeah, one guess is that they increment across some large set of collars or
even all active collars?
…On Fri, May 3, 2019, 2:51 PM rgzn ***@***.***> wrote:
By data point ID, do you mean the first column in a vectronic text file?
Eg. the "2674" in the following snippet:
2674 16245 2019-01-01 20:00:31 2019-01-01 12:00:31
Just curious if I can help answer your question. I have lots of these to
look at. At first glance, they appear to just increment with each position
record for a collar. Not unique to collars or accounts.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADV56DVSHOMG3G6H663ODDPTSQWPANCNFSM4HJ7Z7GA>
.
|
@HansMartinMT or @foresthayes can you please respond to this question "By data point ID, do you mean the first column in a vectronic text file?" |
Using collar::fetch_vectronics the first column I get back is "idPosition". Below are the last 50 values for a single collar. I have not been able to figure out what these values relate to although they do seem to always increase. Note that the increment is often ~50,000 but is also highly variable.
|
We want to determine if we can use the data point ID to allow us to access data starting after a previous download. If the data point ID's are unique to 'our' collars, this could allow us to use a single ID to access for all of the collars instead of having a unique data point ID for each collar.
The text was updated successfully, but these errors were encountered: