Checkout the examples below to see how GoKoala works.
This example uses vector tiles from the PDOK BGT dataset (a small subset, just for demo purposes).
- Start GoKoala as specified in the root README
and provide
config_vectortiles.yaml
as the config file. - Open http://localhost:8080 to explore the landing page
- Call http://localhost:8080/tiles/NetherlandsRDNewQuad/12/2235/2031.pbf to download a specific tile
There are 2 examples configurations:
config_features_local.yaml
- use local addresses geopackages in WGS84, RD and ETRS89 projections.config_features_azure.yaml
- use addresses geopackage (just one in WGS84) hosted in Azure Blob as a Cloud-Backed SQLite/Geopackage.
For the local version just start GoKoala as specified in the root README and provide the mentioned config file.
For the Azure example we use a local Azurite emulator which contains the cloud-backed addresses.gpkg
:
- Run
docker-compose -f docker-compose-features-azure.yaml up
- Open http://localhost:8080 to explore the landing page
- Call http://localhost:8080/collections/dutch-addresses/items and notice in the Azurite log that features are streamed from blob storage
This example uses 3D tiles of New York.
- Start GoKoala as specified in the root README
and provide
config_3d.yaml
as the config file. - Open http://localhost:8080 to explore the landing page
- Call http://localhost:8080/collections/newyork/3dtiles/6/0/1.b3dm to download a specific 3D tile
This example demonstrates multiple OGC APIs (tiles, styles, features, geovolumes) in a single API.
- Start GoKoala as specified in the root README
and provide
config_all.yaml
as the config file.