Re: 20010726: GEMPAK/NAWIPS Shapefiles?

Mike,

The DBF file actually gives field names
(like for the ZONES, you have FIPS, CWA, LAT, LON, ZONE, STATE)
that you will have to modify the code todo whatever you want to for the
different fields. For example, For zones, I created a separate file for
each state and used the ZONE, FIPS and CWA for the $GEMTBL/bounds/zoninfo
file I use for gpwarn.

I put together a tarfile several years ago for the SPC in 
http://www.unidata.ucar.edu/packages/gempak/contrib/readshape.tar.gz

It includes a README file that details how to decode the counties shape file
included within as a starting point. (Its 1999 so take that as an example only).
It also includes the ssfgsf.f file. I modified the FORMAT read statement to
be one character larger than the default. Eg, I had more map segments than
the format allowed. TRhe current ssfgsf.f file in the distribution has been
updated for the 5.6 library, so use that- but you may have to increate
the array sizes depending on the number of line segments in the rivers
database.

Anyhow, thats a starting point. I can look at the rivers shape file on AWIPS
near the end of nest week if you prefer. Send me the URL of the actual file you
are interested in. Otherwise, the code does show how to step through the
segments in relation to the DBF information provided.

When you said "basins", I was wondering if the rfc.nws was what you were were
refering to, or any of the $GEMMAPS/*.rfc.


Steve Chiswell

On Thu, 26 Jul 2001, Michael W Dross wrote:

> 
> Steve,
> 
> Thanks for the quick response. Coincidently I was trying to convert some of
> the the AWIPS shape files:
> 
> http://isl715.nws.noaa.gov/mapdata/newcat/
> 
> If there is a place I can get a copy the program you were referring would
> work
> great for my need.
> 
> Thanks!
> 
> Mike
> 
> 
> 
>                                                                               
>                                       
>                     Steve                                                     
>                                       
>                     Chiswell             To:     Michael W Dross 
> <address@hidden>                          
>                     <chiz@unidata        cc:     address@hidden, GEMPAK 
> support                            
>                     .ucar.edu>           <address@hidden>                     
>                      
>                                          bcc:                                 
>                                       
>                     07/26/2001           Subject:     20010726: GEMPAK/NAWIPS 
>  Shapefiles?                          
>                     06:23 PM                                                  
>                                       
>                                                                               
>                                       
>                                                                               
>                                       
> 
> 
> 
> 
> 
> 
> Mike,
> 
> GEMPAK has the rfc bounds maps to use.
> 
> I have a program that I created to convert shapefiles.
> Of course, since the name attribute fields vary
> in the self describing data sets, you would have to modify the
> fields according to which parameters you wanted to
> use in the shapefile. It works using the .SHP and .DBF
> files that the AWIPS files have.
> 
> If you want to convert from WXP format,
> the doc file in the $GEMMAPS directory describes the
> ascii format for gempak maps. Then, compile the
> ssfgsf program to generate the binary map database.
> 
> Steve Chiswell
> Unidata User Support
> 
> 
> On Thu, 26 Jul 2001, Michael W Dross wrote:
> 
> > Hi,
> >
> > I am wanting to convert some GIS shapefiles (.shp)  into a format that
> > GEMPAK/NMAP2 can display, specifically river basins
> > across our area.  Is there a utility to do this?   I have a program that
> > will convert shapefiles into a format WXP can handle, but
> > I don't thinks this will be of much use in the GEMPAK arena.
> >
> > Thanks!
> >
> > Mike
> >
> >
> 
> 
> 
> 
> 
> 
> 
>