Remko Scharroo

I will use the same implementation as in Sentinel-6 and Jason-3 GDR-F. The coefficients you refer to are there expanded into 2D grids. A file poletide_aux.nc has already been put...

With commit ad3b7ef the issue is fixed in code. Will still need to be applied to all RADS data.

The following mission data have been fully updated with the pole tide fix: - JA3 (10 Feb '22) - S6A - all flavours (11 Feb '22) - SRL (12 Feb...

The dGeoid grid can easily be computed by adding dsea and drad. Both grids are provided for ICE6G.

I have determined the dGeoid for ICE6G, see the image below.  The difference between dGeoid for ICE6G and ICE5G is still significant, as shown in the image below....

As the documentation indicates, the output of `rads2asc` will by default have longitudes from -180 to 180. This is also the case, as I have just tested myself. E.g., the...

There is no command called `rads`.

If have just done this: rads2nc -S 3a -V time,lat,lon,adt,swh,swh_rms,wind_speed,range_numval -o /rads/output/ The longitudes are in the range -180 to 180. An example is provided here: $ ncdump /rads/output/3ap0770c002.nc |...

Not on my side. What version of rads2nc are you running (`rads2nc --version`)? The output message from `rads2nc` to the terminal will also include the following lines: # REJECTED SELECTED...

@milyra, you are right that the longitude boundaries determine the 360-degree shift. If you take the longitude limits away, longitudes will be output the same way as they are in...