On Aug 4, 12:56 pm, weekend <
mehin...@gmail.com> wrote:
> Thought so. The KML is a great way to store 1,000 of maps though since the
> coords and PNG reference are in there. You think I should be working to
> import Bounds data and PNG file name data from a KML?
That is really up to you, and really depends on your data source and
your tools.
If you have a tool that creates the kml/kmz for you that might be
simpler and it is a "standard".
But if your tools provide the bounds and the images in a way that lets
you easily create the native map elements, that might be better as you
won't depend on a third party library (geoxml3) which you don't
control or Google's kml parser on google's servers which occasionally
breaks, and which we have no insight into (doesn't correspond to API
releases, seems to be shared by Google Maps, and both Google Maps
APIs).
I guess you can't get away from ProjectedOverlay though.
Others may have better insight into the advantages and disadvantages
of kml vs other options.
-- Larry