Only data provider can upload netcdf files to the database.
- using FTP, data providers upload their data to their own incoming path.
incoming path isftp://username:password@www.medcordex.eu/incoming_MEDCORDEX/<institution>
where "institution" is the short name of the data provider's institution
There is no need to create sub-directories, but if they exists they will not harm since the automatic procedure will process any file in any sub-directory - Once a day each an automatic procedure "ingests" newly uploaded files.
The procedure searches each data providers' incoming path for a file named PLEASEgo.txt.
If the file is present, then the procedure does the following for each file *.nc present in data providers' incoming path:- it verifies the .nc file is a netcdf file, otherways the file is rejected.
- it executes "ncdump -h" of the .nc file saving the output to a file named *.ncdump
- it verifies the .nc file has the global attribute "Conventions", otherways the file is rejected. If the value of "Conventions" is not "CF-1.6" it is set to "CF-1.6"
- it executes cfcheck of the .nc file saving the output to a file named *.cfcheck
- it splits filenames in tokens and checks their compliance to CORDEX standard, otherways the file is rejected.
- it checks validity of variable name (it is already known), otherways the file is rejected.
- it creates, if not already existing, the required MEDCORDEXPATH as defined here.
- it moves the files .nc .ncdump and .cfcheck into MEDCORDEXPATH
- it inserts/updates the file's record in the db that can be searched on the web.
- files with errors are left in the incoming path, the database is left unchanged and a warning is sent to the data manager
- data priveders can also ftp to www.medcordex.eu to get data uploaded by any other institution
- authorized users can ftp to www.medcordex.eu to get data uploaded by any institution