https://issues.qgis.org/https://issues.qgis.org/favicon.ico2015-01-29T01:27:32ZQGIS Issue TrackingQGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=589272015-01-29T01:27:32ZOlivier ATHIMONolivierisonline@gmail.com
<ul><li><strong>File</strong> <a href="/attachments/download/8344/QGIS_pb_lecture_grd.png">QGIS_pb_lecture_grd.png</a> added</li><li><strong>Target version</strong> changed from <i>Future Release - Nice to have</i> to <i>Future Release - High Priority</i></li></ul><p>Corruption...</p>
<p>QGIS don't show the real value of a pixel for grid named: "Northwood Numeric Grid Format .grd/.tab (*.grd *.GRD)", and used with MapInfo/Vertical Mapper.</p>
<p>When I open and read a .grd MapInfo file (created with Vertical Mapper) with QGIS 2.0 or QGIS 2.2, it displays four bands with the real value, not with the next version of QGIS...</p>
<p>The 3 first show the RGB values and the fourth gives the value of the matrix, namely the altitude to a vertical file.</p>
<p>Inside QGIS (2.7, 2.6.1, 2.6.0 and 2.4), 4th displayed value is a bad value, not the real value.</p>
<p>In addition, when making calculations with this file (.grd) and another (for example, a tiff file) QGIS seems to use the real values (not displayed) of the GRID. Then, it gives a good result for calculation... Not with the plugin "Profile Tool"...</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=589352015-01-29T05:35:09ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li><li><strong>Affected QGIS version</strong> changed from <i>2.6.1</i> to <i>master</i></li></ul><p>Could you please attach a sample dataset? thanks</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=589652015-01-30T02:56:44ZOlivier ATHIMONolivierisonline@gmail.com
<ul><li><strong>Assignee</strong> set to <i>Giovanni Manghi</i></li><li><strong>File</strong> <a href="/attachments/download/8349/MNT_Lidar_1m_Granges.zip">MNT_Lidar_1m_Granges.zip</a> added</li></ul><p>I attached the sample dataset (used for the previous picture).</p>
<p>This morning, i have tried to open it with QGIS 2.6.1 under Debian (Linux)... I have the same problem when i show values with button for information/interrogation => bad value, not real value! I suppose it gives the same problem for calculation.</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=589662015-01-30T02:57:49ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Operating System</strong> deleted (<del><i>Windows</i></del>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li><li><strong>Assignee</strong> deleted (<del><i>Giovanni Manghi</i></del>)</li><li><strong>OS version</strong> deleted (<del><i>Windows 7</i></del>)</li></ul> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=589812015-01-30T04:22:31ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Severe/Regression</i></li></ul> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=592122015-02-09T21:55:42ZMartin Dobiaswonder.sk@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Since QGIS 2.4 there is support for using band offset and scale as reported by GDAL. Indeed the band 4 has offset and scale defined:</p>
<pre>
$ gdalinfo /data/gis/tst-bug12075-band4/MNT_Lidar_1m_Granges.grd
[... omitted lines above ...]
Band 4 Block=2000x1 Type=Float32, ColorInterp=Undefined
NoData Value=-9.99999993381581251e+36
Offset: -6.38000011444092, Scale:0.000509811698468156
</pre>
<p>So the reported values (e.g. -6.378) seems to be the correct - according to the band's offset/scale. Can we close the bug?</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=592412015-02-10T01:43:15ZOlivier ATHIMONolivierisonline@gmail.com
<ul></ul><p>No... I am sorry. You can't close the bug.</p>
<p>I created a video with a query of a pixel with MapInfo 6.5/Vertical Mapper, MapInfo 12, QGIS 2.2 Valmiera, QGIS 2.6.1 Brighton and QGIS 2.7.0.94 (QGIS b35a596) to show you more the problem...</p>
<p><a class="external" href="https://www.youtube.com/watch?v=hnIbBdfcWLI&feature=youtu.be">https://www.youtube.com/watch?v=hnIbBdfcWLI&feature=youtu.be</a></p>
<p>I rewrite the text, shown in the video:</p>
<p>"the grid: MNT_Lidar_1m_Granges.grd (associated with MNT_Lidar_1m_Granges.tab)</p>
<p>1- Open the grid with MapInfo (version 6.5, a very old version) / Vertical Mapper.<br />Query a pixel in the same area <=> when Mapinfo read a pixel, it create an interpolation of the pixel around. So, if you are not exactly in the center, the value change a little but it is the real value.</p>
<p>2- Open the grid with MapInfo (version 12, a recent version), without Vertical Mapper<br />Query a pixel in the same area. You have too an interpolation value (real value)</p>
<p>3- Open the grid with QGIS 2.2.0 - Valmiera<br />Query a pixel in the same area <=> it is the real value (viewed too in GRASS GIS)<br />Use Grid Calculator, select band 4 and save it in GeoTiff.<br />Query a pixel in the same area <=> it is the real value</p>
<p>4- Open the grid with QGIS 2.6.1 - Brighton<br />Query a pixel in the same area <=> it is a bad value!<br />Use Grid Calculator, select band 4 and save it in GeoTiff.<br />Query a pixel in the same area <=> it is the real value</p>
<p>5- Open the grid with QGIS 2.7.0-94 (Master)<br />Query a pixel in the same area <=> it is a bad value!</p>
<p>Use Grid Calculator, select band 4 and save it in GeoTiff.<br />Query a pixel in the same area... => It is a NEW PROBLEM... Just 0 value...??? I am sorry...</p>
<p>Use "Saveas" in Raw Data (not image) => It is a bad value... from grd file<br />Or it is a 0 value from Geotiff created with grid calculator before...</p>
<p>Now, i hope that you understand the problem...</p>
<p>Thanks for your job.</p>
<p>QGIS is great!</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=593522015-02-12T07:59:46ZOlivier ATHIMONolivierisonline@gmail.com
<ul><li><strong>File</strong> <a href="/attachments/download/8416/Misreading_of_band_4_but_real_value_in_the_result_after_this_operation_with_raster_calculator_of_QGIS_until_2.6.1.jpg">Misreading_of_band_4_but_real_value_in_the_result_after_this_operation_with_raster_calculator_of_QGIS_until_2.6.1.jpg</a> added</li><li><strong>File</strong> <a href="/attachments/download/8417/Misreading_of_band_4_and_zero_value_in_the_result_after_this_operation_with_raster_calculator_of_QGIS_Master_2.7.jpg">Misreading_of_band_4_and_zero_value_in_the_result_after_this_operation_with_raster_calculator_of_QGIS_Master_2.7.jpg</a> added</li><li><strong>Assignee</strong> set to <i>Martin Dobias</i></li></ul><p>Hello,</p>
<p>I don't know if you have seen the previous video, but i put another here:</p>
<p><strong><a class="external" href="https://www.youtube.com/watch?v=ZCMV3PyfBc0">https://www.youtube.com/watch?v=ZCMV3PyfBc0</a></strong></p>
<p>to show you the (same) problem with Raster Calculator to do the simple operation to "export" the band 4: "QGIS change the values" of the GEOTIFF result...</p>
<p>In reality, QGIS put the RIGHT values in the OUTPUT file (GEOTIFF), where the query button gives a WRONG value (for the input GRD File / Northwood Numeric Grid Format with QGIS from 2.4 to 2.7)...</p>
<p>Except <strong>for QGIS Master 2.7</strong>, this one give 0 value (and wrong value) all over... <strong><= NEW PROBLEM...</strong></p>
<p>I add 2 pics of the simple operation realized with the raster calculator...<br />One (for QGIS until 2.6.1) gives the RIGHT VALUES in the result.<br />The other (for QGIS Master 2.7) gives 0 VALUES (WRONG VALUES) all over...</p>
<p><strong>Precision: everything was working with QGIS version 2.2... No misreading (with query button), and good result with raster calculator to save band 4 to a GEOTIFF file. The right value before (in the grd file) and after (in the GEOTIFF/.tiff file)</strong></p>
<p>Hope that you will find a solution...</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=593532015-02-12T08:40:56ZMartin Dobiaswonder.sk@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul><p>Then it looks like a bug in GDAL library - I have reported it here: <a href="http://trac.osgeo.org/gdal/ticket/5839" class="external">GDAL #5839</a></p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=593692015-02-12T23:23:26ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>Martin Dobias wrote:</p>
<blockquote>
<p>Then it looks like a bug in GDAL library - I have reported it here: <a class="external" href="http://trac.osgeo.org/gdal/ticket/5839">http://trac.osgeo.org/gdal/ticket/5839</a></p>
</blockquote>
<p>then closing this as upstream?</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=594372015-02-16T23:22:19ZMartin Dobiaswonder.sk@gmail.com
<ul><li><strong>Resolution</strong> set to <i>up/downstream</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Fixed in upstream (both GDAL trunk and 1.11 branch)</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=632992015-08-20T08:13:05ZOlivier ATHIMONolivierisonline@gmail.com
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li></ul><p><ins>With a raster dataname: "MNT.grd" with 4 bands (band1 : Red, band2: Green, band3: Blue, band4: altimetry)...</ins></p>
<p>It had been found that the problem was with the version of GDAL 1.11 ... Ewen Rouault (from GDAL) had after making changes to the GDAL library in Version 1.11.3... [[<a class="external" href="http://trac.osgeo.org/gdal/ticket/5839">http://trac.osgeo.org/gdal/ticket/5839</a>]]</p>
<p><strong>However, now, I have a doubt (though QGIS integrates GDAL 1.11.2 release)...</strong> Indeed, QGIS has seen other changes...</p>
<p>Version 2.8 is the successor to version 2.6 with the same problem (<strong>read error but problem solved by writing to the raster calculator by exporting the result of the expression: "MNT@4" in GeoTIFF format</strong>)...</p>
<p><ins><strong>In version 2.8 of QGIS, the GDAL library was 1.11.2 release. It is also present in version 2.10.</strong><br /></ins><br /><ins><strong>But now, reading and writing</strong> of "MNT@4" in size Geotiff give the same result, <strong>a false result in the two cases...</strong><br /></ins><br />I'll wait for version 2.12 (QGIS) that could possibly incorporate version 2 of the GDAL library ... <strong>but I have a doubt, however, that I consider useful to trace...</strong> If you ever want to check it.</p> QGIS Application - Bug report #12075: Misreading value from a .grd file created with MapInfo (Vertical Mapper)https://issues.qgis.org/issues/12075?journal_id=638732015-09-27T23:28:56ZOlivier ATHIMONolivierisonline@live.fr
<ul><li><strong>Target version</strong> deleted (<del><i>Future Release - High Priority</i></del>)</li><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li><li><strong>Assignee</strong> deleted (<del><i>Martin Dobias</i></del>)</li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>With the update of Gdal (in version 1.11.3), the data are effectively OK in QGIS 2.8.3, QGIS 2.10 and QGIS 2.11 (91e1554 for the future QGIS 2.12)...<br />Thanks at all.</p>