Hello,
We have been looking into this issue. I am able to replicate your same error using the TEMPO V03 L3 NO2 product. The TEMPO data is a NetCDF4 with grouped/hierarchical variables (e.g., most of the variables are not at the root/home level of the file, but are instead in sub-groups). In the L3 NO2, there is one variable "weight" that is at the root level of the file; for this variable, once I import the file into QGIS (Layer > Data Source Manager > Raster), and set the CRS to 4326, this one variable appears in the correct location over North America. However, if I import any of the other variables (e.g., product/vertical_column_troposphere), setting the CRS is not sufficient to correctly display the data. In addition, when I look at the properties>information for these two variables, weight has a origin and pixel size listed, while the product/vertical_column_troposphere does not. This leads me to believe that QGIS is not reading the grouped variables in the NetCDF correctly. Using the warp tool, I can set the CRS for the product/vertical_column_troposphere to 4326 and the layer does appear correctly in the map viewer; however, in my initial tests, it looks like there may be some data loss due to the interpolation occurring (e.g., the min/max of the reprojected data are not the same as in the original). While I think I may have found the cause of this issue, I have yet to find a great solution; however, we are still looking into this.
Can you provide any more details about your use case--which data products you are using and how you would like to process/apply them? We might be able to assist in finding an alternate solution as well.
Thanks,
Georgina
We have been looking into this issue. I am able to replicate your same error using the TEMPO V03 L3 NO2 product. The TEMPO data is a NetCDF4 with grouped/hierarchical variables (e.g., most of the variables are not at the root/home level of the file, but are instead in sub-groups). In the L3 NO2, there is one variable "weight" that is at the root level of the file; for this variable, once I import the file into QGIS (Layer > Data Source Manager > Raster), and set the CRS to 4326, this one variable appears in the correct location over North America. However, if I import any of the other variables (e.g., product/vertical_column_troposphere), setting the CRS is not sufficient to correctly display the data. In addition, when I look at the properties>information for these two variables, weight has a origin and pixel size listed, while the product/vertical_column_troposphere does not. This leads me to believe that QGIS is not reading the grouped variables in the NetCDF correctly. Using the warp tool, I can set the CRS for the product/vertical_column_troposphere to 4326 and the layer does appear correctly in the map viewer; however, in my initial tests, it looks like there may be some data loss due to the interpolation occurring (e.g., the min/max of the reprojected data are not the same as in the original). While I think I may have found the cause of this issue, I have yet to find a great solution; however, we are still looking into this.
Can you provide any more details about your use case--which data products you are using and how you would like to process/apply them? We might be able to assist in finding an alternate solution as well.
Thanks,
Georgina
Statistics: Posted by ASDC - ghayescrepps — Wed Jun 05, 2024 2:36 pm America/New_York