Re: [Therion] Display Station comments on Map?

[Bruce Mutton]

Thanks Ben
Two new insights for me in your examples.  I create surface station maps with 
flags like in your examples, but have never thought to include a previewed cave 
map as well - obvious really!
And I had not appreciated how to use the -station option for scraps, much 
easier than drawing them all in the scrap!

Very timely for me, as I am just in the middle of an interesting surface 
feature - cave feature mapping exercise, and Google Earth does not provide the 
same level of refinement.

Bruce

-Original Message-
From: Therion  On Behalf Of Ben Cooper
Sent: Friday, 6 September 2019 03:52
To: 'List for Therion users' 
Subject: Re: [Therion] Display Station comments on Map?

Hi Max,
To your original question, I achieved something similar a while ago using 
station comments to create an overlay for fixed stations, and another for 
continuations.  The pdf outputs are attached.  While the programmatic selection 
of stations to display would be a nice to have, it is relatively painless to do 
what you want manually. These were achieved using a th2 file with a dedicated 
scrap, as you hinted at, however, I didn't need to plot all the stations - it 
is sufficient just to include the station names in the scrap -stations command, 
making this a very viable approach.

I've included the entire th2 file below - as you can see there is a long list 
of station names in the scrap command, and only three points actually plotted 
(I can't remember why these three were plotted manually, sorry. In the fixed 
stations list, I had to manually plot fixed stations that were created in the 
cave but not yet actually tied into to the survey line - my intention was that 
these would be surveyed eventually, at which point I would not have to manually 
draw them in). It wasn't very onerous generating the th2 file - I basically 
searched all my the files for the stations, manipulated the search output to 
create the list of station names, and then copied the list into my th2 file; 
job done.  In fact one could easily write a script that did all of that and 
just output the entire th2 file.

The full Therion survey with the metapost definitions of the station points 
that I used is available at 
http://cave-registry.org.uk/svn/CheddarCatchment/UpperFlood.  Start with the 
thconfig files called thconfig.UF_Fixed.tp and thconfig.UF_Continuations.tp 
respectively.  

Here's the th2 scrap:
scrap Continuations_s1 -projection plan -stations [M2d@MCGPaper.Entrance 
M11d@MCGPaper.Entrance 11d@MidnightChamber.Entrance BS10@MCGPaper.Entrance 
r4d@CC.GoldenChamber r14@CC.GoldenChamber 31d@BoulderChoke 34@Leg1.MalcolmsWay 
35@Leg1.MalcolmsWay 2@Leg2.MalcolmsWay MW55@MW.WalkThePlankChamber 
ws11@WallStreetCC.WallStreet 1.17@WallStreetDig.WallStreet 
1.0a@Disto.CharnelPassage 1.23@Disto.CharnelPassage 27@Pony.RoyalIcing 
1.2a@HiddenPassage.RoyalIcing 1.9@HiddenPassage.RoyalIcing 
10@EP_Pony.EastPassage 11@EP_Pony.EastPassage 22d@EP_Pony.EastPassage 
23@EP_Pony.EastPassage 32@EP_Pony.EastPassage 45@EP_Pony.EastPassage 
49@EP_Pony.EastPassage 51@EP_Pony.EastPassage 4b@DeepPoolTube.EastPassage 
14@DownUnder.EastPassage 21@BZA_Pony.BeyondZebraAven.EastPassage 
31@BZA_Pony.BeyondZebraAven.EastPassage 35@BZA_Pony.BeyondZebraAven.EastPassage 
45@BZA_Pony.BeyondZebraAven.EastPassage 49@BZA_Pony.BeyondZebraAven.EastPassage 
62@BZA_Pony.BeyondZebraAven.EastPassage 63@BZA_Pony.BeyondZebraAven.EastPassage 
66@BZA_Pony.BeyondZebraAven.EastPassage 67@BZA_Pony.BeyondZebraAven.EastPassage 
1.38@Disto.SouthPassage 1.40@Disto.SouthPassage 1.51@Disto.SouthPassage   
1.0@WPDisto.WestPassage 2.2d@WPDisto.WestPassage 2.5@WPDisto.WestPassage 
2.18@WPDisto.WestPassage F1@NeverlandCC.Neverland G1@NeverlandCC.Neverland 
H1@NeverlandCC.Neverland 3.35@NeverlandDisto.Neverland 
18@NeverlandRopeClimb.Neverland 33@NeverlandRopeClimb.Neverland 
47@NeverlandRopeClimb.Neverland] -scale [-128.0 -128.0 14706.8877 -128.0 0.0 
0.0 376.80614758 0.0 m]

point 2344.46 6494.81 station -name 46@NeverlandRopeClimb.Neverland

point 10441.94 4602.38 station -name 35@EP_Pony.EastPassage

point 4582.73 16269.96 station -name E0@MCGPaper.Entrance

endscrap

Best regards,
Ben


___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Extended profile problems

[Martin Sluka via Therion]

Hi Bill,

> 6. 9. 2019 v 17:41, Bill Gee :
> 
> Thanks!  This is much better, but still not what I want.  I don't want the 
> profile to fold back on itself at all.  I want one continuous profile 
> extending from OC5a on the left to G14 on the right.  Is that possible?

I’m not sure if this is possible without using another centreline file where 
the loop will be not closed. So for map you should have data with loops and for 
extended profile without loops. 

> If I draw them as "projection none", then two questions come up.  First, if I 
> put survey stations in the scrap will they be used to scale the drawing?  
> Second, can two (or more) such scraps be joined?

I don’t know this is possible. Projection none is for sections only.  

Martin___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Detecting errors

[MD]

On 6. Sep 2019, at 08:01, Ben Cooper  wrote:
> 
> In my experience poor calibration is usually down to either just inaccurate 
> calibration shots, or local magnetic anomalies: take off watch, step counter, 
> metal belt buckle, jewellery, glasses, helmet, lights, steel toe caps, etc!!

Took your advice to heart and calibrated without helmet. Much better!

Thanks!

—max
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Detecting errors

[MD]

On 6. Sep 2019, at 18:31, Wookey  wrote:
> 
> What SD numbers do you use for this?
> 
> I agree they should be different, but I've not seen much research
> evidence on what the correct numbers are.

Pre-Disto we used https://de.wikipedia.org/wiki/H%C3%A4ngezeug which should 
result in about the same SD as an Disto.

I toyed with taking the Callibration SD but I‘m not sure this makes sense. 

> Also SDs are about expected errors and do not cover blunder
> probability

I think this is an important point. They tend to mess up things much worse than 
anything else.

—max___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Detecting errors

[Wookey]

On 2019-08-15 11:50 +0200, Benedikt Hallinger wrote:
> To expand a little in this, you could also use the standard „grade“ to tell 
> theriob which centerline data has which quality. We use this to mark the 
> centerlines we have surveyed with distox and traditional way and therion uses 
> this to put more of the errors towards the more bad survey.

What SD numbers do you use for this?

I agree they should be different, but I've not seen much research
evidence on what the correct numbers are.

Also SDs are about expected errors and do not cover blunder
probability very usefully, which is also quite different for fully
digital and paper-based surveying as well as for compass/clino/tape vs
SAP or DistoX. You could adjust the SDs to allow for this, given that
we don't have a better mechanism, but again - how do we choose the
numbers?

I have asked this before and not had useful answers.

I have a re-survey project which has found a lot of errors in old
(both compass/clino and distoX surveys). I'm struggling to work out
what to do with the differences, but it's possible that some plausible
blunder probabilities could be generated if enough resurvey is
done. The main problem is that the resurvey is wrong too, just by a
different unknown amount, and could itself contain blunders.

In practice I found it really difficult to refind all the previous
stations so the resurveys are not mostly leg-for-leg, just connected
every so often.

None of that helps much with the fact that survex does its sums as if
there are only measurments errors, not blunders.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Extended profile problems

[Bill Gee]

Hi Martin -

Thanks!  This is much better, but still not what I want.  I don't want the 
profile to fold back on itself at all.  I want one continuous profile extending 
from OC5a on the left to G14 on the right.  Is that possible?

If I draw them as "projection none", then two questions come up.  First, if I 
put survey stations in the scrap will they be used to scale the drawing?  
Second, can two (or more) such scraps be joined?

-- 
Bill Gee



On Friday, September 6, 2019 10:26:52 AM CDT Martin Sluka via Therion wrote:
> Hi Bill,
> 
> it looks you have not defined „extend“ of centerline in your centerline data. 
> 
> Because extend right is default Therion will extend your stations form OC5a 
> to the right, but it has to close the loop and there should be the problem.
> 
> Your scrap extended Profile-OC5a-G10 includes stations OC5a to G10, stations 
> OC5a-G are extended to East but stations C9 and C10 are extended to West.
> 
> Try to divide that loop to two scraps from OC5a to G8 and G8 to G14 and add 
> extend commands. Not use join commands for first elevation export.
> 
>  extend right
> OC5a  G1 19.6   134 3.0314-3.0   1.0 9.8 18.7 3.5
>   G1G2 20.4   13329.0313   -28.0   3.0 6.6 17.3 4.2
>   G2G3 21.2   12513.0306   -13.0   2.3 3.0 9.3 6.4
>   G3G4 22.660 4.0239-5.0   6.2 2.0 4.8 2.4
>   G4G5  4.548   -10.022810.0   2.6 1.7 1.2 0.3
>   G5G6 12.3   10118.0281   -18.0   1.5 1.5 7.2 0.3
>   G6G7  9.0   127 7.0308-7.0   7.3 16.2 5.1 2.0
>   G7G8 10.944-8.0225 8.0   12.8 10.4 4.1 2.3
>   extend left
> G8G9  8.5   335   -15.015716.0   8.5 27.4 2.7 3.1
>   G9G1015.5   307-1.0128.5   1.0   3.4 3.9 0.7 0.8
>   G10   G1132.0   267-1.5 88.5   2.0   7.4 5.6 0.5 1.0
>   G11   G1221.8   262 0.0 81 0.0   1.7 4.8 1.5 1.4
>   G12   G13 5.7   246 6.0  --6.0   1.8 3.0 1.0 2.0
>   G13   G1413.9   236   -61.0 5762.0   - - - -
>   extend hide 
> G14   G1  5.9 -   -32.022032.0   - - - -
>   
> flags splay
>   G1G1a12.9   200-6.0  - 6.0   20.0 20.0 17.3 4.2
>   G7G7a18.4   24912.0  -   -12.0   10.4 12.8 4.1 2.3
> flags not splay
> 
> Add command select to your thconfig file
> 
> source StarkCaverns.th
> 
> select StarkCavernsProfiles@StarkCavernsProfiles
> 
> 
> # Load the Metapost code for custom symbols
> 
> and add to scrap  G10-G14 (G8-G14) parameter -flip horizontal, because in 
> output it should be flipped.
> 
> 




___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Extended profile problems

[Martin Sluka via Therion]

Hi Bill,

it looks you have not defined „extend“ of centerline in your centerline data. 

Because extend right is default Therion will extend your stations form OC5a to 
the right, but it has to close the loop and there should be the problem.

Your scrap extended Profile-OC5a-G10 includes stations OC5a to G10, stations 
OC5a-G are extended to East but stations C9 and C10 are extended to West.

Try to divide that loop to two scraps from OC5a to G8 and G8 to G14 and add 
extend commands. Not use join commands for first elevation export.

 extend right
OC5a  G1 19.6   134 3.0314-3.0   1.0 9.8 18.7 3.5
  G1G2 20.4   13329.0313   -28.0   3.0 6.6 17.3 4.2
  G2G3 21.2   12513.0306   -13.0   2.3 3.0 9.3 6.4
  G3G4 22.660 4.0239-5.0   6.2 2.0 4.8 2.4
  G4G5  4.548   -10.022810.0   2.6 1.7 1.2 0.3
  G5G6 12.3   10118.0281   -18.0   1.5 1.5 7.2 0.3
  G6G7  9.0   127 7.0308-7.0   7.3 16.2 5.1 2.0
  G7G8 10.944-8.0225 8.0   12.8 10.4 4.1 2.3
  extend left
G8G9  8.5   335   -15.015716.0   8.5 27.4 2.7 3.1
  G9G1015.5   307-1.0128.5   1.0   3.4 3.9 0.7 0.8
  G10   G1132.0   267-1.5 88.5   2.0   7.4 5.6 0.5 1.0
  G11   G1221.8   262 0.0 81 0.0   1.7 4.8 1.5 1.4
  G12   G13 5.7   246 6.0  --6.0   1.8 3.0 1.0 2.0
  G13   G1413.9   236   -61.0 5762.0   - - - -
  extend hide 
G14   G1  5.9 -   -32.022032.0   - - - -
  
flags splay
  G1G1a12.9   200-6.0  - 6.0   20.0 20.0 17.3 4.2
  G7G7a18.4   24912.0  -   -12.0   10.4 12.8 4.1 2.3
flags not splay

Add command select to your thconfig file

source StarkCaverns.th

select StarkCavernsProfiles@StarkCavernsProfiles


# Load the Metapost code for custom symbols

and add to scrap  G10-G14 (G8-G14) parameter -flip horizontal, because in 
output it should be flipped.



Martin



StarkCavernsElevations-G10-G14.pdf
Description: Adobe PDF document


StarkCavernsElevations-OC5a-G10.pdf
Description: Adobe PDF document

And after some editing:



StarkCavernsElevations-OC5a-G14.pdf
Description: Adobe PDF document




> 6. 9. 2019 v 16:09, Bill Gee :
> 
> Hi Martin -
> 
> This is a commercial cave - there are no secrets!  The attached ZIP file has 
> the thconfig, .th, .th2 and centerline data files for the whole project.
> 
> -- 
> Bill Gee
> 
> 
> 
> On Friday, September 6, 2019 8:50:38 AM CDT Martin Sluka via Therion wrote:
>> Bill, 
>> 
>> may you publish all your data? Or send it privately?
>> 
>> Martin
>> 
>>> 6. 9. 2019 v 15:47, Bill Gee :
>>> 
>>> Hello everyone -
>>> 
>>> I have not been putting elevation profiles on my maps for several years 
>>> because it is such a pain to do in Therion.  The time has come where I need 
>>> to start adding them to several maps in progress.  
>>> 
>>> In the past I have defined the profile scraps as type "elevation" and given 
>>> them a viewpoint angle.  The profile I am working on now will not work for 
>>> that because it basically goes around in a circle.  There is no viewpoint 
>>> angle where the entire profile lays out in a line.  The plan view is a loop.
>>> 
>>> So for this one I defined the scrap as type "extended".  Holy cow, that 
>>> makes a mess of things!  Take a look at the attached file.  This is so 
>>> distorted it is hard to figure out how it relates to the drawing!  The 
>>> stations in this profile go about 3/4 of the way around the circle.  The 
>>> upper half of the resulting map is upside down and magnified about 5 times 
>>> larger than it should be.
>>> 
>>> What am I missing???  Do I correctly understand that an "extended" scrap 
>>> should draw just the way it appears on the original sketch?  How should I 
>>> be drawing
>>> 
>>> Maybe I should completely skip using elevations.  I can probably make them 
>>> work by drawing as cross-sections.  Indeed, that might be easier to fit 
>>> onto the final map.  I think the only real problem there is whether 
>>> cross-section scraps can be joined.
>>> 
>> 
>> ___
>> Therion mailing list
>> Therion@speleo.sk
>> https://mailman.speleo.sk/listinfo/therion
>> 
> 
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion

___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Extended profile problems

[Philippe Vernant]

Hi Bill,

Not sure to understand what you are trying to do. Are you trying to make the 
full extended profile of the cave ? In which .th2 is your profile drawing ? 

Phil

> On 6 Sep 2019, at 16:09, Bill Gee  wrote:
> 
> Hi Martin -
> 
> This is a commercial cave - there are no secrets!  The attached ZIP file has 
> the thconfig, .th, .th2 and centerline data files for the whole project.
> 
> -- 
> Bill Gee
> 
> 
> 
> On Friday, September 6, 2019 8:50:38 AM CDT Martin Sluka via Therion wrote:
>> Bill, 
>> 
>> may you publish all your data? Or send it privately?
>> 
>> Martin
>> 
>>> 6. 9. 2019 v 15:47, Bill Gee :
>>> 
>>> Hello everyone -
>>> 
>>> I have not been putting elevation profiles on my maps for several years 
>>> because it is such a pain to do in Therion.  The time has come where I need 
>>> to start adding them to several maps in progress.  
>>> 
>>> In the past I have defined the profile scraps as type "elevation" and given 
>>> them a viewpoint angle.  The profile I am working on now will not work for 
>>> that because it basically goes around in a circle.  There is no viewpoint 
>>> angle where the entire profile lays out in a line.  The plan view is a loop.
>>> 
>>> So for this one I defined the scrap as type "extended".  Holy cow, that 
>>> makes a mess of things!  Take a look at the attached file.  This is so 
>>> distorted it is hard to figure out how it relates to the drawing!  The 
>>> stations in this profile go about 3/4 of the way around the circle.  The 
>>> upper half of the resulting map is upside down and magnified about 5 times 
>>> larger than it should be.
>>> 
>>> What am I missing???  Do I correctly understand that an "extended" scrap 
>>> should draw just the way it appears on the original sketch?  How should I 
>>> be drawing
>>> 
>>> Maybe I should completely skip using elevations.  I can probably make them 
>>> work by drawing as cross-sections.  Indeed, that might be easier to fit 
>>> onto the final map.  I think the only real problem there is whether 
>>> cross-section scraps can be joined.
>>> 
>> 
>> ___
>> Therion mailing list
>> Therion@speleo.sk
>> https://mailman.speleo.sk/listinfo/therion
>> 
> 
> ___
> Therion mailing list
> Therion@speleo.sk 
> https://mailman.speleo.sk/listinfo/therion 
> 
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Extended profile problems

[Bill Gee]

Hi Martin -

This is a commercial cave - there are no secrets!  The attached ZIP file has 
the thconfig, .th, .th2 and centerline data files for the whole project.

-- 
Bill Gee



On Friday, September 6, 2019 8:50:38 AM CDT Martin Sluka via Therion wrote:
> Bill, 
> 
> may you publish all your data? Or send it privately?
> 
> Martin
> 
> > 6. 9. 2019 v 15:47, Bill Gee :
> > 
> > Hello everyone -
> > 
> > I have not been putting elevation profiles on my maps for several years 
> > because it is such a pain to do in Therion.  The time has come where I need 
> > to start adding them to several maps in progress.  
> > 
> > In the past I have defined the profile scraps as type "elevation" and given 
> > them a viewpoint angle.  The profile I am working on now will not work for 
> > that because it basically goes around in a circle.  There is no viewpoint 
> > angle where the entire profile lays out in a line.  The plan view is a loop.
> > 
> > So for this one I defined the scrap as type "extended".  Holy cow, that 
> > makes a mess of things!  Take a look at the attached file.  This is so 
> > distorted it is hard to figure out how it relates to the drawing!  The 
> > stations in this profile go about 3/4 of the way around the circle.  The 
> > upper half of the resulting map is upside down and magnified about 5 times 
> > larger than it should be.
> > 
> > What am I missing???  Do I correctly understand that an "extended" scrap 
> > should draw just the way it appears on the original sketch?  How should I 
> > be drawing
> > 
> > Maybe I should completely skip using elevations.  I can probably make them 
> > work by drawing as cross-sections.  Indeed, that might be easier to fit 
> > onto the final map.  I think the only real problem there is whether 
> > cross-section scraps can be joined.
> > 
> 
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion
> 

<>
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Extended profile problems

[Martin Sluka via Therion]

Bill, 

may you publish all your data? Or send it privately?

Martin

> 6. 9. 2019 v 15:47, Bill Gee :
> 
> Hello everyone -
> 
> I have not been putting elevation profiles on my maps for several years 
> because it is such a pain to do in Therion.  The time has come where I need 
> to start adding them to several maps in progress.  
> 
> In the past I have defined the profile scraps as type "elevation" and given 
> them a viewpoint angle.  The profile I am working on now will not work for 
> that because it basically goes around in a circle.  There is no viewpoint 
> angle where the entire profile lays out in a line.  The plan view is a loop.
> 
> So for this one I defined the scrap as type "extended".  Holy cow, that makes 
> a mess of things!  Take a look at the attached file.  This is so distorted it 
> is hard to figure out how it relates to the drawing!  The stations in this 
> profile go about 3/4 of the way around the circle.  The upper half of the 
> resulting map is upside down and magnified about 5 times larger than it 
> should be.
> 
> What am I missing???  Do I correctly understand that an "extended" scrap 
> should draw just the way it appears on the original sketch?  How should I be 
> drawing
> 
> Maybe I should completely skip using elevations.  I can probably make them 
> work by drawing as cross-sections.  Indeed, that might be easier to fit onto 
> the final map.  I think the only real problem there is whether cross-section 
> scraps can be joined.
> 
> -- 
> Bill Gee
> 
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion

___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

[Therion] Extended profile problems

[Bill Gee]

Hello everyone -

I have not been putting elevation profiles on my maps for several years because 
it is such a pain to do in Therion.  The time has come where I need to start 
adding them to several maps in progress.  

In the past I have defined the profile scraps as type "elevation" and given 
them a viewpoint angle.  The profile I am working on now will not work for that 
because it basically goes around in a circle.  There is no viewpoint angle 
where the entire profile lays out in a line.  The plan view is a loop.

So for this one I defined the scrap as type "extended".  Holy cow, that makes a 
mess of things!  Take a look at the attached file.  This is so distorted it is 
hard to figure out how it relates to the drawing!  The stations in this profile 
go about 3/4 of the way around the circle.  The upper half of the resulting map 
is upside down and magnified about 5 times larger than it should be.

What am I missing???  Do I correctly understand that an "extended" scrap should 
draw just the way it appears on the original sketch?  How should I be drawing

Maybe I should completely skip using elevations.  I can probably make them work 
by drawing as cross-sections.  Indeed, that might be easier to fit onto the 
final map.  I think the only real problem there is whether cross-section scraps 
can be joined.

-- 
Bill Gee



StarkCavernsElevations.pdf
Description: Adobe PDF document
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Detecting errors

[Martin Sluka via Therion]

You are the wizard, but for as normal people the physical laws are valid. ;)

Martin

Odesláno z iPhonu

6. 9. 2019 v 10:39, Pavel Herich :

> Martin,
> I´ve never used this back extention, but before every "topo day" I use to 
> calibrate DistoX, which brings me errors under 0,5 % permanetly, very rarely 
> between 0,5 - 1 %.
> Pavel
> 
> 
> Dňa 2019-09-06 10:00 Martin Sluka via Therion napísal(a):
>>> 5. 9. 2019 v 13:10, Max D :
>>> So I know that if the display is to the right the Disto tends to
>>> reassure an Azimuth 2 degrees to high and if the display is to the
>>> left.
>>> And when the display is to the left it tends to give an Azimuth 1
>>> degree to low.
>> The main source of error could be misaligned back side of Disto with
>> station point especially together with short distance to measured
>> station. There is a way to reduce this error to minimum when the back
>> extension aligned with laser beam of the Disto is used.
>> Martin
>> ___
>> Therion mailing list
>> Therion@speleo.sk
>> https://mailman.speleo.sk/listinfo/therion
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion

___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Detecting errors

[Pavel Herich]

Martin,
I´ve never used this back extention, but before every "topo day" I use 
to calibrate DistoX, which brings me errors under 0,5 % permanetly, very 
rarely between 0,5 - 1 %.

Pavel


Dňa 2019-09-06 10:00 Martin Sluka via Therion napísal(a):

5. 9. 2019 v 13:10, Max D :

So I know that if the display is to the right the Disto tends to
reassure an Azimuth 2 degrees to high and if the display is to the
left.
And when the display is to the left it tends to give an Azimuth 1
degree to low.


The main source of error could be misaligned back side of Disto with
station point especially together with short distance to measured
station. There is a way to reduce this error to minimum when the back
extension aligned with laser beam of the Disto is used.

Martin
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion

Re: [Therion] Detecting errors

[Markus Boldt]

Hi Martin,

in Ebensee I have asked you, if this part is buyable. Is it? And when where.


Best regards

Markus



Von: Therion [mailto:therion-boun...@speleo.sk] Im Auftrag von Martin Sluka
via Therion
Gesendet: Freitag, 6. September 2019 10:00
An: List for Therion users
Cc: Martin Sluka
Betreff: Re: [Therion] Detecting errors





5. 9. 2019 v 13:10, Max D :



So I know that if the display is to the right the Disto tends to reassure an
Azimuth 2 degrees to high and if the display is to the left.

And when the display is to the left it tends to give an Azimuth 1 degree to
low.





The main source of error could be misaligned back side of Disto with station
point especially together with short distance to measured station. There is
a way to reduce this error to minimum when the back extension aligned with
laser beam of the Disto is used.



Martin





___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion