<?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: VPSN&#8217;s take on the Seaside Greenway Bike Route controversy</title>
	<atom:link href="https://vancouverpublicspace.ca/2013/10/24/vpsns-take-on-the-seaside-greenway-bike-route-controversy/feed/" rel="self" type="application/rss+xml" />
	<link>https://vancouverpublicspace.ca/2013/10/24/vpsns-take-on-the-seaside-greenway-bike-route-controversy/</link>
	<description></description>
	<lastBuildDate>Mon, 28 Aug 2017 20:00:29 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: VPSN</title>
		<link>https://vancouverpublicspace.ca/2013/10/24/vpsns-take-on-the-seaside-greenway-bike-route-controversy/#comment-259</link>
		<dc:creator><![CDATA[VPSN]]></dc:creator>
		<pubDate>Tue, 05 Nov 2013 21:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://vancouverpublicspace.wordpress.com/?p=2986#comment-259</guid>
		<description><![CDATA[Voony,
 
You note a good point - we forgot to mention that our post is referencing the Parks Board report dated October 1, 2013 &quot;&lt;a href=&quot;http://former.vancouver.ca/parks/board/2013/131007/documents/Report_SeasideGreenwayImprovements-07-10-2013.pdf&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Seaside Greenway Improvements&lt;/a&gt;&quot; (PDF). In this report you find &quot;Appendix A&quot; which contains an illustration at a large scale showing a &quot;potential route&quot; for bike improvements and another for pedestrian improvements.
 
This illustration doesn’t provide much in terms of the detailed layout people want to see. For example, it’s impossible to determine with any degree of specificity how far the “proposed” trail is from the existing trail, trees or other existing elements, or what design and landscaping elements might be introduced to mitigate any impacts associated with the bike route.
 
The comments from the public that have been reported in the media have stated concern about this level of detail. People want to know the exact location and potential impacts – and yet, because things are at a preliminary stage, these are not well documented in the report. Instead, the level of detail – a concept with more generalities than specifics – left informational gaps. Some of these, in turn, were filled in with unhelpful speculation and conjecture. This didn’t help the controversy!
 
- Adam]]></description>
		<content:encoded><![CDATA[<p>Voony,</p>
<p>You note a good point &#8211; we forgot to mention that our post is referencing the Parks Board report dated October 1, 2013 &#8220;<a href="http://former.vancouver.ca/parks/board/2013/131007/documents/Report_SeasideGreenwayImprovements-07-10-2013.pdf" target="_blank" rel="nofollow">Seaside Greenway Improvements</a>&#8221; (PDF). In this report you find &#8220;Appendix A&#8221; which contains an illustration at a large scale showing a &#8220;potential route&#8221; for bike improvements and another for pedestrian improvements.</p>
<p>This illustration doesn’t provide much in terms of the detailed layout people want to see. For example, it’s impossible to determine with any degree of specificity how far the “proposed” trail is from the existing trail, trees or other existing elements, or what design and landscaping elements might be introduced to mitigate any impacts associated with the bike route.</p>
<p>The comments from the public that have been reported in the media have stated concern about this level of detail. People want to know the exact location and potential impacts – and yet, because things are at a preliminary stage, these are not well documented in the report. Instead, the level of detail – a concept with more generalities than specifics – left informational gaps. Some of these, in turn, were filled in with unhelpful speculation and conjecture. This didn’t help the controversy!</p>
<p>&#8211; Adam</p>
]]></content:encoded>
	</item>
</channel>
</rss>
