Skip to content

conventions for azimuth angle for RHI scans #104

@isabels

Description

@isabels

Using RadxConvert to create cfradial files from Leosphere WLS200s netcdfs, then using HawkEye to plot RHI scans. On all scans, even those that cover a full 180º, HawkEye plots only display the first half of the scan:
lidar WLS200s-181 20200312005030 BETA 117 RHI
This scan covers a full 180º, with the given elevations and azimuths:

   azimuth = 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 

      10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 

      10, 10, 10, 10, 10, 10, 190, 190, 190, 190, 190, 190, 190, 190, 190, 

      190, 190, 190, 190, 189.999, 189.999, 190, 190, 190, 190, 190, 190, 

      190, 190, 190, 189.999, 190, 190, 190, 190, 190, 190, 190, 190, 190, 

      190, 190, 190, 190, 190, 190, 190, 190, 190, 190, 190 ;


   elevation = 11.953, 13.96, 15.956, 17.954, 19.961, 21.955, 23.951, 25.948, 

      27.963, 29.953, 31.958, 33.958, 35.959, 37.956, 39.951, 41.951, 43.948, 

      45.954, 47.951, 49.949, 51.953, 53.955, 55.95, 57.955, 59.948, 61.961, 

      63.959, 65.95, 67.947, 69.948, 71.954, 73.952, 75.958, 77.954, 79.958, 

      81.95, 83.957, 85.948, 87.953, 89.948, 88.05, 86.048, 84.044, 82.044, 

      80.048, 78.047, 76.052, 74.05, 72.053, 70.037, 68.049, 66.04, 64.048, 

      62.052, 60.037, 58.045, 56.045, 54.044, 52.054, 50.044, 48.051, 46.04, 

      44.045, 42.042, 40.05, 38.053, 36.037, 34.045, 32.043, 30.048, 28.043, 

      26.044, 24.039, 22.04, 20.041, 18.051, 16.047, 14.045, 12.041, 10.042, 

      8.04, 6.039, 4.046, 2.053, 0.05 ;

In Leosphere files the azimuth switches by 180º when the elevation passes 90º, which I'm guessing is why HawkEye stops plotting the scan just before 90º elevation. So my question is: is there a convention for how azimuth should be represented on a RHI scan that goes past 90º? Is it incorrect for the azimuth to change when the elevation crosses 90º?

I can do more looking into the code myself, but first I need to know if this is a convention thing that should be fixed in the leosphere input to RadxConvert, or if it's a bug in HawkEye.

Parameter file used:
Hawkeye.rhi.params.txt
Link to netcdf plotted: https://drive.google.com/file/d/1wvjiTl3CQAkxRc_FXxSOfOxm6lgFw_rq/view?usp=sharing

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions