Trouble with M-Local

[Nate The Surveyor]

I have a LDP going. (Low Distortion Projection).
I tried a M-Local today.
The BASE is on "BASE3", with autonomous solution, to kick it off.

Point num 1623 is the same point as 1430, and 520. (520 has an elevation of 0)
AFTER using M-Local, they are 2.66' feet apart. With inverse.

I've tried alot of solutions. Short of standing on my head.

I am concluding that there may be a bug in M-Local.

I have been using "Reverse Shift". This is my first time to use M-Local. (Time to learn something new..)
I also find that M-Local is a bit clunky.... In need of refinement. I shot several old points, and then wished to go through and set some to CHECK, others to hold horiz. and others to HOLD vert.

IF you look at the two above screenshots, The VALUES for point 1430 change, between the two above screenshots.

This is quite simply driving me right up the wall.

Thanks.

Nate

 

[Matt Johnson]

Can you attach the project archive?

 

[Nate The Surveyor]

A few things to add to this, is REVERSE SHIFT is also fouled up.
Trouble is, I USED reverse shift, in the field. I was missing some stuff by 0.2'. I could not figure out why. The FIRST REVERSE SHIFT yielded better results. I decided to go and get food, and solve it. Well, I have been trying to solve this all afternoon.

I set some corners too.

And, I'm sending it in now. It's at 50%.

35-5-24 riner

I was thinking that some underlying projection was wrong... or something. I have been putting all I have into this.

N

 

[Nate The Surveyor]

OK, I have worked on this non stop since 1:00 this after noon. DPOS will not shift the group, (base and todays shots). They appear stuck.
I've tried all I know.
I'm done for today.
N

 

[Matt Johnson]

Hi Nate, many of the points in this project are dated 12/8/2015. Can you confirm that this is a really old project that you opened and started working in again?

These older points weren't saved with all the same fields in the database that the current versions of J-Field saves so there may be compatibility issues with trying to use hybrid RTK with old projects and points.

 

[Nate The Surveyor]

Yes, that is the date.
I am TRYING to think this all through, and not over think it.
I have downloaded all the shots from yesterday, and in Carlson, MOVED the group 1623-1639, so that 1623 matches 1430, (same as 520).
So, I now have all the shots in my system. I have moved them where they need to go. I can export the Underlying SPC coords. I can also export the PDF of this work. For archive. And, start afresh, with importing the whole file, as a local system, with scale factor etc.
I have a feeling that I have already spent way too much time, trying to get this thing right. It has already devoured 2 days, in previous issues with this file.
So, (I always try to have a plan B, and C in the wings) is that a good idea from where you sit, Matt?

Thanks
Nate

 

[Matt Johnson]

Yes, that is the date.
I am TRYING to think this all through, and not over think it.
I have downloaded all the shots from yesterday, and in Carlson, MOVED the group 1623-1639, so that 1623 matches 1430, (same as 520).
So, I now have all the shots in my system. I have moved them where they need to go. I can export the Underlying SPC coords. I can also export the PDF of this work. For archive. And, start afresh, with importing the whole file, as a local system, with scale factor etc.
I have a feeling that I have already spent way too much time, trying to get this thing right. It has already devoured 2 days, in previous issues with this file.
So, (I always try to have a plan B, and C in the wings) is that a good idea from where you sit, Matt?

Thanks
Nate

Yes importing points into a new project from a txt file will work. If you export them as state plane coordinates, I would also import them back into a new project as state plane coordinates if they have good known coordinates.

 

[Nate The Surveyor]

Is there a way to copy the data over, to a new file?
Or, is that the problem...?

 

[Matt Johnson]

I would just import the points from CAD file into a new project until we figure out what went wrong with this one.