We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@kunzel Is there any need for the Trajectory Query service anymore?
We query objects and ROI in geospatial_store.py without a service, is it worth getting the trajectories the same way?
I've added a helper function into geospatial_store.py which could do this, but I haven't implemented it yet.
(I suppose it doesn't visualise them though).
The text was updated successfully, but these errors were encountered:
Merge pull request #12 from PDuckworth/upstream
79b74ae
Upstream
No branches or pull requests
@kunzel Is there any need for the Trajectory Query service anymore?
We query objects and ROI in geospatial_store.py without a service, is it worth getting the trajectories the same way?
I've added a helper function into geospatial_store.py which could do this, but I haven't implemented it yet.
(I suppose it doesn't visualise them though).
The text was updated successfully, but these errors were encountered: