# Importing TM5-MP-DOMINO NO2 product: CLibraryError: record does not contain a field named 'satellite\_altitude'
**URL:** https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657
**Category:** HARP
**Tags:** sentinel-5p, python
**Created:** [June 25, 2023, 3:57am UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657 "2023-06-25T03:57:52Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@anhp95](https://forum.atmospherictoolbox.org/u/anhp95)
#### Post date: [June 25, 2023, 3:57am UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/1 "2023-06-25T03:57:52Z")
Hi,
I am trying to convert TEMIS TM5-MP-DOMINO NO2 product (from [https://www.temis.nl/](https://www.temis.nl/)) from L2 to L3 using harp.
I had this error when trying to import TM5-MP-DOMINO NO2 by harp.import\_product()
CLibraryError: record does not contain a field named 'satellite\_altitude
I would like to ask how to solve this problem.
Thanks.
---
### Author:  [@sander.niemeijer](https://forum.atmospherictoolbox.org/u/sander.niemeijer)
#### Post date: [June 25, 2023, 6:38pm UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/2 "2023-06-25T18:38:31Z")
You can get the official S5P NO2 products from the [S5P Hub](https://s5phub.copernicus.eu/) or new [dataspace service](https://dataspace.copernicus.eu/browser/). This is the only official source for this data and this is where you should get it.
Apparently KNMI also distributes the NO2 data via their TEMIS website, but in a reduced form (which is why the files have a ‘reduced’ postfix in the filename). This apparently removed variables that HARP is expecting to find, such as the satellite altitude. I will contact TEMIS/KNMI to ask why they are providing reduced data in this form, since it is hurting usability.
---
### Author:  [@anhp95](https://forum.atmospherictoolbox.org/u/anhp95)
#### Post date: [June 25, 2023, 6:43pm UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/3 "2023-06-25T18:43:27Z")
Hi Sander,
Thank you for your reply.
I got it.
---
### Author:  [@jvgent](https://forum.atmospherictoolbox.org/u/jvgent)
#### Post date: [January 30, 2024, 12:38pm UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/4 "2024-01-30T12:38:15Z")
Was there any follow-up on why KNMI is providing this format? It seems that there are still files in this ‘reduced’ format on TEMIS.
---
### Author:  [@sander.niemeijer](https://forum.atmospherictoolbox.org/u/sander.niemeijer)
#### Post date: [January 31, 2024, 2:49pm UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/5 "2024-01-31T14:49:20Z")
I raised the point with KNMI back then, but there was no final response on whether they would add the type of variables that we would expect with HARP. I’ve asked KNMI for an update.
---
### Author:  [@sander.niemeijer](https://forum.atmospherictoolbox.org/u/sander.niemeijer)
#### Post date: [February 29, 2024, 1:38pm UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/6 "2024-02-29T13:38:15Z")
I tried to contact KNMI again, but they are unresponsive. Perhaps you can try to contact them yourself?
---
### Author:  [@jvgent](https://forum.atmospherictoolbox.org/u/jvgent)
#### Post date: [March 1, 2024, 2:53pm UTC](https://forum.atmospherictoolbox.org/t/importing-tm5-mp-domino-no2-product-clibraryerror-record-does-not-contain-a-field-named-satellite-altitude/657/7 "2024-03-01T14:53:45Z")
Okay, I will. Thank you. For now I manage to HARP import the files by specifying the missing data variables in the `exclude` option of `harp.import_product()`