AVEVA™ Insight

About CSV and JSON data files

Save PDF

Save PDF

You can upload data to your AVEVA Insight data source using one of four file formats:

CSV and JSON data files must comply with the following standards:

RFC 4180 (https://www.ietf.org/rfc/rfc4180.txt)
UTF-8 text encoding
The timestamp format that is used by JavaScript conforming to ISO 8601
That is: "2016-10-06T00:00:00.000Z", where "Z" corresponds to UTC time. Other offsets (for example, "2016-11-29T10:00:05-08:00") are also allowed.

Note: If the dateTime column is not specified or is left empty, AVEVA Insight uses the date and time that the file was uploaded.
Timestamps should use a maximum millisecond precision of 3 digits. Any more than first 3 are ignored. Milliseconds can be omitted, defaulting to 0.

Data values can be formatted as follows:

Numeric values must use the decimal point separator. A separator for thousands is not supported.
For JSON, place values between double quotation marks (").
For CSV, if a comma appears in a string value, that value must be placed between double quotation marks ("). Otherwise, quotation marks are not required. However, if any value is contained within double quotation marks, AVEVA Insight assumes it is a string value.
For CSV, any of these can indicate the end of line: "\r", "\n", "\r\n", CR, LF, CR/LF

Note about NULL and Not-a-number (NaN) values: Currently, there is no way to upload NULL values from a CSV or JSON file. Empty values are skipped and NULL values are interpreted as strings. If "null" is uploaded for a numeric tag, a type mismatch error results.

If you are using CSV files, decide whether to use the normal ("narrow") format or wide format. Here's the key benefit of each:

Using the narrow format, you can specify OPC quality and storage operation ("original", "latest", or "delete") for each value.
Using the wide format, you have columns as tag names. You cannot specify OPC quality per value.