[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20040317: 20040317: 20040316: gdtopo for current gempak?
- Subject: 20040317: 20040317: 20040316: gdtopo for current gempak?
- Date: Thu, 18 Mar 2004 16:12:29 -0700
Art,
I was looking to add a higher resolution data set to gdtopo.
I downloaded and formatted a global 30s data set from NGDC
(though unlike the 5 minute set, it does not include bathymetry-
oceans are a constant -500m):
http://www.ngdc.noaa.gov/seg/topo/globe.shtml
Would you be interested in this, if the source data set were 1.8GB
uncompressed? Still limited to LLMXTG (750,000) in the GEMPAK grid file
using IJSKIP.
Steve Chiswell
Unidata User SUpport
>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>
>Art,
>
>Were you using the terrain.gsf file I provided, or
>one you had previously converted?
>
>I provided a file which is usable with both big and little
>endian hosts with the updated gdtopo.
>
>If you had a previous file converted into little endian format
>(eg on a linux box), then that would be a problem. Hopefully
>as with gempak map files, a single vision will suffice.
>
>Steve Chiswell
>
>
>>From: "Arthur A. Person" <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200403171427.i2HERnrV010582
>
>>Steve,
>>
>>Thanks for the quick fix. FYI, I did a make on gdtopo in gempak 5.6.k but
>>when I ran it, I got:
>>
>> GDFILE Grid file junk.topo
>> GAREA Graphics area 22;-130;57;-57
>> GDATTIM Grid date/time 010101/1200
>> TOPOFL Topographic file
>>/home/gempak/gempak-5.6.k/gempak/terrain/terrain.gsf
>> Parameters requested: GDFILE,GAREA,GDATTIM,TOPOFL.
>> GEMPAK-GDTOPO>r
>> look 5841 2801 16360641 400000
>> [GDTOPO -11] Number of grid points is too large.
>> Parameters requested: GDFILE,GAREA,GDATTIM,TOPOFL.
>> GEMPAK-GDTOPO>
>>
>>However, your pre-built binary seems to work fine so that's what we're
>>using.
>>
>> Thanks again...
>>
>> Art.
>>
>>
>>On Tue, 16 Mar 2004, Unidata Support wrote:
>>
>>> Art,
>>>
>>> The particular error you show is due to the fact that the PDF format
>>> has changed since the gdtopo.pdf was created for that program.
>>>
>>> I made a quick pass through the code and fixed the coding type mismatches
>>> and brought it up to current (it could still use some improvement toward
>>> the user interface and newer gemlib features).
>>>
>>> The tarfile is available as:
>>> ftp://gbuddy:address@hidden/nawips-5.6/contrib/gdtopo.tar.gz
>>>
>>> In the tarfile is the code, the terrain data file, and binaries for
>>> Linux, Solaris, and Irix. You should be able to build using the supplied Ma
> k
>> efile
>>> as well.
>>>
>>> I ran the gdtopo program with TOPOFL = terrain.gsf on each of the three
>>> platforms as a test and created the ustopo.gem file which is
>>> GAREA = 22;-130;57;-57
>>>
>>> Note that the original gdtopo.README file made mention of many
>>> limitations in the GEMPAK grid file size, but the current maximum
>>> plottable is 400,000, and the GAREA I used was 369,217 points.
>>>
>>> I will try to further clean this up for inclusion with the 5.7.1 release
>>> (since the original size limitations that made the program so difficult to
>>> work with are not so problematic anymore).
>>>
>>> Let me know if you have problems/feedback,
>>>
>>> Steve Chiswell
>>> Unidata User Support
>>>
>>>
>>>
>>>
>>>
>>> >From: "Arthur A. Person" <address@hidden>
>>> >Organization: UCAR/Unidata
>>> >Keywords: 200403161552.i2GFq7rV014719
>>>
>>> >Hi...
>>> >
>>> >I don't think I got a response on the below (unless it got lost
>>> >somewhere)... any thoughts? Also, I've tried building gdtopo under gempak
>
>>> >5.6.k but it gets stuck in a loop printing:
>>> >
>>> > PROCESS HELP=*
>>> > REFGBL ( $MAPFIL,$RESPOND,$GDFILE,$GAREA,
>>> > PARM NAM E=TOPOFL TYPE=(STRING,72) DEFAU
>>> > END-PROC
>>> > .TITLE
>>> > .LEVEL1
>>> > .VAR GDF ILE
>>> > .INCLUDE GEMHLP:GDTOPO.HLP
>>> > .HELP
>>> > .INCLUDE GEMHLP:GDTOPO.HLP
>>> > .HELP
>>> > .INCLUDE GEMHLP:GDTOPO.HLP
>>> > .HELP
>>> > .INCLUDE GEMHLP:GDTOPO.HLP
>>> > .HELP
>>> > .
>>> > .
>>> > .
>>> >
>>> >If I could fix this loop, it might work and be sufficient for our needs,
>>> >but I can't find in the maze of gempak subroutines where the above loop is
>>> >occurring. Any pointers?
>>> >
>>> >
>>> > Art.
>>> >
>>> >
>>> >On Fri, 5 Mar 2004, Arthur A. Person wrote:
>>> >
>>> >> Hi...
>>> >>
>>> >> Is there a version of gdtopo available somewhere for recent versions of
>>> >> gempak? If not, is there an alternative program available for producing
>>> >> contoured fields of high-resolution (<= 10km) topographic data in gempak
> ?
>>> >>
>>> >> Thanks.
>>> >>
>>> >> Art.
>>> >
>>> >--
>>> >Arthur A. Person
>>> >Research Assistant, System Administrator
>>> >Penn State Department of Meteorology
>>> >email: address@hidden, phone: 814-863-1563
>>> >
>>> --
>>> ***************************************************************************
> *
>>> Unidata User Support UCAR Unidata Progra
> m
>>> (303)497-8643 P.O. Box 300
> 0
>>> address@hidden Boulder, CO 8030
> 7
>>> ---------------------------------------------------------------------------
> -
>>> Unidata WWW Service http://my.unidata.ucar.edu/content/support
>
>>> ---------------------------------------------------------------------------
> -
>>> NOTE: All email exchanges with Unidata User Support are recorded in the
>>> Unidata inquiry tracking system and then made publically 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.
>>>
>>
>>--
>>Arthur A. Person
>>Research Assistant, System Administrator
>>Penn State Department of Meteorology
>>email: address@hidden, phone: 814-863-1563
>>
>--
>NOTE: All email exchanges with Unidata User Support are recorded in the
>Unidata inquiry tracking system and then made publically 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.
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.