COGO-calculate function

[Monte King]

I am having an issue that may already have been addressed so correct me if this is old news. In the COGO/direct module I am trying to compute a point using calculate for bearing and distance. The calculate works fine as long as the 2 points being used for bearing/distance are surveyed points. The issue is that when one of the points is an imported "Design" point. I imported a set of points that are in Minn. SPC North format and am running job in same coord system, no problems as far as locating design points on the ground just when using calculate it seems the design points are not being translated to ITRF2008(WGS84) for the computation. For instance the inverse from a design point to a surveyed point is N89-28-51W(Geo) 1315.579 ft.(ground) but in direct using calculate the same "inverse" is N89-17-54W(Geo) 1319.387 ft.(ground) To me the difference seems to be near the difference between NAD83 and ITRF2008(WGS84) but I could be wrong. If I am missing something please let me know or if anyone has any input please feel free.

 

[Matt Johnson]

Hi Monte, it would be helpful if you could attach the project archive for this project. To create a project archive press Archive Current Project in the Files screen.

 

[Monte King]

How do I upload the archive zip file?

 

[Matt Johnson]

Are you able to attach to a post in this forum with the "Upload a File" button?

 

[Monte King]

No when I select zip file and open it just opens the zip folder, can only upload individual files not a folder.

 

[Matt Johnson]

You should be able to select the whole zip file to attach. If not you can email it to me at mattjohnson00@gmail.com

 

[Nate The Surveyor]

Dang. All these problems would just go away, if the earth were flat!

 

[Monte King]

You are correct Nate!!!

Matt here is the archive of the job now that it is below 25 mb!! The points I discovered the issue with are 600300(Design/Imported) and V27AV3(Surveyed). 600300 is a previously surveyed point but I used the surveyed coords and entered them into GMM(CMM sister) as control for an adjustment then exported a csv from GMM and imported into J-Field so I know the coords of 600300 are good. I was trying to compute a point beginning at V27AV3 using the bearing of 600300 to V27AV3 and 2 times the distance of 600300 to V27AV3 for a search location.

 

[Matt Johnson]

It looks like you are correct Monte and there is a bug. I'll see if we can get it fixed in the next update.