![]() ![]() Each file should contain a single Scale statement. The Scale statement specifies a scale factor for values in the color palette from the units used in the color palette to RadarScope’s native units. Table 1 below lists the supported product and unit combinations. RadarScope supports the use of certain units with certain products. Each file should contain a single Units statement. The Units statement identifies the units of the data values specified in the color palette. Table 1 below lists the acceptable product IDs for each product that can use a custom color palette. Each file should contain a single Product statement. For example, a reflectivity color table can specify either “BR” (for base reflectivity) or “DR” (for digital reflectivity). The product statement identifies the radar product types for which this color palette can be used. All text from the semicolon to the end of the line is part of the comment and is ignored by RadarScope. They are preceded by a semicolon ( ) and can contain any text. Comments are placed at the end of a line. ![]() ![]() They can contain any supplemental information that you wish to convey to someone who is viewing or editing the file. RadarScope color palettes are based on the Color Table File Specification originally created by Gibson Ridge Software, with some modifications to support certain RadarScope features.Ĭomments can be included on any line of the file to provide supplemental information. dBZ, miles per hour, etc.), and the colors to associate with those data values. reflectivity, velocity, etc.), the units of data values in the file (e.g. They’re defined in plain text files with a filename extension of “.pal” The contents of the file specify the product types for which the color palette can be used (e.g. RadarScope color palettes specify which colors to apply to data values in a radar product. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |