[ncl-talk] KML Questions

[Rick Brownrigg]

Hi Scott,

Try setting this environment variable before running the script:

    export NCARG_OLD_PS=True     (assuming bash shell)

The issue is that the KML NCL-code that does cropping of pieces of a plot
expects that postscript plots have been generated.  NCL in fact has two
different postscript drivers, one I'll call the original driver, the other
the newer cairo-based driver. At some point in recent versions of NCL
(6.2.0 perhaps -- can't recall exactly), the cairo driver became the
default when one simply opens a workstation with "ps". Apparently however,
the calculations for where on the page to crop are appropriate only for the
original driver, regardless of which driver is actually used;  the two
drivers place things on the page differently.

The above environment variable causes "ps" to map to the original driver.
It should get you back in business as a work-around. I'll open a ticket on
this issue.

Hope that helps...
Rick



On Wed, May 13, 2015 at 11:43 AM, David Brown <dbrown at ucar.edu> wrote:

> Hi Rick,
> I corresponded with Scott and he sent me some test scripts and data. I
> now realize that I forgot to include ncl-talk in my conversation. I
> have not had a chance to look at this issue yet, but I hope to soon.
> However, if you would like to, since I know you have done some work
> with KML, I would be happy to give you what I have. If there is an NCL
> issue here it would be good to get to the bottom of it.
>  -dave
>
>
> On Wed, May 13, 2015 at 9:30 AM, Rick Brownrigg <brownrig at ucar.edu> wrote:
> > Hi Scott,
> >
> > There are no specific plans -- at the moment -- for refined KML
> > functionality.  That could change depending upon level of interest, and
> I'll
> > take your note as a vote of interest!  In general, contributed/external
> NCL
> > routines come with no promise of support by the NCL team, so you might
> > contact the authors of these codes.  That said, if you have a
> self-contained
> > example of what is not happening as expected with Ryan's approach, I'd be
> > happy to take a look -- its odd that things should suddenly no longer
> work.
> >
> > Rick
> >
> >
> > On Mon, May 11, 2015 at 2:12 PM, Scott Capps <scott at allvertum.com>
> wrote:
> >>
> >> Good afternoon,
> >>
> >> I have used NCL to output KML/KMZ files from WRF data using both Ryan
> >> Pavlick's and Mohammad Abouali's code.  Ryan's solution was working but
> >> is no longer working with the latest versions of NCL. For some reason,
> >> it cannot extract the labelbar from the plot and no longer maps the plot
> >> onto Google-Earth correctly.  Using Mohammad's solution, I am able to
> >> get a KML/KMZ file that plots OK in Google-Earth.  However, I am not
> >> given the option to specify a contour spacing value nor can I plot the
> >> colorbar within google-earth.  So, the end user of the KML really has no
> >> idea how the color contours correspond to the actual values contoured.
> >> I really need the ability to specify a contour spacing.  Therefore, I
> >> have two questions:
> >>
> >> Are there plans to refine the KML functionality within NCL in the near
> >> future?
> >> Who do I ask for support from these contributed and external NCL
> routines?
> >>
> >> Thank you,
> >>
> >> Scott
> >> _______________________________________________
> >> ncl-talk mailing list
> >> List instructions, subscriber options, unsubscribe:
> >> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
> >
> >
> >
> > _______________________________________________
> > ncl-talk mailing list
> > List instructions, subscriber options, unsubscribe:
> > http://mailman.ucar.edu/mailman/listinfo/ncl-talk
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20150513/6b6488cc/attachment.html