<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-size: 13px;color: rgb(0, 0, 0);font-family: arial, sans-serif;"><br>Hello Fabian, <br><br>I knew I had heard about the difference in the scale-difference values before but couldn't remember the details. I didn't turn up anything conclusive in the documents that I have access to. I'm on the EPSG subcommittee so I asked the chairperson, Roger Lott if he remembered. He sent the question off to Noel Zinn and Roel Nicolai. <br><br>Roger answered first: <br><br>The reality is that use of either of the two Helmert CTs or the above is unlikely to be appropriate, for two reasons. Principally because there was little civilian access to WGS72 (precise ephemeris) and that, despite CRS labelling, usage was really of WGS72BE. Secondly the DMA recommendation was not to use the direct shift but instead use WGS72>local>WGS84 using the abridged Molodenski parameters for local > WGS. <br><br>Noel turned up some documents. One no longer has a source/citation attached but discusses converting WGS-72 to proposed NAD-83 (PNAD-83) and proposed WGS-84. Conversion from NWL-9D to WGS-72 has a ds value of -0.8263 ppm. A transformation between NWL-9D (NSWC-9Z2) to PNAD-83/WGS-84 has a ds of -0.6 ppm. Concatenate them together and you get +0.2263 ppm for converting from WGS-72 to PNAD-83 or WGS-84. This page has a date of December 7, 1986. <br><br>Noel then retrieved the fact that a US DOD WGS 72 report from 1974 states that between NWL-9D and WGS 72, lists delta-r as -5.27 meters. Noel reports, note that 5.27 / 6378135 = 0.82626E-6. See ds from the first document. Now see DMA 8350.2, table 2.1, converting from NSWC 9Z-2 to WGS 84, which lists a ds of -0.6 ppm, which matches the 2nd transformation from the first document. <div><br></div><div>Noel also points out that Table 7.1 from 8350.2 (1997) lists 1.4 for delta-r between WGS 72 and WGS 84. That ends up 1.4 / 6378135 = 0.2194999E-6, or 0.219ppm to three digits. </div><div><br></div><div>Roel doesn't have access to his records right now, but stated, "two
agencies involved specifying the relationship between the two CRSs in different
ways: one gave it as a radial correction to the orbit parameters, the other as
the 7th parameter of a Helmert transformation. Working the radial correction into
a Helmert ds yields this small difference. When you calculate the effect on
point positioning height (= altitude), the difference was negligible at the
time. Some people made a big fuss about it at the time. I think I recommended
0.219 at the time because I found the four decimal places of 0.2263 over the
top."</div><div><br></div><div>Regards,</div><div>Melita</div><div><br></div><div>Melita Kennedy</div><div>Sr. Esri Product Specialist<br><br>-----Original Message-----<br>>From: proj-request@lists.osgeo.org<br>>Sent: Jun 17, 2019 12:00 PM<br>>To: proj@lists.osgeo.org<br>>Subject: PROJ Digest, Vol 8, Issue 8<br>><br>>----------------------------------------------------------------------<br>><br>>Message: 1<br>>Date: Mon, 17 Jun 2019 07:30:52 +0000<br>>From: "Lesparre, Jochem" <jochem.lesparre@kadaster.nl><br>>To: Fabian Gross <f.gross@sbp.de>, "proj@lists.osgeo.org"<br>> <proj@lists.osgeo.org><br>>Subject: Re: [PROJ] How to apply Helmert trafo <br>><br>>Dear Fabian,<br>><br>>For this transformation push/pop is not needed. That only makes sense in other situations, like when you use a geoid.<br>><br>>If the scale factor also differs from the primary source (EPSG is a secondary source), it should be adapted in the example to avoid confusion. If EPSG differs with the primary source, EPSG should be notified that there might be a mistake in their registry.<br>><br>>Kind regards, Jochem<br>><br>>From: PROJ <proj-bounces@lists.osgeo.org> On Behalf Of Fabian Gross<br>>Sent: Friday, June 14, 2019 3:41 PM<br>>To: proj@lists.osgeo.org<br>>Subject: [PROJ] How to apply Helmert trafo<br>><br>>Dear proj-members,<br>><br>>I would like to apply a Helmert trafo as part of a datum shift.<br>>The example follows the EPSG geomatics guidance 7/2 (report 373-7-2):<br>><br>>From WGS72 (4984) -> WGS84 (4978).<br>><br>>There are 2 issues:<br>>1. How to apply Helmert-Trafo? I.e.<br>><br>> * with or<br>> * without the push/pop of the ellipsoidal height.<br>>Only if it is not pushed/popped do the values fit to the reference and the direct/naive implementation of Helmert.<br>>2. The scale parameters in the example (0.219) and the EPSG catalogue of pyproj (0.2263) do not agree.<br>><br>>The attached file has the test case.<br>><br>><br>>Kind regards<br>><br>>Fabian Gross<br>>Telefon +49 (711) 648 71-995<br>>_________________________________________________<br>>sbp<br>>schlaich<br>>bergermann partner<br>><br>>Beratende Ingenieure<br>>für erneuerbare Energie<br>><br>>Stuttgart . Berlin . New York<br>>São Paulo . Shanghai . Paris<br>><br>>sbp sonne gmbh<br>><br>>Markus Balz Dipl.Ing. (FH)<br>>Andreas Keil Dipl.Ing.<br>><br>>Schwabstrasse 43<br>>70197 Stuttgart<br>>Telefon +49 (711) 648 71-0<br>><br>>www.sbp.de<http: www.sbp.de=""><br>>_________________________________________________<br></http:></proj-bounces@lists.osgeo.org></proj@lists.osgeo.org></f.gross@sbp.de></jochem.lesparre@kadaster.nl></div></div></body></html>