Skip to content

Commit 35832d6

Browse files
Note why member deletion rebuilds the sequence set rather than using deleteTime
deleteTime reconnects the surviving fragments into a single sequence, so deleting a temporal primitive geometry uses an explicit rebuild from the kept member sequences to keep the other members distinct.
1 parent 77014b3 commit 35832d6

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

resource/temporal_prim_geom/Delete.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,9 @@ def delete_single_temporal_primitive_geo(self, collection_id, feature_id, geomet
4848
return
4949
#----------------------------------------------------------------------------------------------------------------------
5050
# Remove the member sequence by rebuilding the sequence set from the kept
51-
# members (deleteTime on a tgeompoint is avoided — it crashes the backend).
51+
# members. deleteTime is not used here: its gap-fill semantics reconnect
52+
# the surviving fragments into a single sequence, whereas deleting a
53+
# temporal primitive geometry must leave the other members distinct.
5254
cursor.execute(
5355
"""UPDATE temporal_geometries SET trajectory = (
5456
SELECT merge(seq)

0 commit comments

Comments
 (0)