Community Forums

Community Forums

Share:
Notifications
Clear all

Compute Inverse  

Page 1 / 4

BurnorMJ
Posts: 30
Member
(@burnormj)
20+ posts
Joined: 2 years ago

Hello community,

Question of the day: 

Why does my tsc3 control when I go to cogo and compute and inverse between two points I get X?

When I import into Carlson 2019 and compute inverse between the same two points I get Y?

Example: (#1000 to #1001) COGO in tsc3= 202.891 H. dist; Carlson= 203.50 

Both the drawing and the tsc3 set to state plane coor. system, only difference i can see in the set up is the DC is US survey feet and Carlson is just US feet. Any insight to this would be most helpful.

 

Topic Tags
29 Replies
MathTeacher
Posts: 1041
Member
(@mathteacher)
1,000+ posts
Joined: 7 years ago

Perhaps the systems have different scale factors. 

Reply
John Hamilton
Posts: 2855
Member
(@john-hamilton)
2,500+ posts
Joined: 10 years ago

I would say that one is ground, one is grid or geodetic, but over that short distance you would have to be at 63,000 foot elevation (minus whatever the grid scale factor is). So not that. So my other thought would be one is a slope distance. Or you did a calibration and got some totally whacked out scale factor.  

Reply

Take the next step in your career, PPI will get you there

Loyal
Posts: 3400
Member
(@loyal)
2,500+ posts
Joined: 10 years ago

Agree with John...

Pretty much has to be a "slope distance" or a totally whacked "calibration."

Of course to err is human, to TOTALLY screw things up requires a computer.

GIGO

Loyal

Reply
Williwaw
Posts: 2339
Member
(@williwaw)
1,000+ posts
Joined: 8 years ago

Maybe your data is being scaled once in the DC and again in Carlson? If this is GPS data, maybe post process the vectors for an independent check on the solutions?

Reply
Page 1 / 4
Scroll to Top