# Meshtile

Meshtile is an HTTP tile server for Meshtastic mesh networks. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/2415/meshtile

## Description

Meshtile is an HTTP tile server for Meshtastic mesh networks. It computes RF signal coverage using propagation and elevation data, then serves 256x256 PNG signal-strength tiles for map visualization.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

32/100 (Low), based on 3 of 4 factors.
- Maintained: 46 (last commit 270 days ago)
- Popular: 6 (1 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/stevenlafl/meshtile
- GitHub: https://github.com/stevenlafl/meshtile
- Unraid: https://ca.unraid.net/apps/meshtile-19son871qrgmkr?q=Meshtile

## Common questions

### What address and port does Meshtile bind to by default?

It binds to 0.0.0.0 on port 8080 by default. The listen port can be changed with the --port option.

### What HTTP path should I use in a reverse proxy to request signal tiles?

Route tile requests to GET /tiles/{z}/{x}/{y}.png.

### Where does Meshtile obtain node and noise floor data?

By default it fetches node and noise floor data from the selected MeshMapper regional instance. You can override the source with a URL or local file using --nodes and --noise-data.

### How does Meshtile choose grid computation concurrency?

The --threads option controls concurrent grid computation threads. A value of 0 means automatic, which uses the CPU core count.

---
Source: Our Local Host (https://ourlocalhost.com/app/2415/meshtile), the self-hosted and open-source app directory.
