Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Latitudinal shift of Cheyenne's SRTM_3s topography data


New member
Dear WRF Community,

I have successfully run a geogrid program using Cheyenne's SRTM_3s topography data for my 259m resolution simulation. However, while I checked the HGT_M variable using ncview I do see a latitudinal shift (to the north) of topography for SRTM_3s. I then checked the same grids with gmted2010_30s data and found everything okay. Since I have to use SRTM_3s topography data for my 259m domain, could anyone please help me to resolve this issue?

My working directory in Cheyenne: /glade/scratch/skarim/fire_project/yarnell_hill_fire/WRFV4.4/WPSV4.4
I have attached the screenshot of SRTM_3s and gmted2010_30s topography for my 259m domain to this thread.

I would be really grateful if someone could help me.
Thanks in advance.

With Kind Regards


  • gmted2010_30s(900m) resolution topography.png
    gmted2010_30s(900m) resolution topography.png
    2.2 MB · Views: 5
  • SRTM_3s (90m) resolution topography.png
    SRTM_3s (90m) resolution topography.png
    2.6 MB · Views: 5
Thanks once again, Ms. Werner. Sorry for being too late to respond to this. I had some family emergencies. So, Here is the update:
I have followed the steps that you suggested; however, d04 (259m) and d05 (86.3m) don't show any topography height. The output of the HGT_M gives 0 everywhere. P.S., I changed the "known_lat" value in the index file -55.99916667 to -89.99583

My working directory in Cheyenne: /glade/scratch/skarim/fire_project/yarnell_hill_fire/WRFV4.0/WPS-4.0

Thanks in advance.

With Kind Regards

I am still stuck with this problem. Any help would be greatly appreciated.
Thanks in advance for your valuable time and help.

With Kind Regards
That is great news! I apologize for the delay in my response. We were busy conducting a tutorial over the past two weeks, so we've gotten a bit behind on forum posts. Thanks for the update.