docs: MobilityAPI ingestion plan for MEOS-API output + OpenAPI missing-work integration#3
Open
estebanzimanyi wants to merge 1 commit into
Conversation
…g-work integration Authored as a parallel-session planning artefact. Maps how MobilityAPI consumes the catalog and projections published by MobilityDB/MEOS-API, and integrates the missing-work items called out in MEOS-API PR MobilityDB#5 ("natural follow-ups" — OpenAPI conformance validation in CI, and an OGC API – Moving Features resource projection). Sections: * Context — MEOS-API as the SoT, MobilityAPI as the OGC-conformant downstream binding. * Per-task split (parallel sessions) — what lives in MEOS-API session, what lives in MobilityAPI session, why they don't block each other. * Missing OpenAPI work — three items from PR MobilityDB#5's follow-ups: MCP manifest (DONE in PR MobilityDB#6), conformance CI (MISSING — MEOS-API), MovFeat resource projection (MISSING — MEOS-API, immediate dependency for MobilityAPI). * Endpoint-by-endpoint gap analysis — each of the 10 hand-written resource/* modules mapped to its generic-OpenAPI + MovFeat-projection equivalent. Classified Replace (5: pure MEOS dispatchers) vs Keep (5: OGC-specific persistence/envelope concerns). * Sequencing — five-step plan respecting the never-wait-for-merge rule. Steps 1-4 unblock today against MEOS-API master; step 5 consumes the MovFeat-projection PR branch the moment it opens. * Invariants and open questions for the maintainer. No code change. Subsequent PRs execute the steps one at a time.
This was referenced May 20, 2026
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.
Planning artefact, no code change. Maps how MobilityAPI consumes the catalog and projections published by MobilityDB/MEOS-API, and integrates the missing-work items called out in MEOS-API PR #5's "natural follow-ups":
What the plan covers
resource/*modules mapped to its generic-OpenAPI + MovFeat-projection equivalent. Classification: 5 Replace (pure MEOS dispatchers) vs 5 Keep (OGC-specific persistence / GeoJSON-envelope concerns).Why this PR exists separately from the execution PRs
Per the cross-repo handoff brief, each downstream session needs to ground its own task list in writing before executing. This is the MobilityAPI session's grounding document; subsequent PRs land the steps one at a time.
What this PR is NOT
Cross-link
I'll also drop a short comment on MEOS-API PR #5 noting that the MovFeat-projection follow-up has a downstream consumer (this plan) — so the MEOS-API session sees the dependency.
Refs