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
The phenomenonTime, resultTime (and validTime) of Datastreams and Observations can be defined as a time interval, following ISO8601.
For our application, it would be very useful to define open intervals. The ISO8601-2:2019 extension (see wikipedia) of the iso standard defines an open interval by using ".." (two dots).
As far as I understand the open interval definition has not been implemented in FROST. Or is it? If it is not, could it be implemented, and if so, when might it be implemented?
The text was updated successfully, but these errors were encountered:
Currently FROST does not allow open ended intervals.
It could be implemented, but there are currently no plans for this. It's not a trivial feature, since the interaction of open intervals with all query features that deal with time, need to be validated.
The phenomenonTime, resultTime (and validTime) of Datastreams and Observations can be defined as a time interval, following ISO8601.
For our application, it would be very useful to define open intervals. The ISO8601-2:2019 extension (see wikipedia) of the iso standard defines an open interval by using ".." (two dots).
As far as I understand the open interval definition has not been implemented in FROST. Or is it? If it is not, could it be implemented, and if so, when might it be implemented?
The text was updated successfully, but these errors were encountered: