SSEC forums

Apologies for my ignorance, but what exactly is the ADL software? Is that run locally? Are you saying the ellipsoid files can be created locally by running the ADL software? Thanks.

The extents used in the newer YAML format should be the outer edges of these pixels and would therefore be half a pixel off from the old .conf format's "origin". I think you hit the nail on the head in your last sentence. The 500m grid values must have come from a newer YAML file and then...

I have been using the VIIRS ellipsoid geolocation files available at NOAA/NESDIS/STAR to remap I- and M-band imagery from S-NPP and NOAA-20 satellites into the ABI and AHI fixed grid projections with polar2grid for a couple of years. I use the resulting remapped images as part of a process to comput...

Sorry for the slow response. I wasn't notified that there was a reply to my original post, or I missed it somehow. I computed the corner parameters of the 500m ABI full disk grid using satpy code found in this file: ~/miniconda3/pkgs/satpy-0.42.2-pyhd8ed1ab_0/site-packages/satpy/readers/abi_base.py ...

It has come to my attention that the last 2 parameters listed for the ABI 500m grid are off by 1/2 the width of a pixel, i.e., 250m. The config file lists the following values:

-5434894.885056, 5434894.885056

I believe these values should instead be:

-5434644.885056, 5434644.885056

That makes perfect sense. Thanks for the information.

No problem. Thanks for the update. How are those last 2 columns computed? Those are the only values I didn't know.

Thanks, David. I have version 2.3 installed. Sounds like I should upgrade.

This forum helped me out last time when I wanted to know the polar2grid configuration parameters for the AHI 2-km grid. Now I would like to remap some VIIRS I01 data to the AHI 0.5 km grid. What parameters should I use? Thanks.

Thanks, David. This is exactly what I needed. I will post again if I have issues. Wayne