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

[IDV #HTP-148933]: Loading .nc files into IDV and aggregating grids by time

I should be able to create a plugin for you but only work for an individual
file. To aggregate files in a time dimension, all these
files need to have the same dimensions, that is not the case for the two
files you send me in the previous email.

The other option is to write a similar aggregate ncml file, and you need to
put all files in the same folder. Again, they need to
have the same dimensions.

Let me know which option you prefer.

Yuan

address@hidden> wrote:

> New Client Reply: Loading .nc files into IDV and aggregating grids by time
>
> Here is an ncml script that worked on a separate series of satellite
> files, attached. It looks like there is some degree of modification (in
> this case, attribute name="coordinates") prior to aggregation.
>
> Good to know that only one variable needs a change to the coordinate
> attribute. But in my case there are hundreds of nc files that would need to
> be modified. How does it work - do you load the modification script into
> IDV or run it at the command line?
>
> Alexa
>
>
> ________________________________
> From: Unidata IDV Support <address@hidden>
> Sent: Wednesday, March 16, 2022 12:49 PM
> To: Van Eaton, Alexa R <address@hidden>
> Cc: address@hidden <address@hidden>; Van
> Eaton, Alexa R <address@hidden>
> Subject: [EXTERNAL] [IDV #HTP-148933]: Loading .nc files into IDV and
> aggregating grids by time
>
>
>
>  This email has been received from outside of DOI - Use caution before
> clicking on links, opening attachments, or responding.
>
>
>
> I am not sure if you can modify the NC fille inside this aggregation ncml,
> I created an ncml file for each NC file and you. only. need
> to add the coordinate attribute to one variable, such as
> "brightness_temperature_4micron".
>
> Yuan
>
> address@hidden> wrote:
>
> > New Client Reply: Loading .nc files into IDV and aggregating grids by
> time
> >
> > Dear Yuan,
> >
> > I've constructed an ncml script to put together those two steps and try
> to
> > apply them to all .nc files in the current directory. It partially works,
> > in that the (long format) variable names now show up in IDV, but they do
> > not plot on a map. Could you take a look and see if this approach makes
> > sense?
> >
> > All the best
> >
> > Alexa
> > ________________________________
> > From: Unidata IDV Support <address@hidden>
> > Sent: Wednesday, March 16, 2022 10:41 AM
> > To: Van Eaton, Alexa R <address@hidden>
> > Cc: address@hidden <address@hidden>; Van
> > Eaton, Alexa R <address@hidden>
> > Subject: [EXTERNAL] [IDV #HTP-148933]: Loading .nc files into IDV and
> > aggregating grids by time
> >
> >
> >
> >  This email has been received from outside of DOI - Use caution before
> > clicking on links, opening attachments, or responding.
> >
> >
> >
> > > Dear Yuan, Sounds promising - thank you for taking a close look! Talk
> > soon, Alexa
> > > ________________________________
> > > From: Unidata IDV Support <address@hidden>
> > > Sent: Tuesday, March 15, 2022 3:19 PM
> > > To: Van Eaton, Alexa R <address@hidden>
> > > Cc: address@hidden <address@hidden>
> > > Subject: [EXTERNAL] [IDV #HTP-148933]: Loading .nc files into IDV and
> > aggregating grids by time
> > >
> > >
> > >
> > > This email has been received from outside of DOI - Use caution before
> > clicking on links, opening attachments, or responding.
> > >
> >
> > So the solution is to use ncml to modify the original files and another
> > ncml to aggregate them together to
> > form a time coordinate.
> >
> > first step:  add <attribute name="coordinates" value="latitude longitude"
> > /> to one of the variable with (y,x)
> >
> > second step: see the attached ncml, I use the mean_feature_time as the
> > time coordinate variable, you can change it to another time variable.
> > and only aggregate brightness_temperature_XXmicron variables and you
> > expand to others too.
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: HTP-148933
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> > ===================
> > 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.
> >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: HTP-148933
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> > Link:
> >
> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fandy.unidata.ucar.edu%2Fstaff%2Findex.php%3F_m%3Dtickets%26_a%3Dviewticket%26ticketid%3D33088&data=04%7C01%7Cavaneaton%40usgs.gov%7C1a7729cc1d624d8e70be08da07860967%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637830569512325808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dEQKM4KaFzYvLe3ufi7CAJFBb2cD%2BJT9BMMpoU35ElU%3D&reserved=0
>
>
>
> Ticket Details
> ===================
> Ticket ID: HTP-148933
> Department: Support IDV
> Priority: Normal
> Status: Open
> ===================
> 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.
>
>
>
>
> Ticket Details
> ===================
> Ticket ID: HTP-148933
> Department: Support IDV
> Priority: Normal
> Status: Open
> Link:
> https://andy.unidata.ucar.edu/staff/index.php?_m=tickets&_a=viewticket&ticketid=33088



Ticket Details
===================
Ticket ID: HTP-148933
Department: Support IDV
Priority: Normal
Status: Open
===================
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.