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 the
attribute.
Another important feature for me is to configure the Topodroid type of
line: "SETTINGS/SKETCHING/LINES/Line Style: Bezier.
When I make "sketch" on Topodroid I already think about Therion
"scraps". I try to limit the length and prevent it from overlap itself,
doing several or as much sketch as needed by survey trip. Every
Topodroid Sketch is after a Therion Scrap. Topodroid export every
sketch/scrap in one .th2 file. For me it is a bit annoying not being
able to export several sketch/scraps in a single file, but I have
learned to live with it and remedy it in Therion.
After exporting to Therion the survey trip, I reorganize the data by
survey or centerlines, in the cave .th file.
I do all the editing processes in Therion (connect lines, check the
sense of the walls, etc), since it is faster. I do the editing in each
separate .th2 file generated by Topodroid.At this time I take the
opportunity to rename the scraps according to the nomenclature adopted
for the cave.
Normally afterwards I group the scraps in files according to the levels
or galleries of the cave. So it's much faster to make the joins. For
this I copy with a text editor all the scrap commands from the
individual file to the destination file. Then I open the destination
file and move all the built-in scrap to its proper position.
Another technique that I use sometimes surveying some gallery in several
survey trips, is to continue with the same session, without creating a
new session, but creating new sketches . So I can see the whole of the
topography in the screen with the option overview. I just have to write
down the date, team and start and end station, and then include it in
the new centerline of the .th file.
Well these some of my TOPODROID-THERION tricks that I now remember.
Last month I gave a 3 days survey course: Digital Survey 3.0; where I
explained all the workflow from the data collection with DistoX2, the
data transfer and drawing with Topodroid, and making the final product
in Therion.
Best regards,
Evaristo.
El 03/12/2018 a las 20:16, Bruce Mutton via Therion escribió:
Hi Marco
That is a good description. I can see a wiki page developing from it.
I don’t think I have seen similar information before?
It is a while since I played with TopoDROID. Is it the intention that
one TopoDROID sketch produces, or is equivalent to, one matching pair
of Therion scraps (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
always been guessing. Is it the survey shot line that goes from ‘from
station’ to ‘to station’?
Regards
Bruce
*From:*Therion *On Behalf Of *Marco Corvi
via Therion
*Sent:* Tuesday, 4 December 2018 03:41
*To:* therion@speleo.sk
*Cc:* Marco Corvi
*Subject:* [Therion] topodroid to therion
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 that is easy to implement and encourages a
naming convention that eases tracing of scraps to their parent
TopoDROID file. And breaking existing scraps into smaller scraps is a
task I find unnecessarily tedious, when one could just have drawn
smaller scraps in the first place.
Am I missing something obvious? What are experienced Therion users
who subsequently became proficient with TopoDROID as a data collector
doing in this space?
--
topodroid has many features requested by users that probably use other
programs than therion to draft their
cave maps,
anyways, i use therion for my cave maps, and here is what i do.
(0) a note3 with a stylus: reasonable compromise between the size of
the android and that of the caves (lucky surveyors might go for a 7"
tablet)
(1) enable only drawing tools that are supported by therion, otherwise
i must go for metapost code
(2) each topodroid survey can have many sketches, and i usually draw
several sketches, except for very simple surveys.
(3) switch off fractional 'extend"
(4) switch off loop closure compensation: better see potential blunders
(5) i usually use "normal" line style, and the decimation button to
simplify them (if need arises)
(6) pre-exporting: check every sketch with joining sketches using the
sketch outline feature, and make then fit nicely
