search

enram / data-repository

Data quality assessment
https://enram.github.io/data-repository/
MIT License
3 stars 1 forks source link

Range scale in spanish pvol data seems inconsistend and wrong #62

Open bart1 opened 3 years ago

bart1 commented 3 years ago

In the polar volume data there seems to be an inconsistency in the range scale where some times the rscale is 500 m and sometimes a 1000m (atleast in ES/BAR). Looking at the ppi this does not seem real as often the static objects shift closer and further form the radar, see the plots below where the cutout for the mountains shift. This might impact the quality of vp`s.

require(bioRad)
#> Loading required package: bioRad
#> Welcome to bioRad version 0.5.2.9410
#> Docker daemon running, Docker functionality enabled (vol2bird version 0.5.0)
require(uvaRadar)
#> Loading required package: uvaRadar
keys<-c("baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T0000_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T0011_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T0021_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T0050_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2100_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2110_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2120_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2130_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2141_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2150_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2201_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2211_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2221_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2230_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2241_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2250_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2300_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2310_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2321_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2330_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2341_8179.h5", "baltrad/init/ES/BAR/2019/09/23/ESBAR_pvol_20190923T2350_8179.h5")
plot(project_as_ppi(scn1<-retrieve_pvol(keys[1])$scans[[1]]))
#> Warning in proj4string(obj): CRS object has comment, which is lost in output

plot(project_as_ppi(scn2<-retrieve_pvol(keys[2])$scans[[1]]))
#> Warning in proj4string(obj): CRS object has comment, which is lost in output


scn1$attributes$where$rscale
#> [1] 1000
scn2$attributes$where$rscale
#> [1] 500
unlist(lapply(keys, function(x) retrieve_pvol(x)$scans[[1]]$attributes$where$rscale))
#>  [1] 1000  500  500 1000 1000 1000 1000 1000  500 1000  500  500  500 1000  500
#> [16] 1000 1000 1000  500 1000  500 1000

Created on 2020-12-01 by the reprex package (v0.3.0)

bart1 commented 3 years ago

I Just check ES/MAD seems to have the same issue where range scale varies

adokter commented 3 years ago

The rscale attribute of scan X is copied from the datasetX/where/rscale attribute in the hdf5 polar volume file. As a first sanity check I would verify these attribute values in the raw hdf5 file, e.g. with HDFView