<?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: Digital Heroes Vote &#8211; result</title>
	<atom:link href="http://www.cyclestreets.net/blog/2009/11/02/digital-heroes-vote-result/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cyclestreets.net/blog/2009/11/02/digital-heroes-vote-result/</link>
	<description>News from CycleStreets</description>
	<lastBuildDate>Wed, 21 Dec 2011 03:32:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Anthony Cartmell</title>
		<link>http://www.cyclestreets.net/blog/2009/11/02/digital-heroes-vote-result/comment-page-1/#comment-1196</link>
		<dc:creator>Anthony Cartmell</dc:creator>
		<pubDate>Wed, 04 Nov 2009 08:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.cyclestreets.net/blog/?p=231#comment-1196</guid>
		<description>Sorry to hear that you didn&#039;t win the funding.

As for the feedback database, is there any way that might be opened up, so the feedback could be crowd-sourced a bit?  

I&#039;m thinking that some problems, such as routes poorly planned due to lack of data in OSM, could be handled by other users. The OSM data issue being a particularly local thing, usually requiring local knowledge to fix.

Just thinking aloud... I&#039;m starting to make use of local volunteers to keep FillThatHole hazard statuses up-to-date, another situation where local knowledge is essential.</description>
		<content:encoded><![CDATA[<p>Sorry to hear that you didn&#8217;t win the funding.</p>
<p>As for the feedback database, is there any way that might be opened up, so the feedback could be crowd-sourced a bit?  </p>
<p>I&#8217;m thinking that some problems, such as routes poorly planned due to lack of data in OSM, could be handled by other users. The OSM data issue being a particularly local thing, usually requiring local knowledge to fix.</p>
<p>Just thinking aloud&#8230; I&#8217;m starting to make use of local volunteers to keep FillThatHole hazard statuses up-to-date, another situation where local knowledge is essential.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

