Page 1 of 1

Therion Length Calculation Question

PostPosted: Dec 2, 2014 11:19 pm
by caver.adam
I'm working on getting data converted from topoDroid to Therion and ran into a problem when combining more than one survey on the same output map. The map is showing that the total length of the cave is the length of the first survey. Anyone encountered this before and know how to solve?

I can provide more info on request but here's the main code. I'm getting the distance for survey bbme1.th but nothing for the other.

.th file:
Code: Select all
survey BigBat -title "Big Bat Cave"

  input 2014_10_26_bbme1/bbme1.th
  input 2014_10_26_bbme1/bbme2.th
 
  equate M1.10@bbme1 M2.10@bbme2
 
endsurvey


.thcnfg file:
Code: Select all
encoding  utf-8
source bigbat.th

layout basics
  units imperial
  scale 1 50
endlayout

layout colors
  #color map-fg [98 87 40]
  #color map-bg [80 80 80]
  #debug station-names
  transparency on
  opacity 60
endlayout

export map -projection plan -o BigBat.pdf \
  -layout colors -layout basics

Re: Therion Length Calculation Question

PostPosted: Dec 12, 2014 1:03 am
by KeyserSoze
I thought there was something fishy going on with that last trip. The passage from the Junction Box to Room 1 has to be longer than 400 feet. It's more like 1200 feet.

Re: Therion Length Calculation Question

PostPosted: Dec 12, 2014 8:55 am
by caver.adam
Actually, that survey is all one sketch and one .th file. Our shot to shot distance was 455 feet. Centerline distance was 415 feet.

This is where I combine your survey and my survey.

Re: Therion Length Calculation Question

PostPosted: Dec 12, 2014 8:58 am
by caver.adam
On a side note - I was told that it's a 300 foot belly crawl. That would correspond with the survey. 300 feet of belly crawl and 100+ feet of walking.

Re: Therion Length Calculation Question

PostPosted: Jan 27, 2015 11:20 am
by caver.adam
Ok, I didn't find an official answer to my question, but I did find a work-around for anyone looking into the same issue.

Surveys are nested in Therion and it makes some interesting behavior. Avoid nested survey tags when possible.

My originals looked something like:

Old Main.th
Code: Select all
survey BigBat -title "Big Bat Cave"

  input 2014_10_26_bbme1/bbme1.th
  input 2014_10_26_bbme1/bbme2.th
 
  equate M1.10@bbme1 M2.10@bbme2
 
endsurvey


Old bbme1.th
Code: Select all
survey bbme1 -title "bbme1"

centerline
     .... data goes here ....
end centerline
 
endsurvey


I changed my input files so they did NOT have "survey" tags in them. I just commented them out with #survey and #endsurvey. Then my input files only go from centerline .... endcenterline. This created another problem where all of the points were nested inside my main file, so I had to update my equate function also.

The new code looked like:

New Main.th
Code: Select all
survey BigBat -title "Big Bat Cave"

  input 2014_10_26_bbme1/bbme1.th
  input 2014_10_26_bbme1/bbme2.th
 
  equate M1.10 M2.10
 
endsurvey


New bbme1.th
Code: Select all
#survey bbme1 -title "bbme1"

centerline
     .... data goes here ....
end centerline
 
#endsurvey

Re: Therion Length Calculation Question

PostPosted: Feb 5, 2015 3:49 pm
by Martin Sluka
Adam, may you send my your data if possible? mailto:martinsluka@mac.com
I'll check it, it is not normal behaviour.

m.s.

Re: Therion Length Calculation Question

PostPosted: Feb 5, 2015 9:38 pm
by caver.adam
Ok. I'll try to get it out Sunday if I can. Between business travel and grad school it will take me some time.

I'm much farther into my project now but I think it will all still make sense.

Re: Therion Length Calculation Question

PostPosted: Feb 6, 2015 3:40 am
by Martin Sluka
caver.adam wrote:I'm much farther into my project now but I think it will all still make sense.


I'm sorry if I'll write something which you know already. Survey on the lovest level is the basic structure unit of data in Therion. It could be something as log of one survey trip including surveying data. It usually include the definition of map of particular part of cave surveyed which is used as control when drawing particular scraps. Therion is able to generate map without a map definition, but in that case it looks for all available data in surveys structure and the result is sometimes unexpected. So very good rule is to define map(s) and "select" particular map in .thconfig file. Maps could be defined on base of surveys or on base of scraps.

Very important: Structure of maps is independent of structure of surveys!!! You may define as many different maps as you want and select relevant map in export definition (.thconfig file).

Surveys in higher levels usually define parts of cave, bigger unit of cave system, caves from an area, caves from a mountain, caves of a state, ....., caves on the Earth. :grin: In such case you should use the "path" in name of survey or scrap: xxx@aaa.bbb.ccc.ddd.eee Something as an email address.

But map may be defined by two (or several) scraps from different surveys or cave system if necessary too when you are looking for connection for example.

Re: Therion Length Calculation Question

PostPosted: Feb 6, 2015 9:15 am
by caver.adam
You may have described my problem. Sounds very likely. I won't be home for a couple days to try it.

Thanks!

Re: Therion Length Calculation Question

PostPosted: Apr 3, 2015 8:27 am
by caver.adam
That was what I needed! Seems to work now. Just took me a long time to have a morning to sit down and work on it.

The layout of the main.th

Code: Select all
encoding  utf-8
survey Main -title "My Survey"

  ####################################
  # Input centerline data
  ####################################
  input inputs/firstsurvey.th
  input inputs/secondsurvey.th

  ####################################
  # Connect centerlines
  # equate the new start to it's place.
  # All points in centerline must be
  # connected or ignored here.
  ####################################
  equate A_1@firstsurvey A_2@secondsurvey

endsurvey


Layout of firstsurvey.th

Code: Select all
encoding  utf-8
survey firstsurvey

#input the th2 sketches
input firstsurveyfirstsketch.th2
input firstsurveysecondsketch.th2

#add the th2 sketches for this survey to the map
map firstsurveymap
  firstsurvey_scrap1
  firstsurvey_scrap2
endmap

centerline
  date 2015.4.3
  team "Adam Sampson" notes

  declination -5.1 degrees
  units tape meters
  units compass degrees
  units clino degrees
 
  data normal  from  to  length  compass  clino
  # add prefixes to data points (my digital survey numbers from 0, 1, 2, etc.
  # I add a survey prefix here and in the .th2)
  station-names A_ []
  # Tie the Survey to a GPS point at the entrance.
  cs long-lat
  fix 0 -86:10.300 37:40.250 200
  station 0 "My Entrance" entrance
    0 1 10 315 -82.5 #numbers not included in this example
    #...
    8 9 4 340 -5.8

endcenterline

endsurvey