actual size of pixel button

falkamelung commented 5 years ago

We stopped with this issue without coming to a conclusion. I have to refresh my memory, but I think the status was:

in zoomed-in state: make pixel a bit smaller so that there is no overlap between pixels (use real radius) What we did was to use a radius ~30% larger to avoid the white spaces in the corners. I came to the conclusion that white area in corners is better than overlap.
in zoomed-out state: The problem was that the specified scaling of pixel size does not work because not all pixels are shown. So we should hardwire a radius in depending on zoom state. You said you have no information on how many pixels are rendered in a given state. Then lets do trail and error (only for zoomed-out state).

The main limitation was that mapbox currently does not support square pixel. Maybe you can raise this as an enhancement request with them?

falkamelung commented 4 years ago

This never worked as well as I hoped. I wonder whether we can do anything about it. If not we should settle on what we have and document this as a known shortcoming.

falkamelung commented 2 years ago

completed

geodesymiami / insarmaps

actual size of pixel button #4