NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Yes, I forgot about the -b flag. That is the appropriate one to use. Russ Rew wrote:
Jim- Unfortunately, ncgen has always treated the no flags case as being just a syntax check. I agree with your intent, but we are captives of history and back compatability.I think ncgen could still treat no flags as a syntax check, but use of -b or -o specifying an output file means a netCDF output should be generated. In that case, I don't see the need for specifying a "-k" when the type of output can be inferred from the CDL. This request was actually entered a few months ago in Jira ticket NCF-124: https://www.unidata.ucar.edu/jira/browse/NCF-124 I don't think it would violate our backward compatibility commitment, which is about APIs and data. --RussJim Cowie wrote:Hi,I built netcdf-4.2-rc1 and I was not able to create a file using ncgen unless I included the '-k kind' option. With this option omitted, nothing happens.I hope this is not intentional because it would be a step in the wrong direction. My goal is to *never* use the -k option, but rather to use the _Format attribute within the CDL to define the output file type at run-time. Based on earlier discussions I've had with Unidata, and some documentation I've seen, this was the intent of the _Format attribute. Using -k would override what is in the CDL. Now I'm not sure what to think.Thanks ... Jim Cowie _______________________________________________ netcdfgroup mailing list netcdfgroup@xxxxxxxxxxxxxxxxFor list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/_______________________________________________ netcdfgroup mailing list netcdfgroup@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
netcdfgroup
archives: