joswig
commented
2 weeks ago For the initial implementation lets limit the scope to
- The json format already supported by our graphQL schema
- CSV matching the format in our docs example, optionally with the time column in UTC
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
I'm frustrated when I want to see some time-series data in Aerie, but I don't want to edit Java.
Describe the feature request
I need or want to be able to upload time-series data and add it to views in a plan like any other resource. If this were spreadsheet data, I'd like multiple resources to be created using the header for names; for example the first row has resource names, the first column is a time value, and the other columns are each values for a resource.
The data could be uploaded once and reused for different mission models and plans.
A bonus would be if it could be used for activities, too.
A bonus would be if I didn't have to worry about the time format or even the file format. For example, as an alternative to timestamp formats, durations could be offsets from the plan start. CSVs, Excel, JSON, and different simple text formats might all be supported. The idea is that the user doesn't need to do any cleaning.
Joe Guinn has given me this request three times.