MeshApp blocked by tile.openstreetmap.org

We discovered that MeshApp included a feature that could prefetch
raster tiles for a selected area from tile.openstreetmap.org across
multiple zoom levels. We understand that this violated the
OpenStreetMap Tile Usage Policy.

We have removed this feature from both the user interface and the
underlying map API.

The corrected version is: MeshApp 2.3.10
Release date: July 29, 2026
Source/release:
https://github.com/smikme/meshapp/releases/tag/v2.3.10
https://github.com/smikme/meshapp/commit/76f70ea57a045a0a490c0687f6e73519f41224a9

The corrected client now:

  • requests only tiles visible in the current interactive viewport;
  • provides no area download, prefetch, or offline download operation;
  • discards queued requests when tiles leave the viewport;
  • limits concurrent tile requests to two;
  • honours Cache-Control and Expires headers;
  • stores ETag and Last-Modified validators;
  • uses conditional requests for expired tiles and handles HTTP 304;
  • applies a seven-day fallback TTL when caching headers are
    unavailable;
  • uses HTTP/2;
  • displays “© OpenStreetMap contributors”;
  • identifiable User-Agen

For the future, if you’re interested in restoring this functionality, I suggest setting up your own tile server to service offline downloads. There’s also the possibility of marking requests as intended for bulk operation as QGIS did, but that’s something you would need to discuss in detail with the infrastructure folks here.

For the future, consider exploring Protomaps. They are explicitly designed to provide easy single-file hosting and area downloads via HTTP range requests. Their CLI tool exposes that functionality, so it shouldn’t be difficult to re-implement it on Android. Now, this means assembling a few parts (this case isn’t a ready-made API) but a clanker will be more than willing to do it for you.
Plus, they’re much smaller due to being vector files.
NB: I am not affiliated with the Operations Working Group ;)

This is a desktop application, so changing the API would be quite costly. The app currently meets all the requirements in full. Can we expect the restrictions to be lifted?

Rather not, but there are companies out there running paid tile server. You pay per tile and they don’t care for what reason you download them.

One example would be GeoFabrik.

This is an open-source, community-driven app, not a commercial project. Without maps, an app like this would be practically unusable.

Understood, though with apps scrapping tiles OSM website would be practically unusable. :wink:

We’ve met all of OSM’s requirements on our end, so we’re now waiting for the restrictions to be lifted. We’re out of ideas at this point.

If so, you might rather want to reach out to the operations team by one of their contact channels mentioned at https://operations.osmfoundation.org/

They might want to differentiate older versions of your app from fixed versions, so you might best describe this to them.

How long ago it was changed? Most of these rules are automatic

The corrected version is: MeshApp 2.3.10
Release date: July 29, 2026

The application identifies itself using the following User-Agent: MeshApp/<VERSION>.

Then I would wait at least few days, maybe week and after that try to contact people if block persists despite all issues being fixed.

OpenStreetMap Foundation operates on shoestring budget and there is a single paid person looking after server and some volunteers. So I would try to avoid adding more work for them.