Pathoverlay does not work with 512x512 tiles.

[osmdroid]

Pathoverlay does not work with 512x512 tiles.

[neilboyd]

Fixed in commit 22677d6

[kurtzmarc]

I think 22677d6 is a bad idea and it will crash. If we start to use longs in MapSize() that means we support a much larger map size - one that Android's canvas does not support since it uses integers for its coordinate system. I suspect that this will break if you zoom in far and travel to the edges of the map. Also it doesn't compile with Java 8 since it appears that implicit conversions from long to int are errors now (I think that's what is happening to me).

[neilboyd]

What should we do instead? Argument check to prevent tiles larger than 256?

[kurtzmarc]

I think I need to take some time to reproduce and explore the problem more, but calling TileSystem.setTileSize(512) might be all that is needed. Can OP try that and confirm?

I think most people are interested in scaling the tiles to the device's dpi which is why they are doing this (it has been proposed as a sort-of-working solution for that). Maybe that's the real problem to solve.

[ziem]

I think most people are interested in scaling the tiles to the device's dpi which is why they are doing this (it has been proposed as a sort-of-working solution for that). Maybe that's the real problem to solve.

I agree! Tiles are too small on high dpi devices like Nexus 5 and posted workaround:
#49 (comment)
is causing problems:
#13
#68

[kurtzmarc]

Please take a look at #81 where we have a potential solution ready for testing.

[kurtzmarc]

I have merged the fix_dpi_scaling branch. Call mMapView.setTilesScaledToDpi(true) to turn on tile scaling. Report all issues to #81.