Add OGC API - Moving Features support #1871
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates related to database and Provider * Modify database schema file * Create a new provider file * Create a new test file to test the provider file
Updates related to api * Create a new api file * Create a new test file to test the api file
revision related to database and Provider * Correcting of test check judgments * Refactoring of parameter names
modify service interface and entry points * Modifying service entry point * Modifying the MF-API service interface
modify movingfeature api * Remove class(Same as other APIs) * Created function 'get_oas_30' as OpenAPI for MovingFeatures (Same as other APIs)
modify service interface * Modified to process MovingFeatures in the same way as other APIs * Change YAML file references to the Web
create new table for new api request * DDL changed because new table was added * Added new API requests and associated tests * Adjusted file placement position
Creating of MF-API documentation * Creating RST files * Creating test files used in the documentation * Adjustment of DB settings
Add used Python packages to the requirements-privider.txt * Add pymeos package
Building a Docker environment * Created a new Dockerfile for MobilityDB. * Modified the existing Dockerfile. * Created a new docker*compose file. * Adjusted the DB hostname. * Created a shell script to create tables.
Docker image Name * Add docker image name setting
Update base image for DockerfileMobilityDB * updating the base image 14-3.2 to 17-3.5.
MF-API Server update and integration (#1)
tomkralidis
changed the title
TaehoonK
changed the title
|
Thank you, @tomkralidis, for your quick action. |
|
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
#1872
Additional information
Dependency policy (RFC2)
Updates to public demo
Contributions and licensing
(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)