Even Rouault <[email protected]> writes: > oh.... so I was wrong and you've spotted the reason for what Greg > notices. So this is (was) a GDAL 3.3 specific bug (3.2 is fine). > > GDAL should have passed HUGE_VAL when no explicit time is specified, > which would be interpreted by PROJ as ignoring the time-dependent > parts (or equivalently using the reference epoch of the > transformation, which nullifies the effect of those time-dependent > parts), but it incorrectly passes 0 currently > > With fix queued in https://github.com/OSGeo/gdal/pull/3738
I applied that patch to beta1 and reinstalled and now the output seems correct. Thanks for the quick analysis and fix. Probably a proj issue, but it would seem that using an epoch of 0 (== 1 BCE?) is well outside the domain of validity of the transform velocity models. But it's hard to draw the line and not really a useful exercise.
signature.asc
Description: PGP signature
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
