Point Protection in the Data Collection Routine

[James Shaw]

SurvCADD XML
Tools | Data Collectors | Sokkia/SDR...

I don't know if this problem is unique to the SDR conversion process but by
glancing at the other collector screens I have a feeling this effects all
collector types. The problem is that there is no point protection feature
during the conversion process. Whenever you convert the raw SDR file to the
RW5 format, any points that appear in the RAW file are automatically added
to the CRD file. It does not care if that point number already exists in
the CRD file or not. To get around this issue we now convert all topo using
a "fake" CRD file that we delete when the conversion process is completed.
Please advise if we are missing a setting somewhere. Otherwise, could
Carlson please add either a point protection feature to the routine or a
toggle to not add the points to the CRD file.

James Shaw
G.W. Stephens

[Ric Carroll, PLS]

In CES, I have had point overwrites too, but I thought it was during the 'Edit-Process Raw Data File'.
I would like to have complete point protection AT ALL TIMES, if so toggled.
As is, I use workarounds too.

FYI:
I used to write an SDR file from Leica DataPro.
Very occasionally I am guilty of recording an observation without a distance, just whatever Az. happens to be set.
I reobserve immediately with ALL the data & the same point number.
I believe that the Carlson interpreter will average 2 such SDR lines.

Ric Carroll, PLS



On Mon, 16 Dec 2002 09:59:08 -0500, "James Shaw" <jshaw@nospam-gwstephens.com> wrote:

SurvCADD XML
Tools | Data Collectors | Sokkia/SDR...

I don't know if this problem is unique to the SDR conversion process but by
glancing at the other collector screens I have a feeling this effects all
collector types. The problem is that there is no point protection feature
during the conversion process. Whenever you convert the raw SDR file to the
RW5 format, any points that appear in the RAW file are automatically added
to the CRD file. It does not care if that point number already exists in
the CRD file or not. To get around this issue we now convert all topo using
a "fake" CRD file that we delete when the conversion process is completed.
Please advise if we are missing a setting somewhere. Otherwise, could
Carlson please add either a point protection feature to the routine or a
toggle to not add the points to the CRD file.

James Shaw
G.W. Stephens