Re: [Therion] Disconnected centrelines - Extended Elevation Control

2017-04-07 Thread Guy Demars via Therion
I had this problem for two pits not connected and i resolve it by using a 
surface suvey

Guy

De : Bruce Mutton via Therion
Envoyé le :samedi 8 avril 2017 00:52
À : 'List for Therion users'
Cc : Bruce Mutton
Objet :[Therion] Disconnected centrelines - Extended Elevation Control

I am braving the creation of some extended elevations of some main routes 
through a cave with a number of branches, loops, through trips and hopefully to 
include a nearby cave.
Looking at the attachment First-Sample… I have an extended elevation that 
traverses a number of centrelines, some in the direction of survey, some  
against the direction of survey and one loop, which itself traverses a couple 
of surveys.  It looks simple, but was a challenge, although it now looks how I 
want it to.

Along the way to building it, there were plenty of times when there were random 
offsets that I had no control over.  Although I have some insights as to why 
that might have been, and think I understand extend start, ignore, hide, there 
were plenty of times when it appeared that large offsets were occurring for no 
apparent reason.

Anyway, the attached First-Sample… looks as I want it.

Now I want to add another very short cave, which is connected by a long series 
of survey centrelines, although these centrelines are not to be part of this 
elevation, so are not included in the centreline maps  I have created.

See the attached 2caves-Sample…
The second cave, and small part of surface survey, should ideally be located 
just to the right of the main elevation, because that is where, in reality 
there is a small gap between them.  There is no survey of the gap of course – 
the survey goes around the long cave passages and surface to get there!  (And 
there are gps fixed stations as well, so the surveys could potentially be 
disconnected, but that might mess with the plan maps – as usual there is a bit 
of misclose!)

I have tried using a start statement for each, and a start statement for only 
one of them.  This has no effect, and even if it did, there is not much chance 
it would produce the result I wanted.

Is there a way to control the starting location of this second piece of 
(disconnected) centreline?

Bruce


___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


Re: [Therion] New version of Therion 5.4.0 available

2017-04-07 Thread Martin Budaj via Therion
Check https://github.com/therion/therion/blob/master/CHANGES

Martin

On Fri, Apr 7, 2017 at 5:39 AM, rowena_l--- via Therion
 wrote:
> Hi,
>
> Is there a summary of new features in the 5.4.0 release?
>
> thanks,
>
> Rowena
>
>
> - Original Message -
> From:
> "List for Therion users" 
>
> To:
> "List for Therion users" 
> Cc:
> "Martin Sluka" 
> Sent:
> Wed, 05 Apr 2017 21:22:44 +0200
> Subject:
> [Therion] New version of Therion 5.4.0 available
>
>
>
> On Github!
>
> No any 1th April!
>
> m.s.
>
>> 5. 4. 2017 v 20:02, Olly Betts via Therion :
>>
>> On Sun, Apr 02, 2017 at 11:49:54PM +0200, Benedikt Hallinger via Therion
>> wrote:
>>> The source giving causing it is:
 fix 1.0 x y z 0 0 0
>>>
>>> If i remove the standard-deviation zeros, cavern stops to complain.
>>>
>>> The reason was that the entrance location was measured by public service
>>> against official grid by theodolite and as such is "perfectly correct".
>>> How can i give this information? Am i forced to use some minimal positive
>>> fraction? (eg. "0.1"?)
>>
>> Just omit the SDs - that means it's an exact fix.
>>
>>> If yes, could this be an cavern bug?
>>
>> It's really a bug in the .svx file therion generates - it should omit
>> the zero SDs even if they're explicitly specified in the .th file, since
>> the documented syntax for an exact *FIX command is that you omit the SDs.
>>
>> Cheers,
>> Olly
>> ___
>> Therion mailing list
>> Therion@speleo.sk
>> https://mailman.speleo.sk/listinfo/therion
>
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion
>
>
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion
>
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


Re: [Therion] Linux and DistoX (Wookey)

2017-04-07 Thread Marco Corvi via Therion
So, thanks to me giving a competent person (who also doesn't own any
Windows or Android devices) a couple of distoX's that needed ...

At the moment this only works with python3 and distoX1, But Stuart
plans to use the topodroid codebase to work out the differences for the
X2 protocol (unless anyone has a doc for this already, or Marco can
tell him).


wookey,

i may be not precise because i do not have the docs at hand.

the distox2 protocol is backward compatible.

therefore, getting the calib raw data from the distox2 is the same as in
distox1, namely two data packets, one for G, one for M.

the commands to toggle calib mode on and off are the same, too.

the computation of the calib coeff has changed a bit with firmware 2.2 (or
2.3, don't remember well) beat added three non-linear coeffs, and these are
written after the other 24.
there is a catch: in the distox1 those mem are set at 0xff (ie -1), so
these three coeff are written with 0 getting to 0xff.
the non-linear calib should not be used for older firmwares.

i have not changed the linux code, and
i do not think to have the time to do that.
i also understand you may not want to use android, but you can use the
android code and turn it in C++
the computational methods are very much C like, and the helper classes are
just basic linalgebra.

if you or stuart have any question, send me email

marco
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


[Therion] Is it possible to use somehow rotated elevation data?

2017-04-07 Thread Nikita Kozlov via Therion
When preparing layout of raster map, we can use command *rotate*, for
example to save space
of minimal bounding box of resulted pdf map.

Is it possible to do same trick with elevation grid data?
For example, I have a mountain with the cave going through it.
Mountain goes from SW to NE.

Can I somehow define rotated by 45 degree coordinate system, to be
understood by therion,
generate elevation data from ASTER in that local rotated coordinate system,
and combine both cave, mount, texture to small, "minimal aligned bounding
box" .lox file?
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion