Re: [Qgis-user] unexpected CRS behavior (GRASS)
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-boun...@lists.osgeo.org> im Auftrag von Tobias Wendorff <tobias.wendo...@tu-dortmund.de> Gesendet: Sonntag, 11. Juni 2017 09:02 An: Andre Joost Cc: qgis-user@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@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
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@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] unexpected CRS behavior (GRASS)
Am 11.06.2017 um 01:35 schrieb Tobias Wendorff: Hi there! I'm experiencing an unexpected behavior. Before filing a bug, could anyone please test this? I'm using v2.18.9-10, but I also had this problem on normal stable; additionally, I'm using GRASS 7.2.1. I've drawn a random linestring across Germany in EPSG:25832 (UTM32N): LineString (452926.428 5430258.436, 474353.217 5556034.254, 651518.642 5480403.767, 768696.380 5642150.589, 716125.982 5713907.693, 797502.108 5831380.482). Let's try the GRASS tool "v.split.vert". I've set the numbers of vertices to "2" and I'm outputting the result to temporary layer. The temp layer suddenly gets a custom CRS: USER:10 and OTF gets activated. The CRS is equal to UTM32N, but I guess, this behavior isn't correct... If you save the Linestring to a shapefile with EPSG:32632, it runs correctly. It seems that GRASS gets confused over the similar WKT definitions . HTH, André Joost ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] unexpected CRS behavior (GRASS)
Hi there! I'm experiencing an unexpected behavior. Before filing a bug, could anyone please test this? I'm using v2.18.9-10, but I also had this problem on normal stable; additionally, I'm using GRASS 7.2.1. I've drawn a random linestring across Germany in EPSG:25832 (UTM32N): LineString (452926.428 5430258.436, 474353.217 5556034.254, 651518.642 5480403.767, 768696.380 5642150.589, 716125.982 5713907.693, 797502.108 5831380.482). Let's try the GRASS tool "v.split.vert". I've set the numbers of vertices to "2" and I'm outputting the result to temporary layer. The temp layer suddenly gets a custom CRS: USER:10 and OTF gets activated. The CRS is equal to UTM32N, but I guess, this behavior isn't correct... Best regards, Tobias ___ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
