Tell us what the image needs to do

The quickest way to evaluate a rendering workflow is to describe the output rather than ask for a generic feature list.

Include, where known:

• Intended use: print, PDF, report, preview, thin client, or analysis.
• Typical and maximum output width and height.
• Required DPI.
• Coordinate reference system and example bounding box.
• MapLibre style and tile provider.
• Expected request volume, concurrency, and latency target.
• Whether attribution or watermark handling is required.

Email info@heuer.nz

Do not include API keys, provider secrets, or private style URLs in the first email. If those are required to reproduce a problem, arrange a secure exchange first.

Before requesting access

• Read the quickstart for the request model.
• Check styles and assets for upstream requirements.
• Review limits and errors for current source-level constraints.
• Review attribution and licensing for responsibilities around map data.