TBC Export confusion

Did you set up the projection at the time you set up the job? I don't ever even see SPC coordinates, only the ground coordinates, we are talking XY and not LAT LONG?

Yes, these are converted projects through the Convert TGO file option. The projects have the proper projections setup.

I thought it may have something to do with the converted TGO files so I setup a brand new TBC project with the proper zone and ground scale factor and imported my DC file. I still get the same results, all my point export data is on grid.

Drag and drop calibration file into job first thing.This will also enable you to make a .kml so you can look at it in google earth.

I was having the same problem. What I do now is write down the LDP metadata that was applied in the TGO file, import the DC file into TBC and re-enter the LDP parameters via project/change coordinate system.
Be sure to check all the settings in project/project settings to make sure they are all as you want.

> I was having the same problem. What I do now is write down the LDP metadata that was applied in the TGO file, import the DC file into TBC and re-enter the LDP parameters via project/change coordinate system.
> Be sure to check all the settings in project/project settings to make sure they are all as you want.

I went back from scratch and prepared a new project template with the appropriate projections. Then I imported the .dc file while keeping the project definition intact... and then of course I continue to get Grid coords only.

I delete that import event and then reimport it, but this time I choose to keep the data collector definition. This DOES result in the ground values showing up on my coordinates. I review all of the project settings and NOTHING is different from the template I setup...except for the fact that now I can get my ground coords. This is very off behavior.

I am confused as to why I must hold the data collector projection information to get this function to work properly and am extremely cautious of a new project where I do not have the ground scale factor established.

Johnk said to drag and drop my calibration file....we have never had the need to calibrate. Or am I missing your point?

> I went back from scratch and prepared a new project template with the appropriate projections. Then I imported the .dc file while keeping the project definition intact... and then of course I continue to get Grid coords only.
>
> I delete that import event and then reimport it, but this time I choose to keep the data collector definition. This DOES result in the ground values showing up on my coordinates. I review all of the project settings and NOTHING is different from the template I setup...except for the fact that now I can get my ground coords. This is very off behavior.
>
> I am confused as to why I must hold the data collector projection information to get this function to work properly and am extremely cautious of a new project where I do not have the ground scale factor established.
>
> Johnk said to drag and drop my calibration file....we have never had the need to calibrate. Or am I missing your point?

To be sure, I'm no TBC expert, heck I was just getting good with TGO when my program quit loading on my aged computer....
Anyway, my procedure is to start a new project, import the dc file (from the TGO project directory), keeping the data collector definition. The problem I was having was, when exporting to my (also old) TSC1, the data collector was not working on the LDP "surface". But when I (in TBC) reentered the LDP parameters by hand, then it transferred everything correctly. I still don't understand why and haven't taken the time to call my buddy Troy at Monsen's and have him walk me thru it yet. I just feel better when actually hand entering the LDP into a new project.

I don't "calibrate" anything either, so I'm not sure how that would work or not.

PS. I'm not sure of your "real" identity yet, or maybe I've forgotten...... email me if you'd like.

I work primarily in construction. The state gives us a few control points with known ground coordinates .We shoot these autonomous and create calibration file by telling the dc which point is the point in primary control. This takes care of scale factor.By dragging and dropping thks file into TBC it knows where you are in the world.By exporting a .kml it will show you where the points are in the world on Google earth relatively close.Not perfect, but close enough you could use the map to find a point.

We're in a completely different world on the opposite end of things. We're the ones establishing the control points. I haven't calibrated as you describe in many many years.

Looks like I'm stuck with hundreds of TGO files in GRID forever. No idea how I am going to efficiently use the point data contained within them. Sure, could export to Grid and then scale in Excel but that's just a recipe for disaster.

Another advantage to this is id the picture in Google earth is new enough, you can see any improvements. Thereby decreasing confusion as how to draw it, and saving trips out to see for yourself

Ok, sorry. Didn't mean to waste your time, just passing on what little I've learned about TBC

Trimble Business Center is active on Face Book. If you contact them on FB and outline your problem, they will respond and offer you some solutions. Being that it is in a public domain, they are quite sensitive to being responsive. It's worked for me in the past.

Good luck. I feel your pain. Cheeres! ~ Willy

> Looks like I'm stuck with hundreds of TGO files in GRID forever. No idea how I am going to efficiently use the point data contained within them. Sure, could export to Grid and then scale in Excel but that's just a recipe for disaster.

Good Lord, yes that is a disaster waiting to happen (at least for me it would be).

Instead of importing a "converted file", try exporting a dc file from TGO, then importing that dc file into TBC.

> Trimble Business Center is active on Face Book. If you contact them on FB and outline your problem, they will respond and offer you some solutions. Being that it is in a public domain, they are quite sensitive to being responsive. It's worked for me in the past.
>
> Good luck. I feel your pain. Cheeres! ~ Willy

Thanks, I will have to try that when I get home since we can't be on Facebook at work.

JohnK - I appreciate you trying to help, it was not a waste of time

Brian A - unfortunately I know longer have a working version of TGO.

First off, I am not an expert by any means so use my advice for what it is worth and also if you find a better solution please post so I can learn as well. I think you can setup a local grid (LDP) that has the same parameters as your state plane except you will pick an elevation average for your site and use the inverse of the elevation factor with that average as your scale factor. This should give you ground coordinates at your site with pseudo state plane coordinates. If it was me, I would setup an LDP for each site instead and use local coords so I would not get confused. It is simple to switch between an LDP and Grid in TBC. just go to project and change the projection to what you want and then export your points.

You can import dc files directly into TBC. You don't need to export them from TGO, just get them from where ever they are stored. One problem is the control points (base points) in the dc files at import. What I've done and I hope there is a better way is set up a clean file in TBC, set up your projection that you want and seed the base control points. Get that all set up. Then start importing dc files. It doesn't matter what SPC or other projection is in the dc file, they will import, but you must have the base points already in TBC or it will be mass confusion. At import it will ask if you want the dc projection or the TBC projection. Always keep the TBC. After each dc import, go in an delete the control points that came in with the dc file so only the TBC control point remains. Then recalculate and all you vectors will start at the base points. If you have coordinates only in a dc file (not RTK vectors) you probably could import a dc file to TBC and accept the dc file projection. Then convert it by changing the projection to your new system, then you probably can export the coordinates and import into your other TBC project.

Hope this helps, ain't learning new software fun. There are some things TGO would do that I just can't do in TBC, like exporting a list of ECEF X,Y&Z's. Hey if anybody can show me how to do this it would be great.

When you say GRID, exactly what GRID you talking about?

We have hundreds, if not thousands of TGO projects with some projects that have hundreds of DC files. We're supposed to reimport all of these files in TBC to make this work?

So I took your advice on one of our smaller projects and things are working much smoother. However, I am still not able to replicate my ground coordinates. A very odd thing is occurring; I am able to replicate the northings exactly but my eastings are off 290 feet. Any idea why this would be happening? I have the coordinate systems setup correctly, or at least I think I do. All I did was select the proper state plane coordinate system and zone.

Too bad there isn't a Trimble person (similar to Ladd Nelson and his excellent Carlson customer service) monitoring this board. 🙁