pnorman left a comment (openstreetmap/openstreetmap-website#6618)
Because the standard layer is only produced in one resolution it is already
being scaled on most devices. It is only left unscaled if one physical pixel is
the same as one device-independent pixel. This is not true for most devices,
and browser zoom renders it untrue for even more.
The issue is the standard layer is not designed to be viewed at map scales
other than one tile = 256 DI pixels. OpenStreetMap Carto has, at least
historically, been designed for this, but it's never been a good option for
server-side rendering stacks. It's one of the reasons on-device rendering is
needed on modern web maps.
Tracestack topo is designed with the same scale and zoom relationship as the
standard layer, assuming 256 device independent pixel tile scales. They produce
`@2x` tiles, i.e. images that are 512px.
I'm not sure how we can reasonably handle a set of layers where some work with
fractional zooms and others don't.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6618#issuecomment-3660085080
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/6618/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
