-
-
Notifications
You must be signed in to change notification settings - Fork 646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Import CSV files with Strings Containing Commas #509
Comments
Ok, I tried my best to address this special case with a custom SplitLine function. I think it should work now. About showing strings, this will be possible in the future. |
Strings added :) PJ_CSV-2021-09-06_01.21.55.mp4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(PlotJuggler 3.3.0 on Windows)
PlotJuggler is unable to import CSV files that contain text strings with commas (text strings are surrounded by quotes)
The import fails differently depending on if the strings containing commas is in the header or the following rows.
Header items that have comma-containing strings
Quotes are ignored and additional columns are assumed:
This type of heater formatting is used by some data acquisition equipment such as the Onset HOBO 4 Channel Thermocouple Logger, which will include information like the channel number, units or settings in addition to the label.
Data entries that have comma-containing strings
This will result in PlotJuggler giving an error that the number of entries in the data row is larger than expected from the header
One example of data that uses this formatting is from the online NOAA climate dataset, where the weather station name may contain a comma: https://www.ncdc.noaa.gov/cdo-web/search
Example data:
In this instance, the "NAME" data which contains a comma is not plottable and could be safely ignored. This does raise questions about support for string entries (if any is intended or would be supported) so that 1) string values could be viewed in the tree in the left hand column (would allow for viewing debug messages for example) and 2) string data could be preserved for csv export
Example file attached (note that some lines have blank entries for temperatures)
2703382.csv
The text was updated successfully, but these errors were encountered: