Repository navigation
Create a moving-feature item through the public MF-JSON reader of tgeompoint - #225
Merged
estebanzimanyi merged 1 commit intoOct 31, 2026
Conversation
…ompoint The createItem route of the OGC API - Moving Features projection reads its MF-JSON payload through tgeompoint_from_mfjson, the public reader of the MovingPoint that temporalTypes states for tgeompoint, and answers the item through the writer Temporal states as its out. Why: IO-B1 of IO-PLAN.md in MobilityDB #2861. temporal_from_mfjson, the route's reader, is internal and no exposable function, so the route had no MEOS backing. Measured: over the catalog of MobilityDB master 1ff2270f7f, 8 of the 16 routes have a MEOS backing and no route names a function absent from the catalog, against 7 and temporal_from_mfjson. The 12 tests of tests/test_movfeat.py pass.
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 createItem route of the OGC API - Moving Features projection reads its MF-JSON payload
through tgeompoint_from_mfjson, the public reader of the MovingPoint that temporalTypes
states for tgeompoint, and answers the item through the writer Temporal states as its
out.
Why: IO-B1 of IO-PLAN.md in MobilityDB #2861. temporal_from_mfjson, the route's reader, is
internal and no exposable function, so the route had no MEOS backing.
Measured: over the catalog of MobilityDB master 1ff2270f7f, 8 of the 16 routes have a MEOS
backing and no route names a function absent from the catalog, against 7 and
temporal_from_mfjson. The 12 tests of tests/test_movfeat.py pass.