You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if GOES-19 could be included in HV as soon as it is available, particularly the coronagraph of course.
Maybe someone has insight when it could be expected.
On Helioviewer.org we still have some work to do because the jpeg2000 images are not oriented the way the web system needs. We're working on a solution to this problem but may not be ready for a few more months.
The letter (GOES-R) was the designation of the satellite before it had reached orbit, GOES-R is now GOES-16.
CCOR-1 is onboard GOES-19 (previously GOES-U).
So a generic "GOES" would be more accurate.
Another thing.. the default contrast settings in JHV are not ideal, maybe that can be improved?
Screenshotss NOAA Website vs JHelioviewer with default settings:
The letter (GOES-R) was the designation of the satellite before it had reached orbit, GOES-R is now GOES-16. CCOR-1 is onboard GOES-19 (previously GOES-U). So a generic "GOES" would be more accurate.
We will start working on the hvpull for GOES/CCOR-1 now. We will also update our data sources table so that "GOES" is displayed instead of "GOES-R", already for SUVI.
Since we have done this, it seems that it is running fine and the data are updated regularly (we have today's data for SUVI and CCOR-1 on https://helioviewer.ias.u-psud.fr/ )
@helioshk JHV shows the data exactly as it was prepared by NOAA. Looks like they prepare it differently for their website. I will raise this next time I'm in contact with them.
@ebuchlin At Goddard we aren't showing CCOR-1 in the Helioviewer web app because it doesn't take into account the image rotation. These jpeg2000's weren't calibrated to render correctly in our web app. JHV processes the WCS metadata independently so it shows correctly there.
We've hidden CCOR-1 from our helioviewer.org instance. It is still available in JHV. I guess we will be able to show it again in helioviewer.org when #513 will be finalized, as WCS information (including roll) should then be taken into account properly.
Can this issue be closed or are we waiting for #513?
IMHO, it's just a crutch: my suggestion would be to replace all that with SunPy which can already read the JP2 metadata and then use the full power of AstroPy to map the data.
Activity
wafels commentedon Oct 14, 2024
GOES-19 CCOR data is not available yet. When it is, we will endeavor to provide JPEG2000 files of the available data as soon as possible.
helioshk commentedon Feb 9, 2025
Preliminary non-operational CCOR images are now available every 15 minutes, I don't know if this also applies for JPEG2000 files though.
https://testbed.spaceweather.gov/products/ccor-1-coronagraph
dgarciabriseno commentedon Feb 10, 2025
I worked with one of the engineers at NOAA to help enable creating JPEG2000s for CCOR.
My information so far is that they will make a public directory of jp2's when CCOR becomes operational, and we'll pull those into Helioviewer.
helioshk commentedon Apr 9, 2025
CCOR-1 is now operational.
helioshk commentedon May 14, 2025
Bump
bogdanni commentedon May 14, 2025
Probably news in couple of weeks.
dgarciabriseno commentedon Jun 30, 2025
Data will be available on JHelioviewer shortly.
On Helioviewer.org we still have some work to do because the jpeg2000 images are not oriented the way the web system needs. We're working on a solution to this problem but may not be ready for a few more months.
helioshk commentedon Feb 2, 2026
CCOR is currently not available on any server. I think it was only on GSFC which seems to be offline. Is it possible to make CCOR available on IAS?
dgarciabriseno commentedon Aug 11, 2026
@ebuchlin Can you pull in CCOR on your end for redundancy?
ebuchlin commentedon Aug 11, 2026
Yes, we will do that (expect a few weeks, because of the summer holidays).
At GSFC, I can only see GOES/CCOR-1/White light, and only in JHV, I guess because of the image rotation issue. The rotation issue is linked to #494.
On our instance of helioviewer.org, we have "GOES-R" (currently only for SUVI) while it is "GOES" at GSFC. Should we change something about that?
helioshk commentedon Aug 26, 2026
The letter (GOES-R) was the designation of the satellite before it had reached orbit, GOES-R is now GOES-16.
CCOR-1 is onboard GOES-19 (previously GOES-U).
So a generic "GOES" would be more accurate.
helioshk commentedon Sep 3, 2026
Another thing.. the default contrast settings in JHV are not ideal, maybe that can be improved?
Screenshotss NOAA Website vs JHelioviewer with default settings:
ebuchlin commentedon Sep 4, 2026
We will start working on the hvpull for GOES/CCOR-1 now. We will also update our data sources table so that "GOES" is displayed instead of "GOES-R", already for SUVI.
ebuchlin commentedon Oct 1, 2026
Since we have done this, it seems that it is running fine and the data are updated regularly (we have today's data for SUVI and CCOR-1 on https://helioviewer.ias.u-psud.fr/ )
bogdanni commentedon Oct 1, 2026
@helioshk JHV shows the data exactly as it was prepared by NOAA. Looks like they prepare it differently for their website. I will raise this next time I'm in contact with them.
ebuchlin commentedon Oct 1, 2026
Aren't they the same JP2 files for JHV and the web app?
bogdanni commentedon Oct 1, 2026
Which web app? They just make separate jpegs for their web page, i.e., https://services.swpc.noaa.gov/products/ccor1/jpegs/
Their processing looks indeed different from the JP2s.
dgarciabriseno commentedon Oct 1, 2026
@ebuchlin At Goddard we aren't showing CCOR-1 in the Helioviewer web app because it doesn't take into account the image rotation. These jpeg2000's weren't calibrated to render correctly in our web app. JHV processes the WCS metadata independently so it shows correctly there.
dgarciabriseno commentedon Oct 1, 2026
We are ingesting it and serving to JHV only at this time.
ebuchlin commentedon Oct 1, 2026
@bogdanni the "wep app" is "helioviewer.org" (including the IAS instance). @dgarciabriseno ah, indeed, then we should also hide it...
ebuchlin commentedon Oct 5, 2026
We've hidden CCOR-1 from our helioviewer.org instance. It is still available in JHV. I guess we will be able to show it again in helioviewer.org when #513 will be finalized, as WCS information (including roll) should then be taken into account properly.
Can this issue be closed or are we waiting for #513?
bogdanni commentedon Oct 5, 2026
Is the approach in #513 the optimal one?
IMHO, it's just a crutch: my suggestion would be to replace all that with SunPy which can already read the JP2 metadata and then use the full power of AstroPy to map the data.