TBC US Survey Foot Scale Only

If I'm using a local coordinate system, no projection/no datum, I'll need to set the .job up using Scale Factor Only 1.000 for use with the S6 to run conventionally. I suspect you'd go that route if you were working in a local 5000,5000 system with assumed elevations. If you were working with a standard projection, those scale factors would be progressive and defined within the projection. Lacking a projection, small site, assumed elevations, I'd go with the SF 1.000. Hope that helps some. I have scads of old 5000,5000,100 surveys done over the years that I'll use to get going on something new and I'll typically start the .job off that way and worry about getting it into a standard projection later post processing the raw GPS data.

Summertime, post: 425786, member: 11519 wrote: Watched a youtube video recently and the presenter set the controller & TBC project to "scale only". He didn't offer an explanation as to why. The scale factor he used was 1.000000 - no scaling at all. Can anyone on here explain why/when a scale only project should be used? Maybe for jobs where elevations don't matter?

I'm curious....

1.00000000000 for all TS work.

That's my standard template for Robot or TS work. I've found that Access likes to seriously screw with shot distances in calibrated job files. Never quite figured out why, just figured out how to work around it. Seems to work OK in standard RTK Network jobs, but any time I've introduced a calibration, it doesn't play well with conventional.

I just export my control from a GPS job file, then import into the Scale Factor Only job for conventional work.

StLSurveyor, post: 425848, member: 7070 wrote: 1.00000000000 for all TS work.

Will 1.000 work?

Could not resist..

thebionicman, post: 425937, member: 8136 wrote: Will 1.000 work?

Could not resist..

I blow it out - all the way

1.0 :p for all conventional/total station work