Summarize activity during 2024 OGC code sprint

opengeospatial · Feb 28, 2024 · 3f51347 · 3f51347
1 parent b02bb2b
commit 3f51347
Showing 1 changed file with 11 additions and 7 deletions.
diff --git a/codesprint/2024_joint_ogc_osgeo_asf_code_sprint/README.md b/codesprint/2024_joint_ogc_osgeo_asf_code_sprint/README.md
@@ -17,7 +17,7 @@ In this code sprint, OGC Moving Features SWG will cover the following tasks:
 - Validation of the designed APIs against the [Abstract Test Suite (ATS)](https://opengeospatial.github.io/ogcna-auto-review/22-003.html#toc36)
 
 *Development*
-- Further implementation of APIs not supported by [MF-API Server](https://github.com/aistairc/mf-api) (queryable API part)
+- Further implementation of APIs not supported by [MF-API Server](https://github.com/aistairc/mf-api) ([queryable API part](https://opengeospatial.github.io/ogcna-auto-review/22-003.html#resource-tgsequenceQuery-section))
 - Refactoring the MF-API server to the latest [pygeoapi](https://github.com/geopython/pygeoapi).
 - Add OGC API - Moving Features as one of [pygeoapi's providers](https://docs.pygeoapi.io/en/stable/data-publishing/index.html#providers-overview)
 
@@ -77,22 +77,26 @@ This is the schedule for the main track.
 ## Daily Summary Report
 ### 24-02-26
 - (Ongoing) Further implementation of APIs not supported by [MF-API Server](https://github.com/aistairc/mf-api) (queryable API part)
-  - [The TemporalGeometry Query Resources](https://opengeospatial.github.io/ogcna-auto-review/22-003.html#_3dd02e21-5ed6-4ad3-bbb4-098f18e0a04d) need to be implemented.
+  - [The TemporalGeometry Query Resources](https://opengeospatial.github.io/ogcna-auto-review/22-003.html#resource-tgsequenceQuery-section) need to be implemented.
   - We try to implement three functions (Distance, Velocity, and Acceleration) using MobilityDB functions
   - [x] Distance: Using [cumulativeLength](https://mobilitydb.github.io/MobilityDB/master/ch08s04.html) function
   - [x] Velocity: Using [speed](https://mobilitydb.github.io/MobilityDB/master/ch08s04.html) function
   - [ ] Acceleration: NOT YET IMPLEMENTED 
   - Extend OpenAPI file (*.yml) for the [queryable APIs](https://opengeospatial.github.io/ogcapi-movingfeatures/openapi/openapi-movingfeatures-1.html#tag/TemporalGeometryQuery)
-  - Result: [Commit](https://github.com/aistairc/mf-api/commit/357eb2c802ddf251d7b0e55df9d6486d179c3d8f)
+  - Result: [Issue #10, MF-API Server](https://github.com/aistairc/mf-api/issues/10) and [Commit](https://github.com/aistairc/mf-api/commit/357eb2c802ddf251d7b0e55df9d6486d179c3d8f)
+- (Ongoing) Validate ATS (Abstract Test Suites) of OGC API - MF Part 1: Core
+  - Result: [Issue #61, OGC API - MovingFeautures](https://github.com/opengeospatial/ogcapi-movingfeatures/issues/61)
 ### 24-02-27
 - (Done) Further implementation of APIs not supported by [MF-API Server](https://github.com/aistairc/mf-api) (queryable API part)
-  - [The TemporalGeometry Query Resources](https://opengeospatial.github.io/ogcna-auto-review/22-003.html#_3dd02e21-5ed6-4ad3-bbb4-098f18e0a04d) need to be implemented.
+  - [The TemporalGeometry Query Resources](https://opengeospatial.github.io/ogcna-auto-review/22-003.html#resource-tgsequenceQuery-section) need to be implemented.
   - [x] Acceleration: Using the speed function result, we calculated the acceleration value of each time interval.
   - Result: [Pull request](https://github.com/aistairc/mf-api/pull/9)
 - (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 of the Shapely version (pygeoapi < 2.0, PyMEOS >= 2.0)
+  - 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](https://github.com/geopython/pygeoapi/pull/1405) and related [Pull request #1556](https://github.com/geopython/pygeoapi/pull/1556))
-  - Therefore, we wait until the restructuring of pygeoapi is complete before integrating the MF-API server into pygeoapi. 
+  - 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](https://github.com/aistairc/mf-cesium/tree/mf-cesium_api) (or Swagger)
+- (Done) Preparing Demo with [STINUUM](https://github.com/aistairc/mf-cesium/tree/mf-cesium_api) (or Swagger)
+- (Done) Generate a new docker package for the v1.0 MF-API Server
+- Results: [Issue #53, STINUUM](https://github.com/aistairc/mf-cesium/issues/53) and [Issue #11, MF-API Server](https://github.com/aistairc/mf-api/issues/11)