enram / data-repository

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

File corrupt in dkrom zip #56

Open bart1 opened 4 years ago

bart1 commented 4 years ago

There is a problem reading this specific file from the zip, it seems to be correct in the repository

require(bioRad)
#> Loading required package: bioRad
#> Welcome to bioRad version 0.5.1.9344
#> Docker daemon running, Docker functionality enabled (vol2bird version 0.5.0)
download.file('https://lw-enram.s3-eu-west-1.amazonaws.com/dk/rom/2019/03/05/05/dkrom_vp_20190305T050500Z_0xf00207.h5','asdf.h5')
read_vpfiles('asdf.h5')
#>                Vertical profile (class vp)
#> 
#>        radar:  dkrom 
#>       source:  NOD:dkrom,WMO:06096,RAD:DN42,PLC:Rømø 
#> nominal time:  2019-03-05 05:05:00 
#> generated by:  vol2bird 0.3.20
download.file('https://lw-enram.s3-eu-west-1.amazonaws.com/dk/rom/2019/dkrom201903.zip', 'asdf.zip')
unzip('asdf.zip','15/05/dkrom_vp_20190315T050500Z_0xf00207.h5')
read_vpfiles('15/05/dkrom_vp_20190315T050500Z_0xf00207.h5')
#> Warning in is.odimfile(file): 15/05/dkrom_vp_20190315T050500Z_0xf00207.h5 is not
#> a HDF5 file
#> Warning in get_odim_object_type(file): 15/05/
#> dkrom_vp_20190315T050500Z_0xf00207.h5 is not a ODIM HDF5 file
#> Warning in read_vp(files): 15/05/dkrom_vp_20190315T050500Z_0xf00207.h5 is not a
#> vertical profile
#> NULL

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

bart1 commented 4 years ago

This file also seems corrupt in in the zip: czska/2019/03/15/05/czska_vp_20190315T051000Z_0x7.h5 I have not checked the original file

bart1 commented 4 years ago

In this case the file itself seems to be corrupt as it it only 0.1 kb: http://enram.github.io/data-repository/?prefix=cz/ska/2019/03/15/05/

bart1 commented 4 years ago

Similair issues in bewid on that day: http://enram.github.io/data-repository/?prefix=be/wid/2019/03/15/05/

bart1 commented 4 years ago

frlep has the same issue on that day http://enram.github.io/data-repository/?prefix=fr/lep/2019/03/15/05/ maybe branch it to a separate issue?