geopython / pygeoapi-examples

Example pygeoapi deployment patterns and configurations

pygeoapi-examples

Example pygeoapi deployment patterns and configurations

pygeoapi-examples's Issues

move sample shapely and land cover processes

Move sample processes from geopython/pygeoapi#1541 to this GitHub repository (for example, place in a processes/ directory).

@Prajwalita

On localhost landing page, links should go to correct port

Description
The ES example's localhost landing page links to subpages with the wrong port when the port set in the docker-compose.yml is different from the port in the pygeoapi docker.config.yml.

Steps to Reproduce
Steps to reproduce the behavior:

1. Set the port in https://github.com/geopython/pygeoapi-examples/blob/main/docker/elastic/docker-compose.yml#L44 to something other than 5000 (I was using 5001).
2. Run docker-compose up from the elastic directory.
3. Click on any link when opening localhost:5001 in the browser.

Expected behavior
I think the port should change across all files when set in one top level variable file.

Screenshots/Tracebacks
If applicable, add screenshots to help explain your problem.

Environment

• OS: Mac
• Python version: Python 3.12.1
• pygeoapi version: geopython/pygeoapi:latest
• pygeoapi-examples version: latest

Additional context
Add any other context about the problem here.

Elastic Docker example should only contain Elastic examples

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.

Remove datasets which are not served with elastic, from the elastic docker example

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.