# Height in IODA GNSS-RO files

**URL:** <https://forums.jcsda.org/t/height-in-ioda-gnss-ro-files/774>\
**Category:** JEDI\
**Created:** [November 3, 2026, 11:17pm UTC](https://forums.jcsda.org/t/height-in-ioda-gnss-ro-files/774 "2026-11-03T23:17:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjm](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@mjm](https://forums.jcsda.org/u/mjm)\
**Post date:** [November 3, 2026, 11:17pm UTC](https://forums.jcsda.org/t/height-in-ioda-gnss-ro-files/774/1 "2026-11-03T23:17:25Z")

</div>

I have one small point I wanted to bring up on the format of the IODA GNSS-RO obsevation files.

These files have a variable called “height” with the following metadata:  
float height(Location) ;  
height:longname = “Geometric altitude” ;  
height:units = “m” ;  
height:\_FillValue = 2.147484e+09f ;

_I think it would reduce confusion with users if you added the words “above geoid” to the longname_. I was confused and had to run some tests to confirm it was actually above the geoid and not the ellipsoid. I understand its a tiny difference but it would be more clear to the user to indicate the referece being the geiod.

To be clear I am creating these file using the gnssro\_bufr2ioda.f90 utility.

Not sure who to tag here, do you know Hailing?  
@hailingz

~mjm

---

<div class="post-metadata">

**Author:** ![stephenh](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.jcsda.org/stephenh/32/28_2.png) [@stephenh](https://forums.jcsda.org/u/stephenh)\
**Post date:** [November 10, 2026, 9:00pm UTC](https://forums.jcsda.org/t/height-in-ioda-gnss-ro-files/774/2 "2026-11-10T21:00:50Z")

</div>

Hi @mjm

This is great feedback. Could you submit a github issue to the jcsda-internal/ioda-converters repo with this suggestion? I think that would help make this visible to someone who could then help with this update to the gnssro\_bufr2ioda.f90 converter.

Thanks!

---

<div class="post-metadata">

**Author:** ![mjm](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@mjm](https://forums.jcsda.org/u/mjm)\
**Post date:** [November 11, 2026, 6:04pm UTC](https://forums.jcsda.org/t/height-in-ioda-gnss-ro-files/774/3 "2026-11-11T18:04:51Z")

</div>

> [@mjm](#):
>
> have one small point I wanted to bring up on the format of the IODA GNSS-RO obsevation files.
> 
> These files have a variable called “height” with the following metadata:  
> float height(Location) ;  
> height:longname = “Geometric altitude” ;  
> height:units = “m” ;  
> height:\_FillValue = 2.147484e+09f ;
> 
> _I think it would reduce confusion with users if you added the words “above geoid” to the longname_. I was confused and had to run some tests to confirm it was actually above the geoid and not the ellipsoid. I understand its a tiny difference but it would be more clear to the user to indicate the referece being the geiod.
> 
> To be clear I am creating these file using the gnssro\_bufr2ioda.f90 utility.

I submitted the github issue:

> <https://github.com/JCSDA-internal/ioda-converters/issues/1844>
>
> One minor point I wanted to bring up on the format of the IODA GNSS-RO obsevatio…n files.
> 
> These files have a variable called “height” with the following metadata:
> float height(Location) ;
> height:longname = “Geometric altitude” ;
> height:units = “m” ;
> height:\_FillValue = 2.147484e+09f ;
> 
> \*\*Proposed Change\*\*
> I think it would reduce confusion with users if you added the words “above geoid” to the longname. I was confused and had to run some tests to confirm it was actually above the geoid and not the ellipsoid. I understand its a tiny difference but it would be more clear to the user to indicate the referece being the geiod.
> 
> \*\*Relevant File(s)\*\*
> I am creating these file using the gnssro\_bufr2ioda.f90 utility but the change would apply to the python version as well.

Thanks for this suggestion @stephenh
