Inconsistent .csv Return Structure

[ARawles]

Not all .csv files are returned in the same format. Currently, the parser assumes that there the file still contains the annoying "//EOF" tag and starts with 4 lines of rubbish.

As someone has pointed out though, with data items like "B1610", the file is returned with a single line with the data item and then the data starting from line 2.

To compensate, the parser will require a more flexible structure.

[ARawles]

The development version (ceb3fc4) now has a slightly more flexible parser that will look for the EOF tag, but I still want to develop this a bit further.

[jimrothstein]

from @ARawles

2. This is a bit of a longer term change, but the return structure of the API keeps changing. For example, sometimes it's a CSV that has this really annoying "EOF" row that makes parsing it really difficult, othertimes that row isn't there and it can be parsed normally. Basically, I want to make the parser more flexible to be able to deal with those idiosyncracies easily. I'm not entirely sure what that's actually going to look like though.