Just to give you an idea of what the Mars, Moon and Sky maps look like
under the API.

http://econym.googlepages.com/marshack.htm
http://econym.googlepages.com/moonhack.htm
http://econym.googlepages.com/skyhack.htm

Note that it's not a good idea to hack the Google code like this. It's
nasty, inefficient and unpredictable. Much better to wait for the API
loader to switch on the _mF[41] flag.

[I would have written this as a reply in my previous thread, but my
messages are taking many hours to appear at the moment, and I only
started that thread 4 hours and 6 minutes ago.]

--
http://econym.googlepages.com/index.htm
The Blackpool Community Church Javascript Team

Here's a funny thing. The sky map appears to be back to front. It's what
you'd see if you were looking down on the sky from outside.

--
http://econym.googlepages.com/index.htm
The Blackpool Community Church Javascript Team

That's probably a spill over from Google Earth, where Sky appears to
be implemented as though you on the inside of 'Earth', so you looking
out at the back of the tiles on the Earth surface. Doesn't help with
working with the tiles in Maps thou ;)

On Dec 10, 2007 7:00 PM, Mike Williams <nos...@econym.demon.co.uk> wrote:

--
Barry

- www.nearby.org.uk - www.geograph.org.uk -

Here's a good link in regards to the sky tiles:
http://csep10.phys.utk.edu/astr161/lect/time/coordinates.html

- pamela

On 10 Dez., 11:18, "Barry Hunter" <barrybhun...@googlemail.com> wrote:

Moon, Mars and Earth maps are now switched on, so you no longer have to
hack the code.

http://econym.googlepages.com/example_moon.htm

The new map types do not appear to support polylines.

--
http://econym.googlepages.com/index.htm
The Blackpool Community Church Javascript Team

On Dec 11, 2:24 am, Mike Williams <nos...@econym.demon.co.uk> wrote:

Mike,
  That map doesn't seem to work initially in Opera (I get a grey
square with controls), clicking on any of the map type buttons or
clicking on one of the check boxes under "Earth" loads tiles.

  -- Larry

http://mapperz.googlepages.com/Google_Sky_Example.html
Google Earth in Sky mode your looking up from Earth
Google Maps API Sky mode your looking down from outside space.
Works well in FireFox 3 beta
Internet Explorer 7 has some funny goings on (try panning)
Tardis optional

On Dec 11, 2:29 pm, "geocode...@gmail.com" <geocode...@gmail.com>
wrote:

What's actually happening is that the new map types have GProjections
that only cover the zoom levels for which there are tiles.

GPolyline.redraw() does calculations with projection.fromLatLngToPixel
using zoom level 17). If the GProjection doesn't go up to zoom 17, then
the GPolyline.redraw() fails. The polyline doesn't get rendered and the
rest of the code that called the redraw doesn't get executed, leading to
the weird panning behaviour.

A workround is to write:

   G_MOON_VISIBLE_MAP.getProjection = function() {
     return G_NORMAL_MAP.getProjection()
   }

etc.

--
http://econym.googlepages.com/index.htm
The Blackpool Community Church Javascript Team

Also in Google Sky the GLargeMapControl seems to have more zoom levels
in the control than there actually are levels of imagery in the map.

Example here: http://virtualtourism.blogspot.com/2007/12/google-promises-moon.html

Maybe Google are going to make available the higher levels of
definition available in sky in Google Earth to the maps api..

Wasn't it cornea who wrote:

I suspect that's a typo. On this line (from APIv2.95) the "19" should
probably be "10".

var
a=[{symbol:"SKY_VISIBLE_MAP",name:"visible",url:de+"sky/skytiles_v1/",zoo
m_levels:19}]

Since the projection associated with that may type is
        new GMercatorProjection(11)
the code will crash when the zoom level exceeds 10.

--
http://econym.googlepages.com/index.htm
The Blackpool Community Church Javascript Team

Hi,

On 15 Dec. 2007, 16:21, Mike Williams <nos...@econym.demon.co.uk>
wrote:

Yeah, I have just run into that bug as well.

Furthermore the GScaleControl() is providing pretty small values. In
general this control might be useless for a map of this type as we
don't know how far away the object we are looking at really is. Where
the pictures from Earth, Moon and Mars is somewhat based on a flat
surface where everything is pretty much the same distance from the
camera we here have depths in the images.

Perhaps GScaleControl() should just not be available as it seem
useless and might provide wrong numbers to people.

Just a thought: it would be nice with a "geocoding" service for the
different map types to be able to look up e.g. Polaris or other stars
and places.