Hi Bruce and Marco,
I use a personal efficient workflow from Topodroid to Therion.
First I have unified symbols in Topodroid and Therion, so that the
symbols used in one are understood by the other. Both use semantic
symbology, so the graphic symbol in each does not matter, only
, but it is
scattered around, and interspersed with information that is not
particularly useful for Therion users.*
bruce, you are right. i misunderstood.
a therion wiki page, a sort of "howto use topodroid for therion", is
probably a good idea
*And little indication of what settings will make lif
Hi Marco
Ah, so midline = the set of legs = centreline!
>>That is a good description. I can see a wiki page developing from it. I
>>don’t think I have seen similar information before?
> that info is in the user manual, more or less
The meaning I meant to convey was; I don’t think I
format (and
a cache) to speed up opening (and saving) the sketches
I am interested in the data naming conventions you use, to facilitate the
tracing of parent and child object relationships (ie data files (TopoDROID
and Therion) through to survey and scrap, for example).
the survey name is the base
(plan and elevation)?
I am interested in the data naming conventions you use, to facilitate the
tracing of parent and child object relationships (ie data files (TopoDROID and
Therion) through to survey and scrap, for example).
And I should just check exactly what you mean by ‘mid-line’? I have
Is there a workflow that is easy to use with ‘TopoDROID to Therion’
process, that also allows more than one scrap per survey trip file? With
limited experimentation (and making assumption that TopoDROID ‘sketches’
might be approximately equivalent to Therion ‘scraps’), I have not yet
found a way
oDROID, as it appears Thorir’s
example was.
Is there a workflow that is easy to use with ‘TopoDROID to Therion’ process,
that also allows more than one scrap per survey trip file? With limited
experimentation (and making assumption that TopoDROID ‘sketches’ might be
approximately equi
