Has anyone noticed that cave lengths and depths reported by the textual (survey-list and cave-list) exports sometimes differ from the length and depth reported by the map (pdf) export, even when all these outputs are produced with the same thconfig run? I have tracked the one case I have noticed down to a particular survey (I think) that is being counted in the textual outputs but not in the map output (45m out of 11.5km). At least this explains the length discrepancy. Survey stations for the 'missing' survey are included in one of the scraps, and are plotted in the output, so I would think it's length should be counted. The depth discrepancy is more perplexing, because this particular survey is halfway between the top and bottom of the cave (in a side passage), and so of course should have no effect on the overall depth. It is possible that the length of the survey is co-incidentally the same as the discrepancy, and there is something else going on. If the cause is as I have described then it will probably have been present in this dataset for the last couple of years. I do recall being perplexed by differing figures in the distant past, but put it in the 'things to do' basket. Any ideas? Regards Bruce
On 07/09/10 10:38, Bruce wrote:
Has anyone noticed that cave lengths and depths reported by the textual (survey-list and cave-list) exports sometimes differ from the length and depth reported by the map (pdf) export, even when all these outputs are produced with the same thconfig run?
Yes, in the therion compiler window, I am getting length: 4156.16m (surface 0.00m, duplicated 477.89m) but the pdf is reporting 3744m For a minute I thought that I had been missunderstanding the duplicates but a quick check with one of my other surveys length: 212.77m (surface 0.00m, duplicated 433.72m) shows that duplicates have already been excluded, plus the numbers do not quite add up Andrew
Further to that on the same survey The sections length in the Config window are OldCave:398.47 2008:625.48 2009:1763.52 2010:956.68+171.84 Which gives 3915.99 but the total is given by the compiler as 4156.16 Now a little playing and 2008 is made from a survex 3d file that has more data in it than is used and actually has 865.63 which is 240.15 more than reported. Which when added to the 3915.99 gives 4156.16. So the root folder under survey structure seems to use the whole length of the 3d file the subfolders do not. And this is just a simple part of my survey, puts into doubt lots of my other length This leads me to the question, why cannot we just use the survex files as a centreline file between the centreline-endcentreline why not have centreline ... survexdata #survexformated data endsurvexdata This would allow lots easier management of the data, I would not have to work out which 3d files to update, which with the above seems to have become even more important, as I will have to remove any 3d data that is also in therion. I cannot just use the parts because I then get a cannot mix local and global co-ordinates error (which I am sure I can get round but feel in the long term converting my svx files to .th is the way forward) thanks Andrew On 13/09/10 14:02, Andrew Atkinson wrote:
On 07/09/10 10:38, Bruce wrote:
Has anyone noticed that cave lengths and depths reported by the textual (survey-list and cave-list) exports sometimes differ from the length and depth reported by the map (pdf) export, even when all these outputs are produced with the same thconfig run?
Yes, in the therion compiler window, I am getting
length: 4156.16m (surface 0.00m, duplicated 477.89m)
but the pdf is reporting 3744m
For a minute I thought that I had been missunderstanding the duplicates but a quick check with one of my other surveys
length: 212.77m (surface 0.00m, duplicated 433.72m)
shows that duplicates have already been excluded, plus the numbers do not quite add up
Andrew
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
On 07/09/10 10:38, Bruce wrote:
Has anyone noticed that cave lengths and depths reported by the textual (survey-list and cave-list) exports sometimes differ from the length and depth reported by the map (pdf) export, even when all these outputs are produced with the same thconfig run?
Further to my above post and Andrew Atkinsons recent posts... I do not have any Survex data, so cannot test that aspect, but I do have Survex installed, and I have investigated a little further using both loop closure types within Therion. As can be expected there is a slight difference between Therion loop closure and Survex loop closure in reported length, depth and range statistics, demonstrated in the attached file. These values are, as far as I can tell, exactly mimicked by the 'surveys' and 'caves' list outputs. So, the compiler reported values match the list outputs for my test case. (I presume the lists always report on the whole survey, not just the exported map -untested). The pdf plan and elevation outputs often report slightly different values to the list outputs(45m in length) in my test case. I have figured out that (logically enough) the figures reported in the pdfs reflect the map definitions that are exported. If you have a 100km survey, but export a map definition of a 50m portion, then you would only want the pdf to report 50m, and not 100km. Do you think this correct? My confusion arises when I think the maps I am exporting contain all of the surveyed passage, but the lengths reported are less than in the lists. (I tried commenting out all my select statements, expecting that all of the defined maps would be exported, but I was surprised to find this was not necessarily the case - but perhaps this is a yet another issue perhaps) Perhaps my 'length difference' issue is unrelated to what Andrew is experiencing or perhaps not? Bruce
(I presume the lists always report on the whole survey, not just the exported map -untested).
After some testing I conclude that the list exports DO report on the entire 'source' survey, regardless of the 'select'ed maps to be exported. Have not checked the numbers are added correctly however. (The numbers still differ between list and pdf). The map outputs, when NO 'map' is 'select'ed, correctly produce a pdf with each defined map on a separate layer when the projection is 'plan'. When the projection is 'elevation 290 deg' only one of the defined maps is exported (only about half of the cave in this case). This dataset works fine when maps are explicitly 'select'ed. Seems the default behaviour might be broken for elevations. Bruce
participants (2)
-
Andrew Atkinson -
Bruce