<?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: Google Projection: 900913</title>
	<atom:link href="http://crschmidt.net/blog/archives/243/google-projection-900913/feed/" rel="self" type="application/rss+xml" />
	<link>http://crschmidt.net/blog/archives/243/google-projection-900913/</link>
	<description>Ramblings of a GIS Hacker</description>
	<pubDate>Wed, 23 May 2012 06:26:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: SRIDs, GeoDjango, PostGIS, and me &#171; nelsonslog</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-22047</link>
		<dc:creator>SRIDs, GeoDjango, PostGIS, and me &#171; nelsonslog</dc:creator>
		<pubDate>Sat, 11 Dec 2010 01:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-22047</guid>
		<description>[...] 900913: Google Maps&#8217; modified Mercator. (It spells &#8220;google&#8221; in l33t). [...]</description>
		<content:encoded><![CDATA[<p>[...] 900913: Google Maps&#8217; modified Mercator. (It spells &#8220;google&#8221; in l33t). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suprageography &#187; Blog Archive &#187; Spherical Mercator Maps in OpenLayers 2.8</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-20455</link>
		<dc:creator>Suprageography &#187; Blog Archive &#187; Spherical Mercator Maps in OpenLayers 2.8</dc:creator>
		<pubDate>Thu, 25 Jun 2009 10:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-20455</guid>
		<description>[...] here at UCL have taken to calling WebMercator, and is also known as EPSG:900913 (the numbers representing Google in l33t-speak&#8230;) - it has now also been assigned an official EPSG number of 4375. Yahoo and [...]</description>
		<content:encoded><![CDATA[<p>[...] here at UCL have taken to calling WebMercator, and is also known as EPSG:900913 (the numbers representing Google in l33t-speak&#8230;) - it has now also been assigned an official EPSG number of 4375. Yahoo and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crschmidt</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-20356</link>
		<dc:creator>crschmidt</dc:creator>
		<pubDate>Thu, 23 Apr 2009 14:11:42 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-20356</guid>
		<description>http://spatialreference.org/ref/epsg/62556405/ is an EPSG code outside of that range. It is deprecated, but still in the distributed EPSG database.</description>
		<content:encoded><![CDATA[<p><a href="http://spatialreference.org/ref/epsg/62556405/" rel="nofollow">http://spatialreference.org/ref/epsg/62556405/</a> is an EPSG code outside of that range. It is deprecated, but still in the distributed EPSG database.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justitia</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-20355</link>
		<dc:creator>Justitia</dc:creator>
		<pubDate>Thu, 23 Apr 2009 09:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-20355</guid>
		<description>In addition, EPSG only use codes between 0 and 32767 (the equivalent of a positive signed short integer) any codes outside of this range are proprietary.  Hence 900913!</description>
		<content:encoded><![CDATA[<p>In addition, EPSG only use codes between 0 and 32767 (the equivalent of a positive signed short integer) any codes outside of this range are proprietary.  Hence 900913!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justitia</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-20354</link>
		<dc:creator>Justitia</dc:creator>
		<pubDate>Thu, 23 Apr 2009 09:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-20354</guid>
		<description>EPSG has added a WGS 84 / Pseudo-Mercator Projection with a code of EPSG:3857 (See at http://www.epsg-registry.org/ )

They remark that "Uses spherical development of ellipsoidal coordinates. Relative to an ellipsoidal development errors of up to 800 metres in position and 0.7 percent in scale may arise. It is not a recognised geodetic system: see WGS 84 / World Mercator (CRS code 3395)."

EPSG had previously had this as a code of EPSG:3785 but this was deprecated under Change Request EPSG::2008.114 and so EPSG:3857 is now valid.</description>
		<content:encoded><![CDATA[<p>EPSG has added a WGS 84 / Pseudo-Mercator Projection with a code of EPSG:3857 (See at <a href="http://www.epsg-registry.org/" rel="nofollow">http://www.epsg-registry.org/</a> )</p>
<p>They remark that &#8220;Uses spherical development of ellipsoidal coordinates. Relative to an ellipsoidal development errors of up to 800 metres in position and 0.7 percent in scale may arise. It is not a recognised geodetic system: see WGS 84 / World Mercator (CRS code 3395).&#8221;</p>
<p>EPSG had previously had this as a code of EPSG:3785 but this was deprecated under Change Request EPSG::2008.114 and so EPSG:3857 is now valid.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 900913</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-20302</link>
		<dc:creator>900913</dc:creator>
		<pubDate>Mon, 30 Mar 2009 17:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-20302</guid>
		<description>i think 900913 is great.
9-g
0-o
0-o
9-g
1-l
3-e

get it? 900913 is equal to google. THAT'S AMAZING !  =-)</description>
		<content:encoded><![CDATA[<p>i think 900913 is great.<br />
9-g<br />
0-o<br />
0-o<br />
9-g<br />
1-l<br />
3-e</p>
<p>get it? 900913 is equal to google. THAT&#8217;S AMAZING !  =-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul mccullough</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-19715</link>
		<dc:creator>paul mccullough</dc:creator>
		<pubDate>Wed, 07 May 2008 16:57:31 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-19715</guid>
		<description>Hey Chris,
Quick question...
RE the post gis insert statement - why is the srid == 96?
I was expecting 900913.
Thanks
Paul</description>
		<content:encoded><![CDATA[<p>Hey Chris,<br />
Quick question&#8230;<br />
RE the post gis insert statement - why is the srid == 96?<br />
I was expecting 900913.<br />
Thanks<br />
Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-18725</link>
		<dc:creator>Allan</dc:creator>
		<pubDate>Wed, 08 Aug 2007 13:42:16 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-18725</guid>
		<description>I don't think it would be a bad thing to have a non-EPSG authority for some set of neo-geography SRS's. On the other hand, since you do have to worry about a number collision, it may be time to have name spaces or even URI instead of numbers. I think EPSG:4326, or even 4326 are valid URI forms. So is http://spatialreference.org/ref/user/6</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it would be a bad thing to have a non-EPSG authority for some set of neo-geography SRS&#8217;s. On the other hand, since you do have to worry about a number collision, it may be time to have name spaces or even URI instead of numbers. I think EPSG:4326, or even 4326 are valid URI forms. So is <a href="http://spatialreference.org/ref/user/6" rel="nofollow">http://spatialreference.org/ref/user/6</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-18722</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 07 Aug 2007 13:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-18722</guid>
		<description>5VV337!</description>
		<content:encoded><![CDATA[<p>5VV337!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morten</title>
		<link>http://crschmidt.net/blog/archives/243/google-projection-900913/comment-page-1/#comment-18721</link>
		<dc:creator>Morten</dc:creator>
		<pubDate>Tue, 07 Aug 2007 07:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/243/google-projection-900913/#comment-18721</guid>
		<description>Google in 1337 speak is 600613.
I think you should instead raise the concern with EPSG. The more people that pledge their case, the better chance there is that they will include it.</description>
		<content:encoded><![CDATA[<p>Google in 1337 speak is 600613.<br />
I think you should instead raise the concern with EPSG. The more people that pledge their case, the better chance there is that they will include it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

