On Wed, Jun 9, 2010 at 13:34, Curt, WE7U <[email protected]> wrote: > I saw that once and then ran out of time trying to duplicate it > (couldn't at that time). The new code tweaks Xastir's zoom levels > to match the map instead of the other way around, so that's likely > most of the issues we're seeing. Hopefully that will be tweaked and > we'll have precise georeferencing then, better than Tigermaps could > deliver (due to their weird projection).
I can reproduce it by loading a Map Bookmark set to level 512. The APRS layer is zoomed to 512, but the OSM layer is not. > Rendered by a server, similar to how Tigermaps were done. Ok, this makes sense as to why the standard xastir map caching is used. I assumed [incorrectly] that it was loading tiles, for which the normal xastir caching wouldn't be well suited. The server-render explains the latency. I've installed map caching now and it's much faster where it can take advantage of the cache. Tom KD7LXL _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
