Forum

Thank you for letting us know of this second error; we will make note of it as well.

Hi Thomas, Thank you for your post. We have verified that this issue occurs with the netCDF4 library and have informed the TEMPO Science Team. At this time, our suggested workaround is to use the h5py library, in which this error has not been seen to occur. For example, "h5py.File(filename, 'r'...

Hello,

Thank you for your question. The TEMPO V03 L3 O3Tot does not contain a quality flag variable (the TEMPO V03 L2 O3Tot does contain a quality flag). However, the TEMPO Science Team is considering adding the quality flag from L2 to L3 for future versions.

Hello, We recommend using the TEMPO L2 data as a polygon in a GIS system (using the 4 pixel corners) to keep an accurate representation of the coverage area. Converting the TEMPO L2 data to a gridded raster requires pixels to be averaged when more then one value falls within a grid box. The other op...

Hello, thank you for your question regarding using TEMPO data in GIS applications. TEMPO Level 3 gridded products are hourly data. Currently, we have an image service for TEMPO gridded L3 NO2 data; this service can be accessed here (https://www.arcgis.com/home/item.html?id=6a1bdd0c076d499da69e867732...

This python snippet can be used to flatten a TEMPO file, if you would like to try it: import xarray as xr input_name="Path/To/NetCDF/File" output_name=input_name + ".flattened.nc4" ds0 = xr.open_dataset(input_name) # List of groups in the file (TEMPO L2 specific) for gn in ['geol...

Thank you for providing additional information. We have been investigating the QGIS documentation as well as the TEMPO data. At this point in time, my assumption is that QGIS is not reading the data from the grouped variables in the TEMPO netcdf 4 files correctly. We were able to use python to flatt...

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 N...

Thank you for your post and we are glad to hear you enjoyed the TEMPO Earthdata webinar! Can you please confirm that you are using TEMPO V03 beta data? Is there a specific collection (e.g., NO2 L3, formaldehyde (HCHO) L2) you are working with? The TEMPO V03 data is in WGS 1984 (CRS: 4326). Please ap...

Thank you for your question about the TEMPO data. Yes, the CRS is WGS84 (EPSG 4326). If you review the global attributes of a granule, you should see an entry for the crs:

:geospatial_bounds_crs = "EPSG:4326";

Please let us know if there are further questions we can assist with.