Yes that's not obvious but internally SRS in GDAL are not modelled as a
proj.4 string, but as WKT. So there's a importFromProj4() and
exportFromProj4(), and >possible loss can happen when some concepts
cannot be matched exactly.
Found these two that not even with the +wktext agree
On vendredi 25 août 2017 18:25:36 CEST Joaquim Luis wrote:
> OK, understood thanks. But got confused too. Why would a GDAL port of a
> proj.4 string do a different thing than the coded in the proj.4 string?
>
Yes that's not obvious but internally SRS in GDAL are not modelled as a proj.4
string,
OK, understood thanks. But got confused too. Why would a GDAL port of a
proj.4 string do a different thing than the coded in the proj.4 string?
Found these two that not even with the +wktext agree
gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aeqd +ellps=WGS84 +units=m
+wktext"
4.897 52.371
Am 25.08.2017 um 13:52 schrieb Even Rouault:
And also found some that do no agree between GDAL and proj. For
example
echo 4.897 52.371 | proj +proj=vandg +ellps=WGS84 +units=m
489005.93 6431581.02
gdaltransform -s_srs EPSG:4326 -t_srs "+proj=vandg +ellps=WGS84
+units=m" 4.897 52.371 4884
Joaquim,
>
> I'm implementing Proj.4 in GMT via GDAL and now, in the the testing stage,
> I'm using data from
>
> https://github.com/Beman/boost-trunk-git-svn/blob/master/libs/geometry/test_
> extensions/gis/projections/projections.cpp#L121
>
> but to my surprise lots of projections are not imp
Hello,
I am using Windows 7 x64, GDAL v2.3.0dev r39906 from
http://www.gisinternals.com/development.php.
Input:https://ufile.io/i5oj3
Output: https://uploadfiles.io/
Command line:
ogr2ogr.exe -f "GPKG" "C:\Temp\output.gpkg" "C:\Temp\input.sqlite" -overwrite
-lco "SPATIAL_INDEX=NO" -lco "GEO