Re: [QGIS-Developer] Error with GRASS in Processing
Hi Nyall, > I can't confirm this - for me it works fine with r.drain and the param > values including the CRS. > > Can you post more steps to reproduce? The processing log would help. it seems the error is only Windows related, on Linux (both 3.0 and master work fine, in Win both 3.0 and master fail). The main error in the log is (I think) this: ERROR: Sorry <[EPSG:3003]> is not a valid option I will update the ticket with a complete log Thanks! Matteo ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
On 18 April 2018 at 04:38, Giovanni Manghiwrote: > Hi Nyall > >> It may not be right for the GRASS provider (it isn't - this is a bug), >> but for other providers it is, as this allows you to take advantage of >> Processing 3.0's new transparent reprojection. > > right, I forgot about that. But then why not having the coordinates > show in one field, and the value of the crs in a separate one? I agree that the point parameter widget isn't ideal. I'd love to see a PR improving this! Nyall ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
On 17 April 2018 at 18:23, matteowrote: > Hi devs, > > testing GRASS within Processing I noticed a small bug in all the > algorithms where you can add a map point coordinates with a click on the > map, like r.viewshed, r.drain > > If the users choose to click on the map to fill the box with the > coordinates of the point, the box is filled with both coordinates AND > the additional EPSG information, like: > > 348403.62350233766,4903994.026987238 [EPSG:32632] > > and this makes GRASS unhappy. > > Should I fill a ticket? I can't confirm this - for me it works fine with r.drain and the param values including the CRS. Can you post more steps to reproduce? The processing log would help. Nyall > > Thanks > > Matteo > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
Hi Nyall > It may not be right for the GRASS provider (it isn't - this is a bug), > but for other providers it is, as this allows you to take advantage of > Processing 3.0's new transparent reprojection. right, I forgot about that. But then why not having the coordinates show in one field, and the value of the crs in a separate one? cheers! -- G -- ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
Hi Nyall, > It may not be right for the GRASS provider (it isn't - this is a bug), > but for other providers it is, as this allows you to take advantage of > Processing 3.0's new transparent reprojection. > > E.g.: > > - canvas in 3857 > - layers in 4326 > - run the shortest path point-to-point alg, and pick a start/end > coordinate off the map. These will be in 3857 (respecting the canvas > crs), but when the alg runs it will reproject it to the required crs > (4326) without hassling the user and making them hate QGIS :) definitely yes. I'm loving this new CRS handling by Processing Thanks! Matteo ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
Hi Giovanni, thanks for the answer. I was not sure if this error was reported somewhere. BTW, done: https://issues.qgis.org/issues/18737 Thanks Matteo ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
On 17 April 2018 at 21:26, Giovanni Manghiwrote: > Hi Matteo, > >> Should I fill a ticket? > > of course you should (for this case as for any other regression/bug as this) > this is not right, and if fact it wasn't ever the case (to have also > the CRS info when using the pick coordinate tool). It may not be right for the GRASS provider (it isn't - this is a bug), but for other providers it is, as this allows you to take advantage of Processing 3.0's new transparent reprojection. E.g.: - canvas in 3857 - layers in 4326 - run the shortest path point-to-point alg, and pick a start/end coordinate off the map. These will be in 3857 (respecting the canvas crs), but when the alg runs it will reproject it to the required crs (4326) without hassling the user and making them hate QGIS :) Nyall ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Error with GRASS in Processing
Hi Matteo, > Should I fill a ticket? of course you should (for this case as for any other regression/bug as this) this is not right, and if fact it wasn't ever the case (to have also the CRS info when using the pick coordinate tool). thanks! -- G -- ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Error with GRASS in Processing
Hi devs, testing GRASS within Processing I noticed a small bug in all the algorithms where you can add a map point coordinates with a click on the map, like r.viewshed, r.drain If the users choose to click on the map to fill the box with the coordinates of the point, the box is filled with both coordinates AND the additional EPSG information, like: 348403.62350233766,4903994.026987238 [EPSG:32632] and this makes GRASS unhappy. Should I fill a ticket? Thanks Matteo ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer