Validation Results

5cb6f4bd64b83e00040000d6

http://opendata.npcs.cz/faktury.php?export=csv

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

Total Rows Processed = 1739

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

4 Errors, 2 Warnings

Context problem: Incorrect content type

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

Structural problem: Invalid Encoding on row 2

2

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.

Structural problem: Unexpected whitespace on row 14

190732;SML2018/259;"ICT_konektivita a LAN 6/2019";25302400;"GiTy, a.s.";14748;"16. 07. 2019"

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: Unexpected whitespace on row 104

190757;SML2018/366;190572;SML2018/259;"ICT_konektivita a LAN 5/2019";25302400;"GiTy, a.s.";14748;"07. 06. 2019"

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.

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.

Context problem: No encoding

The encoding of your CSV file is not being declared in the HTTP response.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8
If you are using a different encoding, then use an appropriate value for the charset parameter.

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.