Why tilegroxy?
Tilegroxy shines when you consume maps from multiple sources. It isn’t tied to any one mapping backend and can pull data from any protocol, whether the standard alphabet soup or a proprietary, authenticated API. Rather than make your frontend aware of every single vendor and exposing your keys, utilize tilegroxy and provide a uniform API with a configuration-driven backend that can be augmented by code when necessary.
Features
- Proxy to ZXY, WMS, TMS, WMTS, or other protocol map layers
- Cache tiles in disk, memory, s3, redis, and/or memcached
- Require authentication using static key, JWT, or custom logic
- Restrict access to a given layer and/or geographic region based on auth token
- Create your own custom provider to pull in non-standard and proprietary imagery sources
- Tweak your map layer with 18 standard effects or by providing your own pixel-level logic
- Combine multiple map layers with adjustable rules and blending methods
- Act as an HTTP server for MapServer and any other CGI application that generates tiles
- Commands for seeding and testing your layers
- Support for both raster and vector format tiles
- Run as HTTPS including Let’s Encrypt support
- Configurable timeout, logging, and error handling rules
- Override configuration via environment variables
- Externalize passwords/keys using AWS Secrets Manager
- Container deployment
- Traces, metrics, and logs available via OpenTelemetry
- Usable as an application or a library