We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From #8:
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:
Closing in lieu of #8 (now transferred here).
Sorry, something went wrong.
No branches or pull requests
From #8:
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: