Open captaincoordinates opened 4 months ago
I'm also interested in learning more about the reasoning around temporal operator SQL statements. From what I can tell pgstac disregards any property provided in the JSON filter and always targets datetime
and end_datetime
Given what I believe to be a valid temporal filter, pgstac's
temporal_op_query
function appears to generate invalid SQL which raises a syntax error. This may simply be a case of me misunderstanding how to execute the function, so any additional information would be very much appreciated. I'm really struggling to find comprehensive documentation on temporal filters.The following query's temporal operator is translated to an SQL construct here. However it appears that
AND rl < lh < rh
is invalid SQL, and should in fact beAND rl < lh AND lh < rh
.Because of challenges around documentation I'm not sure if this is the right way to perform
t_overlaps
. The extension documentation only provides an example of an intersection and from what I can gather pgstac's unit tests only addresst_intersects
,t_after
, andt_before
operators.