I took a look at your application, and it's quite large.

Can you reply back with specific steps to reproduce this?  For example, do I
need to search a specific zip code?

Are you geocoding all 122 points on the map?

On Mon, Feb 8, 2010 at 10:58 AM, Saxan Sartar <[email protected]>wrote:

> I have a page that currently prints 122 points on the map from your
> geocoder services.
>
> But after this change, only 1 point is shown.
>
> http://domino.bnsf.com/website/premtransloader.nsf/SBDest?Open
>
> If I throw an alert in my drawMarkers() function
>
> alert(jsonObj.Mappables.length); --> I get 2 of the 122 markers, instead of
> 1.
>
> The functions are defined in transearch.js (found in the same relative
> path).
>
> Prior to the new release, this was not happening. I am looking into it, and
> also wanted to share with you.
>
> -Tim
>
>
> On Mon, Feb 8, 2010 at 12:49 PM, Daniel Lee <[email protected]> wrote:
>
>> We've recently pushed out a new version of the API.  See the list of
>> changes below:
>>
>> http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIv3Changelog
>>
>> Changed issues:
>> - Issue 2135: Bug: If you reuse a Polygon's MVCArray in a Polyline,
>> the Polyline is closed.
>>
>> Noticeable changes:
>> - Added new Rectangle class:
>>
>> http://code.google.com/apis/maps/documentation/v3/reference.html#Rectangle
>> - Added new Circle class:
>>  http://code.google.com/apis/maps/documentation/v3/reference.html#Circle
>> - Fixed memory leak when creating then removing a marker.
>> - Stopped annotating the MVCArray of LatLngs to close Polygons, as
>> that causes Polylines which share the same MVCArray to be closed too
>> (see Issue 2135 above)
>> - Fixed a bug which sometimes hid onscreen markers if the map's zoom
>> was set to its current value.
>> - Fixed ImageMapType to display correctly on Android.
>> - Changed the polygon clipping scheme to allow polygons which contain
>> the north or south pole.
>> - Increased the latitude range of MercatorProjection to the maximum
>> possible subject to floating point precision.
>>
>>
>> Please test and provide feedback.
>>
>> Thanks!
>>
>> Dann
>>
>> --
>> 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.
>



-- 
Daniel Lee
Developer Programs Engineer
Google, Inc.
345 Spear Street
San Francisco, CA 94105
650 253 0967

-- 
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