Am 06.08.2017 um 11:07 schrieb Erik Josefsson:
It seems I need an interpreter of the output from ogrinfo that can
translate that rather complex output into a simple EPSG-code.
gdalsrsinfo has an easier output, but will not reveal EPSG codes either.
One reason is because many EPSG codes
Am 06.08.2017 um 10:34 schrieb Erik Josefsson:
Here's the loop where it happens (please note that I expect ogr2ogr to
read and write to the same shpfile):
I don't think this is possible. It is safe to write to a temp file, wait
for ogr2ogr to finish, then overwrite the input file with the
Thank you very much Andre.
I'm still puzzled how I can tell ogr2ogr to convert the coordinates
themselves along with the conversion of the CRS (e.g. from EPSG:3008 to
EPSG:3006).
But maybe that is because I have not yet managed to retrieve from the
.shp and .prj files the information that a
Thank you Zoltan!
On 06/08/17 07:05, Siki Zoltan wrote:
> Dear Erik,
>
> if there is a .prj file to your shape and it is valid you need not to
> use -s_srs.
Yes, there is a .prj file to each .shp (in all zip-archives).
> Only one of -a_srs and -t_srs is neccessary in your case, if
> you want
Am 06.08.2017 um 02:22 schrieb Erik Josefsson:
Hello,
I have a handful of zip archives containing original shapefiles with
different coordinate reference systems (e.g. SGER:3008 and SGER:3021).
I want to extract and convert them all to SGER:3006 and thought that
ogr2ogr would do the job, but I
Dear Erik,
if there is a .prj file to your shape and it is valid you need not to use
-s_srs. Only one of -a_srs and -t_srs is neccessary in your case, if you
want to reproject coordinates use -t_srs. If you want only change the
projection but not the coordinates use -a_srs.
Best regards,
Hello,
I have a handful of zip archives containing original shapefiles with
different coordinate reference systems (e.g. SGER:3008 and SGER:3021).
I want to extract and convert them all to SGER:3006 and thought that
ogr2ogr would do the job, but I don't find intelligible instructions on
how to
