https://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-04-24T17:37:56ZQGIS Issue TrackingQGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1042042019-04-24T17:37:56ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Can you attach sample data?</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1042052019-04-24T18:11:43ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>Giovanni Manghi wrote:</p>
<blockquote>
<p>Can you attach sample data?</p>
</blockquote>
<p>I got one file and it’s to big.</p>
<p>I think the problem can be that there’s no coordinate system info in the file and it works in GRASS because you set up a predefined file and coordinate system that GRASS can assume is the same system as the file. If it was possible to tell QGIS what coordinate system to assume is right then it might work.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1042062019-04-24T18:13:31ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>So I guess the problem is the lack of spatial reference in the file.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1042072019-04-24T19:14:20ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><blockquote>
<p>I got one file and it’s to big.</p>
</blockquote>
<p>link?</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1042092019-04-25T07:34:27ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>Giovanni Manghi wrote:</p>
<blockquote><blockquote>
<p>I got one file and it’s to big.</p>
</blockquote>
<p>link?</p>
</blockquote>
<p><a class="external" href="https://sprend.com/download?C=e892a43de33f49b79b63c421e4a03ab8">https://sprend.com/download?C=e892a43de33f49b79b63c421e4a03ab8</a></p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1043292019-05-01T16:42:14ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>What CRS do you use to create your GRASS mapset/location where this data import correctly?</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1043412019-05-02T05:47:20ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>Giovanni Manghi wrote:</p>
<blockquote>
<p>What CRS do you use to create your GRASS mapset/location where this data import correctly?</p>
</blockquote>
<p>CRS<br />EPSG:3011 - SWEREF99 18 00 - Projected</p>
<p>I sett GRASS not to assume any CRS of the data.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1043502019-05-02T08:20:06ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><blockquote>
<p>I sett GRASS not to assume any CRS of the data.</p>
</blockquote>
<p>that is not how Processing works when using GRASS tools: as far as I remember a temporary location/mapset is created on the fly while importing the data, and the CRS used is derived from the data itself. Is this the rule for any lidar data, they do not have an intrinsic CRS?</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1043922019-05-02T21:53:36ZOlivier ATHIMONolivierisonline@live.fr
<ul></ul><p>Is it the same problem than i have ? => <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/21905" title="Functions of GRASS do not work in the Processing for QGIS 3.4.7/3.6.2... but work in the Processi... (Closed)">#21905</a></p>
<p>Before we could use functions of GRASS in Processing/GRASS by using the shortcut "QGIS Desktop"? But now, functions of Processing/GRASS only work by using the shortcut "QGIS Desktop with GRASS"...</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044012019-05-03T10:44:54ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>Giovanni Manghi wrote:</p>
<blockquote><blockquote>
<p>I sett GRASS not to assume any CRS of the data.</p>
</blockquote>
<p>that is not how Processing works when using GRASS tools: as far as I remember a temporary location/mapset is created on the fly while importing the data, and the CRS used is derived from the data itself. Is this the rule for any lidar data, they do not have an intrinsic CRS?</p>
</blockquote>
<p>I think the problem can be that Grass att least needs to know the project CRS to convert the LASfile. Do QGIS create a temporary database/project when processing?</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044212019-05-03T17:50:47ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>Olivier ATHIMON wrote:</p>
<blockquote>
<p>Is it the same problem than i have ? => <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/21905" title="Functions of GRASS do not work in the Processing for QGIS 3.4.7/3.6.2... but work in the Processi... (Closed)">#21905</a></p>
</blockquote>
<p>no, I think the above ticket was already given and answer.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044222019-05-03T17:55:14ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><blockquote>
<p>Do QGIS create a temporary database/project when processing?</p>
</blockquote>
<p>yes, it creates on the fly a mapset/location where it (on the fly) imports the input data, then it process it and export out from the location/mapset. I think it uses the CRS of the input to define the projection for the mapset/location.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044262019-05-03T18:04:11ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>Giovanni Manghi wrote:</p>
<blockquote><blockquote>
<p>Do QGIS create a temporary database/project when processing?</p>
</blockquote>
<p>yes, it creates on the fly a mapset/location where it (on the fly) imports the input data, then it process it and export out from the location/mapset. I think it uses the CRS of the input to define the projection for the mapset/location.</p>
</blockquote>
<p>Maybe you could have a optional setting for overriding the files crs?</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044272019-05-03T18:05:19ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><blockquote>
<p>Maybe you could have a optional setting for overriding the files crs?</p>
</blockquote>
<p>that would be a feature request.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044282019-05-03T18:06:49ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>Giovanni Manghi wrote:</p>
<blockquote><blockquote>
<p>Maybe you could have a optional setting for overriding the files crs?</p>
</blockquote>
<p>that would be a feature request.</p>
</blockquote>
<p>Or a solution to the bug.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044302019-05-03T18:09:40ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Subject</strong> changed from <i>GRASS r.in.lidar fail i QGIS but works in plain GRASS</i> to <i>GRASS r.in.lidar fails in QGIS but works in native GRASS</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li><li><strong>Operating System</strong> deleted (<del><i>Win 10</i></del>)</li></ul> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044322019-05-03T18:15:27ZAndreas Olssonandreas8001@hotmail.com
<ul></ul><p>“<br />-o<br />Override projection check (use current location's projection)<br />Assume that the dataset has same projection as the current location<br />“<br />This option is also in QGIS for r.in.lidar but it needs to know the project crs to actually work.</p> QGIS Application - Bug report #21925: GRASS r.in.lidar fails in QGIS but works in native GRASShttps://issues.qgis.org/issues/21925?journal_id=1044332019-05-03T18:20:16ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><blockquote>
<p>This option is also in QGIS for r.in.lidar but it needs to know the project crs to actually work.</p>
</blockquote>
<p>That GRASS options assumes that the data CRS is the same as the mapset/location (that aleady exist). In QGIS the CRS for mapset/location (that does not exist yet) is derived from the data being used as input (again, I think bit not 100% sure).</p>