In the coverageJSON, it could be represented as the:
CoverageCollection domainType="Trajectory" - but all the trajectories would share the time dimension, which is redundant. also traveling though them by time would require to open each for each timestamp.
CoverageCollection domainType="MultiPoint" - each MultiPoint at a given time, probably better as we're interested in the snapshots, example file attached:
CoverageJSON does not say if CoveragCollection can have domain, but the Collection does not specify order nor the domain of timestamps otherwise, so the proposed encoding add CoverageCollection level domain that specify the values for the constants within the coverages - time in this case.
Use case is to expose data from the OpenDrift model of the particle movement, which is a series of snapshots of the particles movement with some additional properties. It can be produced in such a format originally: https://github.com/ILIAD-ocean-twin/data_access_api/issues/4#issuecomment-1625333841
In this scenario we're interested in the collection of tuples with variables as the function of time:
In the coverageJSON, it could be represented as the:
CoverageCollection domainType="Trajectory" - but all the trajectories would share the time dimension, which is redundant. also traveling though them by time would require to open each for each timestamp.
CoverageCollection domainType="MultiPoint" - each MultiPoint at a given time, probably better as we're interested in the snapshots, example file attached:
MultiTrajectories.json
CoverageJSON does not say if CoveragCollection can have domain, but the Collection does not specify order nor the domain of timestamps otherwise, so the proposed encoding add CoverageCollection level domain that specify the values for the constants within the coverages - time in this case.