MBTiles Viewer Online

Purpose and use cases: The tool validates, inspects, and previews MBTiles databases directly in the browser, without server tooling. Target users are GIS developers, data providers, cartographers, and field researchers who receive MBTiles packages and need quick metadata verification and tile previews before integration.

Core Logic & Features: Required: upload a single MBTiles file; parse the embedded metadata table; report min_zoom, max_zoom, tile count, and schema. Optional/advanced: in-browser tile previews at chosen zooms; generate a metadata JSON export; validate projection when present. No server calls are made; data remains on the client. If the file is not MBTiles or is corrupted, the tool returns precise error codes.

Inputs & Outputs: Input is one MBTiles file (required). Outputs include a JSON metadata summary (name, version, description, min_zoom, max_zoom, format), a small in-browser tile preview, and optional export of metadata or a subset as a new MBTiles or image tiles. Validation enforces standard MBTiles structure.

Algorithms & Calculations: Reads the MBTiles SQLite database, queries the metadata table, derives zoom range from tiles, counts tiles, and confirms tile size. If present, reads projection metadata to report CRS. For previews, renders a tiny subset of tiles within an in-browser canvas.

Error & Edge Cases: Invalid file type or corrupted database yields explicit errors. Missing metadata results in partial outputs with warnings. Extremely large MBTiles may trigger memory limits. If no tiles exist, the tool reports zero count and possible dataset issues.

Industry/Region & Localization: MBTiles follows the MBTiles specification; typical CRS is Web Mercator (EPSG:3857). Outputs use standard units (tile indices, zoom levels) that align with common GIS workflows.

Assumptions & Exclusions: Assumes a compliant MBTiles file stored locally. No network requests, no server-side processing. Does not repackage tiles unless explicitly requested via export.