NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
As Daryl noted, CED isn't one of the projections that the GINI image
format supports (see the GINI specification for its description).
For LCC, a tangent cone is supported (eg Lat1 = Lat2).
Here's a quick script snippet to use a Central lat/lon input to create a
region for nex2gini (CLAT is input command line arg #2, CLON
is command line arg #2). KXKY of 755;605 chosen because of a model
domain ( eg 5km * 151x121 ).
#!/bin/csh -f
set LAT=$1
set LON=$2
set DLAT="3.025"
set DLON=`echo "scale=3; 3.775/c(${LAT}*4*a(1)/180)" | bc -l`
exec nex2gini << EOF
restore $RADNTS/nex2gini.nts
KXKY = 755;605
grdarea = #${LAT};${LON};${DLAT};${DLON}
PROJ = LCC/${LAT};${LON};${LAT}
r
e
EOF
The output can be seen under:
http://www.unidata.ucar.edu/content/software/gempak/wseta/
Steve Chiswell
Unidata User Support
On Mon, 2005-02-28 at 14:41, Daryl Herzmann wrote:
Good afternooon, On Mon, 28 Feb 2005, Ryan Jewell wrote:> Yes I know what the MAN says, but apparently I am too stupid to know how > many pixels are going to be in the image produced when using bounds of > 35;-105;45;-90 and wanting 1km resolution. Please tell me again how > many pixels per degree lat/lon there are for 1km res?Well, a hand waving estimate is 0.01 degree of lat/lon is 1 km. So if you want to go from 35 to 45 in the y direction, you need 10 x 100 or 1000 pixels. and -105 to -90, that is 15 x 100 or 1500 pixels.daryl
gembud archives: