US 7,646,328 B2Grant
Versatile constant altitude plan position indicator for radars
Issue Date:2010-01-12
•27 Claims
•8 Drawing Sheets
Abstract
A method and a system to process radar volume scan data along an azimuth angle of a radar, to interpolate the radar volume scan data taken from adjacent elevation angles along the azimuth angle of the radar to obtain radar data corresponding to a predetermined altitude along the azimuth angle, and to display the radar volume scan data obtained corresponding to the predetermined altitude on a PPI display.
Metadata
Assignee
- Honeywell International Inc.
Inventors
- Vishnu V. Makkapati
- Pravas R. Mahapatra
Application Information
Application Number:US 11/235,047
Filing Date:2005-09-26
Priority Date:2005-03-10
Art Unit:3662
Classifications
IPC:
G01S13/95
Patent Drawings (8 sheets)
Description
Cross Reference to Related Applications
[0001] This application claims priority to India Patent Application No. 150/KOL/2005, filed Mar. 10, 2005, which is incorporated herein by reference.
Background
[0002] Constant Altitude Plan Position Indicator (CAPPI) is a form of data presentation in weather radars. For CAPPI scanning, a horizontal slice is taken through the radar volume scan data at a constant altitude above the earth surface. The radar volume scan data is extracted from full 3-D scan data, and is converted to a 2-D format for presentation in polar coordinates on a computer display, paper printout, or any other two-dimensional surface.
[0003] CAPPI is a variant of the more general Plan Position Indicator (PPI) that displays weather parameters along radials from the radar as function of an azimuth scan angle. A radar antenna transmits and receives pulses at different elevation angles φ and at different azimuth angles θ by both performing a rotating scan operation in the azimuth and by varying the elevation angle. PPI data is generated and recorded by scanning a beam circularly at a constant elevation angle. A volume scan consists of multiple constant-elevation azimuth scans. PPI volume scan data at multiple elevation angles is used to produce CAPPI.
[0004] Near the radar site there is often ground clutter, which may interfere with obtaining a clean display of weather. In the beam position(s) with low elevation angle(s), clutter is often so strong that filtering the ground clutter also removes weather signals resulting in gaps in the weather display.
[0005] In PPI scanning, the radar beam may overshoot precipitation altitudes, for a part of the radial, and thereby not detect any precipitation at the corresponding ranges (i.e. distances from the radar).
[0006] Weather radar systems often deliberately degrade the time resolution for observation in order to improve signal quality and also to reduce the data handling specifications over long observation periods. The PPI volume scanning mode also degrades the spatial resolution by skipping certain elevation angles to reduce the time for scanning the region around the radar.
[0007] The maximum elevation of scan may be limited to a value less than 90° (i.e. vertical pointing), leaving a conical ‘blind zone’ over the radar location. This causes a circular hole to appear in the CAPPI, the hole being larger at higher altitudes.
Brief Description of the Drawings
[0008] FIG. 1 illustrates a schematic radar system according to an example embodiment.
[0009] FIG. 2 illustrates a schematic cross-section of Earth and a surface at a constant altitude above the earth's surface at which Constant Altitude Plan Position Indicator (CAPPI) data is generated according to an example embodiment.
[0010] FIG. 3 illustrates a schematic partial cross-section of CAPPI geometry in a vertical section above a plane tangent to the Earth at the radar location, as employed in an example embodiment.
[0011] FIG. 4 illustrates a schematic plan view of an area around the radar showing a constant-range circle over which CAPPI data is generated according to an example embodiment.
[0012] FIG. 5 illustrates a process of generating a mechanism, such as look up tables, according to an example embodiment.
[0013] FIGS. 6A , 6B, and 6C illustrate a process of generating CAPPI data using the mechanisms generated in FIG. 5 according to an example embodiment.
[0014] FIG. 7 shows a diagrammatic representation of a machine in the form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed, according to an example embodiment.
Detailed Description
[0015] FIG. 1 illustrates a schematic radar system 100 according to an example embodiment. The radar system 100 includes an antenna 101 coupled to a radar receiver 102, a processor 103 coupled to the radar receiver 102, and a Plan Position Indicator (PPI) display 104 coupled with the processor 103. The processor 103 receives volume scan spherical coordinate data from the radar receiver 102, converts the radar data to rectangular coordinate data, and provides the rectangular coordinate data to the display 104. Additionally or alternatively, the processor 103 may receive the volume scan data recorded from a previous scan in a computer memory 105.
[0016] FIG. 2 illustrates a schematic cross-section 200 of Earth 201 and a surface 202 having a constant altitude H above the earth's surface at which Constant Altitude Plan Position Indicator (CAPPI) data is generated according to an example embodiment. An origin of the radar antenna 101 is represented at point D on the earth's surface. The center of the Earth is represented by O. The Earth's radius is represented by Re. Point C represents the point at which the CAPPI data may be generated at the altitude H. The angle at the earth's center between point D and point C is represented by β. The point E is directly above point D at the altitude H.
[0017] An elevation angle φ represents the angle at point D between the earth's surface (i.e. a tangent to the Earth's surface at point D) and the line CD. The specific elevation angle φ may have been skipped during the radar scan operation. In an example embodiment, gaps such as this may be filled using an interpolation scheme to potentially provide spatially continuous information of weather at the given altitude H. The elevation angle φ of the radar is computed for each increment in EC using equation set (2) and FIG. 2 .
[0018]
[0019] Because the Earth is curved and the scan elevation interval may be between a minimum value and a maximum value, a point such as point C in FIG. 2 on the CAPPI surface may have an elevation angle φ outside the scanned elevation interval (or in between two scanned elevation angles). For altitudes on the CAPPI surface that are below the minimum scan elevation, the data may be taken from the lowest elevation angle available. Conversely, if a selected point C is above the maximum scan elevation, the data may be taken from the highest elevation angle available.
[0020] Embodiments may account for bending of the radar beam. The radar beam may bend as it passes through layers of air with different refractive indices. Under standard atmospheric conditions, the bending of the radar beam has a radius of curvature about four times the radius of the Earth. Thus, under normal conditions, a radar beam emitted horizontally and at other elevations would take paths that curve slightly below straight line paths.
[0021] FIG. 3 illustrates a schematic partial cross-section of CAPPI geometry 220 in a vertical section above a plane tangent to the Earth at the radar location D, as employed in an example embodiment. The horizontal line through D is the tangent to the Earth's surface at point D and the arc 225 represents the spherical surface, at a height H above the radar location D, at which Constant Altitude Plan Position Indicator (CAPPI) data is generated according to an additional example embodiment.
[0022] In a volume scanning mode, an elevation angle φ of the antenna 101 is changed incrementally by a determined angle and a horizontally rotating scanning operation is performed along each incremented elevation angle. CAPPI data for point C may not be readily available in the volume scan data, and may be constructed from radar data gathered along other elevation angles and/or azimuth angles, in embodiments of the present invention. The CAPPI data at point C may be generated by interpolating the gathered radar data in elevation. Elevation angles φm and φm-1 denote the elevation angles of the radar scan that are closest to angle φ, on either side, as shown in FIG. 3 . The weather parameter (e.g. reflectivity Z) at the point C, having elevation 4, may be calculated as the weighted average of radar resolution cell data from points A and B, having elevations φm-1 and φm, respectively, in an embodiment.
[0023] In FIG. 3 , the distance from point D to point B (DB) may be represented as RB, the distance from point D to point A (DA) may be represented as RA, and the distance from point D to point C (CD) may be represented as RC. Each of the range lines DB and DA include curves representing bent propagation paths between the radar and the points B and A, respectively.
[0024] In embodiments, the CAPPI construction includes two processes. The first process includes a mechanism to generate CAPPI scan line data of a weather parameter Z. For a specified CAPPI altitude, the two bounding radials φm-1 and φm (i.e. the value of m), the interpolation weight between them, and the ranges CD, DB and DA depend on the length of the arc EC alone, and are independent of the azimuth angle θ.
[0025] In the example embodiments, the CAPPI scan line data is generated by keeping EC constant and varying the azimuth angle θ of the radar from 0 to 2π (or a certain θmin to θmax for a sectoral CAPPI) clockwise or counter-clockwise depending on the direction of the radar scan. As discussed in more detail with regard to the process of FIGS. 6A , 6B, 6C, after completing the circular arc at a constant arc length EC, the arc length EC may be incremented by 1 km (or any other determined step, increment or unit) and the azimuth angle θ may varied again from 0 to 2π (or θmin to θmax).
[0026] In the second step of the CAPPI construction, the CAPPI scan line data is presented to the PPI coordinate conversion, formatting and display mechanism.
[0027] FIG. 4 illustrates a schematic plan view 230 of an area around the radar showing a horizontal projection of a constant-range circle 235 over which CAPPI data is generated according to an example embodiment. The circle 235 includes a radius of (Rc)(cos φ). This radius is the horizontal component of the range shown as the line segment CD in FIG. 3 . The CAPPI scan data may display weather conditions occurring over any given constant-height surface within a half-spherical observation volume of the radar. The CAPPI data may be generated about the radar origin D over azimuth angle θ from 0°≦θ≦360°. The azimuth angle θ may be incremented by 1° or by any other angular increment as specified in the radar data in the CAPPI generation.
[0028] FIG. 5 illustrates a process 300 of generating a mechanism, such as look up tables, according to an example embodiment. The process 300 includes the first of the two processes discussed with regard to FIG. 3 .
[0029] At block 305 of FIG. 5 , the process begins. At block 310, a value of M is selected such that M−1 equals the number of elevation scans performed by the radar 102. In embodiments of the process, set φ0 equal to zero, set φM equal to 90°, and the angles be through φM-1 equal respectively to the radar scan elevation angles from the lowest to the highest along the determined increments.
[0030] At block 320, an arc length EC (φm) may be calculated for each elevation angle φm of the radar. The interval for the elevation number m may be: 0≦m≦M. The elevation number m may be incremented, by 1, for example, in the interval. The arc length EC may be calculated for each elevation angle φm with the formula: EC(φm)=(Re+H)×[cos−1(Re cos(φm)/(Re+H))−φm].
[0031] At block 330, a first mechanism of EC(φm) values in terms of the elevation number m of the radar may be generated using the values generated at block 320. The first mechanism may be a look up table indexed by elevation number m and/or elevation angle φm, a graph, an algorithm, a chart, and/or any other possible mechanism.
[0032] At block 335, the process of generating the first mechanism ends.
[0033] FIGS. 6A , 6B, and 6C illustrate a process 400 of generating CAPPI data using the mechanisms generated in FIG. 5 according to an example embodiment.
[0034] At block 401, the process 400 of FIG. 6A begins.
[0035] At block 405, the process 400 sets the value of the arc length EC, illustrated in FIG. 3 , to zero. The value of M is set to one more than the number of total scan elevation angles φ in the radar volume scan data set.
[0036] At block 410, the length EC is incremented by one step, which may be one (1) km or any other chosen value.
[0037] At block 415, the range CD and the corresponding angle φ may be calculated using equation (2). The range AC may be calculated using the equation: AC=CD×sin(φ−φM-1)/(cos(φM-1+β). The range DA may be calculated by solving for DA in the equation:
[0038]
Optionally, for a given radar and scan cycle, instead of calculating the range DA, the values of range DA may be read from a pre-stored mechanism, such as a pre-stored look-up table LUTR, of range DA indexed by arc length EC. The pre-stored mechanism may be from a previous computation of the range DA for the same CAPPI altitude.
Optionally, for a given radar and scan cycle, instead of calculating the range DA, the values of range DA may be read from a pre-stored mechanism, such as a pre-stored look-up table LUTR, of range DA indexed by arc length EC. The pre-stored mechanism may be from a previous computation of the range DA for the same CAPPI altitude.
[0039] The azimuth angle θ may be incremented from θmin to θmax in steps of Δθ, where Δθ may be any degree, such as 1 degree. The radar data ZA may be retrieved at range DA, from the original scan data at elevation φM-1, for all θ values. The radar data ZA may be stored in a CAPPI scan line data buffer indexed by arc length EC and azimuth angle θ.
[0040] At block 420, the process 400 is queried as to whether EC is less than or equal to EC(φM-1). If the answer to the query is ‘yes’ then the process may proceed to block 410. If the answer to the query is ‘no’, then the process may proceed to block 425.
[0041] At block 425, m may be initialized to M−1 and the process may proceed to block 430 in FIG. 6B .
[0042] At block 430, the weights BC and AC may be calculated using the equations BC=CD×sin(φm−φ)/(cos(φm+β) and AC=CD×sin(φ−φm-1)/(cos(φm-1+β), where CD and φ are obtained using equation (2). Optionally, for a given radar and scan cycle, the values of weights BC and AC may be read from a pre-stored mechanism, such as a pre-stored look-up table LUTW, from a previous computation of BC and AC for the same CAPPI altitude.
[0043] At block 435, determine ranges DB and DA solving for DB and DA in the equations:
[0044]
respectively. Optionally, for a given radar and scan cycle, the values of ranges DB and DA may be read from a pre-stored mechanism, such as the look-up table LUTR indexed by arc length EC, from a previous computation of ranges DB and DA for the same CAPPI altitude.
respectively. Optionally, for a given radar and scan cycle, the values of ranges DB and DA may be read from a pre-stored mechanism, such as the look-up table LUTR indexed by arc length EC, from a previous computation of ranges DB and DA for the same CAPPI altitude.
[0045] At block 440, CAPPI data is calculated at point C. Weather data ZA may be retrieved from the radar volume scan data for elevation φm-1 and range DA. Weather data ZB may be retrieved for elevation φm and range DB from the radar volume scan data. The weather data ZC at CAPPI data point C is the interpolation of ZA and ZB with weights BC and AC, and may be calculated according to the equation
[0046]
[0047] At block 445, the length EC is incremented by one step.
[0048] At block 450, the process is queried as to whether EC is less than or equal to EC(φm-1). If the answer to the query is ‘yes’ then the process may proceed to block 430. If the answer to the query is ‘no’, then the process may proceed to block 455.
[0049] At block 455, m is decremented by 1.
[0050] At block 460, the process is queried as to whether m is equal to 1. If the answer to the query is ‘no’ then the process may proceed to block 430. If the answer to the query is ‘yes’, then the process proceeds to block 465. The process may proceed to block 465 in FIG. 6C .
[0051] At block 465, for a given arc length EC, calculate weight BC using the equation BC=CD×sin(φ1−φ)/(cos(φ1+β), then solve for range DB using the equation:
[0052]
Angle θ may be incremented from θmin to θmax in steps of Δθ. The radar data ZB at range DB may be retrieved from the scan data at elevation φ1, for all θ values. The radar data ZB may be stored in CAPPI scan line data buffer indexed by length EC and angle θ. Optionally, for a given radar and scan cycle, the values of DB may be read from the pre-stored mechanism, such as the pre-stored look-up table LUTR indexed by EC, from a previous computation of range DB for the same CAPPI altitude.
Angle θ may be incremented from θmin to θmax in steps of Δθ. The radar data ZB at range DB may be retrieved from the scan data at elevation φ1, for all θ values. The radar data ZB may be stored in CAPPI scan line data buffer indexed by length EC and angle θ. Optionally, for a given radar and scan cycle, the values of DB may be read from the pre-stored mechanism, such as the pre-stored look-up table LUTR indexed by EC, from a previous computation of range DB for the same CAPPI altitude.
[0053] At block 470, the length EC is incremented by one step.
[0054] At block 475, the process is queried as to whether EC is less than or equal to EC(φ0) at φ0=0°. If the answer to the query is ‘yes’ then the process proceeds to block 465. If the answer to the query is ‘no’, then the process proceeds to block 480.
[0055] At block 480, CAPPI scan line data generation ends.
[0056] At block 485, PPI display scan conversion occurs, as described herein. PPI scan converted CAPPI scan line data may be obtained and stored.
[0057] At block 490, the generated CAPPI radar data Zc along the surface 202 at the altitude H above the earth's surface may be displayed on the display 104 and/or printed.
[0058] FIG. 7 illustrates a diagrammatic representation of a machine in the example form of a computer system 500 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a server computer, a client computer, a personal computer (PC), a tablet PC, a mobile device, a palmtop computer, a laptop computer, a desktop computer, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
[0059] Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
[0060] The example computer system 500 includes the processor 103/502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory 504 and a static memory 506, which communicate with each other via a bus 508. The computer system 500 may further include a video display unit 510 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 500 also includes an input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), a disk drive unit 516, a signal generation device 518 (e.g., a speaker) and a network interface device 520.
[0061] The disk drive unit 516 includes a machine-readable medium 522 on which is stored one or more sets of instructions (e.g., software 524) embodying any one or more of the methodologies or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504, the static memory 506, and/or within the processor 502 during execution thereof by the computer system 500. The main memory 504 and the processor 103/502 also may constitute machine-readable media. In an additional embodiment, the mechanism (such as the look up table) is not stored, but rather a processor or additional processor is used to generate the weights substantially in real-time. This additional embodiment may be useful, e.g. where processing speed is more readily available as compared with memory.
[0062] The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.
[0063] The instructions 524 may further be transmitted or received over a network 526 via the network interface device 520.
[0064] Embodiments may be utilized by running the program on a digital computer that receives data from a radar receiver to generate a CAPPI display on the monitor in quasi-real-time. Embodiments are also useful for generating CAPPI display from pre-recorded radar data available from public or private data archives. The display unit 510 may be of any resolution and embodiments may be implemented without addition of any special hardware to a computer.
[0065] The mechanism(s) may also be implemented on a Digital Signal Processing (DSP) chip or any other computer board. The mechanism(s) is(are) implemented in a high level programming language for ease of coding, though they may also be implemented in other types of programming languages, e.g. in assembly or machine languages to achieve higher processing speed and reduced memory overheads. Due to the versatile nature of the mechanism, the technique may be embedded in hardware for CAPPI display of data from radar receiver during real-time operation.
[0066] Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the example system is applicable to software, firmware, and hardware implementations.
[0067] Using the embodiments of methods and systems described herein, a horizontal slice is taken through the radar volume scan data at constant altitude above the earth surface using Constant Altitude Plan Position Indicator (CAPPI). Weather radar systems often deteriorate the spatial sampling of the scan volume by skipping certain elevation angles to reduce time used for scanning the region around the radar. This results in gaps in the CAPPI data, which have been filled in the embodiment using an interpolation scheme. Other CAPPI schemes may utilize a nearest neighbor approach, which may introduce artifacts into the display, including sharp jumps or boundaries between annular segments of the display. Embodiments determine the display parameter at the CAPPI surface by making a weighted interpolation of data from adjacent scan elevations to obtain a smoother and more accurate CAPPI display. The CAPPI scan line data constructed along each azimuth angle may be scan converted to computer display coordinates.
[0068] In systems described herein, the elevation from the ground of the CAPPI surface may be first specified, and CAPPI data for increments in EC between the vertical and the highest elevation angle of radar is taken from the radar volume scan data for the highest elevation angle. The CAPPI data for increments in EC between the lowest elevation angle and 0° (i.e. horizontal) is taken from the radar volume scan data for the lowest elevation angle. The length of the arc EC for each elevation angle is computed. These pre-computed arc lengths may be used for determining the adjacent elevation angles corresponding to each increment in EC; the scheme may avoid computation of adjacent elevation angles for each increment in EC. Further, interpolation may add little overhead due to calculation of weights and weighted average of weather data from adjacent elevation angles.
[0069] In embodiments described herein, a mechanism, such as a graph, a look-up table (LUT), a set of equations, and/or an algorithm may be used for calculating or storing the arc lengths EC for each radar beam elevation angle φ, and weights and ranges for each increment in EC for a given altitude H from ground. For ease of explanation, the mechanism is a look up table (LUT) in these embodiments. The LUT for ranges and weights (i.e. the second and third mechanisms) is implemented as one dimensional arrays indexed by the number of the increments in EC from the vertical, while the LUT for lengths of EC for each elevation angle is indexed by the elevation number. The LUT can be computed with minimal processing overhead and can be accessed quickly. The technique may be efficient because the memory used for storing the LUTs may be minimal and an efficient calculation of the lengths may add less processing overhead. This technique may not recompute the LUT unless the altitude or the elevation angles of the radar data change. Since the elevation angles of the radar data are less likely to change, multiple LUTs may be computed and stored for different altitudes. The use of LUTs enables high performance with minimal memory overhead and memory may be less expensive as compared to the increase of the processing speed of hardware. It also enables the CAPPI data computation to be carried on processors of lower capability such as those in airborne computers.
[0070] CAPPI may avoid issues associated with PPI by picking constant altitude data from different elevation scans. However, because CAPPI includes data from all elevation scans in the radar volume, processing in some embodiments may take considerably longer than PPI displays.
[0071] As described herein, the CAPPI data generation process described in FIGS. 6A , 6B, and 6C is compatible with any PPI display algorithm or device that may handle any user-specified rotation, zooming, magnification, distance interval, and sector selection. This scheme may provide additional features for displaying CAPPI. The CAPPI data generated using these embodiments are indexed by the horizontal distance (along constant-height arc) from the vertical through the radar, and the azimuth angle, and may be converted to any other coordinate systems, e.g. latitude-longitude, Cartesian. Embodiments are suitable for generating CAPPI data for use with techniques superposing CAPPI data from overlapping radars, where the radar data should be converted from the individual radar coordinates to a universal grid system. CAPPI, generated using this interpolation scheme, suits viewing specifications and may be more accurate and continuous than data generated using a nearest neighbor scheme.
[0072] Embodiments described herein may be used with the presentation and display of weather radar data by users such as meteorologists, air traffic controllers, pilots, TV weather broadcasters, and disaster monitors. Embodiments can be licensed to companies working on general radars, weather radars, imaging radars, meteorological data products and PPI displays.
[0073] The following description includes terms, such as “up”, “down”, “upper”, “lower”, “first”, “second”, etc. that are used for descriptive purposes only and are not to be construed as limiting. The elements, materials, geometries, dimensions, and sequence of operations may all be varied to suit particular applications. Parts of some embodiments may be included in, or substituted for, those of other embodiments. While the foregoing examples of dimensions and ranges are considered typical, the various embodiments are not limited to such dimensions or ranges.
[0074] The Abstract is provided to comply with 37 C.F.R. § 1.74(b) to allow the reader to quickly ascertain the nature and gist of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.
[0075] The illustrations of embodiments described herein are intended to provide a general understanding of the structure of various embodiments, and they are not intended to serve as a complete description of all the elements and features of apparatus and systems that might make use of the structures described herein. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The figures are merely representational and may not be drawn to scale. Certain proportions thereof may be exaggerated, while others may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
[0076] In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments have more features than are expressly recited in each claim. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. One skilled in the art will recognize that other configurations are available and other methods of manufacture may function as well without exceeding the scope of the disclosed subject matter.
[0077] While particular embodiments have been illustrated and described, they are merely examples and a person skilled in the art may make variations and modifications to the embodiments described herein without departing from the spirit and scope of the presently disclosed subject matter.
Claims
The invention claimed is:
1. A method to display weather radar data in a Constant Altitude Plan Position Indicator (CAPPI) system comprising:
processing radar volume scan data along an azimuth angle of a radar;
interpolating the radar volume scan data taken from adjacent elevation angles along the azimuth angle of the radar and in a local vertical direction that is orthogonal to a CAPPI surface to obtain weather radar data corresponding to a predetermined altitude along the azimuth angle; and
displaying the weather radar data obtained corresponding to the predetermined altitude on a two-dimensional display.
2. The method of claim 1 further comprising processing the radar volume scan data along a plurality of azimuth angles to obtain radar Constant Altitude Plan Position Indicator (CAPPI) scan line data corresponding to the predetermined altitude.
3. The method of claim 2 further comprising processing the radar volume scan data along one of the plurality of azimuth angles from a minimum azimuth angle to a maximum azimuth angle to obtain the radar CAPPI scan line data corresponding to the predetermined altitude.
4. The method of claim 2 further comprising generating CAPPI scan line data over a predetermined distance interval from the radar.
5. The method of claim 1 further comprising determining a distance, along a constant altitude surface associated with the predetermined altitude, between an intersection of a vertical at the location of the radar with the constant altitude surface and an intersection of a line of predetermined elevation from the radar with the constant altitude surface.
6. The method of claim 5 further comprising determining two adjacent elevation angles in a radar volume scan data set for any given point on the constant-altitude surface.
7. The method of claim 6 further comprising determining weights for averaging data from the adjacent elevation angles based on the distance along the vertical.
8. The method of claim 7 further comprising calculating the weights and corresponding ranges at the predetermined altitude using at least one of a graph, a chart, a table, an algorithm, and a set of equations.
9. The method of claim 1 wherein interpolating includes using a weighted average interpolation mechanism, wherein the mechanism includes at least one of a graph, a chart, a table, an algorithm and a set of equations.
10. A computer-readable medium having program instructions to perform a method to display weather radar data in a Constant Altitude Plan Position Indicator (CAPPI) system, the method comprising:
processing radar volume scan data along an azimuth angle of a radar;
interpolating the radar volume scan data taken from adjacent elevation angles along the azimuth angle of the radar and in a local vertical direction that is orthogonal to a CAPPI surface to obtain weather radar data corresponding to a predetermined altitude along the aximuth angle; and
displaying the weather radar data obtained correspondence to the predetermined altitude on a two-dimensional display.
11. A process of generating CAPPI data at a point C having an altitude H along an azimuth angle θ, the process comprising:
using a computer processor for calculating arc length EC(φm) for each elevation angle φm of a radar using EC(φm)=(Re+H)× [cos−1 (Re cos (φm)/(Re+H))− φm], where m includes an elevation number, where 0≦m<M, where M−1 includes a number of elevation scans performed by the radar, where Re includes the radius of the earth, and H includes the altitude at which CAPPI data is to be generated;
using the computer processor for generating a first technique of EC(φm) values indexed by a group selected from the elevation number m and the elevation angle φm of the radar;
using the computer processor for determining the elevation angle φ for arc length EC at each determined increment along the arc EC from EC(φM) to EC(φ0) using φ=tan −1[((Re+H)cos (β)−Re)/((Re+H) sin (β))], where β= (EC)/(Re+H);
using the computer processor for determining, at each incremented arc length EC in an interval 0<EC<EC(φM-1), a weight AC using weight AC=CD×sin(φ−φM-1)/(cos(φM-1+β), where CD =√{[(Re+H)sin(β)]2+[(Re+H)cos(β)−Re]2}, and calculating a range line DA for the domain [0: EC(φM-1)] by solving equation
using the computer processor for determining, at each incremented arc length EC in an interval EC(φM-1)<EC<EC(φ1), weights BC and AC, respectively corresponding to elevation angles φm and φm-1 adjacent to elevation angle φ, where weight BC=CD ×sin(φm−φ)/(cos(φm+β) and weight AC=CD×sin(φ−φm-1)/(cos(φm-1+β), calculating a range DB for the domain [EC(φM-1): EC(φ1)]from the radar to a point B vertically above the point C along the azimuth angle θ by solving equation
and calculating the range line DA for the domain [EC(φM-1): EC(φ1)]from the radar to a point A vertically below the point C along the azimuth angle θ by solving equation
and
using the computer processor for calculating, in an interval EC(φ1)<EC<EC(φ0), a weight BC using weight BC=CD×sin(φ1− φ)/(cos(φ1β), and calculating the range DB for the domain [EC(φ1): EC(φ0)]by solving equation
12. The process of claim 11 further comprising using the computer processor for generating a second technique containing the range line DA indexed by arc length EC for the domain [0: EC(φM-1)].
13. The process of claim 12 further comprising using the computer processor for generating a third technique of weights BC and AC indexed by arc length EC for the domain [EC(φM-1):EC(φ1)].
14. The process of claim 13 wherein the first, second and third techniques are selected from a group including an algorithm, a chart, a table, a graph, and an equation.
15. The process of claim 12 further comprising using the computer processor for storing in the second technique, for the domain [EC(φM-1):EC(φ1)],the range DB and the range line DA indexed by arc length EC.
16. The process of claim 12 further comprising using the computer processor for storing in the second technique, for the domain [EC(φ1):EC(φ0)], the range DB indexed by arc length EC.
17. The process of claim 11 further comprising:
using the computer processor for retrieving radar data ZA for the domain [0: EC(φM-1)]at the range line DA from a radar volume scan data at the elevation angle φM-1 and setting radar data ZCto radar data ZA;
using the computer processor for retrieving radar data ZA and ZB at the range lines DA and DB, respectively, for the domain [EC(φM-1): EC(φ1)], from the radar volume scan data at two elevation angles φ adjacent to the point C, and calculating CAPPI data ZC at the point C using equation
and
using the computer processor for retrieving radar data (ZB) at the range DB, for the domain [EC(φ1): EC(φ0)], from the radar volume scan data at the elevation angle φ1and setting radar data ZC to radar data ZB for the domain [EC(φ1): EC(φ0)].
18. The process of claim 17 further comprising:
using the computer processor for setting arc length EC to a minimum distance ECmin;
using the computer processor for setting the increment associated with the arc length EC, ΔEC, to 1 km;
using the computer processor for setting an azimuth angle increment Δθ to 1°;
using the computer processor for setting azimuth angle θ to a starting azimuth angle θmin; and
using the computer processor for querying whether θ≧an ending azimuth angle θmax.
19. The process of claim 18 wherein if θ<θmax, then CAPPI data at point C is generated at the azimuth angle θ, and the azimuth angle θ is set to θ+Δθ.
20. The process of claim 18 wherein if θ≧θmax, and the arc length EC<BC (0°), then the azimuth angle θ is reset to the starting azimuth angle θmin, and the arc length EC is set to EC+ΔEC.
21. The process of claim 17 further comprising using the computer processor for displaying the CAPPI data generated at the altitude in a PPI display.
22. The process of claim 21 wherein the PPI display supports an application selected from a group including rotation, zooming, magnification, distance interval, and sector selection.
23. The process of claim 11 wherein the process includes a group selected from a graph, a chart, a table, an algorithm and a set of equations.
24. The process of claim 11 wherein the process uses a processor using radar volume scan data obtained from a group selected from data obtained in real-time and data retrieved from storage.
25. The process of claim 11 wherein each of the range lines DB and DA include curves representing bent propagation paths between the radar and the points B and A, respectively.
26. A system to display weather radar data in a Constant Altitude Plan Position Indicator (CAPPI) system comprising:
means for processing radar volume scan data along an azimuth angle of a radar;
means for interpolating the radar volume scan data taken from adjacent elevation angles along the azimuth angle of the radar and in a local vertical direction that is orthogonal to a CAPPI surface to obtain CAPPI data corresponding to a predetermined altitude along the azimuth angle;
means for performing the above two steps for the azimuth angles within a specified range; and
means for displaying the CAPPI data obtained corresponding to the predetermined altitude.
27. The system of claim 26 further comprising means for generating CAPPI data from repeatedly performed similar radar volume scans by the radar.
Patent Citations (30)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3769442(A) | 1973-10-01 | Heartz et al. | Examiner |
| US4002827(A) | 1977-01-01 | Nevin et al. | Applicant |
| US4547803(A) | 1985-10-01 | Richards | Applicant |
| US4697185(A) | 1987-09-01 | Thomas et al. | Applicant |
| US4931801(A) | 1990-06-01 | Hancock | Applicant |
| US5027122(A) | 1991-06-01 | Wieler | Examiner |
| US5036326(A) | 1991-07-01 | Andrieu et al. | Applicant |
| US5136296(A) | 1992-08-01 | Roettger et al. | Applicant |
| US5379215(A) | 1995-01-01 | Kruhoeffer et al. | Applicant |
| US5440483(A) | 1995-08-01 | Badoche-Jacquet et al. | Examiner |
| US5519401(A) | 1996-05-01 | Farmer et al. | Applicant |
| US5530450(A) | 1996-06-01 | Sohn et al. | Applicant |
| US5554992(A) | 1996-09-01 | Toth et al. | Applicant |
| US5583972(A) | 1996-12-01 | Miller | Applicant |
| US5742297(A) | 1998-04-01 | Logan | Applicant |
| US6018307(A) | 2000-01-01 | Wakayama et al. | Examiner |
| US6064388(A) | 2000-05-01 | Reyzin | Applicant |
| US6140955(A) | 2000-10-01 | Andrusiak et al. | Applicant |
| US6211814(B1) | 2001-04-01 | Benjamin et al. | Applicant |
| US6240369(B1) | 2001-05-01 | Foust | Applicant |
| US6255981(B1) | 2001-07-01 | Samaniego | Applicant |
| US6272433(B2) | 2001-08-01 | Baron et al. | Applicant |
| US6307500(B1) | 2001-10-01 | Cornman et al. | Examiner |
| US6405134(B1) | 2002-06-01 | Smith et al. | Applicant |
| US6415046(B1) | 2002-07-01 | Kerut, Sr. | Applicant |
| US6573855(B1) | 2003-06-01 | Hayakawa et al. | Applicant |
| US6721678(B1) | 2004-04-01 | Zhang et al. | Applicant |
| US6771207(B1) | 2004-08-01 | Lang | Applicant |
| US6985837(B2) | 2006-01-01 | Moon et al. | Applicant |
| JP54-43496 | 1979-04-01 | Applicant |
Non-Patent Literature (20)
- Sugier, Jacqueline. “Common Software Library”. EUMETNET OPERA Programme. Nov. 6, 2006. pp. 65-66.Examiner
- Sugier, Jacqueline. “Common Software Library”. EUMETNET OPERA Programme. Nov. 6, 2003. pp. 65-66.Examiner
- Doviak, R. J., et al., “Table of Contents”, Doppler Radar and Weather Observations, 2nd Edition, San Diego, CA: Academic Press,(1993).Applicant
- Mahapatra, P. R., et al., “Table of Contents”, Aviation Weather Surveillance System: Advanced Radar and Surface Sensors for Flight Safety and Air Traffic Management, London, UK: IEE Press,(1999).Applicant
- Watson, R. , et al., “Combining ground based meteoroligical radar data from multiple overlapping sites”, Proc. International Geoscience and Remote Sensing Symposium, 3, Italy,(Jul. 1995),1660-1662.Applicant
- Zhang, J. , et al., “Three-dimensional gridding and mosaic of reflectivities from the multiple wsr-88d radars” Proc. 30th International Conference on Radar Meteorology, Munich, Germany,(Jul. 2001),719-721.Applicant
- U.S. Appl. No. 11/206,696, Amendment and Response filed Feb. 6, 2008 to Office Action mailed Nov. 6, 2007., 13.Applicant
- “U.S. Appl. No. 11/206,696 Non-Final Office Action mailed Nov. 6, 2007”, 14 Pages.Applicant
- “Restriction Requirement Mailed Jul. 18, 2007 in U.S. Appl. No. 11/206,696”, RERR,6 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Advisory Action mailed Nov. 17, 2008”, 3 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Final Office Action mailed May 9, 2008”, 9 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Final Office Action mailed Aug. 7, 2008”, 9 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Preliminary Amendment mailed Oct. 31, 2008”, 7 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Response filed Jul. 9, 2008 to final Office Action mailed May 9, 2008.”, 13 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Response filed Aug. 17, 2007 to Restriction Requirement mailed Jul. 18, 2007”, 10 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Response filed Oct. 7, 2008 to Final Office Action mailed Aug. 7, 2008”, 10 pgs.Applicant
- “U.S. Appl. No. 11/206,696 Final Office Action mailed Aug. 7, 2008”, 12 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Non-Final Office Action mailed Dec. 22, 2008”, 9 pgs.Applicant
- “U.S. Appl. No. 11/206,696, Response filed Jun. 22, 2009 to Non Final Office Action mailed Dec. 22, 2008”, 11 pgs.Applicant
- Sugier, J., “Common Software Library”, EUMETNET OPERA Programme, (Nov. 6, 2003), 65-66.Applicant