Closed peterdesmet closed 5 years ago
They must have changes the name of it, completely sure it was sevar then. Maybe they changed it so the tre letter code doesn't overlap with bgvar? 🤷♀️
Hmm, annoying. What do you think: should we should move the content from sevar
to the sevax
directory then, to indicate that it is the same radar? It will still remain sevar
in the data package on Zenodo (which is good). It's unlikely OPERA will change it back for us.
It was annoying that they weren't unique also though. I think it makes sense to move it, but maybe we should just double check that there is not something else going on first. I can look into it.
VAR -> VAX is listed in https://github.com/enram/data-repository/issues/79, closing here.
For our flyway analyses we used the code
sevar
for the Swedish radarVara
. Data are uploaded to the ENRAM repository under that name: http://enram.github.io/data-repository/?prefix=se/var/I noticed however that OPERA calls this radar
sevax
(same radar coordinates) and that from 2017 onwards data are uploaded as such: http://enram.github.io/data-repository/?prefix=se/vax/@CeciliaNilsson709 @leijnse which code is correct?