Custom Query (95 matches)

The idea is that the latest 1.0.x release can read files produced by the latest 1.1.x (and just ignore extra information), but that's not currently true.

This breaks interoperating, so we should try to fix it quickly.

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.

Jenny was unable to get terrain to load, instead just getting a grey disk at altitude 0. I've fixed the error checking for 1.2.20, so it now actually fails, but the inability to load terrain remains. My attempts to debug suggest that the wxZipInputStream class always fails to read anything, returning an unhelpful "generic read error".