I set up on a point NOT in my job or control file, but I know it's bearing and distance relative to another known point (but not the coordinates). Where in SurvCE can I manually force the OP to be there? I know I could do a resection if I had two other points, but thought there was a way to just input the data.
Under COGO - Manual Traverse since you know the target in relation to another.
If you knew the coordinates it would be under Keyboard Input otherwise.
What I would be is to go to COGO and do a point in direction and establish coordinates on my point and then either assign an elevation until you can shoot something with an elevation on it and then adjust all elevations shot with assumed elevation on your point or if you can sight a point with a known elevation on it, then you can use the benchmark routine.
Under the COGO tab, you can use "Point in Direction"
> Under the COGO tab, you can use "Point in Direction"
No "point in direction" under cogo. Point projection?
Also, under Cogo, manual traverse, BS is dimmed out. It
May be though that I needed to pretend I'm on one of the other points, then "manually traverse" to the point I'm on.
I finally gave up and set a prism on the BS.
I would like to learn those other functions though.
> No "point in direction" under cogo. Point projection?
In my version (SurvCE v1.67), Point in Direction is Item 0 on the COGO menu.
That is the version I use personally as well.
I do use 4.0 at work though, and will be sure to check if you still can't find it by Monday AM rcf.
> > No "point in direction" under cogo. Point projection?
>
> In my version (SurvCE v1.67), Point in Direction is Item 0 on the COGO menu.
Hmmm. I'm at 2.07. Go figure.:-(
Argh!
OK. So this didn't go too well. I've managed to translate and rotate the bulk of the day's work, but the final OP, from which I shot a bunch of topo points, refuses to rotate all those points. I attempted to use "set to BS Azimuth" in SurvCE, as I've done many times before, but the backsight was somehow set to 0.
At any rate, using COGO in TraversePC, I've tried to rotate the backsight to the foresight from the previous point (plus 180 degrees), to no avail.
I'm dead ended. It's just not doing it.
So, the question is:
If I were to post a file with the survey, so that someone might be able to point out the error of my ways, what's the best format to use? Just cut and paste the .rw5 text? Output an ascii file of the the points where they are now?
Thanks in advance.:-/
Argh!
A short explanation of what you actually did along with the .rw5 file would go a long way in helping.
Using the Point in Direction, you need to be on a known point for it to work.
I have 2.x on my backup parts unit. I'll take a looksie tomorrow hopefully.
COGO is fun...NOT.
> A short explanation of what you actually did along with the .rw5 file would go a long way in helping.
>
> Using the Point in Direction, you need to be on a known point for it to work.
Thanks. I'll give it a try.
Here's the picture, AFTER some of the moves, as follows:
Point 1:7 (aka 1:6, 1:5, 1:4 etc...TPC insists on using a new point number everytime I bring the raw file in, but they're all the same point) was moved from wherever it was in the rw5, so that point 1 was in the right place (109.81' N56-23-13 from point 2). Then the entire traverse was rotated such that point 1 to point 2 (2:7) is S56-23-13E.
Then, I turned AR what looks like a correct angle to 500 (aka 500:6), of 92-48-57, which would make the azimuth to 500, S36-25-44W. The raw data shows something different. At any rate, if I try to rotate all of the side shots taken from 500 AROUND point 500, to the reciprocal of the foresight (S36-25-44W), that is, to N36-25-44E, it's not correct.
I think the order in which I'm doing things may be the culprit, as follows:
I set the back sight angle from 1 to 2 incorrectly, because 1 wasn't a known point. That was the original problem.
Then, I set the back sight from 500 to 1 incorrectly. Both of these were done (incorrectly) in SurvCE.
Back in the office, I started by translating and rotating the entire traverse, followed by an attempt to rotate just the last portion--the portion from point 500.
I think I should have started from the "end" and worked the other way, using COGO, first adjusting the reciprocal of the foresight to 500. Then doing the rotate, then, lastly, doing the translate of the whole traverse, but I'm not sure of this.
This TPC version of the raw data seems to show the back sight from 1 to 2 and from 500 to 1 the same: 133-36-47:
Here's the rw5:
JB,NMTOPO30MAY15B,DT05-30-2015,TM12:49:32
MO,AD0,UN2,SF1.00000000,EC1,EO0.0,AU0
--SurvCE Version 2.07
--CRD: Alphanumeric
--VT NAD83
--Equipment: Topcon GTS/GPT Series
--TS Scale: 1.00000000
--EDM Mode: Fine
SP,PN2,N 5000.0000,E 5000.0000,EL1000.0000,--N Corner
--Calculated Occupied Point Coordinates from Backsight Check
OC,OP1,N 5109.78450,E 4997.34196,EL1002.143,--
LS,HI5.1000,HR1.0000
BK,OP1,BP2,BS45.0000,BC133.3647
BD,OP1,FP2,AR133.3647,ZE93.1514,SD109.994000,--N Corner
--Calculated: AR133?36'47", HD7071.068, Z1000.000
--Measured: AR133?36'47", HD109.817, Z-2.143
--Delta: AR0?00'00", HD-6961.251, Z-1002.143
LS,HI5.1000,HR5.5000
SS,OP1,FP500,AR226.2544,ZE83.0605,SD275.137000,--ROCK IN FIELD
LS,HI5.1000,HR0.7000
SS,OP1,FP102,AR314.0426,ZE90.2305,SD129.531000,--
LS,HI5.1000,HR5.5000
SS,OP1,FP500,AR226.2538,ZE83.0545,SD275.131000,--
--Backsight Check: PT 1
--Calculated: AR91?25'44"
--Measured: AR91?25'44"
--Delta: AR0?00'00"
OC,OP500,N 5116.59570,E 4724.28222,EL1034.792,--ROCK IN FIELD
LS,HI5.5000,HR0.7000
BK,OP500,BP1,BS91.2544,BC133.3647
SS,OP500,FP102,AR65.3803,ZE96.2628,SD299.318000,--
LS,HI5.5000,HR5.5000
SS,OP500,FP400,AR297.0841,ZE86.4007,SD112.497000,--
SS,OP500,FP501,AR316.1739,ZE86.2433,SD83.056000,--WALL
SS,OP500,FP502,AR327.4925,ZE86.4920,SD67.699000,--
SS,OP500,FP503,AR338.1838,ZE87.4408,SD63.392000,--
SS,OP500,FP504,AR349.1513,ZE89.0227,SD58.280000,--
SS,OP500,FP505,AR2.2928,ZE90.4051,SD55.495000,--
SS,OP500,FP506,AR18.3339,ZE92.4959,SD55.763000,--
SS,OP500,FP507,AR28.1104,ZE94.0435,SD58.535000,--
SS,OP500,FP508,AR42.4504,ZE95.0431,SD64.651000,--
SS,OP500,FP509,AR56.2456,ZE95.3038,SD79.646000,--
SS,OP500,FP510,AR62.5452,ZE95.1953,SD91.621000,--
SS,OP500,FP511,AR66.3053,ZE95.3101,SD99.891000,--EDGE OF FIELD
SS,OP500,FP512,AR71.2421,ZE96.4832,SD108.378000,--
SS,OP500,FP513,AR76.1019,ZE97.5758,SD114.967000,--
SS,OP500,FP514,AR78.1911,ZE98.2830,SD135.592000,--EDGE OF ROW
SS,OP500,FP515,AR97.3537,ZE96.2022,SD77.178000,--EDGE OF FIELD
SS,OP500,FP516,AR112.0440,ZE95.4735,SD65.894000,--
SS,OP500,FP517,AR146.0006,ZE92.0646,SD51.394000,--
SS,OP500,FP518,AR175.2851,ZE90.5216,SD58.622000,--
SS,OP500,FP519,AR204.0610,ZE88.3212,SD66.558000,--
SS,OP500,FP520,AR224.0436,ZE86.4947,SD91.259000,--
SS,OP500,FP521,AR230.0958,ZE87.4050,SD111.865000,--CTR OF OPENING IN WALL
> Under COGO - Manual Traverse since you know the target in relation to another.
> If you knew the coordinates it would be under Keyboard Input otherwise.
This is a mess. I'm going back out today to do it again...at least the first part...establishing the location of point 1, and point 500. I assume I can then cut and paste all the topo shots from 500 into the new raw file, so I don't have to shoot them again.
I did just discover that I probably can use Keyboard input to get point 1 into the file...it dawned on me that for this exercise, I've changed my point of origin TO point 1, so it's coordinates are 5000,5000,1000. DUH.
And, to put the icing on the cake, I checked my field notes and see that I did a little math on the fly, attempting to determine the Azimuth for the backsight from 1 to 2...they clearly show I came up with 133-36-47. This should be 123-36-47 (S56-23-13E). We have discovered the enemy and he is us.
Thanks for the ideas.
As mentioned already, this is indeed now known as Manual Traverse, or Option 9 on the COGO tab.
