In three demos this week, the first question was whether we support OGC API – Features and Tiles end to end. For those of you selling or implementing, are you seeing buyers understand the differences from WMS/WFS, and how are you framing performance and security in a way that keeps the conversation business-focused instead of purely technical?
I pitch it as ‘REST + JSON + cacheable tiles’ — moving from faxed maps to web pages — and tie it to two KPIs: time-to-first-map and cloud egress, then run a one-week bake-off: same layer via WFS/WMS vs OGC API Features/Tiles behind a CDN, comparing P95 latency and egress spend. For security, I translate to ‘OIDC + scoped tokens’ and show that least-privilege cuts surface area; some IT teams still want IP allowlists, which you can layer in. @OGC’s overview helps non-devs: https://ogcapi.ogc.org/.