"I think the carrier might be seeing the unsafe characters in the Styled url (such as the pipe | character) and then encoding the url, which has the effect of double encoding the # (already encoded as %23, which would then become %2523)"
...that makes perfect sense, and that is no doubt the source of the problem exactly. But who to send it to: carrier or Google? On Aug 22, 10:39 am, Sefu <[email protected]> wrote: > Boy, that may have seemed arrogant of me - was just poking fun at the > fact that we saw the same thing at the same time. I'd still be lost in > the details were it not for your insight - thanks a million! > > That problem out of the way, the lack of a "#" character causes other > minor problems elsewhere - transit lines, for example, refuse to be > anything but red when there is a "hue" option present - I even tried > indicating "blue" or "orange" (which worked in earlier experiments), > but rail lines remain stubbornly bright red - I think this concerns > any hue (hex or named) beginning with an alphabetical character (eg > "orange" or "ff9900"). > > In all, would you think this a problem worthy of announcing to Google, > or should I forward it to my carrier? I am certain that the problem > was the same across three carriers here (SFR, Orange, Virgin) - > perhaps they all are using the same 3g network distributor. > > Thanks again, Cheers, > > Sefu. > > On Aug 22, 9:45 am, Sefu <[email protected]> wrote: > > > > > Thanks, William - Great minds think alike, it seems ; ) > > > On Aug 22, 9:43 am, Sefu <[email protected]> wrote: > > > > Om(f)g. > > > > I found it. A simple, stupid error that still may/may not have > > > something to do with my carrier. > > > > I noticed that in your custom map, William, you used only a single > > > 'visible' style option - so I reduced my styles to a single (multiple > > > option) one and started eliminating the options one by one. When I > > > eliminated the "hue" option the map started working - so I replaced > > > it, but this time eliminating the "#" symbol from the hex colour code. > > > The map started working. I then replaced all my styles, but removed > > > the "#" from all of them - and the map still worked. > > > > This is odd because the "#" is present in the hue colour code in both > > > the Google Maps v3 documentation and the Styled Map Wizard (http:// > > > gmaps-samples-v3.googlecode.com/svn/trunk/styledmaps/wizard/ > > > index.html)... but again, this "#" problem may only concern my > > > carrier. > > > > One side effect - when I eliminated the "#", all my orange hues > > > changed to red... and there may be some other colour changes too. > > > > On Aug 22, 9:09 am, Sefu <[email protected]> wrote: > > > > > Yet, William, your map is working in my iphone! > > > > > All I can do is compare the tile request > > > > URL's...http://mt1.google.com/vt/lyr...@130&src=api&hl=en-US&apistyle=s.t:1|p.h:%23ff2200|p.s:50&x=4145&y=2819&z=13&s=Galile > > > > ... > > > > minehttp://mt1.google.com/vt/lyr...@130&src=api&hl=en-US&apistyle=p.v:off... > > > > ... william's > > > > > ...??? > > > > > When I replace my styles with yours (taken from the page source), > > > > william, my map will load in iPhone Safari. > > > > > (scratching head) > > > > > On Aug 22, 8:58 am, Sefu <[email protected]> wrote: > > > > > > Er, wow. > > > > > > I trunciated my styles progressively until there was only one style > > > > > left remaining... and the map as a whole STILL refused to load. Yet > > > > > tiles will load individually: > > > > > >http://mt1.google.com/vt/lyr...@130&src=api&hl=en-US&apistyle=s.t:1|p.h:%23ff2200|p.s:50&x=4145&y=2819&z=13&s=Galile > > > > > > I then stripped ALL styles, and the map suddenly started loading. > > > > > > The only logical source of the problem I can think of is some sort of > > > > > faulty (outdated) compression algorithm used by France's carriers... > > > > > individual image requests to a given domain are not compressed, but > > > > > multiple requests to the same domain are - resulting in corrupted > > > > > url's. If only the iPhone Safari had the 'Activity' window present in > > > > > their mac-based app, I could really see what's going on... > > > > > > On Aug 22, 8:35 am, Sefu <[email protected]> wrote: > > > > > > > There doesn't seem to be any iPhone web debugging app out there.... > > > > > > Your map is working fine, thanks. I'm going to start 'cutting' > > > > > > styles > > > > > > from mine and see what happens. > > > > > > > On Aug 22, 8:17 am, William <[email protected]> wrote: > > > > > > > > On Aug 22, 4:06 pm, Sefu <[email protected]> wrote: > > > > > > > > > If I don't find a suitable iPhone webapp debugging tool, the > > > > > > > > only > > > > > > > > other thing I can do is make a series of progressively > > > > > > > > less-stylised > > > > > > > > maps to find out what the carrier will or will not load. > > > > > > > > I don't know any iPhone debugging tools, but the minimal styled > > > > > > > example I tried before was only administrative features: > > > > > > > >http://www.william-map.com/20100822/1/admin.htm > > > > > > > > ... -- 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.
