Hi, Ævar Arnfjörð Bjarmason wrote: > Evidently yes, I went there after all and this is a blog posting about > some of the progress we've been making: > http://openstreetmap.org/user/%C3%86var%20Arnfj%C3%B6r%C3%B0%20Bjarmason/diary/5800
Comments on that blog entry: 1. MapOf is t...@h only but could trivially be changed. 2. Depending on the reason why you want stitched images: If you want to freeze the current map display then of course you need a stitched image and save that. If your only reason is avoiding JavaScript dependency, then it might be possible to achieve a proper map display by statically combining tiles and using CSS to adjust the viewport. Results would then be identical to a stitched image where CSS is supported, and on non-CSS viewers the map would be up to 510 pixels (worst case) larger in each direction because viewport adjustment doesn't work. 3. Slippymap technology and Mapnik would allow reducing the tile size to, say, 64x64 pixel if desired. Resulting in a much higher amount of HTTP requests, but being able to adjust the map size in 64-pixel steps only would perhaps be acceptable so you could work with full tiles throughout, never stitching or cutting a tile. 4. Bigmap has two aspects, one is combining tiles into a map display using HTML tables (no JS), the other is a Perl script that downloads tiles and combines them into a large PNG. It could trivially be converted to a CGI but what you want would probably be something that runs on the machine with the local tile storage rather than accessing tiles via the web, essentially what 5. Custom on-demand rendering will work if there's a good caching layer in front of it. Bye Frederik _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
