Re: [Therion] distance problem with disto
Marco Hope it is OK to re-post on the forum :) ...
-----Original Message----- From: marco corvi [mailto:marco.corvi@elsagdatamat.com] Sent: Thursday, 27 January 2011 1:19 a.m. To: Bruce Subject: distance problem with disto
hi bruce,
did you mean that the distance shown on the disto display was wrong ? Unsure, I presume the displayed distance matched the distance transmitted. I was driving the pda - I'll check with the distoX operator, as we did have a brief conversation along those lines when it happened.
and that the distance transmitted to pockettopo was wrong as well ? Yes, definitely the wrong distance - was not a units issue, as the next readings were OK (and if I understand correctly 'units' has no effect on the data transmitted- between them the devices can translate I think).
were all the "wrong" values exactly the same, or just similar ? As above, I don't know - I had assumed they would be 'identically incorrect'.
did it happen long ago, or recently ? Saturday 22 January 2011 NZ daylight time.
marco
hi bruce, i had a similar problem once, but it was in a pit with plenty of water, and on the spot i thought it was due to the water splashing around ...
were all the "wrong" values exactly the same, or just similar ? As above, I don't know - I had assumed they would be 'identically incorrect'.
did it happen long ago, or recently ? Saturday 22 January 2011 NZ daylight time.
so this is probably the last survey in the distox memory, and it is still there. just for curiosity (and record), could you dump it ? [can prepare for you a win32 app to do that] does pockettopo save to file the raw data exchanged with the distox ? marco
Marco
so this is probably the last survey in the distox memory, and it is still there.
Yes, it is the most recent survey. The errant measurements were transmitted to pockettopo and deleted on the spot before the survey could proceed (logically enough), so as far as I am aware there will be no electronic record they ever happened, unless the distoX or PockeTopo keeps something sneakily stored away... Directly after the trip we replaced the batteries, and recalibrated twice (the delta values were not that great, about 0.7 then 0.4 I think- both have been saved so I could look them up). The site had a few steel drums and pipes nearby.
just for curiosity (and record), could you dump it ? [can prepare for you a win32 app to do that]
If there is something remaining I could try to pull it out.
does pockettopo save to file the raw data exchanged with the distox ?
I'm not sure, on the face of it as a non-technical user I'd say no. Bruce
sorry to clog the list ...
If there is something remaining I could try to pull it out.
each calibration is about 100 shots (=200 data) the distox stores tha last 4095 data so your distox probably still has the two calibrations and the survey as well as less recent surveys. in this case looking at the distox would answer the two questions in my previous mail: - are the data "wrong" in the distox ? - are the "wrong" data the same or just similar ? as i said, just out of curiosity. marco
in this case looking at the distox would answer the two questions in my previous mail: - are the data "wrong" in the distox ? - are the "wrong" data the same or just similar ?
OK, send me the app and instructions and I'll try to extract the data. Bruce
Hi, I have a cave with a length from about 400m. It is shared into 8 separated *.th and *.th2 Files. All worked well, if I want to get a PDF-File with projection plan. But in the kml-File (made with: export map -fmt kml -projection plan -layout standard -output BTH-11-02-06_GS.kml) there are missing part 4 of the cave. Has anyone an Idea, where the problem could be? Many thanks Markus
I have had this problem before. I gave up using kml about a year ago as they seem to be far fussier than the pdf and lox, so I now grab the sat images and use them. I would guess that the missing parts are were therion has got the inside and outside confused. GMapCatcher works well for getting images, but you are breaking the T+Cs and copyright. ttp://code.google.com/p/gmapcatcher/ Generally I found it came from having the walls the wrong way round, tick should be on the air side. Also pillars (when in a single scrap, I believe) need to have -outline in option set. However, this is/was not always the case, the error of scraps overlapping themselves was a good indication of other places it went wrong, but these are often very difficult to solve, I still have many in my data sets. Andrew On 06/02/11 10:52, Markus Boldt wrote:
Hi, I have a cave with a length from about 400m. It is shared into 8 separated *.th and *.th2 Files. All worked well, if I want to get a PDF-File with projection plan. But in the kml-File (made with: export map -fmt kml -projection plan -layout standard -output BTH-11-02-06_GS.kml) there are missing part 4 of the cave.
Has anyone an Idea, where the problem could be?
Many thanks Markus
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
Hi Andrew, thank you very much for that ideas! As I have looked to the *.th2 File of that part from the cave I found a line which should be an arrow-line but it was a wall-line. That was the error. Now it works well. But why was there no error in the PDF-File? There all looks properly, of course the arrow was not present. Best Regards Markus -----Ursprüngliche Nachricht----- Von: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] Im Auftrag von Andrew Atkinson Gesendet: Sonntag, 6. Februar 2011 12:32 An: List for Therion users Betreff: Re: [Therion] Problem with kml-File for google Earth I have had this problem before. I gave up using kml about a year ago as they seem to be far fussier than the pdf and lox, so I now grab the sat images and use them. I would guess that the missing parts are were therion has got the inside and outside confused. GMapCatcher works well for getting images, but you are breaking the T+Cs and copyright. ttp://code.google.com/p/gmapcatcher/ Generally I found it came from having the walls the wrong way round, tick should be on the air side. Also pillars (when in a single scrap, I believe) need to have -outline in option set. However, this is/was not always the case, the error of scraps overlapping themselves was a good indication of other places it went wrong, but these are often very difficult to solve, I still have many in my data sets. Andrew On 06/02/11 10:52, Markus Boldt wrote:
Hi, I have a cave with a length from about 400m. It is shared into 8 separated *.th and *.th2 Files. All worked well, if I want to get a PDF-File with projection plan. But in the kml-File (made with: export map -fmt kml -projection plan -layout standard -output BTH-11-02-06_GS.kml) there are missing part 4 of the cave.
Has anyone an Idea, where the problem could be?
Many thanks Markus
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
On 6.2.2011, at 15:30, Markus Boldt wrote:
But why was there no error in the PDF-File? There all looks properly, of course the arrow was not present.
wall has special funktion in th2 files. It clip everything what is outside of passage (in bedrock). There are three -outline modes: out - which is standard, in - you use it in case of pillars in one scrap (bedrock is IN wall line) and none. Use none, if you need to draw a wall line but without any effect to clip and outline. But it must be - clip off to be visible if outside of passage. m.s.
On 6.2.2011, at 15:30, Markus Boldt wrote:
But why was there no error in the PDF-File? There all looks properly, of course the arrow was not present.
I have noticed that in the last couple of years the pdf outputs have become much more tolerant of minor inconsistencies in scrap files. Loch files to a lesser extent. Kml files are still quite fussy though. Like Andrew, I found that incorrect wall orientation causes them to be omitted (or 'inside out' around pillars. There are others that I have not solved yet... Bruce
participants (5)
-
Andrew Atkinson -
Bruce -
marco corvi -
Markus Boldt -
Martin Sluka