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.
> I hope someone can tell me what I'm doing wrong. I have not been able > to make sense of the diagnostic from ncecat. I've added blank lines in > my dialog below to facilitate reading my attempts to concatenate three > files. They are all on the same (long, lat) grid. I hoped for a netCDF > dataset with long, lat, behave, cfdrs, nfdrs. ncview * displays > the three as though they were one concatenated dataset. > > Thanks for any help you can give. > > $> ncecat behave.nc cfdrs.nc nfdrs.nc -o fuelState.nc > ERROR: nco_inq_varid() reports requested variable "behave" is not in > input file > ERROR: program exiting through nco_err_exit() which will now call > exit(EXIT_FAILURE) > nco_err_exit(): ERROR nco_inq_varid() > Variable not found > > $> ncecat behave.nc -v cfdrs cfdrs.nc -v nfdrs nfdrs.nc -o fuelState.nc > ncecat: ERROR nco_var_lst_mk() reports user-specified variable "nfdrs" > is not in input file > > $> ncdump -h nfdrs.nc > netcdf nfdrs { > dimensions: > x = 2512 ; > y = 1992 ; > variables: > double x(x) ; > x:long_name = "x coordinate of projection" ; > x:standard_name = "projection_x_coordinate" ; > x:units = "Meter" ; > double y(y) ; > y:long_name = "y coordinate of projection" ; > y:standard_name = "projection_y_coordinate" ; > y:units = "Meter" ; > byte nfdrs(y, x) ; > nfdrs:long_name = "nfdrs" ; > nfdrs:esri_pe_string = > "PROJCS[\"Clarke_1866_Albers\",GEOGCS[\"GCS_Clarke_1866\",DATUM[\"D_Clarke_1866\",SPHEROID[\"Clarke_1866\",6378206.4,294.9786982]],PRIMEM[\"Greenwich\",0.0],UNIT[\"Degree\",0.0174532925199433]],PROJECTION[\"Albers\"],PARAMETER[\"False_Easting\",0.0],PARAMETER[\"False_Northing\",0.0],PARAMETER[\"Central_Meridian\",-154.0],PARAMETER[\"Standard_Parallel_1\",55.0],PARAMETER[\"Standard_Parallel_2\",65.0],PARAMETER[\"Latitude_Of_Origin\",50.0],UNIT[\"Meter\",1.0]]" > ; > nfdrs:coordinates = "x y" ; > nfdrs:grid_mapping = "albers_conical_equal_area" ; > nfdrs:units = "Meter" ; > nfdrs:missing_value = 0b ; > int albers_conical_equal_area ; > albers_conical_equal_area:grid_mapping_name = > "albers_conical_equal_area" ; > albers_conical_equal_area:longitude_of_central_meridian > = -154. ; > albers_conical_equal_area:latitude_of_projection_origin > = 50. ; > albers_conical_equal_area:false_easting = 0. ; > albers_conical_equal_area:false_northing = 0. ; > albers_conical_equal_area:standard_parallel = 55., 65. ; > > // global attributes: > :Conventions = "CF-1.0" ; > :Source_Software = "ESRI ArcGIS" ; > } > Howdy Lee! Sorry, this looks like an NCO problem, not a netcdf problem. You want to contact the NCO team about this question: http://nco.sourceforge.net/ Good luck! Ed Ticket Details =================== Ticket ID: XMF-745403 Department: Support netCDF Priority: Normal Status: Closed