# EarthCARE demo product import failure with HARP 1.23, works with 1.21

**URL:** https://forum.atmospherictoolbox.org/t/earthcare-demo-product-import-failure-with-harp-1-23-works-with-1-21/823
**Category:** HARP
**Tags:** python
**Created:** [September 20, 2024, 12:46am UTC](https://forum.atmospherictoolbox.org/t/earthcare-demo-product-import-failure-with-harp-1-23-works-with-1-21/823 "2024-09-20T00:46:52Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![acorreia](https://forum.atmospherictoolbox.org/letter_avatar_proxy/v4/letter/a/bc79bd/32.png) [@acorreia](https://forum.atmospherictoolbox.org/u/acorreia)
#### Post date: [September 20, 2024, 12:46am UTC](https://forum.atmospherictoolbox.org/t/earthcare-demo-product-import-failure-with-harp-1-23-works-with-1-21/823/1 "2024-09-20T00:46:52Z")

</div>

I’m using HARP 1.23 to import some EarthCARE demo products, downloaded directly from Zenodo at: [https://zenodo.org/records/7728948](https://zenodo.org/records/7728948)  
The MSI\_AOT\_2A product file was imported without any issue. However, trying to import the ATL\_AER\_2A product in a Linux box gives out the error message: “CLibraryError: record does not contain a field named ‘geoid\_offset’”. Downgrading HARP to version 1.21 allowed importing the file without errors. Can you please advise on this workaround? Is it possible future HARP releases will have addressed this issue?  
-Thanks

---

<div class="post-metadata">

### Author: ![sander.niemeijer](https://forum.atmospherictoolbox.org/user_avatar/forum.atmospherictoolbox.org/sander.niemeijer/32/5_2.png) [@sander.niemeijer](https://forum.atmospherictoolbox.org/u/sander.niemeijer)
#### Post date: [September 20, 2024, 8:35am UTC](https://forum.atmospherictoolbox.org/t/earthcare-demo-product-import-failure-with-harp-1-23-works-with-1-21/823/2 "2024-09-20T08:35:16Z")

</div>

Note that the EarthCARE example data from March 2023 is outdated and no longer reflects the format that is used for launch. Some small changes were introduced earlier this year, among which the introduction of a `geoid_offset` parameter that allows calculating heights as proper `altitudes`.  
I don’t believe example data for this updated format was made available publicly. You would have to check with ESA on this.  
The new data was shared with the cal/val teams that are responsible for checking the data quality during the commissioning phase, and we have been able to update our toolset already to support these teams.  
So, in short, HARP should already be up to date to allow you to access the EarthCARE data once it becomes public.

---

<div class="post-metadata">

### Author: ![acorreia](https://forum.atmospherictoolbox.org/letter_avatar_proxy/v4/letter/a/bc79bd/32.png) [@acorreia](https://forum.atmospherictoolbox.org/u/acorreia)
#### Post date: [September 20, 2024, 12:47pm UTC](https://forum.atmospherictoolbox.org/t/earthcare-demo-product-import-failure-with-harp-1-23-works-with-1-21/823/3 "2024-09-20T12:47:30Z")

</div>

Thanks a lot for the prompt reply. I’m glad to know HARP will be good to go once EarthCARE data becomes public.  
-Cheers