Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Past, Current, Predicted trajectories #25

Open
jerstlouis opened this issue Jan 21, 2023 · 0 comments
Open

Past, Current, Predicted trajectories #25

jerstlouis opened this issue Jan 21, 2023 · 0 comments

Comments

@jerstlouis
Copy link
Member

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):

{
    "sat": 25544,
    "tRef": 1674280079,
    "orbitData": [
        { "t": 1674280020, "ln": 143.511, "lt": 17.213, "h": 419, "v": 7.662, "s": true },
        { "t": 1674280080, "ln": 145.941, "lt": 20.143, "h": 419, "v": 7.662, "s": true }
    ]
}

(from https://www.astroviewer.net/iss/ws/orbit.php?sat=25544)

@jerstlouis jerstlouis changed the title Past, Current, Prediected trajectories Past, Current, Predicted trajectories Jan 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant