[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDV #EBW-832151]: Viewing a GEO image
- Subject: [IDV #EBW-832151]: Viewing a GEO image
- Date: Fri, 28 Sep 2012 10:52:09 -0600
> Hello Yuan,
>
> Thank you for your quick reply.
> I made some modifications to "goes.nc". The new file is "goes_new2.nc".
> At the end of the header, I have added new variables.
> I am not sure what dimensions you are referring to that do not have variables
> associated with them.
>
> Thanks again,
> Moula.
>
Still a bad netCDF file, here is a sample file with similar projection for you
to reference:
http://motherlode.ucar.edu:8080/thredds/dodsC/casestudies/idvtest/grids/small_ruc_grid.nc.html
Yuan
>
> -----Original Message-----
> From: Unidata IDV Support [mailto:address@hidden]
> Sent: Friday, September 28, 2012 12:14 PM
> To: Elharti, Abdelmoula
> Cc: address@hidden
> Subject: [IDV #EBW-832151]: Viewing a GEO image
>
> > Hello,
> >
> > I have just uploaded the "goes.nc" file to the site you have recommended.
> >
> > Thanks,
> > Moula.
> >
> Moula,
> I briefly checked the dataset you uploaded, the short answer to your problem
> is that this dataset can not be recognized by the IDV as a geo located
> gridded data type. I am guessing this is an unconventional user created
> netCDF file. The IDV does require user to follow certain conventions when a
> customized dataset is created. One very obvious problem is that there are
> three dimensions declared in the dataset, but none of them has variable to
> associate with. Please reference the following CF convention to make your
> dataset readable in the IDV:
>
> http://cf-pcmdi.llnl.gov/documents
>
>
> Yuan
>
> Ticket Details
> ===================
> Ticket ID: EBW-832151
> Department: Support IDV
> Priority: Normal
> Status: Closed
>
>
Ticket Details
===================
Ticket ID: EBW-832151
Department: Support IDV
Priority: Normal
Status: Closed