Closed letmaik closed 8 years ago
Since SDW folks are nagging about point clouds, it may be a good idea to add a domain profile for that which is similar to Trajectory (without time component).
So, a single point is currently:
{ "type": "Domain", "profile": "Point", "axes": { "x": { "values": [1] }, "y": { "values": [20] }, "z": { "values": [1] }, "t": { "values": ["2008-01-01T04:00:00Z"] } }, "referencing": [...] }
A MultiPoint would be:
{ "type": "Domain", "profile": "MultiPoint", "axes": { "composite": { "dataType": "Tuple", "components": ["x","y","z"], // z optional "values": [ [1, 20, 1], [2, 21, 3] ] }, "t": { "values": ["2008-01-01T04:00:00Z"] } // optional }, "referencing": [...] }
And then we should have a MultiPointSeries as well for consistency, which would simply allow the "t" axis to have multiple time values.
Looks good!
Since SDW folks are nagging about point clouds, it may be a good idea to add a domain profile for that which is similar to Trajectory (without time component).
So, a single point is currently:
A MultiPoint would be:
And then we should have a MultiPointSeries as well for consistency, which would simply allow the "t" axis to have multiple time values.