Thanks, I see the poly wrapping issue. I'll take a look. On Sat, Mar 13, 2010 at 1:43 AM, Brak <[email protected]> wrote:
> For reference, here's the related external issue ticket: > http://code.google.com/p/gmaps-api-issues/issues/detail?id=2230 > > I've also noticed a new issue that I don't believe is fixable from the > outside, but I could certainly be wrong. I had actually assumed that > it would correct itself after I remapped my points/polygons to the new > coordinate system, but that proved to be naive and not based on fact. > Well, the Markers fit well with the new coordinate system, but the > polygons seem to repeat without respect to the (now larger, scaled up) > projection. I assume this is because they are tied to the tile > overlay, which is sort of directly bound to the original Google Map > tiles. The funny thing is that they accept the new projection's > coordinates and draw properly, they just repeat when the world tile > would have repeated had the projection not been there at all > (basically they are tied to live inside that 256x256 0,0 at zoom level > 0 box that the whole world fits in on a standard map. > > I've included 2 links to help explain my issue. The first is a live > working example, but it's in an almost production environment, so > there's a lot of other stuff going on (which I believe is irrelevant, > but should be stated none the less). You have to switch to Satelite > then back to a floor map, then you can drag the marker around to see > the actual coordinates, and see that the points where the repeating > polygons are, are in fact incorrect or as I've been calling them, > ghost polygons. > > http://library.ucf.edu/Administration/Maps/Default_unpublished.asp?develop=1 > > The second is a PDF file I drew to illustrate the point more clearly. > It should explain more clearly (possibly more clearly than all the > above text). > > http://library.ucf.edu/testing/Systems/Library_Maps_Google/GoogleCustomProjectionBug.pdf > > Does this make sense? I hope I explained it properly. > Thanks. > > On Mar 11, 4:28 pm, Ben Appleton <[email protected]> wrote: > > Yes, that will let you track progress. We'll link the internal bug to > the > > external issue tracker item. > > > > On 12 Mar 2010 04:10, "Brak" <[email protected]> wrote: > > > > Should I create an issue ticket in the official bug tracker? > http://code.google.com/p/gmaps-api-issues/ > > > > On Mar 10, 6:46 pm, Ben Appleton <[email protected]> wrote: > > > > > Thanks, that's very helpful. This ... > > > On Thu, Mar 11, 2010 at 3:34 AM, Brak <[email protected]> wrote: > > > > I've got my simple exam... > > > > > http://library.ucf.edu/testing/Systems/Library_Maps_Google/Projection... > > > > > > Does this look like a my-code problem or a more general API issue? > > > > Dun dun dunnnnn! > > > > > > ... > > > ... > > > > > read more ยป > > > > -- > > You received this message because you are subscribed to the Google > Groups... > > -- > 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.
