The IDF specifications document provides details on the conventions that must be followed to create a valid IDF file, as well as guidelines to convert your own data.
The first time SEAScope is started, the application creates a
configuration file named
config.ini that contains paths for
SEAScope expects the
data directory to have one
subdirectory for each data collection: this subdirectory contains one
or several granules, as well as a configuration file (also named
config.ini) that defines how SEAScope should render
When you have new IDF files that you want to visualise with SEAScope,
copy or move them to the directory that corresponds to the collection
they belong to while making sure that you respect the
IDF file layout.
If the granule belongs to a collection which has no directory yet,
you first have to create the collection directory, then to copy/move
the granules inside it and to add a
config.ini file describing how SEAScope should render
this collection's granules. Without the
SEAScope will not detect the collection and will ignore its granules.
Next time you start SEAScope, the application should detect that new granules are available and prompt you to ask if the index should be rebuilt. Agree and SEAScope will rebuild its index: your new granules are now available for visualisation in SEAScope.
Please note that SEAScope will not detect the availability of new granules unless you restart the application!
Check out the tutorials for a step by step guide on how to add the sample data or a case study to SEAScope for your platform.
SEAScope is already able to display a lot of satellite, in-situ and model data coming from several providers.
A bundle containing samples for (almost) all the data currently supported by SEAScope is available here (841 MiB).
Please note that the heavier data collections (from Sentinel-1, Sentinel-2,
MODIS or VIIRS) are not included in the bundle.
These samples, as well as the ones included in the bundle, can be downloaded per collection by browsing this directory tree.
A smaller bundle, used during the OTC23, is available here (105 MiB).
If you need more data from these collections or if you want another type of data to be added to the list, please let us know!