Need help understanding import file to localization job

jahalnon

Member
So I know how to create a localization for a project, but just noticed yesterday (learned the hard way) that when I imported design points into a separate page of the localized project, the points came in filtered through the localization. They were shifted the localization shift, which wasn't much (5.8') but not noticed until end of day and we had to redo a half day of stakeout.

I know, at least we noticed it! But how and why should I have to worry about importing DESIGN points and having them shift?

John
 

Nate The Surveyor

Well-Known Member
What may have happened is:
DPOS shifts the underlying coords.
After DPOS, you must press the button, "LOCALIZE". This updates the relationship between the underlying coords, and the local ones.
If you don't do this, it can have the error, of the amount of the shift, of the underlying coords.
I also, press localize, after loading an archived job, to be sure.
Nate
 

jahalnon

Member
My brain is not making a connection; if I import a new file into Design and into a separate page, in this case Page 2, what should I be setting as the coordinate system?
I have a named system for the project and localization. I THINK I did it correctly when I set it up but did not think I had to protect design points which are on the local system when I import them. ?
 

Nate The Surveyor

Well-Known Member
This does NOT answer your question. But, it does explain the problem.
The LS, internally, in its database, uses lat Lon elev, for every point.
That is its internal database.
Therefore. Plane coords, have to have a conversion, to get them in.
So, SPC coords, have to have a defined plane, to install them.
So, tell it that you are working in Arkansas South Zone, and you install them, and it converts them to lat Lon, and you go to work.
Now, with a local coord system, it has more conversions. It first has to know a rotate, translate, scale factor, and it makes them into SPC, which are then made into lat Lon, and stored.
When you install coords, with an undefined coord system, it has to temporarily store them in limbo, before it has localize parameters.
SPC, and lat Lon are reciprocals of each other, with a minor introduction of error, due to rounding. (Like 1/3 in decimal value).
I know I did not answer your question. But, understanding what's going on is handy.
Also, lat Lon is converted to a world cube, but I forget what it's called. Imagine an ice cube, with a small flat flake in it. That's a plane.
The center of the cube is the middle of the earth.
This is what's involved on making a world survey system.
When you see and use plane coords, in the LS, you are seeing lat long, through a filter, where these coords have been projected to a plane.
I'm not smart, and, I've probably left something important out, but this method (javad) is the finest survey system on earth. It lets you look at coords on any plane, or sub plane, as you desire, or wish, WITHOUT changing the actual coord values, (lat Lon) you can work on multiple coord projections at once, from the same data base.
Nate
 

jahalnon

Member
Thanks Nate, all of that is helpful. I think the simple answer for me is to just double check coordinates when I bring them in. Still minor, but can turn in to a disaster if I am not paying attention.
John
 

Nate The Surveyor

Well-Known Member
If you work on day one, with local coords, and have a localize, in the field, on day one, then your APPROXIMATE, quasi- SPC, will get localized.
After DPOS, the UNDERLYING quasi SPC coords shift a few feet, changing the relationship, between SPC, and your local coords. Thus, the parameters of SPC to local coords change.
After DPOS, press the localize button. At this moment, the LS goes to work, updating the localize parameters. Until you do this, this set of parameters is out of date. (Its quasi to local, instead of real SPC to local).
So, if you did day one, failed to press "LOCALIZE", and used the old parameters, instead of the new parameters, (after DPOS, but before updating) I can see how you might get an error of the amount between old and new parameters.
N
 
Top