> On 01/07/2012 10:45 PM, Unidata IDV Support wrote: > >> I think cross-section is not an issue. The issue is here: > >> > 1. Flow Time/Height Display in case the flow vector fields are 2D > >> > (Reason:The Y axis in control window as no value). > >> > 2. Wind Barb Time/Height Display in case the flow vector fields are 2D > >> > (Reason:same as 1). > >> > 3. Vertical Profile in case the flow vector fields are 2D(Reason:No 3D > >> > available). > >> > > >> > I think that for following controls the categories should be changed > >> > from "*-flowvector-*" to "*-flowvector3d-*" > >> > 1. Vertical Profile > >> > 2. Flow Time/Height Display > >> > 3. Wind Barb Time/Height Display The difference between flowvector and flowvecotr3d is vertical velocity. The flowector3d is for the dataset with u,v, and w. So, if we change the to flowvector3d for the vertical profile, we will lost many derived variable for those dataset only have u and v. The naming is a little confusing, sorry about it. Yuan > >> > > > In general, I would agree your suggestion here. I will double check with > > other developers next week to make sure. > > > > > > Yuan > Did you get chance to check this? > > regards > Ghansham > > Ticket Details =================== Ticket ID: LMS-496434 Department: Support IDV Priority: Critical 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.