Bug report #13148
Netcdf files : computational problem with the gdal tools
|Affected QGIS version:
|Pull Request or Patch supplied:
|Crashes QGIS or corrupts data:
|Copied to github as #:
I'm working at the oceanographic center in France near Toulouse and I'm developing a SIG interface suitable for oceanographers. We have chosen QGIS for it. All files are netcdf files and I use the plugin "netcdf browser" to display it. The netcdf files is composed by several metadata and especially by a scale factor data and an offset data. I realize that QGIS and the GDAL platform can not handle this data automatically. For example, when I want to convert the temperature in kelvin degree to celsius degree, I have to calculate manually the offset and the scale factor with the help of the raster calculator to see the good values of the variable's file (expression for example: ((temperature@1x scale factor)+offset)-273.15). If I only do the conversion ([email protected]), I have inconsistent values. I have to repeat this task each time I want to display or analyze any files. It is the same thing for the other physic variables (sea surface height (ssh) and speed current (U+V). Indeed, I have to create a new layer including the scale factor and the offset before making analysis.
I would like to know if the problem comes from the GDAL Tools or from netcdf files and if it can be solved by the community of QGIS?
Thank you for your kindness, I stand available if you need more information.
PS: I'm sorry because I wanted to send you a netcdf file but it is to heavy (150 Mo). Can I send you by an other way like Dropbox?
#1 Updated by Giovanni Manghi over 8 years ago
- Operating System deleted (
- Status changed from Open to Feedback
- Category changed from GDAL Tools to Rasters
- OS version deleted (
- Target version deleted (
Future Release - Nice to have)
Feel free to link a sample using dropbox, it would certainly help.
Then I would also try 2.8/2.10, of I'm not wrong there have been fixes/improvements since 2.6 regarding this format.
I would also raise the question on the user/developers mailing lists, to try understand where is the problem, gdal or qgis.