2024 Joint OGC – OSGeo – ASF Code Sprint, OGC API – Moving Features Activity
Overview
The OGC Moving Features SWG will participate in the 2024 Joint OGC – OSGeo – ASF Code Sprint (2024 Feb. 26 - 28).
If you want to get more information about this code sprint, please refer to the event wiki page.
We will be working primarily on the OGC API - Moving Feature, but if it’s related to moving features, we’d love to hear from you.
This page summarizes the goal, schedule, and outcomes of the activities related to the code sprint.
Tasks
In this code sprint, OGC Moving Features SWG will cover the following tasks:
Documentation
- Validation against the designed Core APIs
- Validation of the designed APIs against the Abstract Test Suite (ATS)
Development
- Further implementation of APIs not supported by MF-API Server (queryable API part)
- Refactoring the MF-API server to the latest pygeoapi.
- Add OGC API - Moving Features as one of pygeoapi’s providers
And AOB!
On-site OGC API - Moving Features member
If you have any questions about the OGC API - Moving Features during the code sprint, feel free to ask us!
- Taehoon Kim (Co-editor of the OGC API - Moving Features), ✉️, discord: @taehoonkim5747
- Wijae Cho (Developer), ✉️, discord: @WijaeCho#3486
[Note] Previous workshop materials
If you’re new to OGC API - Moving Features, we recommend reading the materials from the previous workshop.
It includes tutorials using MF-API Server and STINUUM (web client), so you can easily and quickly get started with OGC API - Moving Features!
Schedule
The code sprint will be held on Western European Time (WET/UTC/GMT).
You can check here the time in other locations.
This is the schedule for the main track.
| Date | Time | Day/ Activity | Discord channel |
|---|---|---|---|
| 2024-02-20 | Day #0 (pre-event): Welcome Webinar | ||
| 14:00 - 15:00 | Pre-event webinar | V:🏛 #Main Stage | |
| 2024-02-26 | Day #1: Kick-Off | ||
| 09:00 - 10:00 | Welcome session | V:🏛 #Main Stage | |
| 10:00 - 12:30 | Introduce OGC API - Moving Features | On-site | |
| 12:30 - 13:30 | Lunch | 🍜 | |
| 13:30 - 17:00 | Additional implementation of APIs | On-site | |
| 17:00 - 18:00 | Early dinner | 🍜 | |
| 18:00 - 20:00 | Additional implementation of APIs | On-site | |
| 20:00 - 21:00 | Daily Brief Back | V:🏛 #Main Stage | |
| 2024-02-27 | Day #2 | ||
| 09:00 - 10:00 | Additional implementation of APIs | On-site | |
| 10:00 - 10:30 | Stand-up | V:🏛 #Main Stage | |
| 10:30 - 12:30 | Additional implementation of APIs | On-site | |
| 12:30 - 13:30 | Lunch | 🍜 | |
| 13:30 - 17:00 | Refactoring the MF-API server | On-site | |
| 17:00 - 18:00 | Early dinner | 🍜 | |
| 18:00 - 20:00 | Refactoring the MF-API server | On-site | |
| 20:00 - 21:00 | Daily Brief Back | V:🏛 #Main Stage | |
| 2024-02-28 | Day #3: Final Day | ||
| 09:00 - 10:00 | Refactoring the MF-API server | On-site | |
| 10:00 - 10:30 | Stand-up | V:🏛 #Main Stage | |
| 10:30 - 13:00 | Refactoring the MF-API server | On-site | |
| 13:00 - 14:00 | Lunch | 🍜 | |
| 14:00 - 15:00 | Preparing Demo | On-site | |
| 15:00 - 17:00 | Demos & Wrap-up | V::📣 GotoMeet |
Project and Working Group Pitches
Daily Summary Report
24-02-26
- (Ongoing) Further implementation of APIs not supported by MF-API Server (queryable API part)
- The TemporalGeometry Query Resources need to be implemented.
- We try to implement three functions (Distance, Velocity, and Acceleration) using MobilityDB functions
- Distance: Using cumulativeLength function
- Velocity: Using speed function
- Acceleration: NOT YET IMPLEMENTED
- Extend OpenAPI file (*.yml) for the queryable APIs
- Result: Issue #10, MF-API Server and Commit
- (Ongoing) Validate ATS (Abstract Test Suites) of OGC API - MF Part 1: Core
- Result: Issue #61, OGC API - MovingFeautures
24-02-27
- Result: Issue #61, OGC API - MovingFeautures
- (Done) Further implementation of APIs not supported by MF-API Server (queryable API part)
- The TemporalGeometry Query Resources need to be implemented.
- Acceleration: Using the speed function result, we calculated the acceleration value of each time interval.
- Result: Pull request
- (Failed) Update MobilityDB (and PyMEOS) version to 1.1 (Release Candidate)
- We try to update the current used MobilityDB version (1.0) to the latest version (1.1), but there is a conflict with the Shapely version (pygeoapi < 2.0, PyMEOS >= 2.0)
- (Postponed) Integrate MF-API Server with the latest pygeoapi
- The pygeoapi team is preparing the project re-structure (ref. Issue #1405, split api.py and related Pull request #1556)
- Therefore, we will wait until the restructuring of pygeoapi is complete before integrating the MF-API server into pygeoapi.
24-02-28
- (Done) Preparing Demo with STINUUM (or Swagger)
- (Done) Generate a new docker package for the v1.0 MF-API Server
- Results: Issue #53, STINUUM and Issue #11, MF-API Server