[Therion] Recovering data marked as sent from DistoX2

2016-03-25 Thread Wookey
+++ Marco Corvi [2016-03-23 12:52 +0100]:
> andrew,
> 
> topodroid has a function to read the distox2 memory (and optionally save it to
> a text file).
> it is slow, and it has no way to know where the most recent data are. may want
> to read it in small chunks.

And if you don't have an android device to hand you can get Marco's
Linux code (topolinux) to do this too. However it is not packaged (I
never finished that) and has various issues, so you can be pleased
that you don't need it.

(But I must finish that packaging (combined with Mateusz's dxtool)
sometime as getting data out of distoX on Linux remains painful)

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20160325/342e3b8b/attachment.sig>


[Therion] Survex Terrain model problem

2016-03-25 Thread Bruce Mutton


If you are modifying the therion .3d export then it would also be nice to have 
the loop closure error and date explored (or date surveyed) exported with both 
model and map exports. 
Bruce
Sent from my Samsung device, hence the typo's
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.speleo.sk/pipermail/therion/attachments/20160325/2c0393ce/attachment.html>


[Therion] Survex Terrain model problem

2016-03-25 Thread Olly Betts
On Thu, Mar 24, 2016 at 04:30:54PM +0200, Владимир Георгиев 
wrote:
> On Thu, Mar 24, 2016 at 3:50 PM, Olly Betts  wrote:
> > It should be fairly easy to update - just call img_open_write_cs()
> > instead of img_open_write() and pass in the PROJ4 projection string for
> > the output coordinate system as an extra parameter.
> 
> I didn't understand that part. What would be easy to update?

Therion's code should be fairly easy to update.

> Those two functions are part of the Survex source (img.c) from what I see.

Yes.  The second (relatively new) function needs to be used if you want
to specify the coordinate system, but therion probably uses the first
one (which has existed for a very long time).

So it's a matter of changing which function is called by therion, and
passing in the PROJ4 string describing the coordinate system to it.
Therion also uses PROJ4 so the appropriate string should be available.

Cheers,
Olly