Reviewed Maps and Tiles sections of the Workshop - #244
Conversation
doublebyte1
commented
Aug 7, 2026
- Added more images
- Added more references
- Added style file for vector tiles
- improved tiles section
| * Select by area, time and resolution of interest; | ||
| * Change parameters such as the width, height and coordinate reference systems. | ||
|
|
||
| OGC API - Maps is great for *creating custom maps, that could be used for printing or displaying as static images*. OGC API - Maps is **not** great for *providing interactive maps on the web*; there are Standards that are more suitable for that purpose, from the efficiency point of view (see [OGC API - Tiles](./ogcapi-tiles.md)) |
There was a problem hiding this comment.
Debatable? One can have an OGC API - Maps instance with accelerated caching and handling of "dynamic" parameters to cacheable resources (i.e. MapProxy's WMS support atop cached tiles).
Perhaps/suggested below:
!!! note
While OGC API - Maps is great for providing dynamic maps on the Web, if your data has can be based on a set tiling scheme, and the resulting maps do not need to be dynamically generated, [OGC API - Tiles](./ogcapi-tiles.md) provides a suitable approach to serve efficiently using less server resources.
|
|
||
| http://localhost:5000/collections/airports/map?f=png&crs=EPSG:3857 | ||
|
|
||
| You can also use tweak other parameters, like bounding box (`bbox`), bounding box crs (`bbox-crs`) and `with` & `height`, to create custom maps: |
There was a problem hiding this comment.
You can also adjust tweak other parameters (such as bounding box (bbox), bounding box CRS (bbox-crs), as well as width and height to create custom maps:
|
|
||
| !!! note | ||
|
|
||
| Check-out the [OGC API - Maps Standard](https://docs.ogc.org/is/20-058/20-058.html), for more details about the map parameters. |
There was a problem hiding this comment.
See the OGC API - Maps Standard, for more details about supported map parameters.
|
|
||
| !!! note | ||
|
|
||
| OGC API - Maps supports CRS from CURIEs (e.g.: `EPSG:4326`, `CRS84`), safe CURIEs (e.g.: `[EPSG:4326]`, `[CRS84]`) and URIs: |
There was a problem hiding this comment.
OGC API - Maps supports CRS from Compact URIs (CURIEs, i.e. EPSG:4326, CRS84), safe CURIEs (e.g.: [EPSG:4326], [CRS84]) and URIs:
| !!! note | ||
|
|
||
| pygeoapi currently supports two well known Tile Matrix Sets: `WorldCRS84Quad` and `WebMercatorQuad`. Their definition is published on the [/TileMatrixSets](https://demo.pygeoapi.io/master/TileMatrixSets) end point. | ||
| By default pygeoapi supports two well known Tile Matrix Sets: `WorldCRS84Quad` and `WebMercatorQuad`. Their definition is published on the [/TileMatrixSets](https://demo.pygeoapi.io/master/TileMatrixSets) end point. For additional TMS, please check the [pygeoapi documentation](https://docs.pygeoapi.io/en/latest/publishing/ogcapi-tiles.html#providing-custom-tile-matrix-set-definitions). |
There was a problem hiding this comment.
- By default, pygeoapi ...
- For additional TMS support, please check ...
|
|
||
| !!! note | ||
| Please note that the tippecanoe tool requires the input file to be in WGS84, and it always outputs tiles in WebMercator. | ||
| Please note that the tippecanoe tool requires the input file to be in `WGS84`, and it **always** outputs tiles in `WebMercator`. |
There was a problem hiding this comment.
...and always outputs tiles in...