<?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: World file calculator</title>
	<atom:link href="http://egb13.net/2009/03/worldfile-calculator/feed/" rel="self" type="application/rss+xml" />
	<link>http://egb13.net/2009/03/worldfile-calculator/</link>
	<description>Time-lapse, weather, maps, and more</description>
	<lastBuildDate>Sat, 19 Jun 2010 02:29:07 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: egb13</title>
		<link>http://egb13.net/2009/03/worldfile-calculator/comment-page-1/#comment-56</link>
		<dc:creator>egb13</dc:creator>
		<pubDate>Thu, 15 Apr 2010 15:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://egb13.net/?p=59#comment-56</guid>
		<description>Is this program available for download?  The JavaScript code for it can be found at http://egb13.net/jscripts/worldfile.js.  It&#039;s just a couple lines of arithmetic.</description>
		<content:encoded><![CDATA[<p>Is this program available for download?  The JavaScript code for it can be found at <a href="http://egb13.net/jscripts/worldfile.js" rel="nofollow">http://egb13.net/jscripts/worldfile.js</a>.  It&#8217;s just a couple lines of arithmetic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald</title>
		<link>http://egb13.net/2009/03/worldfile-calculator/comment-page-1/#comment-52</link>
		<dc:creator>Donald</dc:creator>
		<pubDate>Fri, 26 Mar 2010 15:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://egb13.net/?p=59#comment-52</guid>
		<description>Is this program available for download?</description>
		<content:encoded><![CDATA[<p>Is this program available for download?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: egb13</title>
		<link>http://egb13.net/2009/03/worldfile-calculator/comment-page-1/#comment-23</link>
		<dc:creator>egb13</dc:creator>
		<pubDate>Thu, 26 Nov 2009 19:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://egb13.net/?p=59#comment-23</guid>
		<description>Replying to myself...  my response to NickMcW is for Google Maps, but he asked about Google Earth.  It&#039;s a more interesting question, but not one I have an answer to.  Yet.</description>
		<content:encoded><![CDATA[<p>Replying to myself&#8230;  my response to NickMcW is for Google Maps, but he asked about Google Earth.  It&#8217;s a more interesting question, but not one I have an answer to.  Yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: egb13</title>
		<link>http://egb13.net/2009/03/worldfile-calculator/comment-page-1/#comment-22</link>
		<dc:creator>egb13</dc:creator>
		<pubDate>Thu, 26 Nov 2009 18:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://egb13.net/?p=59#comment-22</guid>
		<description>If in Google Maps you click on &quot;Link&quot; you get a choice two strings to copy and paste.  The first one, for email or IM, is the bare URL of the displayed map; if you past it in the browser&#039;s address box, you&#039;ll get the map you see displayed.  That Maps URL looks like this:

    http://maps.google.com/?ie=UTF8&amp;ll=36.779042,-103.971863&amp;spn=0.370679,0.801315&amp;z=11

The &quot;ll=&quot; parameter is the latitude and longitude of the center of the map.  The &quot;spn=&quot; parameter must stand for &quot;span&quot;, because it appears to be the height and width of the displayed map in degrees.  Test this by trying to find the coordinates of the upper-left corner: add half the vertical span to the latitude and subtract half the horizontal span from the longitude.  (Moving northwest increases latitude and decreases longitude.)  Applying that formula to the URL above gives this new URL:

    http://maps.google.com/?ie=UTF8&amp;ll=36.964381,-104.372520&amp;spn=0.370679,0.801315&amp;z=11

That indeed looks like the upper-left corner of the original map, and what was at the center (an extinct cinder-cone volcano that you can drive to the top of and hike through the crater) is now at the lower-right corner.

Since you&#039;re already given the degree span, you don&#039;t really need this calculator; divide the vertical and horizontal span values given in the link URL by the pixel dimensions of the image and you have the 1st and 4th parameters for the worldfile.

But I don&#039;t know what projection Google uses to display their maps.  Is it simple latitude x longitude (EPSG:4326)?  Or is it a UTM projection?  Or does it vary by the size of the area covered?  UTM is not good for maps that cover more than a certain distance horizontally.  EPSG:4326 is not good for lots of things.  That&#039;s what is used in the video in my Road Trip! posting, and even though that doesn&#039;t cover a terribly large area (a little over 100 mi horizontally) and the counties shown are noticeably flatter than they should be.  And a worldfile (at least with the 2nd &amp; 3rd parameters zero) is not good for &quot;curved&quot; projections.

Might this be the wrong approach, though?  If you haven&#039;t already investigated Google&#039;s Maps API you might want to.  I see lots of places around the internet making pretty good use of it.  It&#039;s been a very long time since I dabbled in it and am unable to offer any help with that, not to mention that I don&#039;t know what exactly your after anyway.</description>
		<content:encoded><![CDATA[<p>If in Google Maps you click on &#8220;Link&#8221; you get a choice two strings to copy and paste.  The first one, for email or IM, is the bare URL of the displayed map; if you past it in the browser&#8217;s address box, you&#8217;ll get the map you see displayed.  That Maps URL looks like this:</p>
<p>    <a href="http://maps.google.com/?ie=UTF8&#038;ll=36.779042,-103.971863&#038;spn=0.370679,0.801315&#038;z=11" rel="nofollow">http://maps.google.com/?ie=UTF8&#038;ll=36.779042,-103.971863&#038;spn=0.370679,0.801315&#038;z=11</a></p>
<p>The &#8220;ll=&#8221; parameter is the latitude and longitude of the center of the map.  The &#8220;spn=&#8221; parameter must stand for &#8220;span&#8221;, because it appears to be the height and width of the displayed map in degrees.  Test this by trying to find the coordinates of the upper-left corner: add half the vertical span to the latitude and subtract half the horizontal span from the longitude.  (Moving northwest increases latitude and decreases longitude.)  Applying that formula to the URL above gives this new URL:</p>
<p>    <a href="http://maps.google.com/?ie=UTF8&#038;ll=36.964381,-104.372520&#038;spn=0.370679,0.801315&#038;z=11" rel="nofollow">http://maps.google.com/?ie=UTF8&#038;ll=36.964381,-104.372520&#038;spn=0.370679,0.801315&#038;z=11</a></p>
<p>That indeed looks like the upper-left corner of the original map, and what was at the center (an extinct cinder-cone volcano that you can drive to the top of and hike through the crater) is now at the lower-right corner.</p>
<p>Since you&#8217;re already given the degree span, you don&#8217;t really need this calculator; divide the vertical and horizontal span values given in the link URL by the pixel dimensions of the image and you have the 1st and 4th parameters for the worldfile.</p>
<p>But I don&#8217;t know what projection Google uses to display their maps.  Is it simple latitude x longitude (EPSG:4326)?  Or is it a UTM projection?  Or does it vary by the size of the area covered?  UTM is not good for maps that cover more than a certain distance horizontally.  EPSG:4326 is not good for lots of things.  That&#8217;s what is used in the video in my Road Trip! posting, and even though that doesn&#8217;t cover a terribly large area (a little over 100 mi horizontally) and the counties shown are noticeably flatter than they should be.  And a worldfile (at least with the 2nd &#038; 3rd parameters zero) is not good for &#8220;curved&#8221; projections.</p>
<p>Might this be the wrong approach, though?  If you haven&#8217;t already investigated Google&#8217;s Maps API you might want to.  I see lots of places around the internet making pretty good use of it.  It&#8217;s been a very long time since I dabbled in it and am unable to offer any help with that, not to mention that I don&#8217;t know what exactly your after anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NickMcW</title>
		<link>http://egb13.net/2009/03/worldfile-calculator/comment-page-1/#comment-21</link>
		<dc:creator>NickMcW</dc:creator>
		<pubDate>Thu, 26 Nov 2009 16:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://egb13.net/?p=59#comment-21</guid>
		<description>Hi - nice utility, thanks for making it available. It prompts a related question: does anyone know a way to programmatically obtain the corner coordinates of the current view extent in Google Earth? The reason for asking is in order automate the creation of world files - as done with this calculator - for google earth screen-saved images. (The image size, in pixels, will depend on the resolution option chosen in GE; the options available depend on whether the free or pro version is used.)</description>
		<content:encoded><![CDATA[<p>Hi &#8211; nice utility, thanks for making it available. It prompts a related question: does anyone know a way to programmatically obtain the corner coordinates of the current view extent in Google Earth? The reason for asking is in order automate the creation of world files &#8211; as done with this calculator &#8211; for google earth screen-saved images. (The image size, in pixels, will depend on the resolution option chosen in GE; the options available depend on whether the free or pro version is used.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: egb13</title>
		<link>http://egb13.net/2009/03/worldfile-calculator/comment-page-1/#comment-14</link>
		<dc:creator>egb13</dc:creator>
		<pubDate>Tue, 21 Apr 2009 22:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://egb13.net/?p=59#comment-14</guid>
		<description>I&#039;ve made a minor modification to the code to correctly calculate the location of the center of the corner pixel.  It&#039;s really trivial -- just adjust by 1/2 of the pixel size in geo coordinates.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve made a minor modification to the code to correctly calculate the location of the center of the corner pixel.  It&#8217;s really trivial &#8212; just adjust by 1/2 of the pixel size in geo coordinates.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
