Skip to content

Add bulk ingest of a fleet feed (POST /collections/{cid}/bulk)#10

Closed
estebanzimanyi wants to merge 87 commits into
MobilityDB:masterfrom
estebanzimanyi:feat/bulk-ingest
Closed

Add bulk ingest of a fleet feed (POST /collections/{cid}/bulk)#10
estebanzimanyi wants to merge 87 commits into
MobilityDB:masterfrom
estebanzimanyi:feat/bulk-ingest

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

POST /collections/{collectionId}/bulk accepts a batch of (vehicleId, position, time) observations and appends each as one instant to the matching moving feature's tgeompoint trajectory in temporal_geometries, creating the feature on first sight. The batch may be GeoJSON (a FeatureCollection of Point features) or GeoParquet (one row per observation), and may be gzip/deflate/br/zstd-compressed via Content-Encoding; the whole batch commits atomically and an out-of-order instant returns 409. Geometry and temporal work run in MobilityDB (ST_MakePoint / ST_GeomFromWKB, tgeompoint, appendInstant); the parsing and decompression are covered by unit tests run in CI.

sirimeraoui and others added 25 commits March 14, 2026 17:48
MobilityAPI's working tree is the result of two distinct
contribution phases that today's repo doesn't make visible:

1. **pg_mfserv (March 2024)** — the founding OGC API – Moving
   Features Python server for MobilityDB, authored at ULB.
   - Maxime Schoemans (@mschoema) — initial commit, endpoint design.
   - Victor Morabito (@MrMaxime1er) — main developer of the
     pg_mfserv codebase: column discovery, request handling,
     exception handling, route refactors.

2. **MobilityAPI (2025–)** — the current production-grade
   implementation, also at ULB.
   - Sirine Meraoui (@sirimeraoui) — current maintainer; structured
     resource layout, tests, OGC conformance, documentation.

This commit adds three artefacts that surface the lineage:

- **README.md** — new `## History and Acknowledgements` section
  before `## License` crediting all three contributors and pointing
  to pg_mfserv as the archived predecessor.
- **AUTHORS.md** (new) — structured contributor list per phase.
- **CITATION.cff** (new) — machine-readable citation metadata for
  Zenodo / GitHub citation widget, including a `references:` block
  citing pg_mfserv as predecessor work.

License declared in CITATION.cff: PostgreSQL (matching the
MobilityDB main project's license posture).

The lineage credit is symmetric: pg_mfserv's README will gain an
archive banner pointing forward to MobilityAPI in the companion
PR on the pg_mfserv repository.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add lineage credits: pg_mfserv predecessor, AUTHORS, CITATION
…ADME rewrite

The repo is now the canonical home of MobilityAPI but was missing
several artefacts that ecosystem-grade org repos carry:

1. **LICENSE.txt** — The PostgreSQL License, matching the
   MobilityDB main project's licence posture. Without this,
   the repository was effectively all-rights-reserved by
   default. Copyright Université libre de Bruxelles and
   MobilityAPI contributors.

2. **CONTRIBUTING.md** — Development setup, test instructions
   (./run.sh, ./run.sh --with-tests), code-style conventions
   (PEP 8 + ruff), PR conventions. Cross-references AUTHORS.md
   and the lineage section in the README.

3. **.github/workflows/python.yml** — Stub CI:
   - Lint job: ruff check on PRs (warning-only at this stage so
     legacy code isn't blocked; tighten when codebase has been
     once-through).
   - Import-smoke-test job: imports each application module so
     a minimal "code is at least loadable" gate runs on PRs.
   No DB-integration tests at this stage; that's a separate
   GitHub Actions service-container effort once the test
   harness stabilises.

4. **.github/ISSUE_TEMPLATE/{bug,feature}.md** + **PULL_REQUEST_TEMPLATE.md**
   — issue / PR scaffolding. Bug template asks for environment
   info; feature template prompts for OGC-spec references.

5. **README rewrite** — restructured for canonical-home framing:
   - Added badges (License, Python, OGC API conformance).
   - Lead with what MobilityAPI is (HTTP / OGC layer of the MEOS
     ecosystem) rather than the bare introduction.
   - Added a Status section pointing at issues + discussions.
   - Added a "Where MobilityAPI fits" section showing peer SQL
     layers (MobilityDB / MobilityDuck) and language bindings.
   - Cross-link to https://libmeos.org/bindings/mobilityapi/.
   - Added Contributing section pointing at CONTRIBUTING.md.
   - Fixed "Pyhton" / "Developement" typos and the orphaned
     ##Poetry section. Final License section points at LICENSE.txt
     and CITATION.cff.
   - Lineage section (PR #1) preserved unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Canonicalisation bundle: LICENSE, CI, contributor scaffolding, README rewrite
POST /collections/{collectionId}/bulk accepts a batch of (vehicleId, position,
time) observations and appends each as one instant to the matching moving
feature's tgeompoint trajectory in temporal_geometries, creating the feature on
first sight. The batch may be GeoJSON (a FeatureCollection of Point features) or
GeoParquet (one row per observation), and may be gzip/deflate/br/zstd-compressed
via Content-Encoding; the whole batch commits atomically and an out-of-order
instant returns 409. Geometry and temporal work run in MobilityDB
(ST_MakePoint / ST_GeomFromWKB, tgeompoint, appendInstant); the parsing and
decompression are covered by unit tests.
Add a unit-tests job to the Python checks workflow that installs pytest and
pyarrow and runs tests/test_bulk.py, so the bulk parsing and decompression
coverage runs on every push and pull request.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants