Hi Pradeep,
to calculate the destination coordinates of the two points, you can call
gdaltransform with the same gcp parameters as gdal_translate und gdalwarp
before. Gdal uses the same algorithm for transforming raster and vector data.
Martin
Von meinem iPhone gesendet
Am 26.02.2020 um 17:00
Hi Jan,
I had a similar problem, which was solved by normalizing the TPS equations. The
patch
(https://github.com/OSGeo/gdal/commit/c85c58ac781ef781cd126006d91cb5eed2dd53e2)
is included in gdal versions >= 2.4. This may help you as well.
Martin
-Ursprüngliche Nachricht-
Von: gdal-dev
Hi,
trying to transform from a "Miller WGS84" coordinate system, whose exact
definition I don't know I found that the following two transformations yield
the same result, regardless of whether +R_A is present or not.
$ echo "781046.71 6190010.02" | gdaltransform -s_srs "+proj=mill +lat_0=0
+lo
Hi,
motivated by the simple transformation to improve the quality of the TPS
transformation I had a look at the polynomial counterpart. It turned out that
the quality of the approximation not always improves with increasing order of
the polynomial as it should be case. So I tried the same trick
>
>On mardi 27 juin 2017 07:34:59 CEST Rahkonen Jukka (MML) wrote:
>> Hi,
>>
>> There is a well written question in gis.stackexchange about how the -tps
>> option in ogr2ogr behaves
>> https://gis.stackexchange.com/questions/245391/ogr2org-tps-spline-method-cr
>> eates-progressive-error
>>
>> Does