Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Tarquin Wilton-Jones via Therion
> Theodolites are not really set up for doing traverses, for a loop of a few 
> hundred metres we have an mis-closure of about 1m. I would be disappointed if 
> I was using a disto X. It seems to be par for the course. The show cave 
> owners paid for a traverse when they where tunnelling. They claimed 
> millimetre accuracy however were metres out. Lead to a bit of an arguement 
> between the caver surveyors and the paid surveyors about Which direction to 
> dig the tunnel. It was resolved when the tunnel broke through. Luckily the 
> tunnelers listen to the cavers. 

Well, that saves me buying one (as if I could afford one). I was
expecting them to be super-accurate, if calibrated properly. I'm
assuming this is not a calibration issue though. Theodolite grades were
always given as being so much higher than regular surveys, so this is
quite eye-opening.

Presumably the existing "theodolite" mode you were referring to in
Survex/Therion is designed for use with separate positioning and
levelling, since levelling gives extremely high accuracy vertical
position, so all you need then is the horizontal. (This is similar to
how OS land surveys were traditionally done, with the horizontal and
vertical surveys being almost entirely unrelated, and only tied in a few
places for convenience.)

I will add a note that yes, out-of-range crazy numbers is actually
normal with theodolite-style devices. Not just for inclination.
Certainly there are some other surveys done with thodolites (both
professional and home-made) where the compass bearing is over 360, with
full wrap-around.

One other things I just learned from this thread;
degrees:minutes:seconds is a supported format. Cute. Useful for optical
theodolites which are actually accurate enough to measure in such tiny
increments. Never seen it in a cave survey before.
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion


Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Andrew Atkinson


On 14 December 2020 20:03:00 GMT, Martin Budaj  wrote:
>On Mon, Dec 14, 2020 at 8:51 PM Andrew 
>
>
>Check https://www.gnu.org/software/gama/
>
>BTW, how did you get the azimuth (compass column in the data you sent)
>from
>the theodolite data?
>
We set up a leg some distance outside the cave using gps. Then every time the 
target is swapped with the main unit, you have to align it with the back leg. 
It is a tedious process, but  lets splays be recorded easily.
The paid surveyors tried triangulation down the tunnel, but there is not really 
enough room, further round the loop it gets to one person wide with metal 
everywhere.

In places where we haven't been able to get GPS we have used a distox to set up 
the leg

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


Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Martin Budaj
On Mon, Dec 14, 2020 at 8:51 PM Andrew Atkinson  wrote:

> Those fixed positions would need to be calculated, by something. Errors do
> occur which are better distributed about the loops. Most none surveying
> software doesn't really do this.


Check https://www.gnu.org/software/gama/

BTW, how did you get the azimuth (compass column in the data you sent) from
the theodolite data?

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


Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Andrew Atkinson
Thanks, will do as soon as I can.

Wasn't expecting ting such s fast response so converted the data, which, it 
turns out is not simple

Andrew

On 14 December 2020 18:09:30 GMT, Stacho Mudrak  wrote:
>Hello,
>
>could you please try the latest commit? I do not think that even a
>warning
>for 270 (=-90) to 360 (=level) degrees clino is necessary. An error can
>occur if you manually type a comma in the wrong place, but the same may
>happen with compass & tape and there is no warning.
>
>S.
>
>On Mon, 14 Dec 2020 at 09:43, Andrew Atkinson 
>wrote:
>
>> We have now used 3 different 'Total stations' all by different
>> manufacturers
>>
>> All seem to give a choice between
>>
>> 270 as down 0 as level and 90 as up
>>
>> or
>>
>> 0 as down 90 as level and 180 as up
>>
>> None of them have given the choice for negative clino (all the
>machines
>> we have use are old, but digital.
>>
>> So it does seem normal for theodolites!
>>
>> With hindsight I should have chosen the latter,then I could have just
>> calibrated with a calibrate clino 90
>>
>> But it was difficult to get your head round, plus I was using
>pockettopo
>> (and sexytopo) to draw the survey in the cave, so it was easier to
>use
>> the 270 as down version
>>
>> It would be really useful to be able in a centreline-endcentreline
>nest
>> to be able to suppress the out of range error and use the 270 to 360
>> readings, but still have the error/warning for the more normal
>surveys
>>
>> thanks
>>
>> Andrew
>>
>> On 14/12/2020 08:24, Martin Sluka via Therion wrote:
>> > Are you sure those data are “normal”?
>> >
>> > Martin
>> >
>> > Odesláno z iPhonu
>> >
>> > 14. 12. 2020 v 1:10, alastair gott :
>> >
>> >> Hi Andrew, if you can get deg,mins,secs to work in survex then you
>can
>> use the .3d file with the surveys use command. (But I think from your
>> careful wording, you already know this).
>> >>
>> >> import use.3d -surveys use
>> >>
>> >> Not ideal afaik for “mixing local and global coordinates” so
>tricky if
>> your going for a kml output if you have to use with mixed .3d and
>normal
>> .th files.
>> >>
>> >> It would be good if you could select a lookup file for the Clino,
>then
>> you could easily create a translation file in excel and save that as
>a .th
>> for your total station .th file to lookup to. But no idea if this is
>> feasible or even an idea at all.
>> >>
>> >> Al.
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 13 Dec 2020, at 18:15, Andrew Atkinson 
>wrote:
>> >>>
>> >>> Hello
>> >>>
>> >>> I thought that there was a way I could stop the out of range
>error, but
>> >>> I cannot now find it. It would be an a useful command to have as
>> instead
>> >>> of negative readings we got readings between 270 and 359, which
>> although
>> >>> strange is valid. In survex readings over 90 are just a warning,
>which
>> >>> seems far more sensible, the problem is that I don't think that I
>can
>> >>> enter the data in survex either without conversion as I don't
>think
>> that
>> >>> degrees minutes and seconds can be entered.
>> >>>
>> >>> So I'm stuck with data that I have to convert, for different
>reasons
>> >>> depending on whether I use survex of therion.
>> >>>
>> >>> Here is part of the file, I have quiet a few
>> >>>
>> >>> survey
>> >>>
>> >>> centreline
>> >>> data normal from to clino compass tape ignoreall
>> >>> 121:08:2583:37:4017.88
>> >>> 2300:00:00-:-:-0.055
>> >>> 3-02:39:00266:49:003.206
>> >>> 3-314:28:20299:57:452.02
>> >>> 3-16:32:25312:13:201.246
>> >>> 3-06:22:3584:16:101.17
>> >>> 3-309:16:4584:15:501.846
>> >>> 3-55:00:10122:44:500.77
>> >>> 3-325:02:55249:55:451.014
>> >>> 35359:30:50338:07:2516.674
>> >>> 5-306:52:00262:23:201.402
>> >>> 5-59:29:30343:51:301.076
>> >>> 5-305:08:25358:34:301.274
>> >>> 5-315:26:2090:51:351.632
>> >>> 5-29:12:4577:01:351.891
>> >>> 5-19:55:5033:02:003.071
>> >>> 5-348:22:3531:08:253.707
>> >>> 5-350:35:2015:31:254.292
>> >>> 5-13:29:3515:31:204.202
>> >>> 5-12:24:5030:20:207.919
>> >>> 5617:29:0531:28:506.444
>> >>> 6-307:24:35149:47:351.738
>> >>> 6-344:44:40149:45:301.426
>> >>> 6-77:05:35149:36:051.523
>> >>> 6-306:05:00314:12:100.84
>> >>> 6-353:47:5094:54:352.091
>> >>> 6-00:42:00219:31:405.446
>> >>> 6-18:33:50230:03:054.468
>> >>> 6712:26:05241:13:004.272
>> >>>
>> >>> .etc
>> >>>
>> >>> Anyone got a solution that does not mean I have to convert in a
>> spreadsheet?
>> >>>
>> >>> thanks
>> >>>
>> >>> Andrew
>> >>> ___
>> >>> Therion mailing list
>> >>> Therion@speleo.sk
>> >>>
>>

Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Andrew Atkinson
Those fixed positions would need to be calculated, by something. Errors do 
occur which are better distributed about the loops. Most none surveying 
software doesn't really do this. There is a data type that is for theodolite, 
however it is for a data type where all distances are horizontal, which appears 
to be for really old theodolites.

Theodolites are not really set up for doing traverses, for a loop of a few 
hundred metres we have an mis-closure of about 1m. I would be disappointed if I 
was using a disto X. It seems to be par for the course. The show cave owners 
paid for a traverse when they where tunnelling. They claimed millimetre 
accuracy however were metres out. Lead to a bit of an arguement between the 
caver surveyors and the paid surveyors about Which direction to dig the tunnel. 
It was resolved when the tunnel broke through. Luckily the tunnelers listen to 
the cavers. 

Andrew

On 14 December 2020 18:47:11 GMT, Martin Sluka via Therion  
wrote:
>Nor Survex, nor Therion support theodolite, as I know. Isn’t better to
>input such measurements as fix points?
>
>Martin
>
>Odesláno z iPhonu
>
>14. 12. 2020 v 19:09, Stacho Mudrak :
>
>> Hello,
>> 
>> could you please try the latest commit? I do not think that even a
>warning for 270 (=-90) to 360 (=level) degrees clino is necessary. An
>error can occur if you manually type a comma in the wrong place, but
>the same may happen with compass & tape and there is no warning.
>> 
>> S.
>> 
>>> On Mon, 14 Dec 2020 at 09:43, Andrew Atkinson 
>wrote:
>>> We have now used 3 different 'Total stations' all by different
>manufacturers
>>> 
>>> All seem to give a choice between
>>> 
>>> 270 as down 0 as level and 90 as up
>>> 
>>> or
>>> 
>>> 0 as down 90 as level and 180 as up
>>> 
>>> None of them have given the choice for negative clino (all the
>machines
>>> we have use are old, but digital.
>>> 
>>> So it does seem normal for theodolites!
>>> 
>>> With hindsight I should have chosen the latter,then I could have
>just
>>> calibrated with a calibrate clino 90
>>> 
>>> But it was difficult to get your head round, plus I was using
>pockettopo
>>> (and sexytopo) to draw the survey in the cave, so it was easier to
>use
>>> the 270 as down version
>>> 
>>> It would be really useful to be able in a centreline-endcentreline
>nest
>>> to be able to suppress the out of range error and use the 270 to 360
>>> readings, but still have the error/warning for the more normal
>surveys
>>> 
>>> thanks
>>> 
>>> Andrew
>>> 
>>> On 14/12/2020 08:24, Martin Sluka via Therion wrote:
>>> > Are you sure those data are “normal”?
>>> > 
>>> > Martin
>>> > 
>>> > Odesláno z iPhonu
>>> > 
>>> > 14. 12. 2020 v 1:10, alastair gott :
>>> > 
>>> >> Hi Andrew, if you can get deg,mins,secs to work in survex then
>you can use the .3d file with the surveys use command. (But I think
>from your careful wording, you already know this).
>>> >>
>>> >> import use.3d -surveys use
>>> >>
>>> >> Not ideal afaik for “mixing local and global coordinates” so
>tricky if your going for a kml output if you have to use with mixed .3d
>and normal .th files.
>>> >>
>>> >> It would be good if you could select a lookup file for the Clino,
>then you could easily create a translation file in excel and save that
>as a .th for your total station .th file to lookup to. But no idea if
>this is feasible or even an idea at all.
>>> >>
>>> >> Al.
>>> >>
>>> >> Sent from my iPhone
>>> >>
>>> >>> On 13 Dec 2020, at 18:15, Andrew Atkinson 
>wrote:
>>> >>>
>>> >>> Hello
>>> >>>
>>> >>> I thought that there was a way I could stop the out of range
>error, but
>>> >>> I cannot now find it. It would be an a useful command to have as
>instead
>>> >>> of negative readings we got readings between 270 and 359, which
>although
>>> >>> strange is valid. In survex readings over 90 are just a warning,
>which
>>> >>> seems far more sensible, the problem is that I don't think that
>I can
>>> >>> enter the data in survex either without conversion as I don't
>think that
>>> >>> degrees minutes and seconds can be entered.
>>> >>>
>>> >>> So I'm stuck with data that I have to convert, for different
>reasons
>>> >>> depending on whether I use survex of therion.
>>> >>>
>>> >>> Here is part of the file, I have quiet a few
>>> >>>
>>> >>> survey
>>> >>>
>>> >>> centreline
>>> >>> data normal from to clino compass tape ignoreall
>>> >>> 121:08:2583:37:4017.88
>>> >>> 2300:00:00-:-:-0.055
>>> >>> 3-02:39:00266:49:003.206
>>> >>> 3-314:28:20299:57:452.02
>>> >>> 3-16:32:25312:13:201.246
>>> >>> 3-06:22:3584:16:101.17
>>> >>> 3-309:16:4584:15:501.846
>>> >>> 3-55:00:10122:44:500.77
>>> >>> 3-325:02:55249:55:451.014
>>> >>> 35359:30:50338:07:2516.674
>>> >>> 5-306:52:00262:23:201.402
>>> >>> 5-59:29:30343:51:301.076
>>> >>> 5-305:08:25358:34:30  

Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Martin Sluka via Therion
Nor Survex, nor Therion support theodolite, as I know. Isn’t better to input 
such measurements as fix points?

Martin

Odesláno z iPhonu

14. 12. 2020 v 19:09, Stacho Mudrak :

> Hello,
> 
> could you please try the latest commit? I do not think that even a warning 
> for 270 (=-90) to 360 (=level) degrees clino is necessary. An error can occur 
> if you manually type a comma in the wrong place, but the same may happen with 
> compass & tape and there is no warning.
> 
> S.
> 
>> On Mon, 14 Dec 2020 at 09:43, Andrew Atkinson  wrote:
>> We have now used 3 different 'Total stations' all by different manufacturers
>> 
>> All seem to give a choice between
>> 
>> 270 as down 0 as level and 90 as up
>> 
>> or
>> 
>> 0 as down 90 as level and 180 as up
>> 
>> None of them have given the choice for negative clino (all the machines
>> we have use are old, but digital.
>> 
>> So it does seem normal for theodolites!
>> 
>> With hindsight I should have chosen the latter,then I could have just
>> calibrated with a calibrate clino 90
>> 
>> But it was difficult to get your head round, plus I was using pockettopo
>> (and sexytopo) to draw the survey in the cave, so it was easier to use
>> the 270 as down version
>> 
>> It would be really useful to be able in a centreline-endcentreline nest
>> to be able to suppress the out of range error and use the 270 to 360
>> readings, but still have the error/warning for the more normal surveys
>> 
>> thanks
>> 
>> Andrew
>> 
>> On 14/12/2020 08:24, Martin Sluka via Therion wrote:
>> > Are you sure those data are “normal”?
>> > 
>> > Martin
>> > 
>> > Odesláno z iPhonu
>> > 
>> > 14. 12. 2020 v 1:10, alastair gott :
>> > 
>> >> Hi Andrew, if you can get deg,mins,secs to work in survex then you can 
>> >> use the .3d file with the surveys use command. (But I think from your 
>> >> careful wording, you already know this).
>> >>
>> >> import use.3d -surveys use
>> >>
>> >> Not ideal afaik for “mixing local and global coordinates” so tricky if 
>> >> your going for a kml output if you have to use with mixed .3d and normal 
>> >> .th files.
>> >>
>> >> It would be good if you could select a lookup file for the Clino, then 
>> >> you could easily create a translation file in excel and save that as a 
>> >> .th for your total station .th file to lookup to. But no idea if this is 
>> >> feasible or even an idea at all.
>> >>
>> >> Al.
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 13 Dec 2020, at 18:15, Andrew Atkinson  wrote:
>> >>>
>> >>> Hello
>> >>>
>> >>> I thought that there was a way I could stop the out of range error, but
>> >>> I cannot now find it. It would be an a useful command to have as instead
>> >>> of negative readings we got readings between 270 and 359, which although
>> >>> strange is valid. In survex readings over 90 are just a warning, which
>> >>> seems far more sensible, the problem is that I don't think that I can
>> >>> enter the data in survex either without conversion as I don't think that
>> >>> degrees minutes and seconds can be entered.
>> >>>
>> >>> So I'm stuck with data that I have to convert, for different reasons
>> >>> depending on whether I use survex of therion.
>> >>>
>> >>> Here is part of the file, I have quiet a few
>> >>>
>> >>> survey
>> >>>
>> >>> centreline
>> >>> data normal from to clino compass tape ignoreall
>> >>> 121:08:2583:37:4017.88
>> >>> 2300:00:00-:-:-0.055
>> >>> 3-02:39:00266:49:003.206
>> >>> 3-314:28:20299:57:452.02
>> >>> 3-16:32:25312:13:201.246
>> >>> 3-06:22:3584:16:101.17
>> >>> 3-309:16:4584:15:501.846
>> >>> 3-55:00:10122:44:500.77
>> >>> 3-325:02:55249:55:451.014
>> >>> 35359:30:50338:07:2516.674
>> >>> 5-306:52:00262:23:201.402
>> >>> 5-59:29:30343:51:301.076
>> >>> 5-305:08:25358:34:301.274
>> >>> 5-315:26:2090:51:351.632
>> >>> 5-29:12:4577:01:351.891
>> >>> 5-19:55:5033:02:003.071
>> >>> 5-348:22:3531:08:253.707
>> >>> 5-350:35:2015:31:254.292
>> >>> 5-13:29:3515:31:204.202
>> >>> 5-12:24:5030:20:207.919
>> >>> 5617:29:0531:28:506.444
>> >>> 6-307:24:35149:47:351.738
>> >>> 6-344:44:40149:45:301.426
>> >>> 6-77:05:35149:36:051.523
>> >>> 6-306:05:00314:12:100.84
>> >>> 6-353:47:5094:54:352.091
>> >>> 6-00:42:00219:31:405.446
>> >>> 6-18:33:50230:03:054.468
>> >>> 6712:26:05241:13:004.272
>> >>>
>> >>> .etc
>> >>>
>> >>> Anyone got a solution that does not mean I have to convert in a 
>> >>> spreadsheet?
>> >>>
>> >>> thanks
>> >>>
>> >>> Andrew
>> >>> ___
>> >>> Therion mailing list
>> >>> Therion@speleo.sk
>> 

Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Stacho Mudrak
Hello,

could you please try the latest commit? I do not think that even a warning
for 270 (=-90) to 360 (=level) degrees clino is necessary. An error can
occur if you manually type a comma in the wrong place, but the same may
happen with compass & tape and there is no warning.

S.

On Mon, 14 Dec 2020 at 09:43, Andrew Atkinson  wrote:

> We have now used 3 different 'Total stations' all by different
> manufacturers
>
> All seem to give a choice between
>
> 270 as down 0 as level and 90 as up
>
> or
>
> 0 as down 90 as level and 180 as up
>
> None of them have given the choice for negative clino (all the machines
> we have use are old, but digital.
>
> So it does seem normal for theodolites!
>
> With hindsight I should have chosen the latter,then I could have just
> calibrated with a calibrate clino 90
>
> But it was difficult to get your head round, plus I was using pockettopo
> (and sexytopo) to draw the survey in the cave, so it was easier to use
> the 270 as down version
>
> It would be really useful to be able in a centreline-endcentreline nest
> to be able to suppress the out of range error and use the 270 to 360
> readings, but still have the error/warning for the more normal surveys
>
> thanks
>
> Andrew
>
> On 14/12/2020 08:24, Martin Sluka via Therion wrote:
> > Are you sure those data are “normal”?
> >
> > Martin
> >
> > Odesláno z iPhonu
> >
> > 14. 12. 2020 v 1:10, alastair gott :
> >
> >> Hi Andrew, if you can get deg,mins,secs to work in survex then you can
> use the .3d file with the surveys use command. (But I think from your
> careful wording, you already know this).
> >>
> >> import use.3d -surveys use
> >>
> >> Not ideal afaik for “mixing local and global coordinates” so tricky if
> your going for a kml output if you have to use with mixed .3d and normal
> .th files.
> >>
> >> It would be good if you could select a lookup file for the Clino, then
> you could easily create a translation file in excel and save that as a .th
> for your total station .th file to lookup to. But no idea if this is
> feasible or even an idea at all.
> >>
> >> Al.
> >>
> >> Sent from my iPhone
> >>
> >>> On 13 Dec 2020, at 18:15, Andrew Atkinson  wrote:
> >>>
> >>> Hello
> >>>
> >>> I thought that there was a way I could stop the out of range error, but
> >>> I cannot now find it. It would be an a useful command to have as
> instead
> >>> of negative readings we got readings between 270 and 359, which
> although
> >>> strange is valid. In survex readings over 90 are just a warning, which
> >>> seems far more sensible, the problem is that I don't think that I can
> >>> enter the data in survex either without conversion as I don't think
> that
> >>> degrees minutes and seconds can be entered.
> >>>
> >>> So I'm stuck with data that I have to convert, for different reasons
> >>> depending on whether I use survex of therion.
> >>>
> >>> Here is part of the file, I have quiet a few
> >>>
> >>> survey
> >>>
> >>> centreline
> >>> data normal from to clino compass tape ignoreall
> >>> 121:08:2583:37:4017.88
> >>> 2300:00:00-:-:-0.055
> >>> 3-02:39:00266:49:003.206
> >>> 3-314:28:20299:57:452.02
> >>> 3-16:32:25312:13:201.246
> >>> 3-06:22:3584:16:101.17
> >>> 3-309:16:4584:15:501.846
> >>> 3-55:00:10122:44:500.77
> >>> 3-325:02:55249:55:451.014
> >>> 35359:30:50338:07:2516.674
> >>> 5-306:52:00262:23:201.402
> >>> 5-59:29:30343:51:301.076
> >>> 5-305:08:25358:34:301.274
> >>> 5-315:26:2090:51:351.632
> >>> 5-29:12:4577:01:351.891
> >>> 5-19:55:5033:02:003.071
> >>> 5-348:22:3531:08:253.707
> >>> 5-350:35:2015:31:254.292
> >>> 5-13:29:3515:31:204.202
> >>> 5-12:24:5030:20:207.919
> >>> 5617:29:0531:28:506.444
> >>> 6-307:24:35149:47:351.738
> >>> 6-344:44:40149:45:301.426
> >>> 6-77:05:35149:36:051.523
> >>> 6-306:05:00314:12:100.84
> >>> 6-353:47:5094:54:352.091
> >>> 6-00:42:00219:31:405.446
> >>> 6-18:33:50230:03:054.468
> >>> 6712:26:05241:13:004.272
> >>>
> >>> .etc
> >>>
> >>> Anyone got a solution that does not mean I have to convert in a
> spreadsheet?
> >>>
> >>> thanks
> >>>
> >>> Andrew
> >>> ___
> >>> Therion mailing list
> >>> Therion@speleo.sk
> >>>
> 

Re: [Therion] Gradient out of range - does not process

2020-12-14 Thread Andrew Atkinson
We have now used 3 different 'Total stations' all by different manufacturers

All seem to give a choice between

270 as down 0 as level and 90 as up

or

0 as down 90 as level and 180 as up

None of them have given the choice for negative clino (all the machines
we have use are old, but digital.

So it does seem normal for theodolites!

With hindsight I should have chosen the latter,then I could have just
calibrated with a calibrate clino 90

But it was difficult to get your head round, plus I was using pockettopo
(and sexytopo) to draw the survey in the cave, so it was easier to use
the 270 as down version

It would be really useful to be able in a centreline-endcentreline nest
to be able to suppress the out of range error and use the 270 to 360
readings, but still have the error/warning for the more normal surveys

thanks

Andrew

On 14/12/2020 08:24, Martin Sluka via Therion wrote:
> Are you sure those data are “normal”?
> 
> Martin
> 
> Odesláno z iPhonu
> 
> 14. 12. 2020 v 1:10, alastair gott :
> 
>> Hi Andrew, if you can get deg,mins,secs to work in survex then you can use 
>> the .3d file with the surveys use command. (But I think from your careful 
>> wording, you already know this).
>>
>> import use.3d -surveys use
>>
>> Not ideal afaik for “mixing local and global coordinates” so tricky if your 
>> going for a kml output if you have to use with mixed .3d and normal .th 
>> files.
>>
>> It would be good if you could select a lookup file for the Clino, then you 
>> could easily create a translation file in excel and save that as a .th for 
>> your total station .th file to lookup to. But no idea if this is feasible or 
>> even an idea at all.
>>
>> Al.
>>
>> Sent from my iPhone
>>
>>> On 13 Dec 2020, at 18:15, Andrew Atkinson  wrote:
>>>
>>> Hello
>>>
>>> I thought that there was a way I could stop the out of range error, but
>>> I cannot now find it. It would be an a useful command to have as instead
>>> of negative readings we got readings between 270 and 359, which although
>>> strange is valid. In survex readings over 90 are just a warning, which
>>> seems far more sensible, the problem is that I don't think that I can
>>> enter the data in survex either without conversion as I don't think that
>>> degrees minutes and seconds can be entered.
>>>
>>> So I'm stuck with data that I have to convert, for different reasons
>>> depending on whether I use survex of therion.
>>>
>>> Here is part of the file, I have quiet a few
>>>
>>> survey
>>>
>>> centreline
>>> data normal from to clino compass tape ignoreall
>>> 121:08:2583:37:4017.88
>>> 2300:00:00-:-:-0.055
>>> 3-02:39:00266:49:003.206
>>> 3-314:28:20299:57:452.02
>>> 3-16:32:25312:13:201.246
>>> 3-06:22:3584:16:101.17
>>> 3-309:16:4584:15:501.846
>>> 3-55:00:10122:44:500.77
>>> 3-325:02:55249:55:451.014
>>> 35359:30:50338:07:2516.674
>>> 5-306:52:00262:23:201.402
>>> 5-59:29:30343:51:301.076
>>> 5-305:08:25358:34:301.274
>>> 5-315:26:2090:51:351.632
>>> 5-29:12:4577:01:351.891
>>> 5-19:55:5033:02:003.071
>>> 5-348:22:3531:08:253.707
>>> 5-350:35:2015:31:254.292
>>> 5-13:29:3515:31:204.202
>>> 5-12:24:5030:20:207.919
>>> 5617:29:0531:28:506.444
>>> 6-307:24:35149:47:351.738
>>> 6-344:44:40149:45:301.426
>>> 6-77:05:35149:36:051.523
>>> 6-306:05:00314:12:100.84
>>> 6-353:47:5094:54:352.091
>>> 6-00:42:00219:31:405.446
>>> 6-18:33:50230:03:054.468
>>> 6712:26:05241:13:004.272
>>>
>>> .etc
>>>
>>> Anyone got a solution that does not mean I have to convert in a spreadsheet?
>>>
>>> thanks
>>>
>>> Andrew
>>> ___
>>> Therion mailing list
>>> Therion@speleo.sk
>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.speleo.sk%2Flistinfo%2Ftheriondata=04%7C01%7C%7Cccbda31a118a4d7920f708d89f9316f5%7C84df9e7fe9f640afb435%7C1%7C0%7C637434801373846851%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=C3FiInOMQihrMsvJa7aW1p%2FMHe83Q%2BZSDsw1NVslcA8%3Dreserved=0
>> ___
>> 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] Gradient out of range - does not process

2020-12-14 Thread Martin Sluka via Therion
Are you sure those data are “normal”?

Martin

Odesláno z iPhonu

14. 12. 2020 v 1:10, alastair gott :

> Hi Andrew, if you can get deg,mins,secs to work in survex then you can use 
> the .3d file with the surveys use command. (But I think from your careful 
> wording, you already know this).
> 
> import use.3d -surveys use
> 
> Not ideal afaik for “mixing local and global coordinates” so tricky if your 
> going for a kml output if you have to use with mixed .3d and normal .th files.
> 
> It would be good if you could select a lookup file for the Clino, then you 
> could easily create a translation file in excel and save that as a .th for 
> your total station .th file to lookup to. But no idea if this is feasible or 
> even an idea at all.
> 
> Al.
> 
> Sent from my iPhone
> 
>> On 13 Dec 2020, at 18:15, Andrew Atkinson  wrote:
>> 
>> Hello
>> 
>> I thought that there was a way I could stop the out of range error, but
>> I cannot now find it. It would be an a useful command to have as instead
>> of negative readings we got readings between 270 and 359, which although
>> strange is valid. In survex readings over 90 are just a warning, which
>> seems far more sensible, the problem is that I don't think that I can
>> enter the data in survex either without conversion as I don't think that
>> degrees minutes and seconds can be entered.
>> 
>> So I'm stuck with data that I have to convert, for different reasons
>> depending on whether I use survex of therion.
>> 
>> Here is part of the file, I have quiet a few
>> 
>> survey
>> 
>> centreline
>> data normal from to clino compass tape ignoreall
>> 121:08:2583:37:4017.88
>> 2300:00:00-:-:-0.055
>> 3-02:39:00266:49:003.206
>> 3-314:28:20299:57:452.02
>> 3-16:32:25312:13:201.246
>> 3-06:22:3584:16:101.17
>> 3-309:16:4584:15:501.846
>> 3-55:00:10122:44:500.77
>> 3-325:02:55249:55:451.014
>> 35359:30:50338:07:2516.674
>> 5-306:52:00262:23:201.402
>> 5-59:29:30343:51:301.076
>> 5-305:08:25358:34:301.274
>> 5-315:26:2090:51:351.632
>> 5-29:12:4577:01:351.891
>> 5-19:55:5033:02:003.071
>> 5-348:22:3531:08:253.707
>> 5-350:35:2015:31:254.292
>> 5-13:29:3515:31:204.202
>> 5-12:24:5030:20:207.919
>> 5617:29:0531:28:506.444
>> 6-307:24:35149:47:351.738
>> 6-344:44:40149:45:301.426
>> 6-77:05:35149:36:051.523
>> 6-306:05:00314:12:100.84
>> 6-353:47:5094:54:352.091
>> 6-00:42:00219:31:405.446
>> 6-18:33:50230:03:054.468
>> 6712:26:05241:13:004.272
>> 
>> .etc
>> 
>> Anyone got a solution that does not mean I have to convert in a spreadsheet?
>> 
>> thanks
>> 
>> Andrew
>> ___
>> Therion mailing list
>> Therion@speleo.sk
>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.speleo.sk%2Flistinfo%2Ftheriondata=04%7C01%7C%7Cccbda31a118a4d7920f708d89f9316f5%7C84df9e7fe9f640afb435%7C1%7C0%7C637434801373846851%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=C3FiInOMQihrMsvJa7aW1p%2FMHe83Q%2BZSDsw1NVslcA8%3Dreserved=0
> ___
> Therion mailing list
> Therion@speleo.sk
> https://mailman.speleo.sk/listinfo/therion
___
Therion mailing list
Therion@speleo.sk
https://mailman.speleo.sk/listinfo/therion