Thanks for the very clear answer.
On a slightly related issue, can the geometry library be loaded
asynchronously on demand? The documentation
http://code.google.com/apis/maps/documentation/javascript/basics.html#Async
shows how to load the entire API asynchronously, but it might be
useful to load the main part of the API all the time, with the
geometry library loaded only when needed.
My attempts to do this by building a script dynamically (like the
loadScript function in the documentation, but without the callback to
initialize) have not worked.
For what it is worth, the geometry library seems to load pretty
quickly anyway, but better minds than mine thought it useful to place
it in a separate library to improve performance.
- Jeff
On Jan 17, 12:04 am, Ben Appleton <
apple...@google.com> wrote:
> Hi Jeff,
>
> It seems you've hit your browser's URL length limit. We send the
> (compressed) path and the number of samples to the server for subsampling.
> In your case it sounds like the path is too long even after compression.
>
> You'll need to simplify, subsample or split your path as you suggest. You
> may find the google.maps.geometry library useful for this.
>
> Good luck!
> Ben
>
google-maps-js-a...@googlegroups.com<google-maps-js-api-v3%2B
unsub...@googlegroups.com>
> .> For more options, visit this group at
>
>
http://groups.google.com/group/google-maps-js-api-v3?hl=en.
>
>
>
>
>
>
>
>