Going (sort of) along with neavilag's question, what is the real
benefit to using the GroundOverlay class vs. making a custom overlay?
(Or is it simply that GroundOverlay is a special "instance" of a
custom overlay that has a bunch of predefined stuff already set?)


On May 8, 8:11 am, neavilag <[email protected]> wrote:
> Hi, this is great, in the case of GroundOverlays is it possible to put
> the map data (street names, places above ) or set a transparency to
> the image
>
> thanks
>
> On May 7, 9:24 pm, Daniels Lee™ <[email protected]> wrote:
>
>
>
> > We're very excited to announce another recent release of a new version of
> > the API.  This release contains a handful of great new features for you to
> > utilize.  Check them out below!
>
> > KML and Geo RSS 
> > Layers:http://code.google.com/apis/maps/documentation/v3/overlays.html#KMLLa...
>
> > Ground 
> > Overlays:http://code.google.com/apis/maps/documentation/v3/overlays.html#Groun...
>
> > Traffic and Bicycling 
> > Layers:http://code.google.com/apis/maps/documentation/v3/overlays.html#Traff...
>
> > ====
>
> > See the full list of changes 
> > below:http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIv3Cha...
>
> > Changed issues:
> > - Issue 1458: Feature request: KML support in Google API v3
> > - Issue 1658: Add Traffic Overlay
> > - Issue 2209: Stack overflow
> > - Issue 2254: Multiple calls "setMap(gMap)" and "setMap(null)" on Circle
> > object changes it's stroke and fill opacity
>
> > Noticeable changes:
> > - Added KML and GeoRSS Layers
> > - Added Ground Overlays
> > - Added new layers: Traffic and Bicycling
> > - Added "suppressBicyclingLayer" property against DirectionsRendererOptions
> > - Fixed bug to ensure zoom layer is correctly referenced when MapType
> > changes
> > - Renamed DirectionsResult property "start/end_point" to
> > "start/end_location"
> > - Renamed DirectionsLeg property "start/end_geocode" with
> > "start/end_address"
> > - Renamed DirectionsRoute "optimized_waypoint_order" property with
> > "waypoint_order"
> > - Removed support for old directions property names (setTripIndex,
> > getTripIndex, hideTripList, provideTripAlternatives)
> > - Updated GeocoderGeometry.latLng to GeocoderGeometry.location
>
> > Please test and provide feedback!
>
> > --
> > 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 
> > athttp://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 
> athttp://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.

Reply via email to