-
Notifications
You must be signed in to change notification settings - Fork 64
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
Change of terminology and consequently of API #50
Comments
estebanzimanyi
added a commit
to estebanzimanyi/MobilityDB
that referenced
this issue
Feb 7, 2021
estebanzimanyi
added a commit
to estebanzimanyi/MobilityDB
that referenced
this issue
Feb 7, 2021
estebanzimanyi
added a commit
to estebanzimanyi/MobilityDB
that referenced
this issue
Feb 7, 2021
estebanzimanyi
added a commit
to estebanzimanyi/MobilityDB
that referenced
this issue
Feb 7, 2021
estebanzimanyi
added a commit
to estebanzimanyi/MobilityDB
that referenced
this issue
Feb 22, 2021
mschoema
added a commit
that referenced
this issue
Feb 23, 2021
Implement duration and timespan functions wrt Issue #50
Solved in Pull Request #54 |
estebanzimanyi
added a commit
to estebanzimanyi/MobilityDB
that referenced
this issue
Feb 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Currently, MobilityDB uses the term
duration
to refer to the "temporal type", which can be'Instant'
,'InstantSet'
,'Sequence'
,'SequenceSet'
. This is not in accordance with the equivalent functionality in PostGIS which provides the functionGeometryType
to determine the type of a geometry as text, such as'POINT'
,'LINESTRING'
, etc. This prevents the use of "duration" for the usual meaning, e.g., as defined by the Cambridge dictionary:For this reason, currently MobilityDB provides a function
timespan
which correspond to the duration in the dictionary sense described above. Examples of usage are as followsHowever, there are two possible interpretations of such a function depending on whether the time gaps are included or not in the calculation.
Proposed solution
The proposed solution would be as follows
temporalType
for obtaining the temporal type, which is one of'Instant'
,'InstantSet'
,'Sequence'
,'SequenceSet'
.duration
for obtaining the duration without taking time gaps into considerationtimespan
for obtaining the duration taking time gaps into considerationThe proposed change in API would then be as follows
The text was updated successfully, but these errors were encountered: