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
Currently, I am getting feedback from users that find it tricky to analyze data downloaded from the platform because the downloaded CSV seems "inconsistent". By this, they mean that the columns in the downloaded CSV seems to not be always ordered in consistent ways (I guess because components are created dynamically?).
Maybe we could take a look at it and solve also the inconsistency between the CSV downloaded from the API, and the one you get from the SD-card, which have significantly different headers. Let's discuss how we can do it, but it should be fairly simple to map the same short names / descriptions used on both ends given the sensor IDS (which I already do in the scdata package).
The text was updated successfully, but these errors were encountered:
Currently, I am getting feedback from users that find it tricky to analyze data downloaded from the platform because the downloaded CSV seems "inconsistent". By this, they mean that the columns in the downloaded CSV seems to not be always ordered in consistent ways (I guess because components are created dynamically?).
Maybe we could take a look at it and solve also the inconsistency between the CSV downloaded from the API, and the one you get from the SD-card, which have significantly different headers. Let's discuss how we can do it, but it should be fairly simple to map the same short names / descriptions used on both ends given the sensor IDS (which I already do in the
scdata
package).The text was updated successfully, but these errors were encountered: