求助:iOS谷歌地图自定义瓦片缩放时提前消失如何解决
解决方案:为自定义瓦片实现预缩放过渡效果
我之前也遇到过完全一样的问题,谷歌地图iOS SDK的自定义瓦片层默认确实不会像MapKit或MapBox那样自动缩放现有瓦片做过渡,不过我们可以通过缓存低级别瓦片并在新瓦片加载前缩放复用的方式来实现这个效果,具体步骤如下:
1. 切换到GMSAsyncTileLayer(推荐)
虽然你用的是GMSSyncTileLayer,但GMSAsyncTileLayer更适合处理异步瓦片加载,也更容易实现缓存和过渡逻辑。我们先子类化它:
class CustomScalingTileLayer: GMSAsyncTileLayer { // 用NSCache管理瓦片缓存,自动处理内存压力 private let tileCache = NSCache<NSString, UIImage>() // 你的瓦片服务URL模板,替换成自己的地址 private let tileURLTemplate: String init(tileURLTemplate: String) { self.tileURLTemplate = tileURLTemplate super.init() // 开启淡入效果,让新瓦片加载完成后平滑过渡 self.fadeIn = true } }
2. 实现瓦片请求与缩放复用逻辑
重写requestTileForX:y:zoom:receiver:方法,核心逻辑是:
- 优先请求当前缩放级别的瓦片
- 在请求的同时,尝试从缓存中获取低一级缩放级别的瓦片,缩放后临时返回填补加载空白
- 当正确级别的瓦片加载完成后,再替换为高清瓦片
override func requestTileForX(_ x: UInt, y: UInt, zoom: UInt, receiver: GMSTileReceiver) { let currentZoom = zoom let tileKey = "\(currentZoom)_\(x)_\(y)" as NSString // 先检查缓存里有没有当前级别的瓦片,有就直接返回 if let cachedTile = tileCache.object(forKey: tileKey) { receiver.receiveTileWith(x: x, y: y, zoom: zoom, image: cachedTile) return } // 1. 尝试用低一级缩放的瓦片缩放后临时显示 let lowerZoom = currentZoom - 1 if lowerZoom >= minimumZoom { // 计算低级别瓦片对应的坐标(瓦片金字塔结构:每升一级,x/y是前一级的2倍,反向取整即可) let lowerX = x / 2 let lowerY = y / 2 let lowerTileKey = "\(lowerZoom)_\(lowerX)_\(lowerY)" as NSString if let lowerTile = tileCache.object(forKey: lowerTileKey) { // 缩放瓦片到当前级别的尺寸(默认tileSize为256x256) let scaledImage = scaleImage(lowerTile, toSize: CGSize(width: tileSize.width, height: tileSize.height)) receiver.receiveTileWith(x: x, y: y, zoom: zoom, image: scaledImage) } } // 2. 异步请求当前级别的瓦片 guard let tileURL = URL(string: tileURLTemplate.replacingOccurrences(of: "{z}", with: "\(currentZoom)") .replacingOccurrences(of: "{x}", with: "\(x)") .replacingOccurrences(of: "{y}", with: "\(y)")) else { receiver.receiveTileWith(x: x, y: y, zoom: zoom, image: kGMSTileLayerNoTile) return } URLSession.shared.dataTask(with: tileURL) { [weak self] data, _, error in guard let self = self, error == nil, let data = data, let image = UIImage(data: data) else { DispatchQueue.main.async { receiver.receiveTileWith(x: x, y: y, zoom: zoom, image: kGMSTileLayerNoTile) } return } // 缓存当前瓦片,供后续请求复用 self.tileCache.setObject(image, forKey: tileKey) DispatchQueue.main.async { receiver.receiveTileWith(x: x, y: y, zoom: zoom, image: image) } }.resume() } // 辅助方法:将图片缩放到指定尺寸 private func scaleImage(_ image: UIImage, toSize size: CGSize) -> UIImage { let renderer = UIGraphicsImageRenderer(size: size) return renderer.image { context in image.draw(in: CGRect(origin: .zero, size: size)) } }
3. 关键注意事项
- 缓存策略:
NSCache会自动在内存不足时清理缓存,如果你需要持久化缓存,可以改成磁盘缓存(比如用FileManager存储瓦片文件) - 坐标映射:低级别到高级别的坐标转换要准确,
lowerX = x / 2和lowerY = y / 2是瓦片金字塔结构的标准转换逻辑 - 淡入效果:开启
fadeIn = true能让新瓦片加载完成后平滑替换缩放后的临时瓦片,避免突兀切换 - 边界判断:要确保
lowerZoom不低于瓦片层设置的minimumZoom,避免无效的低级别瓦片请求
4. 集成到地图中
最后把自定义瓦片层添加到谷歌地图视图即可:
let tileLayer = CustomScalingTileLayer(tileURLTemplate: "https://your-tile-server/{z}/{x}/{y}.png") tileLayer.minimumZoom = 10 tileLayer.maximumZoom = 18 tileLayer.map = yourGoogleMapView
这样处理后,用户捏合放大地图时,现有低级别瓦片会被缩放临时显示,直到当前级别的瓦片加载完成,就和MapKit、MapBox以及谷歌自身基础瓦片的过渡行为一致了。
内容的提问来源于stack exchange,提问作者Jon Vogel
相关产品推荐
相关产品推荐

