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

[netCDF #UWJ-917865]: NetCDF File Naming Convention

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: [netCDF #UWJ-917865]: NetCDF File Naming Convention
  • Date: Thu, 02 Mar 2017 10:03:53 -0700
Hi Nathan,

This is news to me; granted, I've only been part of the netCDF team for the 
last 5 years, but if this was an issue at some point, it does not appear to be 
an issue now (as far as I can determine).  Can you provide any reference to 
this convention/restriction?  If so, I will see if I can dig deeper into it. 
Otherwise, you should be able to proceed without issue.

Thanks!

-Ward

> 
> Greetings,
> 
> At some point in the past I know that it was inadvisable (not possible?)
> to create file names for  netCDF files that began with a digit, for
> example: 3IMERG.nc
> 
> Can someone update me on this issue?
> 
> Is/Was it a netCDF-3 issue? NetCDF-4?
> 
> Or maybe it has been fixed for so long that no one at UNIDATA remembers
> it working this way in the first place?
> 
> Thanks,
> 
> Nathan
> 
> = = =
> Nathan Potter                        ndp at opendap.org
> OPeNDAP, Inc.                        +1.541.231.3317
> 


Ticket Details
===================
Ticket ID: UWJ-917865
Department: Support netCDF
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.