osmdroid 地图图块仅在缩小后加载

发布于 2025-01-14 06:00:44 字数 1016 浏览 3 评论 0原文

每次全新安装后，我的 MapView 中的图块仅在缩小相当多后才加载。之后它工作正常，但我不知道是什么原因造成的。调试日志如下：

D/OsmDroid: SqlCache - Tile doesn't exist: Mapnik/1/0/0
D/OsmDroid: Archives - Tile doesn't exist: /1/0/0
D/OsmDroid: SqlCache - Tile doesn't exist: Mapnik/3/1/3
D/OsmDroid: Archives - Tile doesn't exist: /3/1/3
D/OsmDroid: SqlCache - Tile doesn't exist: Mapnik/5/5/12
...

我已经在 onViewCreated 中初始化了我的 MapView，如下所示：

map = requireView().findViewById(R.id.map);
map.setTileSource(TileSourceFactory.MAPNIK);
map.getZoomController().setVisibility(CustomZoomButtonsController.Visibility.NEVER);
map.setMultiTouchControls(true);

一旦我获得了位置修复，就会执行以下操作：

IMapController mapController = map.getController();
mapController.setZoom(10.0);
GeoPoint startingPoint = new GeoPoint(location.getLatitude(), location.getLongitude());
mapController.setCenter(startingPoint);

我已按照 osmdroid 教程进行操作，设置了用户代理，添加了对清单的必要权限等等。如果您需要更多信息，请告诉我。

编辑：我正在使用版本 6.1.11

原文

After each fresh install tiles in my MapView only load after zooming out quite a bit. After that it works fine, but I can't figure out what causes this.
The debug logs are as follows:

D/OsmDroid: SqlCache - Tile doesn't exist: Mapnik/1/0/0
D/OsmDroid: Archives - Tile doesn't exist: /1/0/0
D/OsmDroid: SqlCache - Tile doesn't exist: Mapnik/3/1/3
D/OsmDroid: Archives - Tile doesn't exist: /3/1/3
D/OsmDroid: SqlCache - Tile doesn't exist: Mapnik/5/5/12
...

I have initialized my MapView in onViewCreatedlike this:

map = requireView().findViewById(R.id.map);
map.setTileSource(TileSourceFactory.MAPNIK);
map.getZoomController().setVisibility(CustomZoomButtonsController.Visibility.NEVER);
map.setMultiTouchControls(true);

And once I obtained a location fix, the following is executed:

IMapController mapController = map.getController();
mapController.setZoom(10.0);
GeoPoint startingPoint = new GeoPoint(location.getLatitude(), location.getLongitude());
mapController.setCenter(startingPoint);

I have followed the osmdroid tutorial, set the user agent, added the necessary permissions to the manifest and so on. Please let me know, if you need further information.

Edit: I'm using version 6.1.11

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

何止钟意 2025-01-21 06:00:44

我遇到了这个问题。
似乎如果您最初设置任何缩放级别 > 19、图块渲染不正确。

作为解决方法，我将缩放级别设置为 19 而不是 20。然后用户可以根据自己的喜好进行设置

回复收藏 0 原文

罗罗贝儿 2025-01-21 06:00:44

每次放大/缩小时，OsmDroid 都会检查地图视图当前边界内的每个图块索引是否有图块的副本。如果存在副本，将从切片缓存中复制该副本并将其绘制在地图上。如果没有，将从在线地图图块数据库下载图块并绘制在地图上。下载的图块将保存在图块缓存中，以便下次这些图块索引位于视图边界时快速检索。

然而，它确实涉及大量处理每个事件的图块模块提供程序对象。它们保存在 MapTileModuleProviderBase 图块模块提供程序数组中，该数组是在 MapView.setTileProvider() 调用中设置的。如果不包含地图瓦片下载模块提供商，则不会从互联网/网络下载任何瓦片；相反，它将从任何附加的图块模块提供程序检索副本：缓存图块模块提供程序、资产图块模块提供程序、文件存档模块提供程序等。如果图块模块提供程序数组中缺少任何一个图块提供程序，则该图块索引的图块将无法正确绘制，您将看到一个空的灰色“图块”方块。

这些图块模块提供程序可能会引用 OsmDroid 默认配置实例 DefaultConfigurationProvider，以获取控制图块过期率、缓存大小等的属性。这些属性会影响图块绘制性能。

如果您使用 OsmDroid 特定的切片模块提供程序 API（MapsForge、GeoPackage、WMS 等）加载在线/离线地图数据库，这可能会更改当前切片模块提供程序数组结构，请按照以下步骤正确重置为 MAPNIK 数据库


//load MAPNIK basemap updateable from Internet and cacheable

IFilesystemCache tileWriter = null;
INetworkAvailablityCheck networkAvailabilityCheck = new NetworkAvailabliltyCheck(getContext());
List<MapTileModuleProviderBase> defaultProviders = new ArrayList<>();
SimpleRegisterReceiver simpleRegisterReceiver = new SimpleRegisterReceiver(getContext());

if (Build.VERSION.SDK_INT < 10) {
    tileWriter = new TileWriter();
} else {
    tileWriter = new SqlTileWriter();
}

defaultProviders.add(new MapTileAssetsProvider(simpleRegisterReceiver, getContext().getAssets()));

final MapTileAssetsProvider assetsProvider = new MapTileAssetsProvider(
        simpleRegisterReceiver, getContext().getAssets(), TileSourceFactory.MAPNIK);
defaultProviders.add(assetsProvider);

final MapTileFileStorageProviderBase cacheProvider =
        MapTileProviderBasic.getMapTileFileStorageProviderBase(simpleRegisterReceiver, TileSourceFactory.MAPNIK, tileWriter);
defaultProviders.add(cacheProvider);

final MapTileFileArchiveProvider archiveProvider = new MapTileFileArchiveProvider(
        simpleRegisterReceiver, TileSourceFactory.MAPNIK);
defaultProviders.add(archiveProvider);

final MapTileApproximater approximationProvider = new MapTileApproximater();
defaultProviders.add(approximationProvider);
approximationProvider.addProvider(assetsProvider);
approximationProvider.addProvider(cacheProvider);
approximationProvider.addProvider(archiveProvider);

final MapTileDownloader downloaderProvider = new MapTileDownloader(TileSourceFactory.MAPNIK, tileWriter, networkAvailabilityCheck);
defaultProviders.add(downloaderProvider);

MapTileModuleProviderBase[] providerArray = new MapTileModuleProviderBase[defaultProviders.size()];
for (int i = 0; i < defaultProviders.size(); i++) {
    providerArray[i] = defaultProviders.get(i);
}

Log.i(IMapView.LOGTAG, String.format("reset MAPNIK: current tile module providers(%d) = %s",
        providerArray.length,
        Arrays.toString(providerArray)));

MapTileProviderArray obj = new MapTileProviderArray(TileSourceFactory.DEFAULT_TILE_SOURCE, simpleRegisterReceiver, providerArray);
mapView.setTileProvider(obj);

mapView.setTileSource(TileSourceFactory.MAPNIK);

：，我们不需要显式调用 MapView.invalidate() （如果从 UI 线程调用）或 MapView.postInvalidate() （如果从非 UI 线程调用）线程），因为这是由 MapView 处理图块资源的。

public void setTileProvider(final MapTileProviderBase base) {
    this.mTileProvider.detach();
    mTileProvider.clearTileCache();
    this.mTileProvider = base;
    mTileProvider.getTileRequestCompleteHandlers().add(mTileRequestCompleteHandler);
    updateTileSizeForDensity(mTileProvider.getTileSource());

    this.mMapOverlay = new TilesOverlay(mTileProvider, this.getContext(), horizontalMapRepetitionEnabled, verticalMapRepetitionEnabled);

    mOverlayManager.setTilesOverlay(mMapOverlay);
    invalidate();
}

如果您再次在线程中更改 MapView 的任何属性，则必须调用适当的地图视图失效来强制重绘。过于频繁地调用失效会对应用程序的性能产生负面影响。

Every time you zoom in/out, OsmDroid checks to see if there is a copy of the tile for every tile index within the map view's current boundary. If a copy exists, it will be copied from the tile cache and drawn on the map. If not, the tile will be downloaded from the online map tile database and drawn on the map. The downloaded tile will be saved in the tile cache for quick retrieval the next time those tile indices are in the view's boundary.

It does, however, involve a significant number of tile module provider objects that handle each event. They are saved in the MapTileModuleProviderBase tile module provider array that is set in MapView.setTileProvider() call. If the map tile download module provider is not included, it will not download any tiles from the Internet/network; instead, it will retrieve a copy from any attached tile module providers: cache tile module provider, assets tile module provider, file archive module provider, and so on. If any of those tile providers are missing from the tile module provider array, the tile for that tile index will not be drawn properly and you will see an empty grey "tile" square.

These tile module providers may refer to the OsmDroid default configuration instance, the DefaultConfigurationProvider, for properties that control tile expiration rate, cache size, and so on. These properties affect the tile draw performance.

If you use OsmDroid-specific tile module provider API (MapsForge, GeoPackage, WMS, etc.) to load online/offline map databases which may change the current tile module provider array structure, follow these steps to properly reset to the MAPNIK database:


//load MAPNIK basemap updateable from Internet and cacheable

IFilesystemCache tileWriter = null;
INetworkAvailablityCheck networkAvailabilityCheck = new NetworkAvailabliltyCheck(getContext());
List<MapTileModuleProviderBase> defaultProviders = new ArrayList<>();
SimpleRegisterReceiver simpleRegisterReceiver = new SimpleRegisterReceiver(getContext());

if (Build.VERSION.SDK_INT < 10) {
    tileWriter = new TileWriter();
} else {
    tileWriter = new SqlTileWriter();
}

defaultProviders.add(new MapTileAssetsProvider(simpleRegisterReceiver, getContext().getAssets()));

final MapTileAssetsProvider assetsProvider = new MapTileAssetsProvider(
        simpleRegisterReceiver, getContext().getAssets(), TileSourceFactory.MAPNIK);
defaultProviders.add(assetsProvider);

final MapTileFileStorageProviderBase cacheProvider =
        MapTileProviderBasic.getMapTileFileStorageProviderBase(simpleRegisterReceiver, TileSourceFactory.MAPNIK, tileWriter);
defaultProviders.add(cacheProvider);

final MapTileFileArchiveProvider archiveProvider = new MapTileFileArchiveProvider(
        simpleRegisterReceiver, TileSourceFactory.MAPNIK);
defaultProviders.add(archiveProvider);

final MapTileApproximater approximationProvider = new MapTileApproximater();
defaultProviders.add(approximationProvider);
approximationProvider.addProvider(assetsProvider);
approximationProvider.addProvider(cacheProvider);
approximationProvider.addProvider(archiveProvider);

final MapTileDownloader downloaderProvider = new MapTileDownloader(TileSourceFactory.MAPNIK, tileWriter, networkAvailabilityCheck);
defaultProviders.add(downloaderProvider);

MapTileModuleProviderBase[] providerArray = new MapTileModuleProviderBase[defaultProviders.size()];
for (int i = 0; i < defaultProviders.size(); i++) {
    providerArray[i] = defaultProviders.get(i);
}

Log.i(IMapView.LOGTAG, String.format("reset MAPNIK: current tile module providers(%d) = %s",
        providerArray.length,
        Arrays.toString(providerArray)));

MapTileProviderArray obj = new MapTileProviderArray(TileSourceFactory.DEFAULT_TILE_SOURCE, simpleRegisterReceiver, providerArray);
mapView.setTileProvider(obj);

mapView.setTileSource(TileSourceFactory.MAPNIK);

Normally, we don't need to explicitly call MapView.invalidate() (if called from a UI thread) or MapView.postInvalidate() (if called from a non-UI thread) since this is handled by MapView for tile resources.

public void setTileProvider(final MapTileProviderBase base) {
    this.mTileProvider.detach();
    mTileProvider.clearTileCache();
    this.mTileProvider = base;
    mTileProvider.getTileRequestCompleteHandlers().add(mTileRequestCompleteHandler);
    updateTileSizeForDensity(mTileProvider.getTileSource());

    this.mMapOverlay = new TilesOverlay(mTileProvider, this.getContext(), horizontalMapRepetitionEnabled, verticalMapRepetitionEnabled);

    mOverlayManager.setTilesOverlay(mMapOverlay);
    invalidate();
}

If you change any of MapView's properties in a thread again, you must call the appropriate map view invalidation to force the redraw. Calling invalidation too frequently will have a negative impact on the app's performance.

回复收藏 0 原文