Closed peterdesmet closed 8 years ago
I have moved the settings requirement to issue #7
The radar location (lat, lon) and official identifier used by WMO (world meteorological organisation) is stored in the metadata, and I prefer to load it from there into a database table containing radar properties, radar settings, and algorithm settings. The network is not constant, and fairly regularly radars are moved, added, or removed, therefore it would be helpful to be able to accommodate these changes from the start.
hdfview is a reasonably handy tool to quickly inspect hdf5 files and its contained data and metadata
Decided to store metadata in DB. Still need to figure out how to translate this to a data model, but that's another issue.
Do we really need to build this? And if so, how do we keep it simple?
For the flow visualization, we at least need some information on the location of the radars. Maybe a static file with all available radars and their coordinates and name suffices? Alternatively (more complicated), we could extract metadata from the HDF5 files and build an automatically updated metadata file.
A: Load it from the metadata + all metadata should be time based (as radars can move)