RW5 REDUCTION BUG

[Spencer]

Just to let everyone know. It appears that when reducing a open traverse
into an existing,adjusted crd file the crd of the backsight pt.that is
known and existing changes if the distance to the bk is not the same as
calculated.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[Doug Sims]

Thanks for the note. That explains some problems we had in a ALTA survey
not too long ago. I'll keep that in mind next time.

--Doug Sims

Spencer wrote:

Just to let everyone know. It appears that when reducing a open traverse
into an existing,adjusted crd file the crd of the backsight pt.that is
known and existing changes if the distance to the bk is not the same as
calculated.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[Barkley Hensley]

Guys I have requested an example file that illustrates the problem. If
you can get me a file that I can duplicate this error with then I can
get it fixed. I have not received a file yet. If anyone has a file
that will duplicate this bug please email it to me. Thanks!!



Spencer wrote:

Just to let everyone know. It appears that when reducing a open traverse
into an existing,adjusted crd file the crd of the backsight pt.that is
known and existing changes if the distance to the bk is not the same as
calculated.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[Nava Ran]

Name the shot to an existing point with a prefix, if 1345P is an existing
point then when you shot to this point name it M1345P(Measured 1345P).The
Point Protect only checks if the point exists in CRD file and gives the
option to change the name in order not to overwrite the coordinates.

Point Protect: This option will check the coordinate (.CRD) file for
existing point data before processing. If the foresight point number for any
traverse or sideshot record already is a stored coordinate in the coordinate
(.CRD) file, then the program shows a list of conflicting point numbers. You
can either continue processing and overwrite the coordinate (.CRD) file
coordinates with the calculated raw file coordinates or cancel the
processing to go back to the editor to change foresight numbers.


"Spencer" <SJOHNSON@DG-A.COM> wrote in message
news:dnv4o6$3b8$1@update.carlsonsw.com...

Just to let everyone know. It appears that when reducing a open traverse
into an existing,adjusted crd file the crd of the backsight pt.that is
known and existing changes if the distance to the bk is not the same as
calculated.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[SPENCER]

Nava Ran wrote:

Name the shot to an existing point with a prefix, if 1345P is an
existing
point then when you shot to this point name it M1345P(Measured
1345P).The
Point Protect only checks if the point exists in CRD file and gives the

option to change the name in order not to overwrite the coordinates.

Point Protect: This option will check the coordinate (.CRD) file for
existing point data before processing. If the foresight point number for
any
traverse or sideshot record already is a stored coordinate in the
coordinate
(.CRD) file, then the program shows a list of conflicting point numbers.
You
can either continue processing and overwrite the coordinate (.CRD) file

coordinates with the calculated raw file coordinates or cancel the
processing to go back to the editor to change foresight numbers.

"Spencer" <SJOHNSON@DG-A.COM> wrote in message
news:dnv4o6$3b8$1@update.carlsonsw.com...

Just to let everyone know. It appears that when reducing a open
traverse
into an existing,adjusted crd file the crd of the backsight pt.that
is
known and existing changes if the distance to the bk is not the
same as
calculated.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[spencer]

Sorry for the delay on getting back and for the the invisible post. The
problem is not in the forsight but in the backsight. If you were to create
2 coords #1 N5000.00 E5000.00
#2 N5000.00 E5100.00
Then set up on 1 bk 2 and shoot a backsight dist of 100.05 then dump your
data and use the same coords for 1&2 to reduce your data ,the coord for #2
changes by .05
This could cause real problems when reducing data into a coord file that
is made up of an existing adjusted traverse. Say you have an ALTA/ACSM or
a condo survey to do on a job that you already have done a boundary survey
on. Your client has built CONDOS on this site and you set up on different
property corners throughout the survey, bring your data in reduce it with
the existing coords of the job. YOU HAVE NOW JUST MOVED THE COORD OF EVERY
PIN THAT YOU BACKSIGHT IF YOUR DIST TO IT WAS NOT PERFECT.



Barkley if you get with Dave Carlson he is aware of it.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[Rob Cross]

That is not a bug. That is a product of not using the software the way it
was designed. If we are just doing topo, I record the BS shot as a BS shot
and not a sideshot to avoid that very problem. It serves as a check. When
traversing, I like having my BS distances used in my adjustment.

If you are using TDS, just use the BS check function. SurvCE automatically
stores the BS shot as a BS shot and does not include it in any adjustment.
If you still want to sideshoot the BS then use a different point number and
describe it as "BS2".

If you don't want to do it these ways, follow Nava Ran's advice.

"Spencer" <SJOHNSON@DG-A.COM> wrote in message
news:dnv4o6$3b8$1@update.carlsonsw.com...

Just to let everyone know. It appears that when reducing a open traverse
into an existing,adjusted crd file the crd of the backsight pt.that is
known and existing changes if the distance to the bk is not the same as
calculated.


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[spencer]

Rob Im not shooting the backsight as a sideshot that would be crazy and
your comment was a product of you not reading my post and using your brain
to design. I was simply trying to make you guys aware of the problem, was
not asking for advice, but thank you Nava for the considerate response and
Rob Merry Christmas


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##

[Rob Cross]

Sorry I misunderstood "The problem is not in the forsight but in the backsight. If you were to create
2 coords #1 N5000.00 E5000.00
#2 N5000.00 E5100.00
Then set up on 1 bk 2 and shoot a backsight dist of 100.05 then dump your
data and use the same coords for 1&2 to reduce your data ,the coord for #2
changes by .05"

Maybe I didn't make myself clear. How are you recording a shot to the backsite if you are not sideshooting or traversing to it? The only possible way I know of to recreate this is by traversing or sideshooting to point # 2 and having point protect turned off. Could you please explain it so I can avoid the same problem.



"spencer" <SJOHNSON@DG-A.COM> wrote in message news:doekoj$q84$1@update.carlsonsw.com...

Rob Im not shooting the backsight as a sideshot that would be crazy and
your comment was a product of you not reading my post and using your brain
to design. I was simply trying to make you guys aware of the problem, was
not asking for advice, but thank you Nava for the considerate response and
Rob Merry Christmas


##-----------------------------------------------##
Article posted with MyNewsGroups
http://mynewsgroups.sourceforge.net
Share your knowledge in... carlson.carlson-survey
##-----------------------------------------------##