On vendredi 1 septembre 2017 20:42:34 CEST Andre Joost wrote:
> Am 01.09.2017 um 20:14 schrieb Even Rouault:
> >> ogr2ogr -s_srs EPSG:4326 -t_srs "+proj=lcc +lat_1=13.316667
> >> +lat_2=14.25 +lat_0=13.78 +lon_0=-89 +x_0=50 +y_0=295809.184
> >> +k_0=0.6704 +ellps=clrk66 +units=m
Am 01.09.2017 um 20:14 schrieb Even Rouault:
ogr2ogr -s_srs EPSG:4326 -t_srs "+proj=lcc +lat_1=13.316667
+lat_2=14.25 +lat_0=13.78 +lon_0=-89 +x_0=50 +y_0=295809.184
+k_0=0.6704 +ellps=clrk66 +units=m +no_defs
+towgs84=0,125,194,0,0,0,0 +wktext" LimitesNAD27.shp dptoA_WGS_
> This seems to work arbitrary.
Not really. GDAL is an abstraction of a lot of imperfections, so losses can
happen for various
(more or less well documented) reasons each time you export & import.
>
> gdalwarp -overwrite -dstnodata 0 -s_srs EPSG:3857 -t_srs "+proj=lcc
> +lat_1=13.31666
Am 25.08.2017 um 13:52 schrieb Even Rouault:
For unsupported projections, add +wktext. A dummy WKT representation
is then built that captures the full proj.4 string in a EXTENSION
node. Can also serve for supported projections if you want to
overrite the WKT -> proj.4 string conversion done by
