ER wrote: > Changing from ETRS89 to ETRF2000 could (potentially) negatively impact > workflows RDNAP to ETRS89 that behave properly currently. Anyway you can > simulate that by hacking your proj.db and modifying the existing records or > adding ones to see the effect of your changes
I will check that. This kind of risk is exactly the reason I asked the question here, before I send a request to EPSG. Thanks! ER wrote: > The null transformation between ETRS89 and ETRF2014 comes with the definition > of the datum ensemble ETRS89 (cf change > https://github.com/OSGeo/PROJ/issues/3263) The problem is not the null transformation between the ensemble and its members, but that the transformation route through ETRF2014 is recommended. In my opinion, the route trough ETRF2000 should be the default. Not only for the Netherlands but, for Europe in general. Thus ETRS89 -> ETRF2000 -> ITRF2000 -> ITRF2014 instead of ETRS89 -> ETRF2014 -> ITRF2014. What makes PROJ choose the latter? Jochem Disclaimer: De inhoud van deze e-mail is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Gebruik, openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan derden is niet toegestaan. Op al onze producten en diensten zijn onze algemene leveringsvoorwaarden van toepassing [https://www.kadaster.nl/algemene-leveringsvoorwaarden]. Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Our general terms and conditions of delivery apply to all our products and services [https://www.kadaster.com/general-terms-and-conditions].
_______________________________________________ PROJ mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/proj
