TBC trials

I think I know what you're trying to do.

Try this: Highlight the base point. Click on properties. In the properties menu there will be a move survey point. Click on that and you should be allowed to move the base to the new point. I don't know why you have a flag on that point location but I would resolve that even if you need to type in new coordinates for a point there and give it a new name. Once the point is moved it should have a moved next to the point name. Base point 3 becomes 3(MOVED)

Then recompute and it should move all the points with vectors. You can't move as-staked points or calculated positions with the recompute command, only "clean shots". If you want to move as-staked points you need to resolve that first. 

Remember the most important command,,,,,,,UNDO

I think and this is a WAG, is the points selected are dependent on the vectors and the vectors aren't being selected. In any case after translating, likely requires the vectors to be processed again. 

Have you been here?

https://geospatial.trimble.com/en/resources/trimble-business-center-power-hour-webinars

Posted by: @williwaw

↑

I think and this is a WAG, is the points selected are dependent on the vectors and the vectors aren't being selected. In any case after translating, likely requires the vectors to be processed again. 

Have you been here?

https://geospatial.trimble.com/en/resources/trimble-business-center-power-hour-webinars

 

I've been there but thanks for the reminder.  Definitely checking out all the basic level productions (trimble learning center has been pretty cool)

My issue was when transforming that selection it seemed the vectors were included with the point transformation but I went point to point and it throws the whole set north and east of the point it was suppose to transform to.  I know I'm missing something.  I'll make some more attempts with closer look and different parameters if possible.  Mahalo.

@dave-o When you come up with the right process please post about it. I'm getting back into TBC here soon and my TBC Kung Fu is a little rusty.

@williwaw I'd thought that Move Point only allowed you to select one point (which is still true).  The one time I'd done it before I believe(d) it moved only the point. leaving the items connected to it by either TS radial vectors or GNSS unmoved.  That made me go toward trying this point to point Transformation of a selection.  This does work for some point types, but for some reason apparently not for these GNSS points; it continues to throw the whole set off N & E of the selected 2nd point... (?).  So I still don't understand that.

However, what I did successfully here was two parts.  You'll notice in the video I have the rover shots as well as the site control points highlighted.  I used MightyMoe's idea of Moving just the base occupation point.  That worked (! for some reason), bringing all of the connected rover shots with it.  Then I had to select just the control and I did the Transform on them, single point to point, no elevation change (that's why I drew the polyline in there, to have a reference) and that worked.

So I got where I needed but will at some point need to get an understanding of the way different point types seem to have very different capabilities, not just in this area.  Got a lot to learn.

I did successfully process baselines with a project using local EarthScope CORS type Data available on the island and UNAVCOs network monitoring info.  Can you tell I'm proud of that?

@dave-o you should be able to move the base point and then recompute - if your topo observations are held as offsets to the base (that's the usual) the shots depending on that base will sort themselves

The move point should do what you need. The transform command you're using for this task is the wrong way to go. I've never explored using it, but I assume it's doing some type of well, transformation. You need a simple move on the base point to the RTX number for that point. You have to be careful doing it, write down the base, the new coordinates for the base, a couple of located points and make sure they move in unison. The base drops 2.5' in elevation then the points with vectors should drop 2.5', same with NE Lat, long, ect. 

Be sure also to have a clean DC file, one thing that messes it up is to do a days work, download the DC, calculate new points, then upload a new job file and go back to the field without moving the original base point first. Not a good idea. 

I might be looking at this whole thing wrong.  My TBC projects are set up separately from my normal workflow as I begin to understand it.  But... how do you (or do you) deal with a site calibration?  That's what this movement was about - to process the base (multiple base setups on the same point in some cases) with trimbles rtx or by another method and move my points so they are in the their "actual" grid locations.

background: I usually setup my mostly small projects in grid as best as possible.  Here, the record property locations are based off of published triangulation stations and can be 10 or more feet off of "actual" (or current) grid coordinates.  I almost always get out to a site and find my initial monument feet away from the POB.  So I'll calibrate to it.  Sometimes just one point calibration to get the map set, but I'll always check in to at least 2 more if possible to check for rotation issues.

When I bring that into TBC I believe it creates that calibration offset.  I guess a question I can test myself is:  If I bring in the jxl to a grid template and it asks if I want to keep project or keep job, if I keep project does it eliminate the calibration and move everything to "actual" grid locations?  If I'd done that on this job, would my rtx processed base have come in at the same location as my point 1?

I'm not sure how to advise you about control. Since you're on the Big Island, I'm guessing geographic coordinates are unstable even in the short run. 

When I started using GPS I would calibrate to known control points since we had them spread out all over. I quickly found out that probably was the wrong way to go. It was much better to locate areas with a clean projection, then fit, move, rotate the less accurate control onto the projection. Over time that has paid off more than you might imagine. I would get all the old projects on a good projection instead of warping GPS to them. 

Moving an Auto base point over to the more accurate processed location after a day in the field and collecting data as you work is SOP for most. 

Put the days work on a good projection, move older data over to it as you locate older control, that's what we do. 

@dave-o Your workflow is sound. A single point calibration plus at least one check is a good way to get your numbers to match published numbers, particularly when you have a well-defined coordinate system

Don't overthink the processing - Just drag and drop your job file into a TBC project or retrieve it from Connect. I suggest job not jxl just cos its easier

If the project does not have a coordinate system set, it will grab the one from the job.

If the job has a site-calibration you will get that too.

If the project does have system you get asked what do - go with the job 

You do need to be careful if loading a second job with a different site calibration into that project. Here you will probably want to stick with the one you already have

Side note: the format of your data can have an effect - points derived directly from keyed coordinates can behave differently from points derived from observations

One issue is the point you are trying to move is control quality and you are trying to move it to something of less quality.  I don’t think you need to do what you are doing. If you are trying to seed all your data to the new point say a good control point with all the vectors moving correctly like a here position and then to an opus point. Just make the gospel point control quality and the here less quality like survey and simply merge the points. This can be done a couple different ways one name both other exact same and it will prompt you for that or select both and go to merge points and it will ask which one you want to hold and which one is included.  

One thing to keep in mind in TBC vs say cad. If the field process is done correctly and the office side becomes one of the most efficient ways to qa/qc. Also very few time I need to do a translate rotate of raw observations. Even from a here position with rtk base and rover and then updating everything to an OPUS position.  No rotate is needed. Just a translate. But that’s available but not necessary in TBC.  If your field crews run Trimble in the field they can begin a job using RTK base rover stay in same job and run traverse or conventional Topo mapping etc.  when they tie into an existing point previously measured in via RTK or robot etc. it’s the same point number/name. Store another. So you could shot in from multiple directions the same point all the same number. No more 100 = 1. You can select all those groups of points and right mouse click and run a point derivation report each observation will be listed. This helps in some ways before a least squares to identify blunders. You have the tree project and view filters you can use to look at points and raw observations as you bring them in. The vectors spread sheet at top home tab is great for quick checks of rms valorous heights base heights you can add or take away from this in the gear view and vector report to show what you want. Same with optical data. Also the total station editor is not a bad tool either. Under your support tab you have quick links to YouTube Trimble power hours pre recorded training materials all sorts of things to help you get up and running quickly.  Lots of tools built into tbc to aid in learning. I think they have 67 training modules built already free.  If you scale to ground a project of data doesn’t matter if it all started out on say state plane robot rtk your project might require it to be on ground. This is quick easy and you can export survey Trimble jxl file. Now the crew can use that to place in the project folder of Trimble access. No matter what tool they build the daily job from that so rtk robot is all on same system state plane scaled to ground. This beats starting different jobs on a site and keeping rtk and conventional data in separate tbc projects.  Tbc can make you mad at times but I have learned to work with its ways vs trying to do things the way I always have and then trying to fix it. Good luck. I have projects with static network RTK base rover robot and even digital leveling. All in one project. Any point any time I know what field job file it came from how it was positioned what time of day etc.  

@williwaw was a good one today.  The power hours some I go back and re watch. This was a big overview one today on the next release in mid July. It’s amazing what they are doing these days. All manufacturers really.

What is Dave-o trying to accomplish? Just moving survey data to an imported control point value? If so here’s the easiest way to do it

1.  when selected the control point to move data to, right click and choose “add coordinate” making coordinates and elevation “control quality”
2. rename that point the same name as in your survey data, choosing “ “merge”
3.  recompute