GuidesUploading data

Uploading your data to DataCNVS

You can upload any data file to DataCNVS. We keep a copy of the original, work out which of our file readers (parsers) fits it, and turn its contents into searchable, plottable data with units you can trust.

On this page

Each upload moves through four steps, and you can follow every one in the Upload Queue:

Uploading file. Your file is sent securely to your workspace.
Parsing file. DataCNVS picks the right parser and reads the columns, values and metadata in your file.
Identifying variables. Each column is matched to a scientific variable (such as temperature or angle) and its units. You review anything we are unsure about.
Storing. Values are converted to consistent units and saved, ready to use on a canvas.

Most files go from upload to ready without any input from you. When DataCNVS needs a decision, the upload is marked Action required.

Supported file types #

DataCNVS accepts files of any type, and six parsers currently read their contents automatically. This is today's list, not a fixed one. We add new parsers regularly.

Parser	File extensions	What it reads
CSV	.csv	Comma-separated tables; column headers become your data series
Tabular	.txt, .tsv, .tab, .dat, .asc	Text-based scientific tables. Detects headers, units, metadata and the delimiter
JSON	.json	General JSON files, including single values and tables
TRIOS JSON	.json	TA Instruments TRIOS JSON exports, recognized automatically from their contents
Parquet	.parquet	Columnar Parquet files; each column becomes a data series
XRDML	.xrdml	Malvern Panalytical (formerly Philips/PANalytical) XRDML diffraction scans

How DataCNVS picks a parser #

DataCNVS looks at more than the file name. It checks three things, in this order:

File extension, such as .csv or .xrdml.
File type, as reported by your browser. A file with an unfamiliar extension can still be matched if it is recognized as, say, plain text.
What's inside. Some formats share an extension with others. For these, DataCNVS reads the start of the file and checks for the structure that format always has. A TRIOS JSON export is recognized this way, for example.

If a parser built for one specific format matches, it is chosen over a general one. If the contents don't match any specific format, the general parser for that file type is used instead. For example, a .json file that isn't a TRIOS export goes to the JSON parser.

Uploading a file we don't read yet

You can still upload it. We store the original file and the upload shows a Parser selection error in the Upload Queue. If one of the parsers above accepts that file type, you can choose it yourself. Otherwise, ask us to add a parser for that format.

Uploading a file, step by step #

Drop one or more files onto the app to start. The Upload Queue then walks each file through the four steps below.

1. Uploading file #

From the home page: drag files anywhere onto the page (you'll see Drop files to upload).
From a canvas: use Upload Data Files at the bottom of the left sidebar, or drag files onto it. You can select several files at once.
A progress bar shows how much of each file has been sent. Uploads are private to your workspace.

2. Parsing file #

DataCNVS chooses a parser for you. This is shown as Automatic Parser Selection.
Want more control? Open the upload in the Upload Queue and choose Preselect parser before parsing starts, or Select alternate parser afterwards. Each parser has a short description of what it reads.
Advanced users can add optional parser instructions to fine-tune how a file is read.
When parsing finishes, the queue shows how many observations were created. An observation is one measurement or experiment from your file, with its own scalar values and data series.

3. Identifying variables #

DataCNVS suggests a variable and units for every column. Each suggestion is labeled Identified, Needs review or No match found, with a confidence score.
If a column shows No match found, choose Create variable from the dropdown to define one, then assign it a quantity kind (such as temperature or pressure) from the system list. New variables are shared across your team and can be managed under Settings.
DataCNVS remembers the mappings you confirm. A column it has seen before is suggested automatically on your next upload, so there's less for you to review each time.
A Data Preview of each series lets you check it looks right.
Here you can rename an observation, add notes, change a variable or its units, or uncheck rows you don't want imported.
If anything needs a decision, the upload is marked Action required. Choose Update unit mappings to confirm.

4. Storing #

Your values are converted to consistent units and saved. The upload is then marked Completed.
Your new datasets appear on the home page, ready to plot on any canvas.

Finished uploads can be tidied away with Archive. Choose Show Archived to see them again.

Units and conversion #

DataCNVS stores every value in one standard unit per variable, and still shows you the units from your original file. This means data from different instruments and labs can be compared and plotted together without manual conversion.

Your units are kept for display. If your file recorded temperature in °C, you'll still see °C by default.
Mixed sources line up. A file in °F and another in K can sit on the same axis, correctly converted.
Units are checked. When you enter a unit by hand, DataCNVS warns you if it's invalid or unusual for that variable, such as a length unit for a temperature.
You can change your mind. Updating a variable or unit after the upload finishes reconverts only the affected columns.

Using your data on a canvas #

Once an upload is Completed, its observations appear in your datasets list and can be added to any canvas. Plots read the stored values directly, so axes show the right units, and changing an axis unit converts the data for you. Your original file is never altered.

Troubleshooting and FAQ #

My upload shows “Processing error” #

Open it in the Upload Queue and choose Show details. You'll see which step failed and why. Common causes:

Parser selection failed. No parser recognized the file. If a parser accepts that file type, choose it with Select alternate parser, or request a new parser.
Parse failed. The parser couldn't read the file's layout. Try another parser, or add parser instructions.
Unit mapping failed. Some units couldn't be matched. Review the highlighted fields and choose Update unit mappings.

The data came out wrong. Can I try again? #

Yes. Choose Rerun parser, or pick a different parser. This replaces the observations from the earlier attempt, so you'll be asked to confirm first.

How long do you keep my original file? #

We keep the original file for 30 days after upload, so you can re-parse it during that time. Your processed data stays until you delete it.

Can I upload several files at once? #

Yes. Select or drop as many as you like. Each gets its own entry in the Upload Queue.

Something else isn't working #

Email support@datacnvs.com.

Need a format we don't support yet? #

If your instrument or software exports a format we don't read yet, tell us and we'll look at adding a parser. It helps if you include:

the instrument or software, and its version, that created the file
the file extension
a sample file, if you can share one

You can upload these files today. We keep the originals for 30 days, so if a new parser arrives in that time you can re-parse them without uploading again.

On this page