Closed uap-universe closed 12 years ago
Please try with latest head and reopen if still an issue.
Compare this with a split_base of 256 and this with a split_base of 512. The map center is calculated wrong.
In the wrong version the map center is near lat=-3.372803&lng=-39.237671.
My initial guess that the filenames are wrong and therefore there is a HTTP404 is not correct. I simply did not find the map, because it is offset.
Since 1.7 zoom parameters can be passed by command line parameters (-z and -b).
But -b doesn't seem to be working. If I select another base (e.g. 512) the images are rendered correctly. But the google-maps API seems to be referring to the image filenames as if there were rendered with the default base (256).
The result ist, that no map is shown in the browser because the tiles cannot be found (HTTP 404).
I tried to analyze the scripts and i think there is some information missing that must be passed to the libc10t.google.js so that the google-api knows the base tile size is not 256 and it has to look for other filenames.
Linux x64: version: git 43336eb, built on Mar 21 2011