On May 6, 9:05 am, NEW_WORLD_ORDER_PIGS <[email protected]> wrote: > Larry, > > Once again you are correct. This is odd though since I did try to set > it to a lower value (I think 12 was the lowest value though) and it > still didn't work-- if I set it to 2 and use v=2 it now works. Just > as a warning to people though, I was using 32 and it worked with 2.140 > and doesn't with anything later. That really is something.
http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/description.html + The zoomFactor property indicates the difference in magnification between zoom + levels for the polyline. If our encoded polyline has 9 zoom levels and our map + has 18 zoom levels with a magnification factor of 2 between levels (again, like + a G_NORMAL_MAP), then it would make sense to set the zoom level of the polyline + to 4. What did you expect to happen for a zoomFactor of 32? -- Larry > > Thank you once again, > NWOP. > > On May 5, 10:44 pm, "[email protected]" <[email protected]> > wrote: > > > On May 5, 9:33 pm, "[email protected]" <[email protected]> > > wrote:> On May 5, 4:43 pm, NEW_WORLD_ORDER_PIGS > > > > <[email protected]> wrote: > > > > Yes, I was aware of that but that does give me/us some breathing > > > > space. I'd still like to know what has changed in the API and what I > > > > need to do to make our site work with a later version. Perhaps > > > > someone from google can comment on this for both our sake's. > > > > I think your problem is the zoomFactor: 32... > > > > I usually see it set to 2. > > > From Mark McClures encoder: > > > zoomFactor: 2, > > > numLevels: 18 > > > Here is your polyline reencoded by Mark McClure's Polyline > > Encoder:http://www.geocodezip.com/testEncodedPolylinesB.html > > > Here is it with just the zoomFactor changed to > > 32:http://www.geocodezip.com/testEncodedPolylinesB_32.html > > > -- Larry > > > > > On May 5, 5:38 pm, "[email protected]" <[email protected]> > > > > wrote: > > > > > > On May 5, 4:19 pm, NEW_WORLD_ORDER_PIGS > > > > > > <[email protected]> wrote: > > > > > > Larry, > > > > > > > Thank you for looking at this-- if I change the v=2 to v=2.118 it > > > > > > suddenly works. Thank you, thank you, thank you. I tried > > > > > > hard-coding > > > > > > old versions before but it didn't seem to work-- in fact, using 2.s > > > > > > doesn't work either. After all this... I would still like to know > > > > > > what changed in the API and what I need to do to use the later > > > > > > versions to get this to work. > > > > > > Before you get too excited. See this > > > > > thread:http://groups.google.com/group/Google-Maps-API/browse_frm/thread/f347... > > > > > > V2.118 will be deprecated on July 1... (sorry, remembered after I saw > > > > > your post that it worked) > > > > > > -- Larry > > > > > > > Thanks again Larry and Ross-- I kid you not, I appreciate your > > > > > > efforts. > > > > > > NWOP. > > > > > > > On May 5, 4:57 pm, "[email protected]" <[email protected]> > > > > > > wrote: > > > > > > > > On May 5, 3:17 pm, NEW_WORLD_ORDER_PIGS > > > > > > > > <[email protected]> wrote: > > > > > > > > Ross, thank you for taking a look-- I really appreciate it. In > > > > > > > > testing I've hard-coded the color and it doesn't make any > > > > > > > > difference. > > > > > > > > The javascript error is actually part of the masterpage and has > > > > > > > > no > > > > > > > > effect on the map functionality (I've verified this by using a > > > > > > > > different master page in testing). I've looked at most of the > > > > > > > > easy > > > > > > > > stuff and the script ends up in the API and often in a function > > > > > > > > called > > > > > > > > "WO"-- I don't know if that is significant or not. I've also > > > > > > > > tried > > > > > > > > grossly simplifying the linestring to just 2 points and it > > > > > > > > still hangs > > > > > > > > up. This entire problem started a month ago and when I changed > > > > > > > > the v= > > > > > > > > string from v=2.x to v=2 it the website worked for about 1 week > > > > > > > > and > > > > > > > > started failing again-- with no changes whatsoever to the > > > > > > > > website. > > > > > > > > I've since used v=2.s and hard-coded versions prior to April > > > > > > > > and it > > > > > > > > doesn't seem to matter-- I am really at a loss and have traced > > > > > > > > this > > > > > > > > over and over again only to find that there is an infinite loop > > > > > > > > in the > > > > > > > > API going on. > > > > > > > > V2.118 seems to work for me. I seem to recall problems with > > > > > > > polylines > > > > > > > after 2.118, I don't remember where they were fixed. A quick > > > > > > > sampling > > > > > > > (v2.142, v2.151) don't work. > > > > > > > > Have you tried using "normal" unencoded polylines? > > > > > > > > -- Larry > > > > > > > > > I would like to know what part of the api this is > > > > > > > > happening in but I'm going to bet it is part of the line > > > > > > > > rendering > > > > > > > > code since I've verified everything else works. > > > > > > > > > Thanks again Ross, NWOP. > > > > > > > > > On May 5, 3:58 pm, Rossko <[email protected]> wrote: > > > > > > > > > > In your setLineString() code, there is - > > > > > > > > > var overlay = GPolyline.fromEncoded({ > > > > > > > > > color: statusColors[feature.properties.Status], > > > > > > > > > but there's no 'Status' in the JSON for the line. > > > > > > > > > No idea if setting color to 'undefined'' messes up polys like > > > > > > > > > this, > > > > > > > > > but it can't help? > > > > > > > > > > There's still a flash-related javascript error on page load. > > > > > > > > > > cheers, Ross K- Hide quoted text - > > > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > > - Show quoted text -- Hide quoted text - > > > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
