| Concept | Description | |---------|-------------| | | A small raster (PNG/JPEG) or vector (PBF/MVT) image representing a geographic area at a specific zoom level. | | Tile Matrix | A grid of tiles; origin (usually top-left or bottom-left) varies by standard. | | Tile Server | An HTTP endpoint that serves tiles based on URL patterns (e.g., /z/x/y.png ). | | Tile Set / Layer | A collection of tiles forming a complete map layer. | | Service Metadata | Capabilities document (WMTS GetCapabilities , TileJSON, or HTML link headers). |

: Compatible with Windows Vista, 7, 8, and 10.

| Challenge | Description | |-----------|-------------| | | 404 may indicate a void (ocean) vs missing endpoint. | | Variable naming conventions | z/x/y vs level/col/row vs z/x/-y . | | Authentication | Many tile servers require API keys or tokens; discovery requires credential injection. | | Zoom limits | Without metadata, brute-forcing z=18 is expensive (2^36 tiles). | | Vector tiles | MVT tiles contain variable binary data; probing must decode protobuf headers. | | Rate limiting / DDoS risk | Active probing can appear as an attack. |