You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MobilityAPI-Python: OGC API – Moving Features server over MobilityDB
A PyMEOS-backed Python implementation of OGC API – Moving Features (OGC 22-003r3)
over MobilityDB. The HTTP server exposes collections and moving features with the
full read/write lifecycle (GET/POST/PUT/DELETE), the temporal-geometry sequence,
the derived temporal-geometry queries (distance, velocity, acceleration), and
temporal properties; a bulk-ingest extension appends a GeoJSON/GeoParquet fleet
feed as instants. PyMEOS performs the temporal-data conversion (MF-JSON in and
out), so the server holds the OGC request/response shaping and the database holds
the temporal computation. The repository carries a notebook tutorial over Danish
AIS data, unit tests, and the PostgreSQL License. The compiled Go server at
MobilityDB/MobilityAPI is the reference (production) implementation.
about: Suggest a new endpoint, OGC-conformance improvement, or backend integration
4
+
title: "[FEAT] "
5
+
labels: enhancement
6
+
---
7
+
8
+
## Motivation
9
+
10
+
What problem does this feature solve, or what use case does it enable?
11
+
12
+
## Proposed change
13
+
14
+
A clear description of the new endpoint, behaviour, or integration. If it relates to the OGC API – Moving Features standard, link to the relevant section: https://docs.ogc.org/is/22-003r3/22-003r3.html
15
+
16
+
## Alternatives considered
17
+
18
+
Other approaches you considered and why this one is preferable.
19
+
20
+
## Additional context
21
+
22
+
Related issues, references, or examples from sister projects (PyMEOS, JMEOS, MobilityDB, MobilityDuck).
How you verified the change. Output of `./run.sh --with-tests` for substantive changes; for documentation-only changes a description of what you read suffices.
16
+
17
+
## Checklist
18
+
19
+
-[ ] Tests pass locally
20
+
-[ ]`ruff check .` passes
21
+
-[ ] Documentation updated where relevant
22
+
-[ ] Entries in `AUTHORS.md` / `CITATION.cff` updated if this is a first-time substantial contribution
MobilityAPI is the result of contributions from several individuals across two phases. The project's lineage starts with **pg_mfserv** (2024), an OGC API – Moving Features prototype that established the Python-server skeleton and the PyMEOS-based MobilityDB integration pattern. **MobilityAPI** (2025–) extends that foundation into a production-grade implementation with a structured resource layout, comprehensive tests, and OGC conformance.
4
+
5
+
## Founding phase (2024) — as `pg_mfserv`
6
+
7
+
Affiliated with [Université libre de Bruxelles (ULB)](https://www.ulb.be/).
8
+
9
+
-**Maxime Schoemans** ([@mschoema](https://github.com/mschoema)) — initial commit, OGC API – Moving Features endpoint design, project skeleton.
0 commit comments