What file formats does this auditor support?

It accepts single vector tile files (.mvt, .pbf), gzip-compressed tiles (.gz), and PMTiles v3 container archives (.pmtiles).

How does the tool determine polygon ring winding order?

It applies the surveyor's formula to the decoded screen coordinates (y-down), requiring positive area for exterior rings and negative area for interior rings.

What tile encoding thresholds trigger a budget warning?

Tiles exceeding approximately 500 KB in compressed size or containing more than 10,000 features are flagged for review.

Are z, x, and y tile coordinates required?

No, but providing z/x/y coordinates is required to extract a specific tile from a PMTiles archive and calculate its geographic bounding box.

Does this tool execute in the browser or send data to a server?

All Protocol Buffer decoding, PMTiles directory parsing, and geometry validation execute locally in client-side TypeScript.

Elysia Tools

Navigation

Geography

MVT Mapbox Vector Tile PMTiles Google MVT Projection and Tilelive Encoding Auditor

Audit .mvt/.pbf vector tiles and PMTiles v3 archives against the Mapbox Vector Tile Specification 2.x: protobuf Layer/Feature/Value decoding, MoveTo/LineTo/ClosePath command-stream validation, ring winding and tag indexes, Web Mercator Google-tile XYZ bounds, PMTiles v3 directory decoding and tile-size vs feature-count budgets.

Details

What this tool helps you do

Pure-TypeScript wire-format audit: a hand-rolled protobuf reader decodes Tile.layers → Layer(version/name/features/keys/values/extent) → Feature(tags/type/geometry) → Value (string/float/double/int/uint/sint-zigzag/bool). The geometry interpreter follows spec §4.3 exactly — CommandInteger = id | count<<3, zigzag ParameterIntegers, dX/dY ≠ (0,0), ClosePath count 1 polygons only, POINT = single MoveTo, LINESTRING = MoveTo+LineTo repetitions — and classifies each ring via the surveyor’s formula so exterior rings must have positive (visually clockwise, y-down) and interior rings negative area. Tile-size vs feature-count budgets follow tilelive/tippecanoe practice (≈500 KB and ≈10 000 features per tile as review thresholds). PMTiles v3 is decoded per the spec: 127-byte header, gzip/brotli internal compression, varint directories with delta TileIDs on the Hilbert curve, run-length tile entries and run-length 0 leaf pointers, cluster and conformance checks, plus tile extraction at a given z/x/y. The Web Mercator panel validates the Google tile scheme XYZ (0 ≤ x,y < 2^z) and computes the geographic tile bbox and resolution.

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Samples

MVT Mapbox Vector Tile PMTiles Google MVT Projection and Tilelive Encoding Auditor

What this tool helps you do

Run this tool

Examples that match this tool

Continue with connected tools and hubs

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Auditing a Raw MVT Tile with Complex Polygons

2. Inspecting a PMTiles v3 Archive and Extracting Tiles

FAQ

MVT / PMTiles Samples

Hex/Unicode Encoding Format Samples

Web File Operations Go Samples

Web File Operations Python Samples

JavaScript Deobfuscator

Chess FEN, PGN & Elo Rating Tutor

CSV Transformer

Lotka–Volterra Predator-Prey Dynamics Simulator