<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Switching between mapping APIs and universal zoom levels</title>
	<atom:link href="http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/feed/" rel="self" type="application/rss+xml" />
	<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 00:50:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Klokan Petr Pridal</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-106</link>
		<dc:creator>Klokan Petr Pridal</dc:creator>
		<pubDate>Tue, 19 May 2009 14:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-106</guid>
		<description>Hi,

I just would like to mention here the mashup for tile coordinates detection:

http://www.maptiler.org/google-maps-coordinates-tile-bounds-projection/

You can search a place, or zoom&amp;pan to it and you will see directly the coordinates of the tiles and bounds in several systems.

On the website is also the Python module (open-source) for calculating and conversion of all the systems...</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I just would like to mention here the mashup for tile coordinates detection:</p>
<p><a href="http://www.maptiler.org/google-maps-coordinates-tile-bounds-projection/" rel="nofollow">http://www.maptiler.org/google-maps-coordinates-tile-bounds-projection/</a></p>
<p>You can search a place, or zoom&amp;pan to it and you will see directly the coordinates of the tiles and bounds in several systems.</p>
<p>On the website is also the Python module (open-source) for calculating and conversion of all the systems&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shivaji</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-105</link>
		<dc:creator>Shivaji</dc:creator>
		<pubDate>Tue, 16 Dec 2008 10:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-105</guid>
		<description>Hi, I need to take a road and buildings all the shapes is that possible for me.
And i need all this things are need in SHP files
thanks.</description>
		<content:encoded><![CDATA[<p>Hi, I need to take a road and buildings all the shapes is that possible for me.<br />
And i need all this things are need in SHP files<br />
thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Janes&#8217; Code Weblog &#187; Once more with the maps</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-104</link>
		<dc:creator>David Janes&#8217; Code Weblog &#187; Once more with the maps</dc:creator>
		<pubDate>Sun, 07 Dec 2008 12:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-104</guid>
		<description>[...] Migurski added a very informative comment about tiling levels here, with a pointer to way more detailed information [...]</description>
		<content:encoded><![CDATA[<p>[...] Migurski added a very informative comment about tiling levels here, with a pointer to way more detailed information [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Janes</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-103</link>
		<dc:creator>David Janes</dc:creator>
		<pubDate>Sun, 07 Dec 2008 12:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-103</guid>
		<description>Thanks Michal. And then Askimet ate it, sorry for taking so long to get it up here!</description>
		<content:encoded><![CDATA[<p>Thanks Michal. And then Askimet ate it, sorry for taking so long to get it up here!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michal Migurski</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-102</link>
		<dc:creator>Michal Migurski</dc:creator>
		<pubDate>Tue, 02 Dec 2008 21:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-102</guid>
		<description>(I just wrote a lengthier version of this comment, then my browser ate it. rewriting, sad.)

Eugene&#039;s right on the mark with his explanation. We did a bunch of this same exploration about two years ago with Modest Maps, summarized here:
    http://modestmaps.mapstraction.com/trac/wiki/TileCoordinateComparisons

An additional convenience of the scheme used by Google &amp; VEarth gets you is the ability to use simple arithmetic in your exponents with your map code. With the furthest-out zoom level equal to zero, you can easily determine how many tiles your complete map contains at each zoom, and rapidly convert between them. For example, at zoom level zero, 2^0 = 1 tiles across to cover the whole world; at zoom level one, 2^1 = 2 tiles across to cover the whole world; at zoom level two, 2^2 = 4 tiles across to cover the whole world, etc.

Yahoo&#039;s choice of numbering scheme makes probably the least sense of all, because they&#039;ve given themselves an implied maximum zoom.

The Modest Maps python branch has some of the most succinct bits of code &amp; math for dealing with this:
    http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Tiles.py
    http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Google.py
    http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Microsoft.py
    http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Core.py#L43</description>
		<content:encoded><![CDATA[<p>(I just wrote a lengthier version of this comment, then my browser ate it. rewriting, sad.)</p>
<p>Eugene&#8217;s right on the mark with his explanation. We did a bunch of this same exploration about two years ago with Modest Maps, summarized here:<br />
    <a href="http://modestmaps.mapstraction.com/trac/wiki/TileCoordinateComparisons" rel="nofollow">http://modestmaps.mapstraction.com/trac/wiki/TileCoordinateComparisons</a></p>
<p>An additional convenience of the scheme used by Google &amp; VEarth gets you is the ability to use simple arithmetic in your exponents with your map code. With the furthest-out zoom level equal to zero, you can easily determine how many tiles your complete map contains at each zoom, and rapidly convert between them. For example, at zoom level zero, 2^0 = 1 tiles across to cover the whole world; at zoom level one, 2^1 = 2 tiles across to cover the whole world; at zoom level two, 2^2 = 4 tiles across to cover the whole world, etc.</p>
<p>Yahoo&#8217;s choice of numbering scheme makes probably the least sense of all, because they&#8217;ve given themselves an implied maximum zoom.</p>
<p>The Modest Maps python branch has some of the most succinct bits of code &amp; math for dealing with this:<br />
    <a href="http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Tiles.py" rel="nofollow">http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Tiles.py</a><br />
    <a href="http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Google.py" rel="nofollow">http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Google.py</a><br />
    <a href="http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Microsoft.py" rel="nofollow">http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Microsoft.py</a><br />
    <a href="http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Core.py#L43" rel="nofollow">http://modestmaps.mapstraction.com/trac/browser/trunk/py/ModestMaps/Core.py#L43</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Knecht</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-101</link>
		<dc:creator>Stefan Knecht</dc:creator>
		<pubDate>Tue, 02 Dec 2008 19:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-101</guid>
		<description>What a marvellous article -- will crosspost &amp; comment with full kudos!</description>
		<content:encoded><![CDATA[<p>What a marvellous article &#8212; will crosspost &amp; comment with full kudos!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugene</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-100</link>
		<dc:creator>Eugene</dc:creator>
		<pubDate>Tue, 02 Dec 2008 16:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-100</guid>
		<description>It&#039;s extremely likely that Microsoft and Yahoo! followed Google&#039;s lead here. But the derivation is actually quite logical. The first ingredient is the Mercator projection, which is the best projection suited for slippy maps like these since it preserves shape and angles. (Google once used a plate caree projection for the satellite maps but quickly abandoned it because circles became ellipses far from the equator.) The second ingredient is using a quad-tile implementation with 256-pixel-width map tiles; it&#039;s also quite convenient that a square cut of the Mercator projection of the world spans from ~85°S to ~85°N, which covers most of the places most people would be interested at (too bad for the poles).

What&#039;s not logical is the fact that Google uses a spherical approximation of the WGS84 datum (which is actually not too inaccurate) for computational efficiency. The question is whether Microsoft and Yahoo! also uses this spherical approximation. If not, there will be places on the three maps that will be off. It&#039;s been confirmed over at http://cfis.savagexi.com/2006/05/03/google-maps-deconstructed that Microsoft also uses a spherical approximation. Yahoo is likely doing the same thing.</description>
		<content:encoded><![CDATA[<p>It&#8217;s extremely likely that Microsoft and Yahoo! followed Google&#8217;s lead here. But the derivation is actually quite logical. The first ingredient is the Mercator projection, which is the best projection suited for slippy maps like these since it preserves shape and angles. (Google once used a plate caree projection for the satellite maps but quickly abandoned it because circles became ellipses far from the equator.) The second ingredient is using a quad-tile implementation with 256-pixel-width map tiles; it&#8217;s also quite convenient that a square cut of the Mercator projection of the world spans from ~85°S to ~85°N, which covers most of the places most people would be interested at (too bad for the poles).</p>
<p>What&#8217;s not logical is the fact that Google uses a spherical approximation of the WGS84 datum (which is actually not too inaccurate) for computational efficiency. The question is whether Microsoft and Yahoo! also uses this spherical approximation. If not, there will be places on the three maps that will be off. It&#8217;s been confirmed over at <a href="http://cfis.savagexi.com/2006/05/03/google-maps-deconstructed" rel="nofollow">http://cfis.savagexi.com/2006/05/03/google-maps-deconstructed</a> that Microsoft also uses a spherical approximation. Yahoo is likely doing the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Online Maps Share Same Zoom Levels &#124; Maps &#38; Atlas</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-99</link>
		<dc:creator>Online Maps Share Same Zoom Levels &#124; Maps &#38; Atlas</dc:creator>
		<pubDate>Tue, 02 Dec 2008 06:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-99</guid>
		<description>[...] David Janes: &#8220;Did you know that Google Maps, Yahoo Maps and Virtual Earth all use the same map tile resolutions? That is, you can actually seamlessly switch between mapping systems and have everything line up exactly the same way.&#8221; Examples provided. Google has one wider zoom than the others; Yahoo lacks the two closest levels of Google and Virtual Earth. Via Global Nerdy. [...]</description>
		<content:encoded><![CDATA[<p>[...] David Janes: &#8220;Did you know that Google Maps, Yahoo Maps and Virtual Earth all use the same map tile resolutions? That is, you can actually seamlessly switch between mapping systems and have everything line up exactly the same way.&#8221; Examples provided. Google has one wider zoom than the others; Yahoo lacks the two closest levels of Google and Virtual Earth. Via Global Nerdy. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Dunn</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-98</link>
		<dc:creator>Craig Dunn</dc:creator>
		<pubDate>Mon, 01 Dec 2008 20:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-98</guid>
		<description>Cool post - I&#039;ve often wondered whether this was just coincidence or some sort of &#039;standardisation&#039; (or a function of sources/providers of the imagery and maps).

The same is true of OpenStreetMap tiles, and the &#039;overlays&#039; used by Google (for streets &amp; streetview) and Yahoo. Google Moon &amp; Mars also use the same tile system, but with fewer zoom levels (6 or 7). In other countries (ie. outside the USA) the &#039;lowest&#039; zoom level varies as they don&#039;t always have high-resolution imagery for each country (and across the oceans).

You can play interactively at http://silverlightearth.com/2/ (although due occasional updates by the tile servers some selections occasionally won&#039;t load). For example, you can overlay Googles &#039;blue glow&#039; streetview indicator over OpenStreetMap or overlay Googles roads over Virtual Earth&#039;s or NASAs satellite imagery...
http://conceptdev.blogspot.com/2008/08/silverlightearth-gets-openstreetview.html</description>
		<content:encoded><![CDATA[<p>Cool post &#8211; I&#8217;ve often wondered whether this was just coincidence or some sort of &#8216;standardisation&#8217; (or a function of sources/providers of the imagery and maps).</p>
<p>The same is true of OpenStreetMap tiles, and the &#8216;overlays&#8217; used by Google (for streets &amp; streetview) and Yahoo. Google Moon &amp; Mars also use the same tile system, but with fewer zoom levels (6 or 7). In other countries (ie. outside the USA) the &#8216;lowest&#8217; zoom level varies as they don&#8217;t always have high-resolution imagery for each country (and across the oceans).</p>
<p>You can play interactively at <a href="http://silverlightearth.com/2/" rel="nofollow">http://silverlightearth.com/2/</a> (although due occasional updates by the tile servers some selections occasionally won&#8217;t load). For example, you can overlay Googles &#8216;blue glow&#8217; streetview indicator over OpenStreetMap or overlay Googles roads over Virtual Earth&#8217;s or NASAs satellite imagery&#8230;<br />
<a href="http://conceptdev.blogspot.com/2008/08/silverlightearth-gets-openstreetview.html" rel="nofollow">http://conceptdev.blogspot.com/2008/08/silverlightearth-gets-openstreetview.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Universal Zoom Levels for Google Maps, Live Search Maps and Yahoo! Maps</title>
		<link>http://code.davidjanes.com/blog/2008/11/08/switching-between-mapping-apis-and-universal-map-levels/#comment-97</link>
		<dc:creator>Universal Zoom Levels for Google Maps, Live Search Maps and Yahoo! Maps</dc:creator>
		<pubDate>Sun, 09 Nov 2008 15:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=152#comment-97</guid>
		<description>[...] article Switching Between Mapping APIs and Universal Zoom Levels at David Janes’ Code Weblog explains that the mapping systems differ in their zoom [...]</description>
		<content:encoded><![CDATA[<p>[...] article Switching Between Mapping APIs and Universal Zoom Levels at David Janes’ Code Weblog explains that the mapping systems differ in their zoom [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

