[Qgis-user] unexpected CRS behavior (GRASS)

[Stefan Blumentrath]

See also:
https://issues.qgis.org/issues/10137 and
https://issues.qgis.org/issues/14499 for the QGIS side of it.

And
https://trac.osgeo.org/grass/ticket/3262
https://trac.osgeo.org/grass/ticket/3193
on the GRASS side, maybe also related:
https://trac.osgeo.org/grass/ticket/2229

I did not check CRS handling in v.out.ogr though (which I guess Processing is using for vector data).
It could also be an issue in the way processing generates the location (e.g. without explicitly defining EPSG code, (but I did not look at the source code)... 

If QGIS would use v.external.out SRID of the output could be handled explicitly. But that approach might have drawbacks if tools can be chained in processing...

Cheers
Stefan

________________________________________
Von: Qgis-user <qgis-user-bounces at lists.osgeo.org> im Auftrag von Tobias Wendorff <tobias.wendorff at tu-dortmund.de>
Gesendet: Sonntag, 11. Juni 2017 09:02
An: Andre Joost
Cc: qgis-user at lists.osgeo.org
Betreff: Re: [Qgis-user] unexpected CRS behavior (GRASS)

Hi Andre,

nice to read from you here.

Am So, 11.06.2017, 07:56 schrieb Andre Joost:
> If you save the Linestring to a shapefile with EPSG:32632, it runs
> correctly.

Interesting :) Thanks for pointing this out.

> It seems that GRASS gets confused over the similar WKT definitions .

GRASS or QGIS? I didn't check the temporary shapefile, which gets
written. I'll do that soon.

Best regards,
Tobias

_______________________________________________
Qgis-user mailing list
Qgis-user at lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user