Meshtastic-Android icon indicating copy to clipboard operation
Meshtastic-Android copied to clipboard

[Bug]: Custom tile sources (such as opentopo) do not buffer

Open b8b8 opened this issue 6 months ago • 9 comments

Contact Details

No response

What happened?

Custom tile sources such as OpenTOPO do not buffer/store correctly, wiping out the map when actively scrolling. The maps do render eventually when you stop scrolling.

Image

Image

App Version

2.6.35

Phone

Pixel9a

Device

T1000E

Firmware

2.7.5

Relevant log output


Code of Conduct

  • [x] I agree to follow this project's Code of Conduct

b8b8 avatar Aug 14 '25 04:08 b8b8

There's no caching implementation currently, this is probably very dependent on your internet connection (and api ratelimits) currently.

jamesarich avatar Aug 17 '25 14:08 jamesarich

bump

b8b8 avatar Sep 25 '25 13:09 b8b8

This is probably cause why OpenStreetMap blocked tile use for Meshtastic App. If there is no caching and with this number of Meshtastic users it is certain that OSM tile server takes huge amount of hits from Meshtastic apps all over the World.

When dealing with map tiles, caching is a must. It is not just about OSM - Google is not tolerant either and it will eventually react too.

pedjas avatar Oct 12 '25 23:10 pedjas

This is probably cause why OpenStreetMap blocked tile use for Meshtastic App. If there is no caching and with this number of Meshtastic users it is certain that OSM tile server takes huge amount of hits from Meshtastic apps all over the World.

When dealing with map tiles, caching is a must. It is not just about OSM - Google is not tolerant either and it will eventually react too.

This is not relevant to this bug report.

Also Openstreetmap tiles load without issue on the fdroid release of the Meshtastic app. OpenTOPO maptiles load correctly on the google and fdroid release. Full googlemaps allows offline maps and automatically updates this cache in the background periodically. Caching is a must, yes. But also you can manually add your own KMZ, KML, or GEOJSON files to the meshtastic app for truly offline maps.

b8b8 avatar Oct 13 '25 00:10 b8b8

This is not relevant to this bug report.

How it is not relevant when this bug is probably the cause why OpenStreetMap blocked Meshtastic APP so we cannot use map tiles from openstreetmap.org?

Also Openstreetmap tiles load without issue on the fdroid release of the Meshtastic app.

Probably FDroid version represents itself as different app so it os not part of the block.

OpenTOPO maptiles load correctly on the google and fdroid release.

OpenTOP is not hosted at OpenStreetMaps servers and is not handled by block. Also, probably it is very low number of user who actually use that map so it does not cause issues.

But also you can manually add your own KMZ, KML, or GEOJSON files to the meshtastic app for truly offline maps.

This is completely irrelevant. This is not about offline maps, it is about caching tiles so that app does not load the same tile each time from remote server, causing high load on server.

pedjas avatar Oct 13 '25 08:10 pedjas

This is probably cause why OpenStreetMap blocked tile use for Meshtastic App. If there is no caching and with this number of Meshtastic users it is certain that OSM tile server takes huge amount of hits from Meshtastic apps all over the World. When dealing with map tiles, caching is a must. It is not just about OSM - Google is not tolerant either and it will eventually react too.

This is not relevant to this bug report.

Also Openstreetmap tiles load without issue on the fdroid release of the Meshtastic app. OpenTOPO maptiles load correctly on the google and fdroid release. Full googlemaps allows offline maps and automatically updates this cache in the background periodically. Caching is a must, yes. But also you can manually add your own KMZ, KML, or GEOJSON files to the meshtastic app for truly offline maps.

How do you add custom off line maps and sources?

I don't see that option. I am using f-droid 2.7.5

BobsBlueNorth avatar Nov 10 '25 00:11 BobsBlueNorth

This is probably cause why OpenStreetMap blocked tile use for Meshtastic App. If there is no caching and with this number of Meshtastic users it is certain that OSM tile server takes huge amount of hits from Meshtastic apps all over the World. When dealing with map tiles, caching is a must. It is not just about OSM - Google is not tolerant either and it will eventually react too.

This is not relevant to this bug report. Also Openstreetmap tiles load without issue on the fdroid release of the Meshtastic app. OpenTOPO maptiles load correctly on the google and fdroid release. Full googlemaps allows offline maps and automatically updates this cache in the background periodically. Caching is a must, yes. But also you can manually add your own KMZ, KML, or GEOJSON files to the meshtastic app for truly offline maps.

How do you add custom off line maps and sources?

I don't see that option. I am using f-droid 2.7.5

It's only available on the Google play store release

b8b8 avatar Nov 10 '25 01:11 b8b8

This issue hasn not had any comment or update in the last 30 days. If it is still relevant, please post update comments. If no comments are made, this issue will be closed in 7 days.

github-actions[bot] avatar Dec 10 '25 06:12 github-actions[bot]

Bump

b8b8 avatar Dec 10 '25 14:12 b8b8