> Hi Koen,
> You might just be hitting a limitation within flash rather than in the
> maps api, I think you're right it's the sprite size and 1K by 1K
> should work and 100K by 100K shouldn't work (4096px * 4096px at max)
> so you could get 1/25th of you're data, the only other option I've
> seen is cutting up the original image and loading pieces of it into
> different bitmap data objects then laying them down next to each other
> using flash (so you could do this making 5 rows and 5 columns out of
> you're image).  Check out the posts herehttp://www.bit-101.com/blog/?p=1426
> about the size limitations in the comments there's some links to
> potential solutions depending on your needs.  Sorry I can't be more
> specific I have run into this problem myself with drawing line's
> between points on the map when I'm zoomed in really far since the
> starting point can be far off screen, I don't get an error but my
> lineTo or curveTo calls end up drawing these huge shapes, it appears
> some sort of estimation that is used in drawing the lines gets wacky
> when it's drawing over a huge distance, so far I've just toggled the
> visibility off when the zoom level is high which is sort of ok because
> you can't see where the line is going to if you're zoomed in that far
> anyways, but obviously its not ideal.  Also I don't have anything on
> the additions to GroundOverlay, was this working for you at some
> point, seems strange if it was?  Only way I could see this working is
> because you're loading the image rather than calling the constructor
> on a bitmapData with a size larger than 4096x4096 which I've heard is
> a hack to get around the limitation.
> Good luck,
> Shaun

> On Sep 27, 5:26 am, Koen M <rockinf...@gmail.com> wrote:

> > Hi all,

> > I was working on our fietsnet.be project today, and unfortunately I
> > did not manage to upgrade that app from Google Maps flash api 1.9 to
> > 1.16

> > The error occurs in a custom GroundOverlay object, to display a 100K
> > by 100K pixel sprite object as overlay. Apparently the dimension of
> > the sprite is the problem, as reducing it to say 1K by 1K solves it.

> > Unfortunately, reducing the dimension is not an option for us. The
> > sprite is our base container for bicycle track networks in a large
> > geographic area, and we noticed polylines are not accurately
> > positioned in Flash beyond two decimal digits. By going from 100K to
> > 1K we'd lose a hundredfold in positional accuracy; this would be
> > become strongly visible when zooming in.

> > I understand that in api 1.11, GroundOverlay was adapted a bit to to
> > accommodate for 3D viewing. Apart from setting
> > GroundOverlayOptions::renderContent=false, are there additional things
> > I should know to make this approach work again?

> > Thanks heaps,

> > Koen | fietsnet.be- Hide quoted text -

> - Show quoted text -