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.
On 3/30/2011 9:52 AM, Don Murray wrote: > New Client Reply: specifying level with isl > > Yuan- > > On 3/30/11 9:42 AM, Unidata IDV Support wrote: >> On 3/30/2011 9:40 AM, Don Murray wrote: > >>> I'm more concerned when I use the same units and it doesn't pick the >>> right level. I just tried using the 500[hPa] with my suggested change >>> and it gives a new level, but at least it subsets correctly and doesn't >>> keep the [hPa]. I suppose one could check to see what the default level >>> in the list of levels is and then do the conversion, but that's more >>> work than it's worth. >> >> I agree. >> >> Your other ticket is very tough, I spent one day without any progress! > > I actually have a fix for that. I'll try to check it in today. The > basic problem is that all images have Red, Green, Blue for their > MathTypes and the background images map to RGB and the drawing control > images map to RGBA. > > Don > Great, now I can relax and join the lunch with you. :) Yuan >> >> Yuan >>> On 3/30/11 9:36 AM, Unidata IDV Support wrote: >>>> On 3/30/2011 9:24 AM, Don Murray wrote: >>>>> New Client Reply: specifying level with isl >>>>> >>>>> Yuan- >>>>> >>>>> The level may not be hectopascals - it could be whatever the vertical >>>>> unit of the data are. Try using just: >>>>> >>>>> if (level instanceof String) { >>>>> try { >>>>> Real level1 = Util.toReal(level.toString()); >>>>> getDataSelection().setLevel(level1); >>>>> } catch (Exception e) { >>>>> System.err.println("error parsing level: " + level >>>>> + " >>>>> " + e); >>>>> } >>>>> >>>>> and see if that works. I think you are on the right track. >>>>> >>>>> Don >>>> >>>> >>>> OK, so it doesn't matter to have 50000 Pa to go with the 500 hPa. >>>> >>>> >>>> Yuan >>>>> >>>>> >>>>> On 3/29/11 3:29 PM, Unidata IDV Support wrote: >>>>>>> In the attached isl script, the level for display is set using the >>>>>>> display property: >>>>>>> >>>>>>> <display param="Geopotential_height" type="planviewcontour"> >>>>>>> <property name="dataSelectionLevel" >>>>>>> value="50000[Pa]"/> >>>>>>> >>>>>>> I fixed one problem where the unit was not being parsed and attached to >>>>>>> the Real. However, if you load the isl in the IDV and look at the >>>>>>> control, the level is listed as 50000[Pa]. Somehow, the level is not >>>>>>> getting converted to the same type as the other list of levels. This >>>>>>> doesn't cause any problems, per se, but may lead to confusion on the >>>>>>> user's part. The level should probably be converted to a Real of the >>>>>>> same type as the other Real objects in the levels field. >>>>>>> >>>>>>> Don >>>>>> >>>>>> Don, >>>>>> I made some changes in the PlanViewControl, but it need more >>>>>> testing. Please take a try. >>>>>> >>>>>> >>>>>> Yuan >>>>>>> -- >>>>>>> Don Murray >>>>>>> NOAA/ESRL/PSD and CIRES >>>>>>> 303-497-3596 >>>>>>> http://www.esrl.noaa.gov/psd/people/don.murray/ >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> Ticket Details >>>>>> =================== >>>>>> Ticket ID: IJD-786869 >>>>>> Department: Support IDV >>>>>> Priority: Normal >>>>>> Status: Closed >>>>>> >>>>> >>>> >>>> >>>> >>>> Ticket Details >>>> =================== >>>> Ticket ID: IJD-786869 >>>> Department: Support IDV >>>> Priority: Normal >>>> Status: Open >>>> >>> >> >> >> >> Ticket Details >> =================== >> Ticket ID: IJD-786869 >> Department: Support IDV >> Priority: Normal >> Status: Open >> > Ticket Details =================== Ticket ID: IJD-786869 Department: Support IDV Priority: Normal Status: Open