<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.3" -->
<rss version="2.0">
	<channel>
		<title>Technical Overview: GeoRSS</title>
		<description>Comments for Technical Overview: GeoRSS at http://www.geowebguru.com , comment 1 to 5 out of 5 comments</description>
		<link>http://www.geowebguru.com</link>
		<lastBuildDate>Wed, 10 Mar 2010 00:41:20 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.3</generator>
		<item>
			<title>Chris: geo:point tag</title>
			<link>http://www.geowebguru.com/articles/108-technical-overview-georss#comment-40</link>
			<description>Chris:  So, back to the geo:point tag!   This is considered optional? I got the feeling that the W3C way of doing things was a bit rough-and-ready. Almost as if it developed by accident without much thought or planning, and an attempt has since been made to standardise it. - Richard Marsden</description>
			<pubDate>Tue, 17 Mar 2009 02:57:58 +0100</pubDate>
		</item>
		<item>
			<title>Okay heard back from JomComment</title>
			<link>http://www.geowebguru.com/articles/108-technical-overview-georss#comment-39</link>
			<description>I filed a ticket with JomComment on this angle bracket problem. I'm not too happy with the response. For now we shall have to insert spaces into XML/HTML tags (eg. as I've done above). I'll try to get a text comment added to this effect. - Richard Marsden</description>
			<pubDate>Tue, 17 Mar 2009 02:54:57 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.geowebguru.com/articles/108-technical-overview-georss#comment-38</link>
			<description>A bit of a kludge, but inserting spaces works for now:

&amp;lt; rss version=&quot;2.0&quot; xmlns:geo=&quot;http://www.w3.org/2003/01/geo/wgs84_pos#&quot; &amp;gt;
&lt; channel &gt;
&amp;lt; title&amp;gt;Mount Saint Helens - Mount Margaret Trail&lt; /title&gt;
&amp;lt; link&amp;gt;&lt; /link&gt;
&lt; description&gt;Trailheads and campsites in the Mount Margaret area of Mount Saint Helens, WA&lt; /description&gt;
&lt; item &gt; 
&amp;lt; title&amp;gt;Lakes Trailhead&lt; /title&gt;

&lt; description&gt;This is where we started our hike, just down the road from the visitor center. You could also start at the visitor center.&lt; /description&gt;
&lt; geo:lat&gt;46.2913246&lt; /geo:lat&gt;
&lt; geo:long&gt;-122.2658157&lt; /geo:long&gt;
&lt; /item&gt;
&lt; /channel&gt;
&lt; /rss&gt;  - Richard Marsden</description>
			<pubDate>Mon, 16 Mar 2009 12:25:52 +0100</pubDate>
		</item>
		<item>
			<title>Apparntly it keeps hiding the angle brackets....</title>
			<link>http://www.geowebguru.com/articles/108-technical-overview-georss#comment-36</link>
			<description>Apparntly it keeps hiding the angle brackets.... - Chris Pietschmann</description>
			<pubDate>Mon, 16 Mar 2009 12:10:30 +0100</pubDate>
		</item>
		<item>
			<title> isn't always necessary</title>
			<link>http://www.geowebguru.com/articles/108-technical-overview-georss#comment-34</link>
			<description>I've seen feeds that implement the W3C Basic Geo Vocabulary (WGS84_POS) that don't even use the  tag, and just put the  and  tags directly within the feed to geocode a specific feed item. I'm not sure how widely this is used, but it is supported when importing GeoRSS feeds into MS Virtual Earth.

This is just something to keep in mind when writing a parser. Like you said, you'll want to use GeoRSS when building new feed generators.

Here's an example of what I mean within an RSS 2.0 feed:


  
    Mount Saint Helens - Mount Margaret Trail
    
    Trailheads and campsites in the Mount Margaret area of Mount Saint Helens, WA
    
      Lakes Trailhead
      This is where we started our hike, just down the road from the visitor center. You could also start at the visitor center.
      46.2913246
      -122.2658157
    
  
 - Chris Pietschmann</description>
			<pubDate>Mon, 16 Mar 2009 12:07:40 +0100</pubDate>
		</item>
	</channel>
</rss>
