Ok I got it working.
I think the problem was I was only copying the encoded string and not
the rest of the stuff. When I copied all the code the map set it
started working.
Thanks for the help
var poly = new GPolygon.fromEncoded({
polylines: [
{ color: "#4d4b4b",
weight: 4,
opacity: 0.8,
points: "c}wbMlgw|`...@ylmg@e~wkjx...@}
`udRrdsqXnihCduxsAv{_yLp_jHrdypNkmhl[fsia@",
levels: "PPPPPPP",
zoomFactor: 2,
numLevels: 18},
{ points:
"wpnbg~qyen...@_xfccdmkpysxissdcshrsdwqjuew{dz~igil_wbs|
bntl{xgwgcic{_g_`ffjdshlnpgmerpc...@jxugeb@kobbgekcqjgrfa...@gbrwoj_ofoso_oko`god@klLobFwgN_}
Iw{Dg|ekdpglceakoybq{kcxcebhgcec}h_mg}kackleynwzv...@s_ssf\\ckgwrkgod}
nFcvD{zKkmI}iVwwFsrVgxB}
z...@s]opncfbmyc_tawvizaasclzj{~inko{zju@kppachasgpa_]...@_ncbnzqcbhaflc}
gb~ohpivvnluebtekbgfrjhue~~wv_c~zestaj_pkllzf...@~cnn`gnwmiycrdnltlvjobbdjik~rdfwew{dvlnvgnxjgmenxjbfbrjfc~ef~xllljaj|
z...@vsc{ffs|gk}akbbs_nz{hv...@skh~vgstabtr@rta...@l}
a...@`fb~rigqcvgv@nkSv_iAzaZvcK}vBfpZ|
z...@ljqb~mipboculbytttn@vbnmikfp...@xteuugabm@e{{EgiLssjAwzGocWk_AqdIvxWy}
wdojvgxjno`gndpanjhffiqzycbrkhrcrasvebyjn~g...@sv@dbdkk^i_...@kwxwvsisfsbtmjmq_xkoh}
af~}p...@nk|b{cefynomcrikfjnvusml...@caqzvmk`mu{dsrqxnb_eu`jzcpvhk^fef}
LgE`hxHnK|fmOgEzfFkmcB?",
levels: "PDFDEP",
color: "#0000ff",
opacity: 0.7,
weight: 3,
numLevels: 18,
zoomFactor: 2}],
fill: true,
color: "#CCCCCC",
opacity: 0.7,
outline: false
});
map.addOverlay(poly);
On Mar 9, 4:36 pm, Rossko <[email protected]> wrote:
> As I
> said,http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/examplePo...
> works. What's different about yours?
>
> The example is available online, so strings can be pasted into
> decoding utilities etc and otherwise inspected.
> Yours aren't, the groups interface may have distorted them. I tried
> reconstructing them, but the inner poly was just a squiggle not a
> closed poly. I guess that's just a mangling, but can't check your
> actual
> string.http://groups.google.com/group/Google-Maps-API/web/why-including-a-li...
>
> The example has identical opacity etc. for both polylines, yours
> doesn't.
>
> But I think this may be the root -
> The example has the outer first, and 'winds' it clockwise.
> The inner comes second, and is wound counterclockwise.
> In yours, both wind the same way, clockwise.
>
> Guru Mike has posted erudite things on winding and holes
> -http://econym.org.uk/gmap/chrome.htm#winding
--
You received this message because you are subscribed to the Google Groups
"Google Maps API" 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-api?hl=en.
