Just to clarify, longitudes by definition wrap at +/- 180 degrees, but in v3 the tile space does not wrap. Which wrapping do you mean?
On Mon, Feb 22, 2010 at 9:43 AM, Yonas Sahlemariam Haile < [email protected]> wrote: > Is there any way in Gmap V3 to stop the tilespace wrapping about longitude, > there was a method, projection.prototype.getWrapWidth(zoom) in Gmap V2 . if > this method returns infinity the map overlays won't repeat. i need the map > overlays stop wrapping horizontally on euclidean projection i made, i hope > there is obvious way of handling this but i couldn't figure it out. thanks > in advance for your help... > > projection.prototype.getBounds > > > On Mon, Feb 22, 2010 at 7:08 AM, Philip <[email protected] > > wrote: > >> I thought of using an OverlayView, but the hassle of maintaining the >> tile lists seemed too much like hard work. As I look at it, the >> difference between a MapType and an OverlayView is that the former >> deals with the tile mapping onto the screen and which tiles are >> required. The latter allows irregular tiles, and is good for small >> objects that have limited bounds. >> >> Philip >> >> On Feb 21, 9:44 am, bratliff <[email protected]> wrote: >> > On Feb 20, 5:10 pm, Philip <[email protected]> wrote: >> > >> > >> > >> > > I finally wrote my own MercatorProjection, but I suspect that the V3 >> > > code doesn't use it. >> > >> > > To see a demo of the resulting day/night shading on a map see: >> > >> > >http://pskreporter.info/grid/test.html >> > >> > > Note that the shading is calculated locally and is for the current >> > > time (and auto-updates -- currently every 10 seconds for demo >> > > purposes, but in real life, probably once per minute). Unfortunately, >> > > it doesn't work in IE owing to the lack of a canvas object. The >> > > explorer canvas project doesn't help as they don't support one of the >> > > canvas methods that I need. Anyway, it works in a modern firefox and >> > > chrome. >> > >> > > No image tiles were used! >> > >> > > Philip >> > >> > You might consider a simple OverlayView to improve performance. You >> > can manipulate all tiles in a single "idle" event rather than one >> > event occurance per tile. You can also reposition existing "out of >> > view" tiles rather than acquire / release tiles through the API. In >> > my experience, the only useful information provided by "getProjection" >> > is the x offset & y offset to translate from world coordinates to >> > container coordinates. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Maps JavaScript API v3" group. >> To post to this group, send email to >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-maps-js-api-v3%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-maps-js-api-v3?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
