![]() ![]() I spoke with our boat captains to clarify the Hypack issue with the LNN sequence. Thanks! I can force GM to parse it by removing the first row (containing LNS) but it breaks the format for Hypack. So the line names, LNS, don't correspond to their proper lines. Right now the parsing starts using LNS, which shifts all the ATTR values down one trackline. So, for GM to parse this correctly, I would expect ATTR_1 = LIN num of points, ATTR_2 = LNN name, ATTR_3 = EOL. After that are corresponding num of rows of shot points, PTS. LIN is followed by a value of the number of point records along the line ("shot points" they are sometimes called). LNS is a single occurrence in the file (LNS value = number of lines in file) and should be skipped. It looks like improper parsing of the file by starting with the first row of data (LNS). I'm currently using 12.02 The line names, contained in the string starting with LNN do not correspond to their proper lines. I noticed a quirk in loading in an LNW file this way (just now putting into workflow many months later!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |