You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Patch upstream django to support 4D LineStrings.
Use Z coordinate for time, store altitudes separately.
The text was updated successfully, but these errors were encountered:
We need
LineString
s 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:
LineStrings
.The text was updated successfully, but these errors were encountered: