[Ncep.list.emc.fv3gfs_tickets] FV3GFS Ticket #17: Explore use of GMTED2010 terrain data

FV3GFS Trac Ticket ncep.list.emc.fv3gfs_tickets at noaa.gov
Wed Jun 14 14:43:01 UTC 2017

#17: Explore use of GMTED2010 terrain data
  Reporter:  george.gayno@…  |      Owner:  george.gayno@…
      Type:  task            |     Status:  accepted
  Priority:  major           |  Milestone:
 Component:  component1      |    Version:
Resolution:                  |   Keywords:  GMTED2010

Comment (by george.gayno@…):

 The C768 terrain was also created without the RAMP data (i.e., using
 GMTED2010) for Antarctica.  This was done by commenting out the copy of
 this data in the
 fv3gfs_make_orog.sh] script as follows:

 $ svn diff fv3gfs_make_orog.sh
 Index: fv3gfs_make_orog.sh
 --- fv3gfs_make_orog.sh (revision 94344)
 +++ fv3gfs_make_orog.sh (working copy)
 @@ -90,10 +90,10 @@
  #  cp /home/z1l/GFS_tools/orog/a_ocean_mask${lonb}x${latb}.txt  fort.25
  #  cp $MTN_SLM fort.14

 -  cp ${indir}/thirty.second.antarctic.new.bin fort.15
 +#  cp ${indir}/thirty.second.antarctic.new.bin fort.15
    cp ${indir}/landcover30.fixed .

 Plots of the terrain over Antarctica with and without RAMP are here:

 GFDL warned about problems with GMTED2010 over the Antarctic peninsula -
 it does not resolve its high mountain range very well.  Bob Grumbine also
 had reservations concerning GMTED2010:

 The GMTED looks wonky, especially on the northern parts of the Antarctic
 peninsula.  You are right that the transantarctic mountains should extend
 the length of the peninsula, which they don't seem to.  And thousand meter
 differences are far more than allowable.  The GMTED also doesn't seem to
 appropriate separation between the peninsula and the island at 64 S, 58 W
 (coast is quite close to exactly this).

Ticket URL: <https://svnemc.ncep.noaa.gov/trac/fv3gfs/ticket/17#comment:6>
fv3gfs <https://svnemc.ncep.noaa.gov/trac/fv3gfs>
NGGPS FV3GFS Development

More information about the Ncep.list.emc.fv3gfs_tickets mailing list