Leica Viva question

I had this issue a while back, and I am trying to remember what I did. Can you view the data "As Stored"? I think that would give you the averaged coordinate. Or are you trying to hold the GPS line for azimuth and overwrite the backsight coordinates using the total station distance?

Control jobs are where you keep your control/design data. Work jobs are for your measured data, the "pick-ups". Using that method, your control/design data remains clean and untouched. Your surveyed data is also easy to manage: the file only contains the measured information.

Control (Office) | Survey (Field)

There's more to it, but in a nutshell, that's the idea behind it I think.

Thanks

I'll try using a separate control job today and see if that works.

I don't want to average the points. I only stored one point #201 the software just magically added the additional points when I did the TPS setup.

I just want to keep my control data separate and not have to worry about accidentally using one of the new points that has a slightly different XYZ.

in your data/point management, try filtering by 'highest class'. that should mean the coords and eliminate multiple points in the display

I keep gps and total station data in different job files because some of the GPS data is lost when you are setting up on the point with the total station. To do this I export my GPS observations to an ascii/text file and then import the data into a new job on the collector. When I set up the instrument, I change the point number of my station and then store my BS. For example if I GPS'd control points 1-6, I export those points and create a new job and reimport the points. Then I renumber point 1 to 100, set up on 100 BS 2, then take a store shot on 2, which is point 101. If I check into point 6 later on, I will store that also. At the end, I can adjust my traverse to get a longer baseline than my initial setup had

This is how we handle it and as long as you do the prep work (lets face it, some jobs you just get out there and get it done) it works perfectly.

Thanks for all the help guys.

I used a control job today and it did just what I was hoping for. All my control points stayed in the control file and the duplicate points were stored to the working job.

Why does Leica create another point every time you do a set up? I can't imagine why anyone would want to have multiple control points all with slightly different coordinates and elevations.

Beavers,

I need to post a full explanation. I think you will see what is happening once I can get a chance to put it in writing. I think I may just take the time an write up a document that will explain things. I think most users never have the system explained. I think a link to a document would be the best way to go so I can do allot of screen shots.

The basic philosophy behind what you see as duplicate points is that Leica systems are designed around... if someone took the time and effort to measure something... the data must be important to them.

Once I get the document finished I will post a link for everyone who is interested to look at it.

Thanks Mark. Looking forward to your explanation.

I don't see any mention of this in any of the Leica manuals. It's not just Leica...I've run into the same thing in the past with Trimble. The manufacturer's build all of these features into their software, but then their manuals only scratch the surface when it comes to explaining what the software is capable of and how it all works.

g'day Beavers,

i rather think you don't have to worry about getting the 'right' or 'wrong' point on your later setups. if you leave the filter on 'highest class' then the TPS point will be the best one and will be the appropriate point to set up on.

when you set up on GPS point 200 it will create a REF class point for TPS purposes at the same coordinates. when you backsight 201 with the TPS it will force the azimuth of the setup shot to be straight over 201 but with the better TPS observation. so if you move to 201 you will be on the same azimuth but at the better TPS derived distance and height difference from 200.

RE: the two TPS 201 points. if you 'EDIT' the point and press 'MORE' you can see the source of the point which will tell you where the points came from (BS setup, survey or other).

i've used the 1200 & VIVA for a while now and only once have i felt the need to use separate measure and control jobs.

Hi

I have a different question about the VIVA GS15 files:

When I export the job with a ASSCI format the rod heights don't show up.
The DBX files - raw data - were suppose to show the rod heights but there is nothing
there as well.

Can anybody please tell me where can I change settings so I can see the rod heights ?

Thank you very much for your help.

Miguel Correia

You need to built a format file (*.frt) with LGO. You can customize it to include all kinds of information, including the one on your wish list.

Then load that format file on the controller for export.

Easy to build, take time to read instructions in the help menu.

Are you trying to see the rod heights on the controller or in LGO?

In LGO, import the raw file, and click the GPS-Proc tab, and then you'll see one of the columns with Height Reading.

Beavers,

Give me a few days... like I said I have been needing to write this up for awhile... I want to make some good examples that are from questions from other users.

The manuals touch on this but everyone needs a solid explanation to have confidence in the gear and how he data is being handled.

In the image that you posted above, if you get in the habit to press F5 more when you review your data, the software provides useful information to indicate the nature of the points. You may find it useful from time to time.

As for Trimble, I see it this way.
Your control points are realy stored points,
the other points with the same names you can view in the software are obersvations to these control points (and their deltas are mostly displayed with them but that depends of how your display is configured)

Chr.

Legal record of what points/setup you actually used to place those marks which pissed someone, somewhere, off.

If it was just "I used those control points" you only have your word.
If it's "I used these control points, here's the location recorded on the day. You can clearly see that I am within the station setup tolerance." it can mean a big difference in lawyer fees.

I always store a shot on my back sight point along with a check shot to another CP every time I set up for just the reason you mentioned.

It would be nice if Leica would store the other points with a prefix or suffix attached to the point. Having multiple points with the same name and different coordinates in the same file just seems like you are asking for trouble at some point. I know you can filter them out, but still...Murphy's Law.