[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #JCJ-120912]: Limit on number of characters in GEMPAK inputs?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [GEMPAK #JCJ-120912]: Limit on number of characters in GEMPAK inputs?
  • Date: Fri, 25 May 2007 15:41:55 -0600
> Hi Steve,
> 
> I am listing the surface data using SFLIST for a list of METAR
> stations.  So, I enter AREA=@JFK;NYC;LGA;... etc.  As the list grows
> longer, I find that some of the requested stations are not listed.  Is
> there a 80-character limit in GEMPAK?  I have to break up the list for
> now.
> 
> Kwan
> 
> 

Kwan,

There is a general line length limit of LLMXLN (which is 128 characters
at compile time, though there are a few places where string lengths in 
processing the
list may be shorter (the stn list is limited to 40 id's for example).

If necessary, you can use the SPRI parameter and create a unique station 
priority
list of stations (a station table and update the data with SFMOD), and then
key on those stations you can identify with a certain priority of greater than 
a certain priority.

Steve Chiswell
Unidata User Support

Ticket Details
===================
Ticket ID: JCJ-120912
Department: Support GEMPAK
Priority: Normal
Status: Closed