BNC Analyze Elevation cut-off angle

[sgonnet@…]

Hi BKG Team

It would be very interesting to be able to set an elevation cut-off angle for the analysis module.
Similarly for the Edit module, being able to filter all observations below a certain threshold would be really cool.

[stuerze]

Hello,

for the elevation determination the position of both is required, satellite and station. Hence, only within the analysis module it would be able to add a cutoff angle. But why you would like to exclude the observations below a specific elevation angle. Isn't it from interrest to see the behavior of multipah and SNR especially in connection with elevation and azimuth?

Best regards, Andrea

[anonymous]

Hi

Thank you for your answer.
I would like to be able to determine in the QC logfile of the analysis which ones are from low elevation and which ones are from higher elevation.
Sometimes I have files with high multipath values, for example, but if I filtered out all observations below 5-7°, I'm sure those values would be much more "acceptable".
Best regards
Sylvain

[stuerze]

Hi,

elevation and azimth are available within the epoch-wise output:

> 2025 02 18 00 00  0.0000000 49  0.7
G01   1.47  153.67   8  C1C  . 0.00  L1L s. 29.4  C1L  . 0.00  L2S s. 42.2  C2S  . 0.00  C2W  . 0.00  L5Q s. 44.0  C5Q  . 0.00
G03  37.32  105.75   8  L1C .. 51.4  C1C  . 0.03  L2S .. 47.4  C2S  . 0.04  L2W .. 51.5  C2W  . 0.04  L5Q .. 53.9  C5Q  . 0.04
G04  75.99   90.75  10  L1C .. 51.1  C1C  . 0.09  L1L .. 51.5  C1L  . 0.09  L2S .. 53.8  C2S  . 0.02  L2W .. 50.1  C2W  . 0.02  L5Q .. 57.4  C5Q  . 0.02
G06  54.75  -75.86   8  L1C .. 52.3  C1C  . 0.06  L2S .. 50.9  C2S  . 0.02  L2W .. 52.7  C2W  . 0.02  L5Q .. 54.8  C5Q  . 0.05
G07  11.66  177.38   6  L1C .. 48.6  C1C  . 0.05  L2S .. 39.0  C2S  . 0.06  L2W .. 46.6  C2W  . 0.06
G09  66.10 -137.10   8  L1C .. 52.8  C1C  . 0.02  L2S .. 50.0  C2S  . 0.03  L2W .. 52.6  C2W  . 0.03  L5Q .. 56.3  C5Q  . 0.05
G11  26.64  -48.74  10  L1C .. 50.6  C1C  . 0.03  L1L .. 50.3  C1L  . 0.04  L2S .. 45.2  C2S  . 0.02  L2W .. 42.1  C2W  . 0.02  L5Q .. 49.5  C5Q  . 0.03
G17   4.20 -137.71   6  L1C .. 41.2  C1C  . 0.08  L2S .. 36.5  C2S  . 0.03  L2W .. 41.1  C2W  . 0.04
G19  17.24 -115.89   4  L1C .. 45.9  C1C  . 0.10  L2W .. 42.2  C2W  . 0.09
G20   2.59  -66.40   4  L1C .. 42.9  C1C  . 0.04  L2W .. 35.4  C2W  . 0.05

And they are used to make the plotts.

I think, within the QC of the RINEX files all data should be analysed. The degradiation with respect to low elevantions is than visible within the plotts and values.

Within other applications, such as PPP, the cutof-angle can be choosen respectively.

Best regrads, Andrea

[sgonnet@…]

Hi

Yes, I agree that we need to review all the analyzed data.

Could we consider separating the values into two categories in the log, for example:

G:   1C: Slips <10° (file + found):      301 +      186  
G:   1C: Slips >=10° (file + found):      100 +      43 

And apply the same approach for gaps, mean SNR, and mean MP?

Best regards
Sylvain

[stuerze]

I think then you would have to do the overall analysis for the two elevation angle ranges. And that would only be possible if the navigation file is included.

Perhaps more meaningful would be the graphical representation of the epoch-wise output.

[anonymous]

Unfortunately, I'm analyzing thousands of files and can't review each individual graph.

That's why I rely on log files for my analysis.

[stuerze]

Ok, I will have a look on it.