Basically this in CoordinateSystem.cpp in the Gocad Fileo section
richard = boost::algorith::trim(*it)
else if (richard == “END_ORIGINAL_COORDINATE_SYSTEM”)
{
std::cout << “testing END COORD”;
return true;
}
dataset from Windows machine originally most likely, and no trimming of that string in the code, so didn’t match the equality when just a single and only token.
Hi, thanks for further testing. I’m not sure I got you correctly, your suggestion is to trim the *it before testing against an expected/possible string?
Could you post (or send a private mail dmitri.naumov@ufz.de) the dataset where trimming is required? Or is it the same as above in the google-drive link? This would help to identify the parsing problems.
The one dataset we have for testing is this one: Top-Lower-Shaly.ts and there are no spaces (or similar) around the keywords…
For the windows, I could imagine that the different line ending then on linux hinders the parser.
– d
Yes, that was it - I can chase that up, pretty big so would have to upload - although public so can send you a link.