I've attempted to write a parser but immediately hit a snag.
generates an input past end of file error. I believe this is because the file contains multiple lines and a non binary input doesn't like a read operation pulling in more characters than the line length, is that correct?
if I input as binary then I do not get the error but I am not sure how to recover the contents of the file at that point. I played with a simple binary to text converter but it seems to produce gibberish.
reminder of the scenario here - file is a normal CSV with multiple lines, but one field is hosting binary data (photometric information) which is known to contain carriage returns characters occasionally.
Sample file posted. Hoping someone can take a look at that file.
I do not believe that quote characters or commas appear in the photometric record but if they can that throws a bit of a wrench into this. This data seems to be fixed length (15210 characters) and the field is identified as "None#Other" so the parser could be coded to understand that when it gets to this field it should simply copy in those 15210 characters into the next record and move on.
I observe also that the number of records per line is determined by the first row so the carriage returns could be ignored completely by a parser armed with that information.
This photometric stuff does not exist in all files we are trying to process.
thank you for any advice.
Bookmarks