https://issues.qgis.org/https://issues.qgis.org/favicon.ico2015-04-09T22:09:38ZQGIS Issue TrackingQGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=603922015-04-09T22:09:38ZPaolo Cavallinicavallini@faunalia.it
<ul></ul>My preference:
<ul>
<li>name reflecting the command (e.g. Buffer, Dissolved, Reprojected, etc.)</li>
<li>avoid padding words like Output, Layer, Raster, Grid, etc.</li>
</ul> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=603942015-04-09T22:41:18ZPaolo Cavallinicavallini@faunalia.it
<ul><li><strong>Subject</strong> changed from <i>Processing: bettern naming structure for output</i> to <i>Processing: better naming structure for output</i></li></ul> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=603952015-04-09T22:41:49ZPaolo Cavallinicavallini@faunalia.it
<ul></ul><p>Mostly done for GDAL (ogr still to be done)</p> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=604072015-04-10T03:50:37ZAlexander Bruy
<ul></ul><p>AFAIK Processing assigns names to the outputs based on the name of the output parameter or using name of the output file (there is an option in the Processing settings for this).</p>
<p>Of course we can edit all algorithms and change labels for outputs, but IMO this is not optimal solution as some algorithms produce multiple outputs and it may be difficult to find short and meaningful names for them. Maybe some generic approach can be used, for example using combination from algorithm and output name, or output name + file name.</p> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=604082015-04-10T03:59:40ZPaolo Cavallinicavallini@faunalia.it
<ul></ul>I am talking about labels, sorry for the confusion. For labels we are not forced to be very short. I tried with GDAL and some SAGA commands, and I did not find difficult to give understandable names.<br />The problem is IMHO twofold:
<ul>
<li>calling a resulting raster in many different and uninformative ways (e.g. Raster, Output, Grid, Layer, etc.) is confusing and does not look nice</li>
<li>more substantially, it is difficult for the user to select one of the results of previous analyses as an input for further ones, if there is no clue about the origin from the name.<br />Please have a look to my recent commits, I believe the situation is much more clear now.<br />I do not think an automatic approach can give very good results; the main disadvantage of my proposal it that it takes some times to fix all the output names in a coherent manner.</li>
</ul> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=606722015-04-27T22:39:04ZVictor Olayavolayaf@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Yes, definitely the labels can be changed, and that won't break anything in the execution of algorithms.</p>
<p>As you say, it's a tedious task and requires time, but +1 fro mme if you feel like changing any of them for a better name</p> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=607132015-04-28T06:56:53ZPaolo Cavallinicavallini@faunalia.it
<ul></ul><p>Glad you agree. Have you checked what I have done so far? Agreed with that? Main stuff missing is GRASS, where both 6 and 7 should be updated.</p> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=619632015-06-07T02:04:38ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Category</strong> changed from <i>94</i> to <i>Processing/Core</i></li></ul> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=665222015-12-20T08:39:00ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=781122017-04-30T23:07:20ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Regression?</strong> set to <i>No</i></li><li><strong>Easy fix?</strong> set to <i>No</i></li></ul> QGIS Application - Bug report #12542: Processing: better naming structure for outputhttps://issues.qgis.org/issues/12542?journal_id=885112018-03-07T16:48:03ZPaolo Cavallinicavallini@faunalia.it
<ul><li><strong>Assignee</strong> deleted (<del><i>Victor Olaya</i></del>)</li><li><strong>Resolution</strong> set to <i>worksforme</i></li><li><strong>Affected QGIS version</strong> changed from <i>2.8.1</i> to <i>3.0.0</i></li><li><strong>Description</strong> updated (<a href="/journals/diff/88511?detail_id=77407" title="View differences">diff</a>)</li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Seems good enough now. Feel free to reopen if not.</p>