In this thread, Royevrus suggested a way to make Carlson.rw5 files look like TDS .rw5 files, for creation of dat files into Star*net:
It's been working great, until I came upon this oddity:
What I tried to do in SurvCE was rather than do a set, then do another set etc. (same set of points), when it gets to the list of points to collect sets on, I put, for example:
"1800"
"1800"
"1800"...taking a foresight on 1800, then another, then another, then reverse, reverse, reverse...then the backsight.
But what starts out looking fine, giving me the back sight data to 1600:
--Set Collection with Obs Order 123...321...
OC,OP1700,N 427097.64340,E 1617857.41604,EL1246.050,--
LS,HI5.1900,HR5.1000
BK,OP1700,BP1600,BS5.2324,BC0.0000
LS,HI5.1900,HR5.1000
BD,OP1700,FP1600,AR0.0000,ZE100.1418,SD257.796000,--
FD,OP1700,FP1800,AR215.2642,ZE81.2759,SD282.490000,--
FR,OP1700,FP1800,AR35.2651,ZE278.3205,SD282.488000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
--SS,OP1700,FP1600,AR0.0000,ZE100.1423,SD257.795000,--
And what looks like proper foresight data:
BD,OP1700,FP1600,AR0.0000,ZE100.1418,SD257.796000,--
FD,OP1700,FP1800,AR215.2649,ZE81.2752,SD282.489000,--
FR,OP1700,FP1800,AR35.2633,ZE278.3202,SD282.489000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
And again:
BD,OP1700,FP1600,AR0.0000,ZE100.1418,SD257.796000,--
FD,OP1700,FP1800,AR215.2651,ZE81.2753,SD282.488000,--
FR,OP1700,FP1800,AR35.2645,ZE278.3208,SD282.489000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
But then it looks like something goes whacko here:
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
BR,OP1700,FP1600,AR179.5943,ZE259.4531,SD257.794000,--
I'm ready to dump this file and do it again, rather than try to create the SS results, but it begs the question:
Is it improper to populate the SurvCE "Set Collection List" screen with multiple instances of the same point?
Is the above just the results of a fritzy DC cable (it's been acting weird)?
Something else?
Bump...
