- From: Jerome St-Louis via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Nov 2023 16:59:16 +0000
- To: public-sdwig@w3.org
In my view, the main goal and advantage of OGC API - Tiles over WMTS, and the reason we developed the Tileset Metadata in 2DTMS 2.0, is the ability to share **data** tiles for purposes other than visualization and for client-side visualization / styling / queries (no need for server round-trip "GetMapInfo"). This applies to any type of data, whether that is coverage tile, vector tiles, 3D mesh tiles, or point cloud tiles. Even with the commonly distributed Mapbox Vector Tiles tilesets, at least the most detailed tiled zoom level should be suitable for purposes other than visualization. The [MVT spec](https://github.com/mapbox/vector-tile-spec/tree/master/2.1) states its purpose as: > This document specifies a space-efficient encoding format for tiled geographic vector data. It is designed to be used in browsers or server-side applications for fast rendering or lookups of feature data. -- GitHub Notification of comment by jerstlouis Please view or discuss this issue at https://github.com/w3c/sdw/issues/1288#issuecomment-1802295119 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 November 2023 16:59:22 UTC