Tencent Maps JSAPI GL Development

Problem

Tencent Maps JSAPI GL development is not only about creating a map instance. Teams often run into exposed Keys, inconsistent coordinate systems, wrong extra library loading, uncertain visualization data formats, and missing HTML error handling for container absence, CDN failure, or unsupported WebGL. This skill organizes those constraints into documentation, examples, and a safe workflow.

How It Works

• Classify the request as base maps or data visualization, then search references/jsapigl/docs/ or references/visualization/docs/.
• Confirm classes, properties, events, and parameters using docs such as markers, heatmaps, arc lines, models, or GeoJSON/MVT layers.
• Locate runnable HTML examples from 129 JS API demos and 44 visualization demos to validate data shape.
• Handle Keys by saving a user-supplied Key, guiding users to a temporary Key when needed, or switching candidates on failure.
• When generating HTML, check map.qq.com/api/gljs loading, fixed container size, TMap namespace, and proxying guidance for plaintext Key risk.

Boundaries and Notes

Use it for Tencent Maps JSAPI GL, not other map SDKs. Coordinates should be GCJ-02; convert WGS-84 or BD09 first. Load extra libraries with the libraries URL parameter, such as model, weather, or visualization. Browsers need WebGL support, and generated code should handle missing containers, CDN errors, and unsupported browsers.