Problem Mapbox Satellite and .mtiles layer

Hi

To report a bug I encountered on the map widget only with the configuration
Mapbox Satellite + 1 layer .mbtiles

It works for Mapbox Satelite Hybrid, google.....
The problem is just on Mapbox Satellite

The .mbtiles layer seems to appear for a micro second and then disappears. I tested on 3 differents devices.

The bug is just on ODK-Collect-v2022.3.0.apk version
Earlier versions do not have this problem, on ODK-Collect-v2022.2.3.apk it works fine.

Configuration


Not working with Mapbox Satellite

Working with other choice Mapbox Satellite Hybrid

Example .mtiles targeting the Corsica region
test.zip (1022.5 KB)

Have a nice day

Hi @Olivier_Poujade

Thanks for reporting the issue. I can confirm that there is something wrong there. I've reported the issue in our repository https://github.com/getodk/collect/issues/5236 and will try to fix it.

1 Like

I just noticed something else in 2022.3.0 with mapbox base layer that is different to the previous release. I forgot to check this in the beta, but confirmed it's there too.

Previously, I could zoom in to a frankly ridiculous level, and it pixellated but it didn't stop you from doing so (I don't have any vector tilesets but assume these would render nicely). Now there is a hard stop shortly after the last zoom level in the tileset appears. The other base layers also all had this, but at lower zoom levels, which is why I only used mapbox.

For comparison:
Measuring a 10m scale bar on the device screen at maximum zoom on a 10" tablet,
Google: 34mm (zoom level 20?)
OSM/USGS/Stamen/Carto: 68mm (zoom level 21?)
Mapbox: 136mm (zoom level 22?)

On a 5" handset with 2022.3Beta2 it measures 122mm, basically the same as current release, but on a 12" tablet with 2022.2.3 it measures 1550mm (extrapolating from 1m at 155mm)

It is definitely getting into false precision, but the extra zoom did allow for some very nice drawing markups at the sub metre level.

We did upgrade Mapbox to the newest version in this release, so it could be that zoom limitations have changed without us realizing. We'll need to investigate and see if there's anything we can do to restore the previous behaviour, and potentially even make that kind of zooming possible in OSM/Google Maps.