Validation Results


Sorry, your CSV did not pass validation. Please review the errors and warnings below:

Total Rows Processed = 10

Download Standardised CSV
3Errors 4Warnings 1Messages
Structure 2 2 1
Schema 0 0 0
Context 1 1 0

Your CSV file appears to only contain a single column. This may indicate that it is being incorrectly parsed. You can try resubmitting it using a different dialect.

3 Errors, 4 Warnings

Context problem: Incorrect content type

Your CSV file is being delivered with an incorrect Content-Type of text/html; charset=iso-8859-1.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8

Structural problem: Unexpected whitespace on row 1


Quoted columns in the CSV should not have any leading or trailing whitespace.
Remove any spaces, tabs or other whitespace from either side of the delimiters in the row.

Structural problem: Missing Columns on row 9

<p>Additionally, a 403 Forbidden

Row 9 contains a different number of columns to the first row in the CSV file.
This may indicate a problem with the data, e.g. an incorrectly escaped value, or that you are mixing together different tables of information.

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: Possible title row detected

Your CSV seems to contain unstructured text at the beginning of the file.
It is important that your CSV only contains structured data - any background information or metadata should be included on a referring web page or accompanying document.

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.

Context problem: Incorrect Encoding

Your CSV appears to be encoded in UTF-8. We recommend you use UTF-8.

Structural problem: Non-standard Line Breaks on row 1

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.

Next Steps

Publish and transform your data using DataGraft, either as enhanced CSV or Linked Data.