Static Maps¶
Static maps are map images embedded in alert messages. This page covers advanced static map configuration. For basic setup, see Geocoding.
Custom Map Templates¶
The map's appearance (markers, polygons, layout) comes from the templates on your TileServerCache server, named poracle-<type> (e.g. poracle-monster, poracle-raid, poracle-questsummary). Edit those templates on the tileserver to change what the maps look like. PoracleNG only sends the data fields for each alert type.
config/customMaps/ is not about static maps
Despite the name, files in config/customMaps/ are lookup tables for DTS templates, read with the {{map}} helper. They have no effect on static map images. See Advanced DTS — Custom Maps.
TileserverCache Settings¶
The tileserver settings control how maps are generated for each alert type:
[geocoding.tileserver_settings.default]
type = "staticMap"
width = 500
height = 250
zoom = 15
pregenerate = true
include_stops = false
Multi-Static Maps¶
Multi-static maps combine multiple map views (e.g. street view + satellite) into a single image:
Pre-generating Maps¶
When pregenerate = true, map tiles are pre-generated by the tileserver cache, reducing latency for alerts:
Including Pokestops¶
Show nearby pokestops on the map:
Map Style by Time of Day¶
Configure different map styles for different times of day:
[geocoding]
day_style = "osm-bright"
dawn_style = "osm-liberty"
dusk_style = "osm-liberty"
night_style = "dark-matter"
Use the #(style) placeholder in your TileserverCache URL templates to automatically select the appropriate style.
Discord Image Upload¶
Instead of linking to map images, Poracle can download and upload them directly to Discord's CDN:
This can be useful if your tileserver is not publicly accessible.