For what it's worth, even when fully escaped that URL only amounts to 520 bytes:
http://mt1.google.com/vt/lyr...@130&src=api&hl=en-US&apistyle=s.t:5%7Cp.h:%23ff8000%7Cp.s:49%7Cp.l:60,s.t:82%7Cp.s:-30%7Cp.h:%236eff00%7Cp.l:-5,s.t:82%7Cs.e:l%7Cp.s:-30%7Cp.h:%236eff00%7Cp.l:-20,s.t:3%7Cs.e:g%7Cp.h:%23ff8800%7Cp.s:-69,s.t:3%7Cs.e:l%7Cp.h:%23ff8800%7Cp.s:-69,s.t:2%7Cs.e:g%7Cp.h:%23ff8800,s.t:33%7Cp.h:%23ff3c00%7Cp.l:-17%7Cp.s:9,s.t:40%7Cs.e:g%7Cp.h:%2333ff00%7Cp.l:30,s.t:65%7Cs.e:g%7Cp.s:80%7Cp.h:%23ff9100,s.t:6%7Cp.h:%230099ff%7Cp.l:40%7Cp.s:25,s.t:1%7Cp.h:%23ff2200%7Cp.s:50&x=4149&y=2818&z=13&s=G<http://mt1.google.com/vt/http:%E2%80%8B/%E2%80%8B/%E2%80%8Bmt1.google.com/%E2%80%8Bvt/%e2%80%8blyr...@130&src=api&hl=en-US&apistyle=s.t:%E2%80%8B5%7Cp.h:%E2%80%8B%23ff8000%7Cp.s:%E2%80%8B49%7Cp.l:%E2%80%8B60,s.t:%E2%80%8B82%7Cp.s:%E2%80%8B-30%7Cp.h:%E2%80%8B%236eff00%7Cp.l:%E2%80%8B-5,s.t:%E2%80%8B82%7Cs.e:%E2%80%8Bl%7Cp.s:%E2%80%8B-30%7Cp.h:%E2%80%8B%236eff00%7Cp.l:%E2%80%8B-20,s.t:%E2%80%8B3%7Cs.e:%E2%80%8Bg%7Cp.h:%E2%80%8B%23ff8800%7Cp.s:%E2%80%8B-69,s.t:%E2%80%8B3%7Cs.e:%E2%80%8Bl%7Cp.h:%E2%80%8B%23ff8800%7Cp.s:%E2%80%8B-69,s.t:%E2%80%8B2%7Cs.e:%E2%80%8Bg%7Cp.h:%E2%80%8B%23ff8800,s.t:%E2%80%8B33%7Cp.h:%E2%80%8B%23ff3c00%7Cp.l:%E2%80%8B-17%7Cp.s:%E2%80%8B9,s.t:%E2%80%8B40%7Cs.e:%E2%80%8Bg%7Cp.h:%E2%80%8B%2333ff00%7Cp.l:%E2%80%8B30,s.t:%E2%80%8B65%7Cs.e:%E2%80%8Bg%7Cp.s:%E2%80%8B80%7Cp.h:%E2%80%8B%23ff9100,s.t:%E2%80%8B6%7Cp.h:%E2%80%8B%230099ff%7Cp.l:%E2%80%8B40%7Cp.s:%E2%80%8B25,s.t:%E2%80%8B1%7Cp.h:%E2%80%8B%23ff2200%7Cp.s:%E2%80%8B50&x=4149&y=2818&z=13&s=G> It would be interesting to test the maximum length of a working URL for your 3G network. I suggest you contact them about this; the more reports they receive the faster they'll fix it. Note too: goo.gl, bit.ly and other URL shortening services just redirect your browser to the full URL. So I don't think they will work around your carrier's URL length problem? - Ben On Sun, Aug 22, 2010 at 2:50 PM, Sefu <[email protected]> wrote: > Thanks again, William. > > Both URL's seem to be working - perhaps it is the excessive length > that is being blocked by (my) carrier(s)? > > On Aug 22, 4:16 am, William <[email protected]> wrote: > > another thing to check is whether it's just the length of the url, or > > something about the characters in styled map url, so you could try the > > following url which is less than the 160 characters (sms) and 140 > > character (tweet) that limit mobile communications. But packet length > > limits in the physical network layers shouldn't affect the abstract > > Internet Protocol layer?? > > > > Styled URL: > http://mt0.google.com/vt/lyr...@130&src=api&hl=en-GB&apistyle=p.v:off...p.v:on,s.t:6|p.v:on&x=126&y=93&z=8&s=Galileo > > > > Regular Map Tile URL: > http://mt0.google.com/vt/lyr...@130&src=api&hl=en-GB&x=126&y=93&z=8&s... > > > > ... > > -- > 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]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
