Load data into Aerie from UI

[bradNASA]

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.

[joswig]

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

[dandelany]

We discussed the first implementation of CSV support in Slack today. Unlike JSON files, CSV files can't easily contain a schema or other metadata describing the format, so we decided to enforce these restrictions on CSV file uploads:

• CSVs will only support numeric profiles, ie. we will assume the following type/schema for all CSV uploads:

  "type": "discrete",
  "schema": { "type": "real" },
  

• The CSV will be assumed to have a header with column names
• The time column must be named time_utc and will allow only the following timestamp formats: 2024-183T00:00:00 or 2024-07-01T11:40:55.219Z.
• The start time of the dataset will be defined as the minimum time value in the time_utc column
• Any datasets requiring more flexibility than this should just use JSON files for import

CSVs will uploaded to a particular plan. On upload, the user will have the option to associate the dataset with (only) the currently selected simulation dataset.

[ewferg]

Any reason we can't support a profile with enumerated states as strings? That seems like it could also be a common use case.