You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@sis.apache.org by MUELLER-SCHRAMM Gerd <ge...@hexagon.com> on 2020/09/01 07:38:26 UTC
RE: Transformation from EPSG:2154 to EPSG:28992
Hi Matrin,
Thanks for the fix. I've tried it and it works nice.
Regards,
Gerd
Gerd Müller-Schramm
Software Developer, GeoMedia Smart Client Kommunal
Hexagon Geospatial
Hexagon
T: +49 (0) 89 96 106 4117
E: gerd.mueller-schramm@hexagon.com
Office: HxGN Safety & Infrastructure GmbH
Wittenberger Straße 15B
04129 Leipzig
Germany
hexagon.com
-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.com>
Sent: Montag, 31. August 2020 23:12
To: user@sis.apache.org
Subject: Re: Transformation from EPSG:2154 to EPSG:28992
This email is not from Hexagon’s Office 365 instance. Please be careful while clicking links, opening attachments, or replying to this email.
Hello Gerd
The proposed fix has been pushed. It can be tested with SIS 1.1-SNAPSHOT on the following Maven repository:
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Fgroups%2Fsnapshots%2F&data=02%7C01%7C%7C89ad2ec3a346494cc7b508d84df29192%7C1b16ab3eb8f64fe39f3e2db7fe549f6a%7C0%7C0%7C637345051522319770&sdata=oTg4vi9H1cWVlpLw99BqsLwB5%2F4NQWfEgQ17om12Lo0%3D&reserved=0
Regards,
Martin
Re: Transformation from EPSG:2154 to EPSG:28992
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Le 01/09/2020 à 09:38, MUELLER-SCHRAMM Gerd a écrit :
> Thanks for the fix. I've tried it and it works nice.
>
Thanks for letting us know. I forgot to add that the fix will report an
accuracy of 3000 metres instead of 100 metres if the EPSG database is
not installed, because otherwise it has no way to know the datum domain
of validity (unless WKT 2 is used instead of WKT 1).
Martin