Hi Ryan,
I looked at the interface code for rgba2png. The interface appears to be the following:
procedure rgba2png(png_output_file_name : string, Red : uint, Green : uint, Blue : uint, Alpha : uint, Width [1] : uint, Height [1] : uint, nFrames [1] : uint)
Red, Green, Blue, Alpha all need to be the same dimensionality and dimension sizes, and must be at least 2D, but no limit to the number of left hand dimensions.
width is the dimension size of the rightmost dimension.
height is the next dimension to the left.
nFrames should be less than or equal to the product of the remaining dimension sizes.
I am not sure why these last three arguments are necessary -- it seems that they could all be determined from the RGBA variables.
-dave
On Apr 7, 2014, at 3:41 PM, Ryan Pavlick <ryan.pavlick@gmail.com> wrote:
> I solved the problem with the coordinate system discrepancies with a few lines of code:
>
> nlat = dimsizes(lat)
> nlon = dimsizes(lon)
>
> lat2d = conform_dims((/nlat,nlon/),lat,0)
> lon2d = conform_dims((/nlat,nlon/),lon,1)
>
> RasterTimeSeries2KML("olr_200212_21F_VarAlpha",olr,lon2d,lat2d,TimeTag,Opt)
>
> _______________________________________________
> 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
Received on Mon Apr 07 16:29:37 2014
This archive was generated by hypermail 2.1.8 : Tue Apr 15 2014 - 10:45:19 MDT