716 lines
18 KiB
HTML
716 lines
18 KiB
HTML
|
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type"
|
||
|
|
content="text/html; charset=iso-8859-1">
|
||
|
|
<meta name="GENERATOR"
|
||
|
|
content="Mozilla/4.79 [en] (X11; U; Linux 2.4.9-34smp i686) [Netscape]">
|
||
|
|
<title>ifpServerText User's Guide</title>
|
||
|
|
</head>
|
||
|
|
<body bgcolor="#ffffff">
|
||
|
|
<h1 class="1Heading">
|
||
|
|
ifpServerText User's Guide</h1>
|
||
|
|
<div class="1Heading">April 4, 2006<br>
|
||
|
|
<br>
|
||
|
|
</div>
|
||
|
|
<a name="TableofContents"></a>Table of Contents
|
||
|
|
<h4 class="1Heading"><a href="#Overview">Overview</a></h4>
|
||
|
|
<h4 class="1Heading">
|
||
|
|
<a href="#Running">Running the ifpServerText Program</a></h4>
|
||
|
|
<h4 class="1Heading">
|
||
|
|
<a href="#ExampleData">Example Output</a></h4>
|
||
|
|
<div class="1Heading"><b><a href="#formats">Output Formats</a></b></div>
|
||
|
|
<div class="1Heading">
|
||
|
|
<hr width="100%"></div>
|
||
|
|
<h2 class="1Heading">
|
||
|
|
<a name="Overview"></a>Overview</h2>
|
||
|
|
<div class="1Heading">The ifpServerText is a program to allow reading,
|
||
|
|
writing, deleting, and inventorying text data in the ifpServer.
|
||
|
|
It
|
||
|
|
is an easy way to store items such as smart tools directly into the
|
||
|
|
ifpServer.
|
||
|
|
The following data types are supported:
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<table nosave="" border="1" cols="2" width="100%">
|
||
|
|
<tbody>
|
||
|
|
<tr>
|
||
|
|
<td><b>Category</b></td>
|
||
|
|
<td><b>Description</b></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>Tool</td>
|
||
|
|
<td>Smart tools</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>Procedure</td>
|
||
|
|
<td>Procedures</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>Utility</td>
|
||
|
|
<td>Utilities for smart tools and procedures</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>TextUtility</td>
|
||
|
|
<td>Utilities for text products</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>TextProduct</td>
|
||
|
|
<td>Text product definitions</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>EditArea</td>
|
||
|
|
<td>Edit areas</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>EditAreaGroup</td>
|
||
|
|
<td>Edit area group definitions</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>WeatherElementGroup</td>
|
||
|
|
<td>Weather element groups</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>SelectTR</td>
|
||
|
|
<td>User-defined selection time ranges</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>SampleSet</td>
|
||
|
|
<td>Sample Sets</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>ColorTable</td>
|
||
|
|
<td>Color Tables</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>Map</td>
|
||
|
|
<td>Map Backgrounds and Attributes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td style="vertical-align: top;">Combinations<br>
|
||
|
|
</td>
|
||
|
|
<td style="vertical-align: top;">Zone Combiner Active Combination
|
||
|
|
Files<br>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<div class="1Heading">
|
||
|
|
<hr width="100%"></div>
|
||
|
|
<h2 class="1Heading">
|
||
|
|
</h2>
|
||
|
|
<h3 class="1Heading"><a name="Running"></a>Running the ifpServerText
|
||
|
|
Program</h3>
|
||
|
|
<div class="1Heading"> </div>
|
||
|
|
<div class="1Heading">The command line syntax is:</div>
|
||
|
|
<div class="1Heading"><tt>ifpServerText -h hostname -p portnumber [-u
|
||
|
|
user]
|
||
|
|
[-s -n name -f filename -c class] [-d -n name [-c Config]] [-i [-c
|
||
|
|
Config]
|
||
|
|
[-g -f filename -n name [-c Config]] [-m infoType]</tt></div>
|
||
|
|
<div class="1Heading">
|
||
|
|
<br>
|
||
|
|
A sample command line to store data is:
|
||
|
|
<br>
|
||
|
|
<tt>ifpServerText -h dx4f -p 98000000 -s -n MaxT_Tool -f /tmp/maxt.py
|
||
|
|
-c Tool</tt></div>
|
||
|
|
<div class="1Heading"> </div>
|
||
|
|
<table nosave="" border="1" width="100%">
|
||
|
|
<tbody>
|
||
|
|
<tr>
|
||
|
|
<td><b>Option Syntax</b></td>
|
||
|
|
<td><b>Optional or Mandatory</b></td>
|
||
|
|
<td><b>Description</b></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-h hostname</td>
|
||
|
|
<td>Mandatory (See Note)</td>
|
||
|
|
<td>Specifies the host, upon which the ifpServer is running.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-p port</td>
|
||
|
|
<td>Mandatory (See Note)</td>
|
||
|
|
<td>Specifies the port, upon which the ifpServer is running.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-u user</td>
|
||
|
|
<td>Optional. </td>
|
||
|
|
<td>The connection to the ifpServer will be made using this user,
|
||
|
|
which
|
||
|
|
defaults to the UNIX login user. </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td><b><i>MetaData Mode:</i></b></td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-m infoType</td>
|
||
|
|
<td>Mandatory for meta mode.</td>
|
||
|
|
<td>infoType specifies the type of data to be obtained.
|
||
|
|
Choices are
|
||
|
|
"site", "sitetimezone", "domain", and "singleton". The "site"
|
||
|
|
will
|
||
|
|
list the site for which the ifpServer is configured. The
|
||
|
|
"sitetimezone"
|
||
|
|
lists the site and the timezone for the ifpServer. The
|
||
|
|
"singleton"
|
||
|
|
lists all of the databases that are configured as singletons. The
|
||
|
|
"domain"
|
||
|
|
lists the common database domain information.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-f filename</td>
|
||
|
|
<td>Optional</td>
|
||
|
|
<td>Indicates the name of the file to contain the output
|
||
|
|
information.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td><b><i>Save Mode:</i></b></td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-s</td>
|
||
|
|
<td>Mandatory for save mode.</td>
|
||
|
|
<td>Indicates SAVE mode, requires the -n, -f, and -c switches.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-n name</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the name to store the file under in the ifpServer</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-f filename</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the filename source for the operation.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-c class</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the type of the file. Must be one of:
|
||
|
|
Config,
|
||
|
|
"Tool", "Procedure", "Utility", "TextUtility",
|
||
|
|
"TextProduct",
|
||
|
|
"EditArea", "EditAreaGroup", "WeatherElementGroup", ColorTable",
|
||
|
|
"SampleSet",
|
||
|
|
"SelectTR", "Combinations".</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td><b><i>Delete Mode:</i></b></td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-d</td>
|
||
|
|
<td>Mandatory for delete mode.</td>
|
||
|
|
<td>Indicates DELETE mode, requires the -n switch. The -c
|
||
|
|
switch
|
||
|
|
is used only for the class type of Config.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-n name</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the name of the entry to be deleted from the
|
||
|
|
ifpServer.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-c Config</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the type of the file. Must be one of:
|
||
|
|
Config,
|
||
|
|
"Tool", "Procedure", "Utility", "TextUtility",
|
||
|
|
"TextProduct",
|
||
|
|
"EditArea", "EditAreaGroup", "WeatherElementGroup", ColorTable",
|
||
|
|
"SampleSet",
|
||
|
|
"SelectTR", "Combinations".</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td><b><i>Inventory Mode:</i></b></td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-i</td>
|
||
|
|
<td>Mandatory for inventory mode.</td>
|
||
|
|
<td>Indicates INVENTORY mode. The -c switch is used only
|
||
|
|
for the
|
||
|
|
class type of Config.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-c Config</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the type of the file. Must be one of:
|
||
|
|
Config,
|
||
|
|
"Tool", "Procedure", "Utility", "TextUtility",
|
||
|
|
"TextProduct",
|
||
|
|
"EditArea", "EditAreaGroup", "WeatherElementGroup", ColorTable",
|
||
|
|
"SampleSet",
|
||
|
|
"SelectTR", "Maps, "Combinations"</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td><b><i>Get Mode:</i></b></td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
<td><br>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-g</td>
|
||
|
|
<td>Mandatory for get mode.</td>
|
||
|
|
<td>Indicates GET mode, requires the -n switch. The -f
|
||
|
|
switch is
|
||
|
|
used to output the resulting file to another file, otherwise the output
|
||
|
|
goes to the terminal. The -c switch is used only for the class
|
||
|
|
type
|
||
|
|
of Config.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-f filename</td>
|
||
|
|
<td>Optional</td>
|
||
|
|
<td>If present, the retrieved file will be written to the
|
||
|
|
specified location.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td>-c Config</td>
|
||
|
|
<td>Mandatory</td>
|
||
|
|
<td>Indicates the type of the file. Must be one of:
|
||
|
|
Config,
|
||
|
|
"Tool", "Procedure", "Utility", "TextUtility",
|
||
|
|
"TextProduct",
|
||
|
|
"EditArea", "EditAreaGroup", "WeatherElementGroup", ColorTable",
|
||
|
|
"SampleSet",
|
||
|
|
"SelectTR", "Maps", "Combinations".</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
<font color="#3366ff">Note: The -h serverhost and -p port are
|
||
|
|
predefined
|
||
|
|
based on your installation configration of GFESuite. The -h and
|
||
|
|
-r
|
||
|
|
will be defined for the server host and port specified during
|
||
|
|
installation.
|
||
|
|
If you wish to connect to another server, then these switches will be
|
||
|
|
necessary. </font><font color="#3366ff"> If environment
|
||
|
|
variables ${CDSHOST} or
|
||
|
|
${CDSPORT} are defined, then the default server and port will be
|
||
|
|
determined from the environment variables, unless overridden with the
|
||
|
|
user specified -h and -p switches.</font>
|
||
|
|
<p><br>
|
||
|
|
</p>
|
||
|
|
<div class="1Heading">
|
||
|
|
<hr width="100%"></div>
|
||
|
|
<h3 class="1Heading">
|
||
|
|
<a name="ExampleData"></a>Example Execution</h3>
|
||
|
|
<div class="1Heading">Note that in the following examples, the -h and
|
||
|
|
-p
|
||
|
|
switches are not included. They will default to the currently
|
||
|
|
installed
|
||
|
|
ifpServer configuration.</div>
|
||
|
|
<h4>
|
||
|
|
Saving Data</h4>
|
||
|
|
<tt>camper> <b><i>ifpServerText -s -n MyMaxTool -f
|
||
|
|
../examples/smartTools/Td_SmartTool.py
|
||
|
|
-c Tool</i></b></tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:02.123 IFPServerText.py 289 EVENT: ifpServerText Starting</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:02.132 IFPServerText.py 289 EVENT: Build Date: Mon Sep 2
|
||
|
|
01:43:14 2002 Built By: mark Built On: camper.fsl.noaa.gov (linux2)
|
||
|
|
Version:
|
||
|
|
development</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:02.142 Client.C 161 EVENT: Establishing connection to server
|
||
|
|
on camper.fsl.noaa.gov:98000000 ver=20020626</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:02.150 Client.C 181 EVENT: Connection complete to server
|
||
|
|
on camper.fsl.noaa.gov</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:02.420 IFPServerText.py 164 EVENT: Saved file
|
||
|
|
../examples/smartTools/Td_SmartTool.py
|
||
|
|
under MyMaxTool</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:02.425 IFPServerText.py 289 EVENT: ifpServerText Finished</tt>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h4>Obtaining an Inventory</h4>
|
||
|
|
<tt>camper > <b><i>ifpServerText -c Tool -i</i></b></tt> <br>
|
||
|
|
<tt>21:13:53.870 IFPServerText.py 289 EVENT: ifpServerText Starting</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:53.878 IFPServerText.py 289 EVENT: Build Date: Mon Sep 2
|
||
|
|
01:43:14 2002 Built By: mark Built On: camper.fsl.noaa.gov (linux2)
|
||
|
|
Version:
|
||
|
|
development</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:53.887 Client.C 161 EVENT: Establishing connection to server
|
||
|
|
on camper.fsl.noaa.gov:98000000 ver=20020626</tt>
|
||
|
|
<br>
|
||
|
|
<tt>21:13:53.894 Client.C 181 EVENT: Connection complete to server
|
||
|
|
on camper.fsl.noaa.gov</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Name
|
||
|
|
Access Protect</tt>
|
||
|
|
<br>
|
||
|
|
<tt>----
|
||
|
|
------ -------</tt>
|
||
|
|
<br>
|
||
|
|
<tt></tt><tt>AdjustValue_Down
|
||
|
|
USER
|
||
|
|
Read-Only</tt>
|
||
|
|
<br>
|
||
|
|
<tt>AdjustValue_Up
|
||
|
|
USER
|
||
|
|
Read-Only</tt>
|
||
|
|
<br>
|
||
|
|
<tt></tt><tt>Assign_Value
|
||
|
|
USER Read-Only</tt>
|
||
|
|
<br>
|
||
|
|
<tt>MyMaxTool
|
||
|
|
USER Read-Write</tt>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h4>Getting Data</h4>
|
||
|
|
<p><br>
|
||
|
|
<tt>camper > <b><i>ifpServerText -g -c Tool -n Assign_Value -f
|
||
|
|
1.txt</i></b></tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:19:16.275 IFPServerText.py 286 EVENT: ifpServerText
|
||
|
|
Starting</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:19:16.279 IFPServerText.py 286 EVENT: Build Date: Tue
|
||
|
|
Sep 3 14:33:58 2002 Built By: mark Built On: camper.fsl.noaa.gov
|
||
|
|
(linux2) Version: development</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:19:16.291 Client.C 161 EVENT: Establishing connection to server
|
||
|
|
on localhost:98000044 ver=20020626</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:19:16.312 Client.C 181 EVENT: Connection complete to server
|
||
|
|
on localhost</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:19:16.436 IFPServerText.py 197 EVENT: Got
|
||
|
|
Assign_Value
|
||
|
|
--- written to 1.txt</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:19:16.437 IFPServerText.py 286 EVENT: ifpServerText
|
||
|
|
Finished</tt>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
|
||
|
|
</p>
|
||
|
|
<h4>Deleting Data</h4>
|
||
|
|
<tt>camper > <b><i>ifpServerText -c Tool -d -n MyTool</i></b></tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:21:34.030 IFPServerText.py 286 EVENT: ifpServerText
|
||
|
|
Starting</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:21:34.034 IFPServerText.py 286 EVENT: Build Date: Tue
|
||
|
|
Sep 3 14:33:58 2002 Built By: mark Built On: camper.fsl.noaa.gov
|
||
|
|
(linux2) Version: development</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:21:34.043 Client.C 161 EVENT: Establishing connection to server
|
||
|
|
on localhost:98000044 ver=20020626</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:21:34.059 Client.C 181 EVENT: Connection complete to server
|
||
|
|
on localhost</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:21:34.359 IFPServerText.py 185 EVENT: Deleted MyTool</tt>
|
||
|
|
<br>
|
||
|
|
<tt>15:21:34.360 IFPServerText.py 286 EVENT: ifpServerText
|
||
|
|
Finished</tt>
|
||
|
|
<p></p>
|
||
|
|
<hr width="100%">
|
||
|
|
<h3><a name="formats"></a>Output Formats</h3>
|
||
|
|
The output formats for each of the classes are described in this
|
||
|
|
section.
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h4>Tool, Procedure, Utility, TextUtility, TextProduct, Config,
|
||
|
|
Combinations<br>
|
||
|
|
</h4>
|
||
|
|
The output format is the exact copy of the file in the ifpServer.
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h4>EditArea</h4>
|
||
|
|
Note that this format is not identical to the format of the stored data
|
||
|
|
in the ifpServer, and thus you cannot use the ifpServer format in this
|
||
|
|
routine.<br>
|
||
|
|
<br>
|
||
|
|
<tt>INCLUDE </tt>(or EXCLUDE) flag for the polygon
|
||
|
|
<br>
|
||
|
|
<tt>25
|
||
|
|
</tt>(number of points in this polygon)
|
||
|
|
<br>
|
||
|
|
<tt>-115.23 40.23 </tt>(longitude,
|
||
|
|
latitude for point 1)
|
||
|
|
<br>
|
||
|
|
<tt>-115.11 40.25 </tt>(longitude,
|
||
|
|
latitude for point 2)
|
||
|
|
<br>
|
||
|
|
<tt>......</tt>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h4>EditAreaGroup</h4>
|
||
|
|
The output consists of a list of edit area names, one per line, that
|
||
|
|
are
|
||
|
|
contained within the edit area group, such as:
|
||
|
|
<p><tt>CO_048</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_035</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_046</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_033</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_030</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_049</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_042</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_041</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_038</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_044</tt>
|
||
|
|
<br>
|
||
|
|
<tt>CO_036</tt>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
</p>
|
||
|
|
<h4>WeatherElementGroup</h4>
|
||
|
|
The output consists of the identical format of the weather element
|
||
|
|
group
|
||
|
|
in the ifpServer, such as:
|
||
|
|
<p><tt>MinT_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>MaxT_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>T_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Td_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Wind_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Wx_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Sky_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>PoP_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>SnowAmt_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>QPF_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>FzLevel_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>SnowLevel_SFC:SITE_GRID__Fcst_00000000_0000 -1</tt>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
</p>
|
||
|
|
<h4>SelectTR</h4>
|
||
|
|
The output consists of the identical format of the user-defined
|
||
|
|
selection
|
||
|
|
time range in the ifpServer, such as:
|
||
|
|
<p><tt>54 78</tt>
|
||
|
|
</p>
|
||
|
|
<h4>SampleSet</h4>
|
||
|
|
<tt>#of samples</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude1 latitude1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude2 latitude2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
<h4>ColorTable</h4>
|
||
|
|
<tt># of color cells</tt>
|
||
|
|
<br>
|
||
|
|
<tt>red1 green1 blue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>red2 green2 blue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>.....</tt>
|
||
|
|
<h4>Maps</h4>
|
||
|
|
Map data is much more complicated since there can be POINT, POLYGON,
|
||
|
|
and
|
||
|
|
POLYLINE types of map data. Shapefile attributes are also
|
||
|
|
included
|
||
|
|
in the data stream.
|
||
|
|
<p>For POINT data:
|
||
|
|
<br>
|
||
|
|
<tt>POINT</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude1 latitude1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>label1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>symbolFlag1</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of attributes</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName1: attributeValue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName2: attributeValue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
<br>
|
||
|
|
<tt>POINT</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude2 latitude2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>label2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>symbolFlag2</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of attributes</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName1: attributeValue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName2: attributeValue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
</p>
|
||
|
|
<p>For POLYGON data:
|
||
|
|
</p>
|
||
|
|
<p><tt>POLYGON</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of points</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude1 latitude1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude2 latitude2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>...</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of attributes</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName1: attributeValue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName2: attributeValue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
<br>
|
||
|
|
<tt>POLYGON</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of points</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude1 latitude1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude2 latitude2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>...</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of attributes</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName1: attributeValue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName2: attributeValue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
</p>
|
||
|
|
<p>For POLYLINE data:
|
||
|
|
</p>
|
||
|
|
<p><tt>POLYLINE</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of points</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude1 latitude1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude2 latitude2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>...</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of attributes</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName1: attributeValue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName2: attributeValue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
<br>
|
||
|
|
<tt>POLYLINE</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of points</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude1 latitude1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>longitude2 latitude2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>...</tt>
|
||
|
|
<br>
|
||
|
|
<tt># of attributes</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName1: attributeValue1</tt>
|
||
|
|
<br>
|
||
|
|
<tt>attributeName2: attributeValue2</tt>
|
||
|
|
<br>
|
||
|
|
<tt>....</tt>
|
||
|
|
</p>
|
||
|
|
<h4>MetaInfo</h4>
|
||
|
|
For "site":
|
||
|
|
<br>
|
||
|
|
<tt>siteID</tt>
|
||
|
|
<p>For "sitetimezone":
|
||
|
|
<br>
|
||
|
|
<tt>siteID timezone</tt>
|
||
|
|
</p>
|
||
|
|
<p>For "singleton":
|
||
|
|
<br>
|
||
|
|
<tt>BOU_GRID__MSAS_00000000_0000</tt>
|
||
|
|
<br>
|
||
|
|
<tt>BOU_GRID__Official_00000000_0000</tt>
|
||
|
|
<br>
|
||
|
|
<tt>BOU_GRID__Fcst_00000000_0000</tt>
|
||
|
|
<br>
|
||
|
|
<tt>BOU_GRID__ISC_00000000_0000</tt>
|
||
|
|
<br>
|
||
|
|
<tt>BOU_GRID__LAPS_00000000_0000</tt>
|
||
|
|
<br>
|
||
|
|
<tt></tt>
|
||
|
|
</p>
|
||
|
|
<p>For "domain":
|
||
|
|
<br>
|
||
|
|
<tt>ProjectionID: Grid211</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Grid Size: (145, 145)</tt>
|
||
|
|
<br>
|
||
|
|
<tt>Grid Domain: ((38.0, 27.0), (9.0, 9.0))</tt>
|
||
|
|
<br>
|
||
|
|
<tt>latLonOrigin: (-95.0, 25.0)</tt>
|
||
|
|
<br>
|
||
|
|
<tt>projectionID: 'Grid211'</tt>
|
||
|
|
<br>
|
||
|
|
<tt>gridPointLL: (1, 1)</tt>
|
||
|
|
<br>
|
||
|
|
<tt>lonCenter: 0.0</tt>
|
||
|
|
<br>
|
||
|
|
<tt>latLonUR: (-49.384998321533203, 57.290000915527344)</tt>
|
||
|
|
<br>
|
||
|
|
<tt>gridPointUR: (93, 65)</tt>
|
||
|
|
<br>
|
||
|
|
<tt>stdParallelTwo: 25.0</tt>
|
||
|
|
<br>
|
||
|
|
<tt>projectionType: 'LAMBERT_CONFORMAL'</tt>
|
||
|
|
<br>
|
||
|
|
<tt>stdParallelOne: 25.0</tt>
|
||
|
|
<br>
|
||
|
|
<tt>latIntersect: 0.0</tt>
|
||
|
|
<br>
|
||
|
|
<tt>lonOrigin: 0.0</tt>
|
||
|
|
<br>
|
||
|
|
<tt>latLonLL: (-133.45899963378906, 12.189999580383301)</tt>
|
||
|
|
<br>
|
||
|
|
<tt></tt>
|
||
|
|
</p>
|
||
|
|
</body>
|
||
|
|
</html>
|