Problem with binary data generation using convert_geotiff

[huyang]

Hello, WRF Forums!
I’ve been using convert_geotiff to generate binary input files, and I’ve run into an odd issue. WRF doesn’t seem to recognize my defined missing value of -32768 — it’s converting this negative value to positive 32768 instead. This ends up creating spurious anomalous values across all ocean grid cells.

Here’s the command I used:
convert_geotiff -w 2 -t 1500 -u "meters MSL" -d "3s topography" -b 0 -m -32768 strm3s.tif
I’ve also attached index for reference.

 

[ninininifree]

Hi @huyang ,

I hope you're doing well. I came across your post, and I’m experiencing a very similar issue.

I’m trying to use higher-resolution topography than the default WRF datasets, specifically SRTM data. When I run the convert_geotiff tool, I’ve noticed that the negative missing values in the input data are being converted into positive values in the output.

Have you found any solution to this, or do you know why this sign change is happening?

At first glance, it seems that modifying the missing value in the index file (i.e., using a positive value instead of a negative one) could work as a workaround. However, I’d really like to understand the reason behind this behavior.

Thanks in advance for any insight you can share!