Hello,

I am attempting to convert some NEXRAD Stage III – XMRG formatted data
from a River Forecast Center (specifically from CNRFC). This is for use
in a distributed hydrologic model for some watersheds. I have some
downloaded Stage III data from a National Weather Service web site, and
compiled C-source code that apparently is designed to convert the data
from XMRG to an ASCII format for use in ArcView. The compiled program is
called xmrgtoasc.exe.

When I run the program from a command line with the appropriate set of
arguments, it does not get beyond writing the first header record. The
program doesn’t seem to be able to read the second header record
correctly and exits without converting any data. I don’t know if it
works correctly on a UNIX-based system, but I only have Windows 98 on a
PC. I need it to run on a PC.

I attempted to ask the author of a procedure written on how to use the
program, but since it works okay for him and his data on whatever system
he uses, he suggested the problem must be with my approach. I followed
the written procedure to a tee. Sorry, the written procedure and
conversion utility did not work on WGRFC derived data either – when
running the program on a PC.

Does anyone know of any updated C source code that when compiled should
run without issue on a PC? Thoughts, ideas????? Is the published XMRG
format correct?

Thanks,
Robert

That's kind of the approach I am taking with troubleshooting, and I see
where it exits. I am not sure why it is not following a different
subroutine that has been designed to handle the data correctly.

Rodney Blackall wrote:

In article ,
Robert G. Burns wrote:

[Snip]



When I run the program from a command line with the appropriate set of
arguments, it does not get beyond writing the first header record. The
program doesn't seem to be able to read the second header record
correctly and exits without converting any data. I don't know if it
works correctly on a UNIX-based system, but I only have Windows 98 on a
PC. I need it to run on a PC.



[Snip]

Can you not get the program to print the name of each sub-routine it
enters? That way you will soon find out where it exits and what trivial
coding error has crept in.