multiple dynamic miniprods created for the same swath and drifter
multiple miniprods may be created for the same swath file and (here for instance) same Argo float, one (or a few) seconds apart. This result actually in redundant data (two miniprod overlapping each other). I think it is due to the fact that the colocation may be performed independently at each time of the in situ. One rule for MDB is to keep one and only one matchup per (swath file, in situ platform) pair (the closest one in time) which is not the case here. I don't want to forbid the current behaviour (could be wanted by some users?) but at least there should be an option to enforce the above rule (to be set with the colocation criteria).
An example of that:
felyx-miniprod --dynamic --mode=local /home/cerdata/provider/ghrsst/satellite/l2p/gcom_w1/amsr2/jaxa-l2p-amsr2/2013/300/20131027154252-JAXA-L2P_GHRSST-SSTsubskin-AMSR2-v1_A_v02.0-fv01.0.nc amsr2-jaxa-l2p-v01.0
would give, among others :