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.
Hi there, > Ever since the new update, I've noticed that the GOES imagery data appears > to be *significantly *lower resolution than before. The CH02 visible band > (which should have 0.5km resolution) appears to be the same resolution as > the CH10 band, for example (1km resolution). I'm not sure if this issue is > a problem on my end or on yours, any ideas? > After conducting some further tests, I've determined that CH02 for both full > disks is really low resolution. The CONUS views seem to be working okay. Sorry it's taken me a moment to get back to you. The GOES-16 and -17 FullDisk imagery is coming from NOAAPort and distributed in the NIMAGE IDD feed has always had 6km resolution. NOAA made this decision to save bandwidth in the NOAAPort SBN. Hope that clears things up. --Shay Carter She/Her/Hers AWIPS Software Engineer UCAR - Unidata If you're interested, please feel free to fill out a survey about the support you receive: https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform Ticket Details =================== Ticket ID: VDI-502577 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly 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.