Tileserver GL

Tileserver GL
Name	Tileserver GL
Developer	Friedrich "Fs" contributors
Released	2016
Programming language	JavaScript, Node.js
Platform	Cross-platform
License	BSD-3-Clause

Tileserver GL is an open-source vector and raster tile server for serving Mapbox Vector Tiles and static tiles. It provides a bridge between tile data sources, styling specifications, and web mapping clients, enabling delivery of tilesets to browsers, mobile apps, and GIS tools.

Introduction

Tileserver GL operates within the ecosystem of web mapping tools such as Mapbox GL JS, Leaflet, OpenLayers, Cesium, QGIS, and ArcGIS Pro. It interoperates with tiling workflows derived from projects like tippecanoe, Mapnik, GDAL, PostGIS, and GeoServer, and complements cloud services including Mapbox, Amazon Web Services, Google Cloud Platform, Microsoft Azure, and DigitalOcean. The project sits among other servers such as TileStache, Tileserver PHP, TileServer-Carto, MapProxy, and mbtiles-server.

Architecture and Components

Tileserver GL is built on Node.js and uses express.js for HTTP serving, integrating runtime components like vector tile parsers, rasterizers, and static file handlers. It reads tile storage formats from mbtiles containers, and interfaces with style specifications like Mapbox Style Specification and sprite sheets from SVG and PNG assets. The server leverages rendering backends used by mapbox-gl-native and shares lineage with mapbox-gl-js renderers, while supporting tile generation pipelines involving tippecanoe, ogr2ogr, FME, TileMill, and CartoCSS workflows. Auxiliary components often used in deployments include nginx, HAProxy, systemd, Docker, Kubernetes, and Traefik for reverse proxying and orchestration.

Supported Data and Formats

Tileserver GL serves vector tiles in Mapbox Vector Tile format (MVT), raster tiles in PNG and JPEG, and can serve UTFGrid interactivity layers used in projects like OpenStreetMap render stacks. It supports data packaged as MBTiles (SQLite), GeoPackage inputs common in Esri ecosystems, and tiled raster formats produced by gdal_translate and gdalwarp. Styling inputs conform to the Mapbox Style Specification and can include assets created with TileMill, Mapbox Studio, QGIS Composer, and Adobe Illustrator exports for sprite generation.

Deployment and Installation

Installation methods mirror modern DevOps patterns: installing via npm on Linux, macOS, and Windows hosts; running within Docker containers; or deploying to cloud platforms like AWS Elastic Beanstalk, Google Compute Engine, Azure App Service, and Heroku. Production setups commonly use nginx reverse proxies, container registries such as Docker Hub or GitHub Container Registry, orchestration via Kubernetes with persistent volumes backed by Amazon EBS or GCE Persistent Disk, and CI/CD pipelines orchestrated with GitHub Actions, GitLab CI, Jenkins, or CircleCI.

Configuration and Styling

Configuration is driven by JSON style documents compatible with the Mapbox Style Specification and can reference sprite sheets, glyph sources, and data sources hosted locally or on CDN providers such as Cloudflare and Fastly. Designers export styles from Mapbox Studio, QGIS, TileMill, or craft them by hand, integrating fonts from Google Fonts or Font Awesome for glyphs. Customization often uses tools like sed, jq, node-cmd scripts, and asset bundlers such as webpack or parcel for build-time packaging.

Performance and Scaling

Performance strategies include pre-generating tiles with tippecanoe, caching with Varnish, CDN offloading to Cloudflare or Fastly, and using in-memory caching with Redis or file-system caches on SSD instances. Horizontal scaling patterns employ container orchestration with Kubernetes and load balancers like HAProxy or nginx plus autoscaling in AWS Auto Scaling groups. Monitoring and observability integrate Prometheus, Grafana, Datadog, New Relic, and logging to ELK Stack (Elasticsearch, Logstash, Kibana) or Splunk.

Licensing and Community

Tileserver GL is released under permissive licensing aligned with BSD-family terms and receives contributions via platforms like GitHub and GitLab. The community intersects with stakeholders from Mapbox, OpenStreetMap Foundation, OSGeo, PostGIS, and various municipal GIS departments. Discussion and support occur on channels including Stack Overflow, project issue trackers on GitHub, mailing lists affiliated with OSGeo, and chatrooms on Slack and Matrix. Commercial support and hosting are offered by GIS consultancies and cloud integrators such as Carto, Mapbox, Boundless (software), and regional system integrators.

Category:Web mapping