When creating Starnet .DAT files manually, I always input the Back Sight distances. The process I'm using now to create them (via TPC) doesn't appear to.
Does anyone who's familiar with the Star*net Carlson Converter know if it does? Would someone who uses it consider converting this short .rw5 file and posting the Starnet Listing, for comparison? Not only does it seem some of the data is missing; some of the measurements just seem wrong. (I know some of my H.R.'s are screwed up, but this is intended to be an apples to apples comparison). I don't want to go down this path if it's not solid.
Here's the picture:
Here's the unadulterated .rw5 file:
JB,NM100-3102-500-100,DT10-11-2015,TM13:19:38
MO,AD0,UN2,SF1.00000000,EC0,EO0.0,AU0
--SurvCE Version 2.07
--CRD: Alphanumeric
--VT NAD83
--Equipment: Topcon GTS/GPT Series
--TS Scale: 1.00000000
--EDM Mode: Fine
--HR/HI Checked 14dec2015
SP,PN2,N 428317.2010,E 1618591.5090,EL999.0000,--
SP,PN100,N 428377.9830,E 1618500.0690,EL1000.0000,--
--Set Collection with Obs Order 123...321...
OC,OP100,N 428377.98300,E 1618500.06900,EL1000.000,--
LS,HI5.1600,HR0.0000
BK,OP100,BP2,BS123.3646,BC0.0000
LS,HI5.1600,HR0.0000
BD,OP100,FP2,AR0.0000,ZE93.2551,SD,--
LS,HI5.1600,HR5.0500
FD,OP100,FP3102,AR180.2804,ZE88.3406,SD129.574000,--
FR,OP100,FP3102,AR0.2754,ZE271.2548,SD129.572000,--
LS,HI5.1600,HR0.0000
BR,OP100,FP2,AR179.5942,ZE266.3347,SD,--
--SS,OP100,FP2,AR0.0000,ZE93.2602,SD0.000000,--
--LS,HI5.160000,HR5.050000
--SS,OP100,FP3102,AR180.2808,ZE88.3409,SD129.573000,--
--LS,HI5.160000,HR0.000000
--Set Collection with Obs Order 123...321...
OC,OP3102,N 428450.56971,E 1618392.78497,EL1003.345,--
LS,HI4.9500,HR5.2200
BK,OP3102,BP100,BS124.0454,BC0.0000
LS,HI4.9500,HR5.2200
BD,OP3102,FP100,AR0.0000,ZE91.2402,SD129.569000,--
LS,HI4.9500,HR4.9500
FD,OP3102,FP500,AR66.3331,ZE84.2242,SD298.914000,--
FR,OP3102,FP500,AR246.3320,ZE275.3703,SD298.915000,--
LS,HI4.9500,HR5.2200
BR,OP3102,FP100,AR179.5959,ZE268.3548,SD129.566000,--
--SS,OP3102,FP100,AR0.0000,ZE91.2407,SD129.567500,--
--LS,HI4.950000,HR4.950000
--SS,OP3102,FP500,AR66.3326,ZE84.2249,SD298.914500,--
--LS,HI4.950000,HR5.220000
--Set Collection with Obs Order 123...321...
OC,OP500,N 428158.20537,E 1618337.86503,EL1032.616,--
LS,HI4.9500,HR5.2200
BK,OP500,BP3102,BS10.3820,BC0.0000
LS,HI4.9500,HR5.2200
BD,OP500,FP3102,AR0.0000,ZE95.4236,SD298.910000,--
LS,HI4.9500,HR4.9500
FD,OP500,FP100,AR25.4741,ZE96.5158,SD275.066000,--
FR,OP500,FP100,AR205.4739,ZE263.0742,SD275.070000,--
LS,HI4.9500,HR5.2200
BR,OP500,FP3102,AR179.5954,ZE264.1648,SD298.909000,--
--SS,OP500,FP3102,AR0.0000,ZE95.4254,SD298.909500,--
--LS,HI4.950000,HR4.950000
--SS,OP500,FP100,AR25.4743,ZE96.5208,SD275.068000,--
--LS,HI4.950000,HR5.220000
And here is my .DAT file into Starnet:
#Coordinates
C 100 428377.9830 1618500.0690 1000.0000 ! ! !
C 3102 428450.5620 1618392.7964 1003.3455 * * *
C 2 428317.2010 1618591.5090 999.0000 ! ! !
C 500 428158.2289 1618337.8824 1032.6161 * * *
#Observations
D 100-3102 129.5188
V 100-3102 -1.8145 5.16/5.05
A 100-2-3102 180.280800
D 3102-500 297.4461
V 3102-500 29.2706 4.95/5.22
A 3102-100-500 66.332600
Thanks in advance.
Well your first set is FUBAR for STARNET.
No BS distances...so, you'd only have the BS angle.
Normally you'd get the "DV" code as shown on this BS check;
# SurvCE Version 2.07
# CRD: Alphanumeric
# NY Long Island NAD83
# Equipment: Leica Robotic Total Station
# TS Scale: 1.00000000
# EDM Mode: Standard
# P.C. mm Applied: 4.4000
# P.C. mm Applied: -5.6000
# ****TPS****
# 57 DEGREES
# 30.3 PRESSURE
# 83 % HUMIDITY
# -1.5PPM
# Set Collection with Obs Order 123...321...
.Delta Off
DV GLR-TL 254.9245 87-52-01.50 5.080/5.140 'TL
M TL-GLR-GCE 77-19-14.00 151.3197 89-57-30.00 5.080/5.115 'GCE
DV GLR-TL 254.9246 87-52-00.50 5.080/5.140 'TL
M TL-GLR-GCE 77-19-15.50 151.3192 89-57-36.50 5.080/5.115 'GCE
DV GLR-TL 254.9246 87-52-00.50 5.080/5.140 'TL
M TL-GLR-GCE 77-19-13.00 151.3192 89-57-28.00 5.080/5.115 'GCE
# Warning: Vertical Angles to foresight differ by 0å¡00'20".
# SS,OPGLR,FPTL,AR0.0000,ZE87.5201,SD254.924574,--TL
# LS,HI5.080000,HR5.115000
# SS,OPGLR,FPGCE,AR77.1914,ZE89.5732,SD151.319350,--GCE
# LS,HI5.080000,HR5.140000
# Set Collection with Obs Order 123...321...
P.S. Note how the raw observations are the only data not noted (#) out...
Scott Zelenak, post: 349158, member: 327 wrote: Well your first set is FUBAR for STARNET.
No BS distances...so, you'd only have the BS angle.Normally you'd get the "DV" code as shown on this BS check;
Yes, I see that. But why no BS distance on the second set? I see it in the .RW5. I was using "Set Collection" in the data collector. Is the file you posted from a .DAT file created by the converter?
Why not combine these "D", "V", and "A" codes into "M" codes?
"D 100-3102 129.5188
V 100-3102 -1.8145 5.16/5.05
A 100-2-3102 180.280800"
.
becomes this;
M 2-100-3102 180.2808 88.3409 129.573000 5.16/0.00
You seem to be doing a lot of extra work.
Are you computing the delta elevation and horizontal distance and also changing the foresight heights?
That could be your elevation problem there.
Let the software do the work....
Thats straight out of the converter...
Scott Zelenak, post: 349162, member: 327 wrote: Why not combine these "D", "V", and "A" codes into "M" codes?
"D 100-3102 129.5188
V 100-3102 -1.8145 5.16/5.05
A 100-2-3102 180.280800"
.
becomes this;
M 2-100-3102 180.2808 88.3409 129.573000 5.16/0.00You seem to be doing a lot of extra work.
Are you computing the delta elevation and horizontal distance and also changing the foresight heights?
That could be your elevation problem there.Let the software do the work....
The output file I've posted is in that format because it's what TPC creates from the .rw5. There aren't any options available. I've added the HR's and HI's in Starnet, because the software doesn't bring them in. But I see your point about this. I have the Project setting "Horizontal difference/Elevation difference" set. So the software must already be taking that into account (duh!). How else would it be able to compute the Delta E?
As for the separate lines for D, V and A: As I'm learning, I've found it easier to "#" out a single measurement, tracking down blunders. It makes for longer listings, but easier for a grasshopper to work with.