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.
>Thanks for the help. I have been able to use SNLIST to see the data >it has the correct STNM = 94119, but has the following as well > >SLAT = ****** SLON = -9999.00 SELV = -9999.0 Luke, This means that the STNM wasn't found in your stations.tbl file, either because your stations.tbl file doesn't match the column locations as you will find in $GEMTBL/stns/snstns.tbl, or you have tabs instead of spces in the file. If you send me your stations.tbl file, I could look if you can't see anything wrong. >I looked at the station table and saw my entry that I added using >STSNS, but still doesn't seem to work. Anyway to just force the file >to have the right lat/lon/elevation? The way to update the station information in a GEMPAK file is through a station table and the use of SNSTNS. However, if your stations.tbl has a problem as previously likely in the use of dcuair, then this won't correct that problem. >Thanks Much >Luke You should be able to plot the profile using AREA=@94119 at this point. You just won't be able to use other geography methods such as AU:c since that info from the station table isn't part of the the station information from the stations.tbl file at this point. Steve Chiswell Unidata User Support Ticket Details =================== Ticket ID: KIE-803069 Department: Support GEMPAK Priority: Normal Status: Open