titiler-pgstac VS ogcapi-tiles

PgSTAC also provides a geometrysearch function (used by TiTiler-PgSTAC) that assists in creating dynamic tiles from the results of a STAC search. The geometrysearch function allows the ability to register a search to obtain a hash of the filter json. This hash can then be used along with a passed-in geometry to return only the Items that (based on their geometry) are visible when displayed within the geometry. The geometrysearch function can be useful to create things like, for example, a Z/X/Y tile service from search results to make a mosaic of the most recent imagery with less than 10% cloud cover.

TiMVT and TiFeatures are two open source projects we’ve recently released. TiMVT is for vector tiles and TiFeatures is for OGC features.

The next step in terms of web mapping interoperability came with OGC API – Tiles. As with other Standards and candidate standards from the OGC API “family,” it leverages many of the patterns/best practices that we see on the web today (e.g. the use of http status codes, recommended JSON encodings, self-documented using OpenAPI). This was intentional, so as to decrease the learning curve for web developers. As with other OGC APIs, it has a modular structure; i.e. a developer can pick some parts of OGC API – Tiles and integrate them into their existing application. Another very interesting feature about this candidate standard is the tile abstraction – you can serve raster tiles, along with vector tiles, and/or styled tiles. You can explore an example of OGC API – Tiles “in action”, here.