Height range on crow differs from vpts file

[bart1]

On crow the height for bewid seems to be capped: https://crow.aloftdata.eu/#/?radar=bewid&date=2024-03-13&interval=72&timedisplay=radarLocal&vpiMode=vid&vpColorScheme=viridis&lang=en : How ever if I read the file directly from baltrad using bioRad this issue is not there:

require(bioRad)
#> Loading required package: bioRad
#> Welcome to bioRad version 0.7.3
#> Attempting to load MistNet from: /home/bart/R/x86_64-pc-linux-gnu-library/4.4/vol2birdR/lib 
#> MistNet successfully initialized.
#> using vol2birdR version 1.0.2 (MistNet installed)
vpts<-read_vpts(list_vpts_aloft("2024-3-13", "2024-03-14",radars="bewid"))
plot(vpts[as.Date(vpts$datetime) %in% as.Date(c("2024-3-13", "2024-03-14"))])
#> Warning in plot.vpts(vpts[as.Date(vpts$datetime) %in% as.Date(c("2024-3-13", :
#> Irregular time-series: missing profiles will not be visible. Use
#> 'regularize_vpts' to make time series regular.
#> Warning in plot.vpts(vpts[as.Date(vpts$datetime) %in% as.Date(c("2024-3-13", :
#> Dropped 384 profiles with duplicate datetime values

^{Created on 2024-07-15 with reprex v2.1.0}

I guess here something goes wrong in visualizing on crow?

[niconoe]

I've investigated the issue, and noticed something weird in the data file (used by ENRAM CROW, I am not sure what Biorad is using): it appears we have 3 data rows for each height/timestamp combinations. I am not sure what it's supposed to mean (the values differ slightly on those), but CROW is currently not equipped to deal with this (especially the grouping in populateDataFromCrowServer), which triggers the issue.

The "problematic" source file for this case is: https://aloftdata.s3-eu-west-1.amazonaws.com/baltrad/daily/bewid/2024/bewid_vpts_20240314.csv

We can compare this to the equivalent (is it the source?) file used from INBO CROW: https://opendata.meteo.be/ftp/observations/radar/vbird/bewid/2024/bewid_vpts_20240314.txt

We can see that the former file is 3x larger, with repeated rows (same height/timestamp).

Can someone (@peterdesmet maybe) can confirm it is normal to have such data files, and if so, how they should be interpreted by CROW (which row should be kept and which ones should be disregarded).

Thanks a lot!

[peterdesmet]

I would keep the first row and disregard the rest.

[niconoe]

No problem, I'll adjust CROW to do exactly this!

[peterdesmet]

Thanks!!