<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.10" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: &#8220;geo:&#8221; URI JavaScript parser</title>
	<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/</link>
	<description>a Uniform Resource Identifier for geographic locations</description>
	<pubDate>Wed, 19 Nov 2008 23:51:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.10</generator>

	<item>
		<title>by: Christian</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-52</link>
		<pubDate>Wed, 11 Apr 2007 20:14:33 +0000</pubDate>
		<guid>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-52</guid>
					<description>John,

basically you find all information needed (lat &#038; lon) for a geouri in the address bar when you hit "link to this page" in the Google Maps interface.

You're right, additional parameters could be placed in the search bar or as well as bubble content in Google Maps for instance. 

Height and scale are two different parameters: height is part of the location definition and scale is a viewing property. We can't use the height for defining the viewing scale.

And no, Google is not involved in this project ;-) All those examples are just proof of concepts and you could substitute Google maps with any other mapping API (as shown with OpenLayers).</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>basically you find all information needed (lat &#038; lon) for a geouri in the address bar when you hit &#8220;link to this page&#8221; in the Google Maps interface.</p>
<p>You&#8217;re right, additional parameters could be placed in the search bar or as well as bubble content in Google Maps for instance. </p>
<p>Height and scale are two different parameters: height is part of the location definition and scale is a viewing property. We can&#8217;t use the height for defining the viewing scale.</p>
<p>And no, Google is not involved in this project <img src='http://geouri.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  All those examples are just proof of concepts and you could substitute Google maps with any other mapping API (as shown with OpenLayers).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Wolfe</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-50</link>
		<pubDate>Tue, 10 Apr 2007 10:13:16 +0000</pubDate>
		<guid>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-50</guid>
					<description>(note to above: I placed a %_2_0 between "Guggenheim" and "Museum" but the parser translated it to a blank space).

Is there an easy way to find geo information (lat and long) in the appropriate format?  In other words: how do I, as a webmaster, find the numbers to put in the geo: string?  If this was a feature added to Google maps (finding the string) it would be real nice.  I could then look up the location on the map and copy the geo: info and place it in my uri. Then I would also know approximately what map would appear.  

Along the same line; would Google Maps use the height parameter to scale the map appropriately?  

(Is anyone at Google being of any help with this project?)</description>
		<content:encoded><![CDATA[<p>(note to above: I placed a %_2_0 between &#8220;Guggenheim&#8221; and &#8220;Museum&#8221; but the parser translated it to a blank space).</p>
<p>Is there an easy way to find geo information (lat and long) in the appropriate format?  In other words: how do I, as a webmaster, find the numbers to put in the geo: string?  If this was a feature added to Google maps (finding the string) it would be real nice.  I could then look up the location on the map and copy the geo: info and place it in my uri. Then I would also know approximately what map would appear.  </p>
<p>Along the same line; would Google Maps use the height parameter to scale the map appropriately?  </p>
<p>(Is anyone at Google being of any help with this project?)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Wolfe</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-49</link>
		<pubDate>Tue, 10 Apr 2007 09:47:22 +0000</pubDate>
		<guid>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-49</guid>
					<description>I just added the Fire fox extension and used the example in the last comment.  When Google Maps comes up, the search bar and the result area  both list the geo info (lat and long numbers) and nothing else.  This might be a good area for the ? part of the uri. (I am a non-technical home user.) Perhaps add something like ?id=Guggenheim Museum and have that be entered into the field.  I know that if I called up two or three of the museums listed and saved or printed them, I would forget which one was which otherwise.</description>
		<content:encoded><![CDATA[<p>I just added the Fire fox extension and used the example in the last comment.  When Google Maps comes up, the search bar and the result area  both list the geo info (lat and long numbers) and nothing else.  This might be a good area for the ? part of the uri. (I am a non-technical home user.) Perhaps add something like ?id=Guggenheim Museum and have that be entered into the field.  I know that if I called up two or three of the museums listed and saved or printed them, I would forget which one was which otherwise.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christian</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-26</link>
		<pubDate>Wed, 14 Mar 2007 10:10:33 +0000</pubDate>
		<guid>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-26</guid>
					<description>Thanks for the OpenLayers example!

I just added another &lt;a rel="nofollow" href="http://www.geoland.at/index.php?option=com_content&#038;task=view&#038;id=30&#038;Itemid=71&#038;lang=en" rel="nofollow"&gt;WMS&lt;/a&gt; to your script to have some more information in the background. Unfortunately that area isn't covered very well by free data services...

&lt;a rel="nofollow" href="http://spanring.eu/geouri/geouri_ol.html" rel="nofollow"&gt;OpenLayers example plus   geoland.at-WMS&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for the OpenLayers example!</p>
<p>I just added another <a href="http://www.geoland.at/index.php?option=com_content&#038;task=view&#038;id=30&#038;Itemid=71&#038;lang=en"rel="nofollow"  rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.geoland.at');">WMS</a> to your script to have some more information in the background. Unfortunately that area isn&#8217;t covered very well by free data services&#8230;</p>
<p><a href="http://spanring.eu/geouri/geouri_ol.html"rel="nofollow"  rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/spanring.eu');">OpenLayers example plus   geoland.at-WMS</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Christopher Schmidt</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-25</link>
		<pubDate>Tue, 13 Mar 2007 23:37:49 +0000</pubDate>
		<guid>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-25</guid>
					<description>GeoURI Example using OpenLayers:

http://openlayers.org/~crschmidt/vector-2.4/examples/geouri.html

Code doesn't require jquery. Nor an API key. However, the 'extends' method is new in the vector-2.4 branch. Once this is trunk, I'll make it a standard example.</description>
		<content:encoded><![CDATA[<p>GeoURI Example using OpenLayers:</p>
<p><a href="http://openlayers.org/~crschmidt/vector-2.4/examples/geouri.html" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/openlayers.org');">http://openlayers.org/~crschmidt/vector-2.4/examples/geouri.html</a></p>
<p>Code doesn&#8217;t require jquery. Nor an API key. However, the &#8216;extends&#8217; method is new in the vector-2.4 branch. Once this is trunk, I&#8217;ll make it a standard example.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alexandre Leroux</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-24</link>
		<pubDate>Tue, 13 Mar 2007 13:50:43 +0000</pubDate>
		<guid>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comment-24</guid>
					<description>Hi. Just found out the Firefox add-on named geoURI handler 0.0.1 is not compatible with FF 2.0.0.2 and no update is available. Cheers!</description>
		<content:encoded><![CDATA[<p>Hi. Just found out the Firefox add-on named geoURI handler 0.0.1 is not compatible with FF 2.0.0.2 and no update is available. Cheers!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
