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

4D coordinates #256

Open
landswellsong opened this issue Jun 4, 2017 · 0 comments
Open

4D coordinates #256

landswellsong opened this issue Jun 4, 2017 · 0 comments

Comments

@landswellsong
Copy link
Member

We need LineStrings to have 4 coordinates in order to painlessly determine the time when the satellite path intersects the selection geometry. 4th coordinate is meant to be used for linear referencing, but we could in principle reuse it for time values i.e. seconds passed since the start of the session.

The Django's GEOS implementation doesn't support anything with more than 3 coordinates even though the underlying GEOS library does.

As a temporary countermeasure, I'm using the Z coordinate for storing time values. Altitude filters are thus not implemented and Cesium draws wrong altitude.

I see the following solutions so far:

  1. Patch upstream django to support 4D LineStrings.
  2. Use Z coordinate for time, store altitudes separately.
@projob projob added the inbox label Jun 4, 2017
landswellsong added a commit that referenced this issue Jun 4, 2017
landswellsong added a commit that referenced this issue Aug 21, 2017
Temporary countermeasure against #256
landswellsong added a commit that referenced this issue Oct 21, 2018
Temporary countermeasure against #256
landswellsong added a commit that referenced this issue Oct 30, 2018
Temporary countermeasure against #256
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants