docs: add Ecosystem section listing MobilityDB org projects#3
Open
estebanzimanyi wants to merge 1 commit into
Open
docs: add Ecosystem section listing MobilityDB org projects#3estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
estebanzimanyi
force-pushed
the
docs/ecosystem-section
branch
2 times, most recently
from
70ef6fc to
4cc93f1
Compare
Add the MEOS.js (JavaScript/WebAssembly/Node.js) binding to the Language bindings table — it is a real, non-archived org repository (github.com/MobilityDB/MEOS.js); the earlier 'no MEOS.js binding exists' parenthetical was factually wrong and is corrected here so the text matches the org repositories and the ecosystem figure.
estebanzimanyi
force-pushed
the
docs/ecosystem-section
branch
from
4cc93f1 to
bd2554e
Compare
estebanzimanyi
added a commit
that referenced
this pull request
May 20, 2026
…follow-up)
Adds 'generator/movfeat.py' and 'generate_movfeat_openapi.py' as a
second OpenAPI projection alongside the generic RPC-style projection
in 'generator/openapi.py'.
The MovFeat projection maps the subset of MEOS functions that have an
OGC API – Moving Features (OGC 22-003r3) analogue onto the
OGC-defined REST resource hierarchy under
'/collections/{collectionId}/items/{featureId}/…'. Each route carries
'x-meos-{function,decode,encode}' extensions so a downstream OGC
server (MobilityAPI, in this ecosystem) can dispatch each call to the
right MEOS function without re-deriving the mapping.
Reuses the _value_schema / _type_schema / _enum_schema helpers from
'generator/openapi.py' so component schemas and the MeosError
response are byte-identical across the two projections. Smoke-tested
locally on the catalog produced by 'run.py' against MobilityDB master
headers: 10 paths, 5/6 unique MEOS function dependencies present in
the catalog (temporal_as_mfjson, temporal_from_mfjson, tpoint_speed,
temporal_derivative, tpoint_cumulative_length, tpoint_azimuth).
Closes the 'OGC API – Moving Features resource projection' natural
follow-up named in PR #5's body. The MobilityAPI ingestion plan
(MobilityAPI #3, step 5) consumes this projection.
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
1 participant
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.
Adds an Ecosystem section (Engine / Language bindings / Analytics & services) with verified github.com/MobilityDB repositories, including MobilitySpark and the MEOS.NET (C#) binding, and corrects the bindings parenthetical (no MEOS.js binding exists in the org; .NET/C# clarified).