-
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
Upload buehlot #14
base: master
Are you sure you want to change the base?
Upload buehlot #14
Conversation
metadata confusion
Buehlot upload is working fine in my local database
I can also send you the raw data, to which I made some small changes, which I have also documented in the upload script. |
Thanks a lot. I will have a look at the weekend or early next week. |
Alex just sent me the rest of the data, plus there was probably an error in the data I had so far, which Alex has now fixed. After that you can review the pull request |
perfect, I'll wait for your feedback |
Hey Alex, |
Just some unclear variable and unit conversion
…into upload_buehlot
Buehlot upload is running from start to finish. There exist mainly unclarities in some variables and possible variable conversions: 1. Ott water level:metadata:
plotted data:
2. TruTrack water height:metadata:
plotted data:
|
The Bühlot upload script works on my local database.
At the moment, precipitation and air temperature data for the operator KIT are uploaded by the upload_buehlot_kit script.
We can wait until I get the other data, or we can upload the first data as is.
Maybe you could look at how I saved the warnings in the details. Currently each warning gets an extra detail with tstamp and the warning as value. So a lot of lines are written in the details, but I don't know if this is a problem and I didn't have a better idea yet. At the end of the script is an example of how I find a warning about a tstamp.