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

[LDM #YPE-630569]: 20181017: feature request for LDM date processing

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: [LDM #YPE-630569]: 20181017: feature request for LDM date processing
  • Date: Thu, 18 Oct 2018 09:12:14 -0600
Hi,

I've added this as an issue to the LDM GitHub repository.

> As per the discussion in the LDM training workshop on October 16/17:
> 
> It would be very useful if 'pqact' could use the Julian day (day of
> year) in a manner that is analogous to the day of month to calculate
> the year, month, and day.
> 
> Example Product ID:
> 
> The following is an example of the Product ID for GOES-16 ABI Full Disk
> Channel 13 imagery in the SATELLITE (aka DIFAX) feed:
> 
> /data/cspp-geo/GRB-R/OR_ABI-L1b-RadF-M3C13_G16_s20182901645381_e20182901656159_c20182901656223.nc
> 
> The time portions of this Product ID are of the form:
> 
> CCYYJJJHHMMSSx
> 
> Meaning for first time group (starts with 's'):
> 
> CCYY   - 2018   (%Y%m)
> JJJ    - 290    (%j)
> HHMMSS - 164538 (%H%M%S)
> x      - 1 -- tenths of a second
> 
> Example of desired pqact use:
> 
> SATELLITE<tab>(OR_(ABI)-L1b-RadF-M.C(..)_G(..)_s....(...).*)
> <tab>FILE -close
> <tab>/data/ldm/pub/native/satellite/GOES/GRB\4/\2/FullDisk/Channel\3/(\5:yyyy)(\5:mm)(\5:dd)/\1

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YPE-630569
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.