[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GEMPAK #IRA-792189]: Fwd: [gembud] GEMPAK Docker Image
- Subject: [GEMPAK #IRA-792189]: Fwd: [gembud] GEMPAK Docker Image
- Date: Mon, 11 Dec 2017 08:45:17 -0700
I believe that GEMPAK uses code from McIDAS to render raw level 2 and 3 NEXRAD
files, and so GP programs are unable to re-project to anything other than the
native projection in each file.
One known workaround is to use NEX2GINI or NEX2IMG with a single-entry
nexrad.tbl file (in pwd) for the site you wish to render, output to any GEMPAK
supported projection. Hopefully you can see how this can be done procedurally
for all NEXRAD sites.
Another known workaround is to instead use the Python modules Matplotlib,
Cartopy, MetPy, and python-awips to render level 3 images
http://python-awips.readthedocs.io/en/latest/examples/generated/NEXRAD_Level_3_Plot_with_Matplotlib.html
https://unidata.github.io/MetPy/latest/examples/formats/NEXRAD_Level_3_File.html
> On Sat, Dec 9, 2017 at 9:28 AM, Derek Seymour <address@hidden> wrote:
> >
> >
> > I wanted to see if you knew of a way to specify a different projection
> > from the gpnids_gif program. Below is part of the script I'm using to
> > convert NEXRAD NIDS data into GIF. I'm tried changing the PROJ but haven't
> > been successful and I'm not sure what projection "rad" is using.
> >
> > gpnids_gif << EOF
> > RADFIL = ${FILENAME}
> > RADTIM = last
> > PROJ = rad
> > AREA = ${LAT1};${LNG1};${LAT2};${LNG2}
> > GAREA = ${LAT1};${LNG1};${LAT2};${LNG2}
> > DEVICE = gif|${GIFFILE}|${GIFWIDTH};${GIFHEIGHT}
> > MAP = 7/1/1 + 8/1/1
> > \$mapfil = hicnus.nws+histus.nws
> > LATLON = 0
> > PANEL = 0
> > TITLE = 1/-2/${TITLE}
> > TEXT = 0.7//////sw
> > COLORS = 7=38:38:38;8=112:112:112
> > LINE = 2;3//2
> > IMCBAR = 0
> > CLRBAR = 0
> > CLEAR = y
> > LUTFIL = default
> > STNPLT = 5|0|disco_sites.tbl
> > r
> >
> > e
> > EOF
> >
> >
> > Or perhaps there's a different GEMPAK program I should be using. My goal
> > is to quickly convert NIDS NEXRAD 3 data into georeferenced raster images
> > for use within mapping software.
> >
> > Thanks so much!
> > - Derek
> >
> > On Wed, Dec 6, 2017 at 4:07 PM, Michael James <address@hidden> wrote:
> >
> >> Greetings GEMPAK users,
> >>
> >> I have published the latest Unidata GEMPAK 7.4.1 release as its own
> >> Docker image, available at
> >>
> >> https://hub.docker.com/r/unidata/gempak/
> >>
> >> To Run Containerized GEMPAK (on any Docker-supported host machine):
> >>
> >> 1) docker pull unidata/gempak
> >>
> >> 2) docker run --user gempak -it unidata/gempak:latest
> >>
> >> 3) from within the container you have GEMPAK programs available in $PATH,
> >> and an example script is supplied to show grid parameters from the latest
> >> "A2NAM" grid (defined in $GEMTBL/config/datatype.tbl and
> >> $GEMTBL/data-access/nam.xml to reference the 12km NAM domain), pulled from
> >> the cloud-based AWIPS EDEX server
> >>
> >> [gempak@1b075df3bed4 ~]$ ./rungempak.sh
> >> GDFILE = A2NAM
> >> LSTALL = YES
> >> OUTPUT = T
> >> GDATTIM = all
> >> GLEVEL = 750
> >> GVCORD = PRES
> >> GFUNC = TMPK
> >> GEMPAK-GDINFO>
> >> GRID FILE: AWIPSDB/nam.xml/171206/1200F000
> >>
> >>
> >> GRID NAVIGATION:
> >> PROJECTION: LCC
> >> ANGLES: 25.0 -95.0 25.0
> >> GRID SIZE: 614 428
> >> LL CORNER: 12.1900 -133.4590
> >> UR CORNER: 57.3285 -49.4154
> >> ...
> >> Number of grids in file: 21854
> >> Maximum number of grids in file: 21854
> >>
> >> NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
> >> 10975 171206/1200F000 750 PRES TMPK
> >>
> >> 11176 171206/1200F001 750 PRES TMPK
> >>
> >> 11382 171206/1200F002 750 PRES TMPK
> >>
> >> 11588 171206/1200F003 750 PRES TMPK
> >>
> >> 11794 171206/1200F004 750 PRES TMPK
> >>
> >> 12000 171206/1200F005 750 PRES TMPK
> >>
> >> 12206 171206/1200F006 750 PRES TMPK
> >> ...
> >>
> >
> >
>
>
Ticket Details
===================
Ticket ID: IRA-792189
Department: Support GEMPAK
Priority: Normal
Status: Open
===================
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.