Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

A very bad CSV, that validate can not map

See original GitHub issue

Overview

Hi, I have this csv that has a lot of errors.

But, if I run

frictionless validate --buffer-size 250000 --sample-size 750 _11012018072326.csv

I have only the error below, that blocks the real CSV validation check.

I have no info about the real source encoding, then I apply this solution: I run iconv -f utf-8 -t utf-8 -c input.csv >output.csv and then I use frictionless validate on the output.

I know, it’s not a real solution, but in this way I can map several useful CSV errors.

Is there a validate option, similar to the iconv one, to remove the unsupported character, and then to apply the validation to this cleaned input?

Thank you

===  =====  ==============  ============================================================================================================================
row  field  code            message
===  =====  ==============  ============================================================================================================================
            encoding-error  The data source could not be successfully decoded: 'utf-8' codec can't decode byte 0x8d in position 1447: invalid start byte
===  =====  ==============  ============================================================================================================================

Please preserve this line to notify @roll (lead of this repository)