Timeline for OSM Python Utils: Modifying generate_tiles.py to create 512 x 512 tiles?
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:33 | history | edited | CommunityBot |
replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
|
|
Dec 22, 2012 at 1:12 | comment | added | elrobis | @BradHards thanks for taking an interest. We (me and another fella at my company) formerly used 256x tiles in our stuff, but we found---in our case---512 creates a better UX. I realize alot of queries on this subject suggest 256x creates a better user experience, but this wasn't the outcome of our experimentats. Maybe our server is slow, but our product, for enterpise clients (not the general public using smart phones), uses a full-screen map viewport. So that said, all of our existing sites use 512x, and I want to stay true to 512x tiles when we deploy the OSM data. | |
Dec 22, 2012 at 0:25 | comment | added | BradHards | Maybe you can explain why you are trying to make bigger tiles - that might allow people to come up with better solutions to the real problem you are trying to solve. | |
Dec 22, 2012 at 0:24 | comment | added | BradHards | There is an implicit assumption that a particular zoom level covers a particular cartesian area in most tools. See wiki.openstreetmap.org/wiki/Zoom_levels. Consider what the output at zoom level 0 should look like. | |
Dec 21, 2012 at 18:30 | history | edited | elrobis | CC BY-SA 3.0 |
Following a 2nd test run, I had more info for the post; also included some image samples.
|
Dec 21, 2012 at 6:36 | answer | added | AndreJ | timeline score: 2 | |
Dec 21, 2012 at 4:28 | answer | added | om_henners | timeline score: 1 | |
Dec 20, 2012 at 16:36 | history | asked | elrobis | CC BY-SA 3.0 |