I am wondering how OGC API - Moving Features can enable streaming the current position of a moving object, as well as its past actual trajectory and predicted future trajectory.
Am I correct in understanding (from the overview page), that the relevant resource would be:
GET /collections/{collectionId}/items/{mFeatureId}/tgeometries
Retrieve the movement data of the single moving feature with id mFeatureId.
Is there a mechanism (e.g., a property) that could be used to distinguish between actual historic temporal geometry/properties, current geometry/properties, and predicted geometry/properties?
As a related use case, consider the following ISS tracking positions (not including orientation, but i this case it is easy to deduct the orientation based on the direction of movement):
I am wondering how OGC API - Moving Features can enable streaming the current position of a moving object, as well as its past actual trajectory and predicted future trajectory. Am I correct in understanding (from the overview page), that the relevant resource would be:
GET /collections/{collectionId}/items/{mFeatureId}/tgeometries
Retrieve the movement data of the single moving feature with id mFeatureId.
Is there a mechanism (e.g., a property) that could be used to distinguish between actual historic temporal geometry/properties, current geometry/properties, and predicted geometry/properties?
As a related use case, consider the following ISS tracking positions (not including orientation, but i this case it is easy to deduct the orientation based on the direction of movement):
(from https://www.astroviewer.net/iss/ws/orbit.php?sat=25544)