Bing image servers messed up googze

[GoogleCodeExporter]

Waze has switched to have Bing aerial images. Googze has stopped working since.

Original issue reported on code.google.com by stefan.n...@gmail.com on 22 Feb 2011 at 6:22

[GoogleCodeExporter]

anyway to fix this ?

Original comment by superkc...@gmail.com on 22 Feb 2011 at 7:28

[GoogleCodeExporter]

Original comment by ryti...@gmail.com on 22 Feb 2011 at 8:43

• Changed state: Started
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I checked it... the main problem is that the bing piles, that is not existing 
in some levels, not loading a filler image (like "no photo available in this 
level"), just an empty file. So, if you want to replace the tile you must solve 
this...

Original comment by wro...@gmail.com on 23 Feb 2011 at 6:45

[GoogleCodeExporter]

Rytis, ive got a working file, created from your work, may I send it to you to 
help the process?

Original comment by wro...@gmail.com on 23 Feb 2011 at 6:49

[GoogleCodeExporter]

Sure.

Original comment by ryti...@gmail.com on 23 Feb 2011 at 7:03

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks, I made it live, but I'd rather convert Bing maps to AGS (x/y/z) so that 
I can implement server-side image stitching (since I don't really want to 
rewrite caching, etc). I found documentation here: 
http://msdn.microsoft.com/en-us/library/bb259689.aspx - but I'm having trouble 
converting quads to x/y/z. The result is quite close, but some digits are 
always off... Calling for help :)

Original comment by ryti...@gmail.com on 23 Feb 2011 at 8:13

[GoogleCodeExporter]

I was thinking at first in BBoxes from roads layer to get x/y/z coordinates 
because it is constant in all zoom levels. Like Your US server try. (The 
quadkey conversation is giving same result with every map replacement: It is 
visible only the same zoom levels where the Bing Maps has a working tile)

Original comment by wro...@gmail.com on 23 Feb 2011 at 9:21

[GoogleCodeExporter]

The satelite function is working again.
When I enable the street overlay I only see blank squares.:-)

Original comment by vdveen.p...@gmail.com on 24 Feb 2011 at 8:05

[GoogleCodeExporter]

Google overlay is working only where Bing maps are available.

Original comment by martin.k...@gmail.com on 24 Feb 2011 at 9:33

[GoogleCodeExporter]

yeah alot of places bing doesn't have maps are close zoom level :(

but good work so far keep it up ^_^

Original comment by superkc...@gmail.com on 24 Feb 2011 at 11:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok, the solution for the Google maps XYZ parameters:

You can use the variables tilex and tiley (from Wazle.js), but You must create 
a new variable for the correct zoom level, which is equal with tilez-8.

Use this parameters, and your script is good as the old one.

Original comment by wro...@gmail.com on 26 Feb 2011 at 9:06

[GoogleCodeExporter]

Original comment by ryti...@gmail.com on 27 Feb 2011 at 6:27

• Changed state: Fixed

[GoogleCodeExporter]

I am struggling with this also, I am getting an image then a few secs later get 
no image with the broken image icon

Original comment by jerrenal...@gmail.com on 28 Feb 2011 at 3:14

[GoogleCodeExporter]

Do a forced refresh (Ctrl+F5 or Shift+F5).

Original comment by ryti...@gmail.com on 28 Feb 2011 at 6:56

[GoogleCodeExporter]

Well, I still have problems with the script.

For most places the script works fine but there are places where it won't show 
any
satellite maps.

Original comment by stefan.n...@gmail.com on 28 Feb 2011 at 7:04

[GoogleCodeExporter]

The new fix works only when the Streets checkbox is on. At least e.g. here: 
http://world.waze.com/cartouche/?zoom=4&lat=49.28971&lon=16.09437&layers=T0FTFFF
FTFFTTTTFFTTTT

Original comment by drajsa...@gmail.com on 28 Feb 2011 at 10:18

[GoogleCodeExporter]

Should be OK now.

Original comment by ryti...@gmail.com on 28 Feb 2011 at 8:23

[GoogleCodeExporter]

One thing to know!

If the googze is not working, set the Cartouche language to English!
And it is working in the www.waze.com/cartouche site, so the US server got 
googze from now!

Original comment by wro...@gmail.com on 28 Feb 2011 at 9:08

[GoogleCodeExporter]

Yes, works perfectly, many thanks!

Original comment by drajsa...@gmail.com on 1 Mar 2011 at 10:21

[GoogleCodeExporter]

Today don´t work googze for me. I see only khaki color in background. 
Yesterday worked correctly :(

Original comment by Libor.An...@gmail.com on 2 Mar 2011 at 9:38

[GoogleCodeExporter]

Correction: when I change language of Cartouche to Deutsch and after that back 
to English then Googze work OK again :D

Original comment by Libor.An...@gmail.com on 2 Mar 2011 at 9:45

[GoogleCodeExporter]

Fixed.

Original comment by ryti...@gmail.com on 2 Mar 2011 at 9:52

[GoogleCodeExporter]

Today I have the same problem as yesterday - only background color is sometimes 
khaki, sometimes dark grey and somtimes I see dark-medium-light grey stripes. 
Change language from English to another language and back to English or check 
streets is not working.
I try it on Win7 and WinXP with Google Chrome 9.0.597.107

Original comment by Libor.An...@gmail.com on 3 Mar 2011 at 6:46

[GoogleCodeExporter]

The problem stems from the fact that Waze once again changed they way its 
tiling works: if they don't have imagery for a specific tile from Bing, it 
won't show up at all, therefore there is nothing for us to replace it with. 
Sadly, without extensive hacking of Waze code there is nothing that we can do 
about this. Sorry.

Original comment by ryti...@gmail.com on 3 Mar 2011 at 6:58

[GoogleCodeExporter]

Too bad. I still have one not refreshed window with the previous cartouche but 
I will have to restart the computer once... With the new cartouche I have 
something only at zoom levels 1 and 2 in quite big portion of area which is 
useless. Let's hope they will change it soon.

Original comment by drajsa...@gmail.com on 9 Mar 2011 at 3:31