-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposed Recipes for Himawari-8 Level 3 SST #173
Comments
@sharkinsspatial, per our "jam" session yesterday with @wildintellect, Anthony Lukach, and Aimee Barciauskas, I'm posting details on our work to identify gaps in the available files in AWS S3. We may want to tidy things up a bit within a single script, but here are all the parts. Produce List of Actual L3C FilesTo produce a list of the relevant L3C files in lexicographical (and also chronological order, given the naming convention):
Example file:
Upon visual inspection, we identified 3 places where the file pattern shifts:
Further, the actual transition from Produce List of Expected L3C FilesGiven that our visual inspection of the S3 file list makes it apparent that there are numerous gaps, we want to produce a list of expected hourly files so that we can identify all of the gaps. This logic is similar to what we'll need for our
To produce the list of expected files:
Identify Missing L3C FilesWe can now produce a list of files that are missing from S3:
For reference, I've attached a list of missing files, through 2022-08-17: l3c-missing.txt |
@Patrick-Keown In preparation for generating a
Thank you in advance for any input you can provide. |
Hi Patrick, Sean,
I'm definitely not the best person to talk about L3 products. STAR
transitioned all Himawari 8 processing to OSPO about a year and a half
ago and I was only tangentially related to that process.
As for the times missing, could you please provide some examples?
Are you only using the L2 SST data?
Thanks,
Matt.
Matthew Jochum
NESDIS / STAR / ITT
System Owner - NOAA5018
Network Lead
O: 1-301-683-3506
I don't always test my code,
but when I do, I do it in production.
…On 8/22/22 09:59, Patrick Keown - NOAA Federal wrote:
Hi Sean,
I am CC'ing Matt Jocum who I believe will be able to answer your data
specific questions on Himawari data.
Matt,
Are you able to assist?
Thanks,
Patrick Keown
Program Manager, NOAA Open Data Dissemination (NODD)
Office of the Chief Information Officer (OCIO)
National Oceanic & Atmospheric Administration
(615) 319-5906 | ***@***.***
"Be sure when you step, step with care and great tact" - Dr. Seuss
On Fri, Aug 19, 2022 at 5:39 PM Sean Harkins ***@***.***>
wrote:
> @Patrick-Keown <https://github.com/Patrick-Keown> In preparation for
> generating a kerchunk index for the Himawari-8 Level 3 SST data we have
> identified several missing hourly time steps and a potential inconsistency
> in the timestamps for changes in product version id. There is email contact
> associated with the NOAA BDP https://registry.opendata.aws/noaa-himawari/
> but in the spirit of tracking of conversation in an open repository I was
> hopeful that you might be able to provide some feedback on these anomalies,
> if there is more appropriate point of contact for these discussions please
> let me know.
>
> - Are these missing hourly timestamps expected?
> - Is there documentation describing the key naming structure for the
> version and the STAR to NCCF transition?
>
> Thank you in advance for any input you can provide.
>
> —
> Reply to this email directly, view it on GitHub
> <#173 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AOISIED6AK4NMX2UIYV76ADVZ75G7ANCNFSM5626VOGQ>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
@Patrick-Keown I don't see an email in the chain for Matthew Jochum, is there a good contact point for him (you can message me directly with it so as not to publish his email on a open channel). For a list of the missing L3 SST time steps you can review this list https://github.com/pangeo-forge/staged-recipes/files/9377046/l3c-missing.txt compiled by @chuckwondo . |
It looks like Matt mentioned to me that he may not be the best contact.
With that said, I would actually reach out to ***@***.***
and they would be able to direct you to the appropriate contact.
Patrick Keown
Program Manager, NOAA Open Data Dissemination (NODD)
Office of the Chief Information Officer (OCIO)
National Oceanic & Atmospheric Administration
(615) 319-5906 | ***@***.***
"Be sure when you step, step with care and great tact" - Dr. Seuss
…On Wed, Aug 24, 2022 at 4:45 PM Sean Harkins ***@***.***> wrote:
@Patrick-Keown <https://github.com/Patrick-Keown> I don't see an email in
the chain for Matthew Jochum, is there a good contact point for him (you
can message me directly with it so as not to publish his email on a open
channel). For a list of the missing L3 SST time steps you can review this
list
https://github.com/pangeo-forge/staged-recipes/files/9377046/l3c-missing.txt
compiled by @chuckwondo <https://github.com/chuckwondo> .
—
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOISIEF5MNBYSRUHEX4GYQTV22CWDANCNFSM5626VOGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi Sean,
I am CC'ing Matt Jocum who I believe will be able to answer your data
specific questions on Himawari data.
Matt,
Are you able to assist?
Thanks,
Patrick Keown
Program Manager, NOAA Open Data Dissemination (NODD)
Office of the Chief Information Officer (OCIO)
National Oceanic & Atmospheric Administration
(615) 319-5906 | ***@***.***
"Be sure when you step, step with care and great tact" - Dr. Seuss
…On Fri, Aug 19, 2022 at 5:39 PM Sean Harkins ***@***.***> wrote:
@Patrick-Keown <https://github.com/Patrick-Keown> In preparation for
generating a kerchunk index for the Himawari-8 Level 3 SST data we have
identified several missing hourly time steps and a potential inconsistency
in the timestamps for changes in product version id. There is email contact
associated with the NOAA BDP https://registry.opendata.aws/noaa-himawari/
but in the spirit of tracking of conversation in an open repository I was
hopeful that you might be able to provide some feedback on these anomalies,
if there is more appropriate point of contact for these discussions please
let me know.
- Are these missing hourly timestamps expected?
- Is there documentation describing the key naming structure for the
version and the STAR to NCCF transition?
Thank you in advance for any input you can provide.
—
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOISIED6AK4NMX2UIYV76ADVZ75G7ANCNFSM5626VOGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Dataset Name
Himawari-8
Dataset URL
https://registry.opendata.aws/noaa-himawari/
Description
@pbranson Has prototyped some initial kerchunk index generation for the Himawari-8 Level 3 SST data as part of a project for OceanHackWeek in this repo. Using his example, I'll try to put together a initial recipe ref oceanhackweek/ohw22-proj-kerchunk#2
License
Open Data
Data Format
NetCDF
Data Format (other)
No response
Access protocol
S3
Source File Organization
s3://noaa-himawari8/{dataset}/{year}/{month}/{day}/{hour}/YYYYMMDDHHHHSS-STAR-L3C_GHRSST-SSTsubskin-AHI_H08-ACSPO_V2.80-v02.0-fv01.0.nc
Which alters to
s3://noaa-himawari8/{dataset}/{year}/{month}/{day}/{hour}/YYYYMMDDHHHHSS-NCCF-L3C_GHRSST-SSTsubskin-AHI_H08-ACSPO_V2.80-v02.0-fv01.0.nc
from 7 April 2021 forward.Example URLs
Authorization
No response
Transformation / Processing
NA
Target Format
Reference Filesystem (Kerchunk)
Comments
No response
The text was updated successfully, but these errors were encountered: