Quote Originally Posted by SixDegrees View Post
This problem is often handled by implementing a tile server. In the simplest form, you have a map at fairly high resolution that is accessed as an array of tiles. The tiles can vary in size, and in many cases can be precomputed, but your client program determines the center and extent of the view and the server figures out which tiles are required to fill in the resulting rectangle. Tile position can be handled in a number of ways, but is often embedded in the filename.
That's exactly how my widget works. Thus handling wrapping is as simple as bounding the coordinates and mapping them to proper tiles. Since zooming works by replacing one tile with four other tiles Graphics View doesn't help much here. There is a map API in QtMobility that is based on Graphics View and you can implement your own tile content-provider for it but IMHO it's a bit of an overkill. Still it might be easier in terms of software development to implement a tile provider for a solution that already exists instead of trying to implement your own that works in a similar way.