Problems with the Tunnel Survex reader

From Fs_wiki

Jump to: navigation, search

Footleg

Tunnel did not handle my survex data files correctly when they contained plumbed legs expressed using +V and -V for the clino readings. The survey was split into seperate unconnected pieces which were placed some distance apart when I tried to import the centre line into a sketch. I was able to get around this by using UP and DOWN instead of +V and -V for the clino data.

These values can be seen in [1] and have now been implemented in the sourceforge version.
Survex can't handle unconnected pieces (it ignores all but the first one). Don't you need to use *fixes?
Footleg: I have a *fix on the entrance, and survex handled the entire survey fine with the +V and -V clino readings. I think Tunnel broke the survey into pieces because of a parsing problem, and so created unconnected pieces, only one of which contained a fixed point. When I replaced the +V with UP and -V with DOWN then Tunnel parsed the survey fine, and created one connected cave, fixed at the entrance.
Julian: So this is now fixed then, and it reads in your data?
Footleg: No, I still see my survey fragmented if it contains +V or -V. I can work around it by reformating my data to use UP and DOWN before openning the SVX file in Tunnel.
Julian: In LegLineFormat.java line 343 it should be: 
if (aclino.equalsIgnoreCase("up") || aclino.equalsIgnoreCase("u") || aclino.equalsIgnoreCase("+V"))  clino = 90.0F;

which should make them equivalent. If not, something odd is happening. 


Does this now work, if so move to fixed bugs section.
Footleg: No, I still see the problem. Try to create a new sketch using the file 'Cave.svx' which I emailed to you the other day. Import the centreline and you see the cave is split into more than one piece.
Retrieved from "-- /wiki/pages/Problems_with_the_Tunnel_Survex_reader"