Transformation Problems and Questions

Reach RS2 / RS2+ RTK / PPK configuration
1

I am running into some problems when trying to transform coordinates between ITRF 2014 (2010) and NAD83(2010). I have been running some tests trying to find what software I like to do the transformations and was using either the Coordinate sheets from CORS station and also OPUS solutions to validate that the software and my workflow are working correctly.

The problem is that when I take the coordinates on the above sheets and enter them into various softwares, the results do not match up.

Example:
OPUS Solution Obtained from Emlid Reach RS2
image

HTDP Online Transformation

image
image684Ɨ417 36.8 KB

I have a similar experience when using a CORS Coordinate Sheet with listed ITRF 2014 (2010) and NAD83(2011) coordinates.

Example CORS Coordinate Sheet:

image
image668Ɨ439 36 KB

image

Thanks in advance for any input as to what I may be doing wrong.

3

Hi @jaja6009,

Looks like the 74Ā° 30ā€™ W longitude from OPUS is used as the E longitude in HTDP. Does it help if you enter 285Ā° 29ā€™ instead?

4

Yes, that was my first thought.

I found the problem and a problem.

When I entered Cartesian X,Y,Z from the Coordinate sheet it worked perfectly.
In the HTDP instructions it makes no mention of having to use Cartesian X,Y,Z.
I also tried the .exe version of this tool written in I think Fortran and it had the same results.

image
image569Ɨ553 17 KB

image
image660Ɨ470 36.1 KB

I am not sure why Cartesian X,Y,Z is needed and doing internet searches on the HTDP tool shows many just entering L,L,H and getting their transformations.

5

Hi @jaja6009,

Have you tried transforming ITRF2014 LLH to NAD83(2011) using these coordinates (E LON instead of W LON)?

Screenshot 2021-11-30 at 13.51.08
Screenshot 2021-11-30 at 13.51.081190Ɨ494 102 KB

I suppose it should work fine. If there are difficulties, Iā€™d suggest contacting NGS to check why it happens. Alternatively, you can try to transform the coordinates in a GIS app.

1 Like
7

I emailed NGS and now feel stupid.
The application assumes that all longitudes are west, so if the -74 xx xx.xxxxx is entered without the negative sign it works fine.

Thank you for your help!

9

Hi @jaja6009,

No one is immune to such mistakes, so thanks for posting the solution here! It can help other users to figure it out.

11

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.