-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove datasets which are not served with elastic, from the elastic docker example #8
Labels
Comments
On it |
Fixed in PR geopython/pygeoapi#1364 |
2 tasks
Thanks @krishnaglodha! Please see my comment here: geopython/pygeoapi#1364 (review) |
This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days. |
Note: I'm thinking this issue belongs on https://github.com/geopython/pygeoapi-examples, rather than here, after #1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In the elastic docker example, pygeoapi is configured to serve 4 datasets, but only 1 of them is actually using elastic as a backend provider.
Steps to Reproduce
Start the docker-compose file and navigate to the collections page. You will see 4 datasets there.
These datasets use different providers: CSV, GeoJSON, SQLiteGPKG. Only one of them uses elastic.
Expected behavior
In this example, we should publish only the dataset that is served using the elastic provider:
In order to achieve this, you can edit the pygeoapi configuration file to remove all the datasets that are not published using the elastic provider.
The text was updated successfully, but these errors were encountered: