Comment by apt-apt-apt-apt
3 days ago
For others curious like I was, it seems he hired a cartographer to render essentially a set of huge, nice-looking, custom map images with details like hiking trails that Apple Maps doesn't have.
So unlike Apple Maps, which is dynamically rendered, it basically shows image tiles. It allows for a nicer-looking, more detailed map, but affects things like needing separate downloads for different zoom levels, rotation, updatability.
The use of the cartographer to generate separate designs and the technology used to render/deliver those designs are two entirely separate concerns.
His original map provider offers both vector and raster tile services: https://www.thunderforest.com/maps/outdoors/
A common pattern is to use a vector tile service + style definition directly or to generate raster tiles if those are desired.
Good point, I assumed he was using images because his screenshots show text perfectly following the curves of rivers, which seems hard to do with dynamic rendering.
That’s the point of a vector (not raster) tiles. Wh do you say it is hard to do with dynamic rendering? With Maplibre or any modern map SDK this this is standard…
1 reply →
I'm afraid you're mistaken. He hired a cartographer to iterate over the design, but from the images, he likely used that feedback to create a map style.
For example https://wiki.openstreetmap.org/wiki/Map_style
However, you're also kind of correct in that the rendered tiles are typically cached server-side (presumably also for Apple Maps).
I think this may not even be possible because Apple does not give access to the Metal graphics API on Apple Watch to third-party developers.