Structural problem: Invalid Encoding on row 1
Your CSV appears to be encoded in
UTF-8, but invalid characters were found.
This can often be caused by copying and pasting data from a different source.
Dialect: Non standard dialect
Although your CSV validates, to make it as easy as possible for your data to be reused, we recommend using commas as delimiters, double quotes to enclose fields, and autodetecting line endings.
Structural problem: Check CSV parsing options
Your CSV file appears to only contain a single column. This may indicate that it is being incorrectly parsed.
We recommend using commas as delimiters and escaping values in columns where necessary.
Structural problem: Non-standard Line Breaks on row 29
Your CSV appears to use
LF line-breaks. While this will be fine in most cases, RFC 4180 specifies that
CSV files should use
CR-LF (a carriage-return and line-feed pair, e.g.
\r\n). This may be labelled as "Windows line endings" on some systems.
Publish and transform your data using DataGraft, either as enhanced CSV or Linked Data.