Repository navigation
Bind MobilityDB master and regenerate the functions and types packages - #30
Merged
Merged
Conversation
The functions and types packages are regenerated from the catalog of MobilityDB master a23e01a60b, and the hand-written calls follow the MEOS signatures there: the distances, lengths and speed of a temporal point and the ever, always and temporal within distance take the model of the earth last, which they are given as the spheroid, the model MobilityDB defaults to and the one MEOS measures a geography on; temporal_as_mfjson takes its options as bits, the bounding box being bit 1; and the MF-JSON call passes the reference system string it frees. Witness: the gomeos package builds against the libmeos of a23e01a60b and its 121 examples pass with TZ=UTC; the functions and types packages build, and the portable-parity test passes. Why: the committed packages and the hand-written calls are what a go get consumer compiles, and they compile against the MEOS they name.
estebanzimanyi
force-pushed
the
bump/meos-master
branch
from
October 27, 2026 14:18
780573c to
7a43149
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The functions and types packages are regenerated from the catalog of
MobilityDB master a23e01a60b, and the hand-written calls follow the MEOS
signatures there: the distances, lengths and speed of a temporal point and
the ever, always and temporal within distance take the model of the earth
last, which they are given as the spheroid, the model MobilityDB defaults
to and the one MEOS measures a geography on; temporal_as_mfjson takes its
options as bits, the bounding box being bit 1; and the MF-JSON call passes
the reference system string it frees.
Witness: the gomeos package builds against the libmeos of a23e01a60b and
its 121 examples pass with TZ=UTC; the functions and types packages build,
and the portable-parity test passes.
Why: the committed packages and the hand-written calls are what a go get
consumer compiles, and they compile against the MEOS they name.