Add OGC API - Moving Features support
Overview
We have developed a feature to support the OGC API - Moving Features. This implementation has a strong dependency on MobilityDB and a specific table schema. We also added/edited documentation (data-publishing, tour, transactions section) for OGC API - Moving Features.
Related Issue / discussion
https://github.com/geopython/pygeoapi/issues/1872
Additional information
Dependency policy (RFC2)
- [x] I have ensured that this PR meets RFC2 requirements
Updates to public demo
- [x] I have ensured that breaking changes to the pygeoapi master demo server have been addressed
- [x] https://github.com/geopython/demo.pygeoapi.io/blob/master/services/pygeoapi_master/local.config.yml
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)
- [x] I'd like to contribute [feature Y|bugfix X|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution
- [x] I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines
Thank you @TaehoonK for this valuable contribution! Note that this PR addresses #1872.
I'll take a first pass in the next week or so and provide initial feedback.
Thank you, @tomkralidis, for your quick action. To be honest, I just tried to merge it with the main branch code of the latest pygeoapi. Because there are some conflicting codes; I wanted to start with the latest code. Some parts still need to be resolved. I will let you know when I fixed them all.
This Pull Request has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.
This Pull Request has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.
As per RFC4, this Pull Request has been closed due to there being no activity for more than 90 days.