[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20040329: no luck remapping composite NEXRAD images

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20040329: no luck remapping composite NEXRAD images
  • Date: Mon, 29 Mar 2004 17:46:20 -0700
>From: Owen Cooper <address@hidden>
>Organization: Aeronomy Laboratory/NOAA
>Keywords: 200403292103.i2TL3WrV015923 McIDAS IMGREMAP NEXRCOMP

Hi Owen,

>I've had no problem in the past remapping GOES imagery to a mercator 
>projection.  But I'm having no luck remapping the 1 km USA composite
>NEXRAD image to a mercator projection.

>I've tried everything I can think of but I always get one of two errors, 
>either the image does not exist or the requested portion of the image 
>does not exist.

It sounds like you need to include the SSIZE=ALL keyword sequence.

>Can you do me a favor and see if you can re-map a composite NEXRAD image 
>to mercator, and if so, can you send me the command that you used?

Done.  Here is the command I ran:

IMGREMAP NEXRCOMP/1KN0R-NAT MYDATA/IMAGES.1234 PRO=MERC RES=5 SSIZE=ALL

You will need to adjust things like the output image size, etc.  The
command above was the first thing I tried as a proof of concept that
there is no problem remapping the NEXRCOMP composite images.

Please let me know if this doesn't work for you, or if you have
further questions on running IMGREMAP.

>thanks!

No worries.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.