The information is available at rendering time, so it shouldn't be very difficult. However, I would not want anyone to get their expectations too high. I don't believe that we will ever get 'slippy' map type performance because we handle the pixels one at a time.
I won't be able to work on any code for about 10 days or so, but I'll put it on my list of ideas to work on. ...jerry On Tue, Aug 17, 2010 at 11:35 AM, Tom Hayward <[email protected]> wrote: >> Note that for the USGS topo (UTM projection) map code we did NOT >> reproject the map, instead going for "good enough" map reprojection >> with custom code focusing on speed. The resulting 7.5' quadrangle >> pixels may be off from their true position by a small number of >> meters as a result, but they render very quickly in Xastir. The >> 1:100k and 1:250k maps are not as well positioned, but they're also >> not anywhere near as detailed. > > Ok Jerry, how hard would it be to skip the projection for high > layer-number tiles (the close zoomed-in ones)? I assume the projection > difference is minimal there, so it would be worth a pixel different > for the faster render times. > > Tom > _______________________________________________ > Xastir mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
