Custom Query (111 matches)

I don't know if the bug is caused by cavern, the Inkscape import filter for Survex 3d files, or Inkscape itself, but the angles are different in Inkscape than in the original .svx file. Example:

*data normal from to tape compass clino
1       2       3.75    209.4   -14.1
3       2       6.57    18.3    -3.3
3       4       3.45    292.4   6.5
3       5       2.97    225.6   10.5
5       6       1.79    111.9   3.4

In Inkscape, the angles are:

1-2 ... 209.45°
3-2 ... 18.21°
3-4 ... 292.45°
3-5 ... 225.69°
5-6 ... 111.98°

The error in 3-5 is noticeable.

I've been noticing these differences for many years and blamed them on some maximum resolution or snapping in Inkscape. But the lines can actually be manually drawn with the correct length and angle in Inkscape. So there must be a serious inaccuracy somewhere in the transformation process.

I've been able to convert the 3d file for hand plotting to get coordinates for particular stations, very useful for finding the cave end on the surface. This feature seems to have stopped working and keeps asking me to look for another program to process the data. Any ideas what I'm doing wrong or is the feature no longer available in Aven?

Hey!

I'm use a lot of Export function to get cave surveys positions and found out that JSON format exported by Survex isn't correct.

This is file exported as JSON from Survex:

var p = [0.00,0.00,0.00,10.00,10.00,10.00]
var groups = [
[[0.00,0.00,0.00],[0.00,0.00,10.00]],
[[0.00,0.00,0.00],[0.00,10.00,0.00]],
[[0.00,0.00,10.00],[10.00,0.00,10.00]],
[[10.00,0.00,10.00],[10.00,0.00,0.00]],
[[10.00,0.00,0.00],[0.00,0.00,0.00]],
[[10.00,10.00,0.00],[0.00,10.00,0.00]],
[[10.00,10.00,0.00],[10.00,0.00,0.00]],
[[10.00,10.00,10.00],[10.00,10.00,0.00]],
[[10.00,10.00,10.00],[10.00,0.00,10.00]],
[[0.00,10.00,10.00],[10.00,10.00,10.00]],
[[0.00,10.00,10.00],[0.00,0.00,10.00]],
[[0.00,10.00,0.00],[0.00,10.00,10.00]]
]}

You can use simple site checking format validation: ​https://jsonformatter.curiousconcept.com/#

Trying to parse that file as JSON without additional pre-processing will always fail.