-
Notifications
You must be signed in to change notification settings - Fork 1
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
Realtime source data cannot ever be colocated #2
Comments
I wonder if there is every lat,lng drift, which would also cause some weirdness here. @caparker do you have a recommended alternative to lat,lng? |
I think we should use some sort of namespace idea that includes the node/system/sensor to match directly to the sensor, much like they are doing in the second update. But we do have to decide what to do if the names all match but lat/long has changed. I would assume at that point its a new deployment of the same set of instruments. |
We are using only the location to match a sensor node
Which could lead to issues if two sensors are co-located.
The text was updated successfully, but these errors were encountered: