Closed peterdesmet closed 1 year ago
You're right about the purpose of the radar archive. I will discuss the option of merging the two databases at the OPERA meeting in 1.5 weeks.
@leijnse @BarVodSur I'd like to pick up this issue again. It would be great if both files could be merged and all radars have a finishyear
property (that is empty for active radars). It would also be good to have a replacedby
property, to link replacements of radars or radar codes.
Although a single file would be better in my opinion (with e.g. different numbers assigned to radars that got replaced but didn't change their odimcode
like deeis
), we can currently deal with 2 files. Those are merged in this script (https://github.com/enram/aloftdata.eu/blob/main/_data/OPERA_RADARS_DB.R) to create a single list at https://aloftdata.eu/radars/
I noticed on the opera map that OPERA also has an
RADAR ARCHIVE
(raw file). Some of the radars have a number identical to theRADARS
database.The main difference seems to be that these radars have a new property
finishyear
and a status0
, with the exception ofskjav
andskkoj
(also appearing inRADARS
) that have status1
and an invalidfinishyear
.@leijnse I assume the purpose of this file is to track historical radars? If so, can we suggest to merge this information with the
RADARS
database/file: it already contains 39 radars with"status": "0"
and would make for a single reference.