Timeline for Calculating Mercator d3 scaling to match Leaflet zoom level
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2018 at 21:40 | vote | accept | Yuri Astrakhan | ||
| Jan 8, 2018 at 2:50 | history | edited | Andrew Reid | CC BY-SA 3.0 |
added 219 characters in body
|
| Jan 8, 2018 at 2:44 | comment | added | Andrew Reid | @Yurik, my bad, I missed this comment, have updated the answer with an explanation of this method as well. | |
| Jan 8, 2018 at 2:44 | history | edited | Andrew Reid | CC BY-SA 3.0 |
added 1404 characters in body
|
| Jun 19, 2017 at 20:47 | comment | added | Yuri Astrakhan | Andrew, if the formula works, do you mind adding it at the beginning, just so that if anyone looks for a simple way, they can use it? | |
| Jun 19, 2017 at 19:11 | comment | added | Andrew Reid | Yeah, as soon as I posted I figured that the zoom level and the scale might be able to be linked nicely - after all doubling the scale quadruples the size of the map, same as zoom level. However, given the non-conforming nature of the web mercator, the bbox approach might offer a closer fit, but, areas near the poles or small scales/zoom levels may still cause grief either way. | |
| Jun 19, 2017 at 1:54 | history | edited | Andrew Reid | CC BY-SA 3.0 |
added 1 character in body
|
| Jun 19, 2017 at 1:37 | comment | added | Yuri Astrakhan |
thank you for an amazing reply!!! I arrived at this formula myself, but it seems it might not be 100% correct (even though I did try it and it seems to be matching almost perfectly, so there must be something I'm missing: 256 * Math.pow(2, zoom) / 2 / Math.PI
|
|
| Jun 19, 2017 at 1:33 | history | answered | Andrew Reid | CC BY-SA 3.0 |