<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Processing GPX data with Flex</title>
	<atom:link href="http://note19.com/2007/11/19/processing-gpx-data-with-flex/feed/" rel="self" type="application/rss+xml" />
	<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 07:15:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Brian</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2196</link>
		<dc:creator><![CDATA[Brian]]></dc:creator>
		<pubDate>Mon, 09 Feb 2009 19:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2196</guid>
		<description><![CDATA[The source code viewer is part of the Export Release Build in FB3.

Check out the MapQuest Developer Network - definitely still around.

http://developer.mapquest.com/home]]></description>
		<content:encoded><![CDATA[<p>The source code viewer is part of the Export Release Build in FB3.</p>
<p>Check out the MapQuest Developer Network &#8211; definitely still around.</p>
<p><a href="http://developer.mapquest.com/home" rel="nofollow">http://developer.mapquest.com/home</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sj</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2171</link>
		<dc:creator><![CDATA[sj]]></dc:creator>
		<pubDate>Thu, 05 Feb 2009 19:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2171</guid>
		<description><![CDATA[Hi Brian, I like the source code browser that you&#039;re using. Is it an open source project or did you write it yourself? The MapQuest mash up looks very good. I didn&#039;t know that they were still around.]]></description>
		<content:encoded><![CDATA[<p>Hi Brian, I like the source code browser that you&#8217;re using. Is it an open source project or did you write it yourself? The MapQuest mash up looks very good. I didn&#8217;t know that they were still around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2169</link>
		<dc:creator><![CDATA[Brian]]></dc:creator>
		<pubDate>Thu, 05 Feb 2009 17:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2169</guid>
		<description><![CDATA[Here&#039;s a sample of parsing the gpx in Flex with the MapQuest ActionScript API - http://devblog.mapquest.com/2009/02/04/dump-your-garmin/]]></description>
		<content:encoded><![CDATA[<p>Here&#8217;s a sample of parsing the gpx in Flex with the MapQuest ActionScript API &#8211; <a href="http://devblog.mapquest.com/2009/02/04/dump-your-garmin/" rel="nofollow">http://devblog.mapquest.com/2009/02/04/dump-your-garmin/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2168</link>
		<dc:creator><![CDATA[Brian]]></dc:creator>
		<pubDate>Thu, 05 Feb 2009 17:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2168</guid>
		<description><![CDATA[Hey SJ, thanks for your reply.  I figured after almost a year I wouldn&#039;t get anything!

The new namespace actually hasn&#039;t worked for me.  The only thing that has worked is removing the topografix namespace from the gpx file (what end users want to do that?) or just treating the xml as a string (NOT elegant).

I&#039;ve been looking into this in my spare time for 3 days now and this is the only place that directly addresses this issue.  Do you know if this is an issue with flex or with the namespace?]]></description>
		<content:encoded><![CDATA[<p>Hey SJ, thanks for your reply.  I figured after almost a year I wouldn&#8217;t get anything!</p>
<p>The new namespace actually hasn&#8217;t worked for me.  The only thing that has worked is removing the topografix namespace from the gpx file (what end users want to do that?) or just treating the xml as a string (NOT elegant).</p>
<p>I&#8217;ve been looking into this in my spare time for 3 days now and this is the only place that directly addresses this issue.  Do you know if this is an issue with flex or with the namespace?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sj</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2161</link>
		<dc:creator><![CDATA[sj]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 22:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2161</guid>
		<description><![CDATA[Hi Brian, I&#039;ve touched that code for a year now so not sure if there is an effective workaround or not. Clearly removing the namespace works, so that may be your best bet.]]></description>
		<content:encoded><![CDATA[<p>Hi Brian, I&#8217;ve touched that code for a year now so not sure if there is an effective workaround or not. Clearly removing the namespace works, so that may be your best bet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2158</link>
		<dc:creator><![CDATA[Brian]]></dc:creator>
		<pubDate>Wed, 04 Feb 2009 19:13:28 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-2158</guid>
		<description><![CDATA[I&#039;m having trouble getting flex to read the gpx even with the new namespace.  I&#039;m using HTTPService to read the gpx in e4x resultFormat.  I still get &quot;a term is undefined and has no properties&quot; back.  Here is the basic code...

    	XML.ignoreWhitespace = true;
    	namespace topo = &quot;http://www.topografix.com/GPX/1/0&quot;;
	use namespace topo;
    	var gpx:XML = XML(e.result);
    	outputTextArea.text += gpx.wpt[0].name + &quot;\n&quot;;

outputTextArea.text += gpx.children(); works great with the new namespace.  Removing the namespace from the gpx makes the code above work great.  Any help would be great.  Thanks.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m having trouble getting flex to read the gpx even with the new namespace.  I&#8217;m using HTTPService to read the gpx in e4x resultFormat.  I still get &#8220;a term is undefined and has no properties&#8221; back.  Here is the basic code&#8230;</p>
<p>    	XML.ignoreWhitespace = true;<br />
    	namespace topo = &#8220;http://www.topografix.com/GPX/1/0&#8243;;<br />
	use namespace topo;<br />
    	var gpx:XML = XML(e.result);<br />
    	outputTextArea.text += gpx.wpt[0].name + &#8220;\n&#8221;;</p>
<p>outputTextArea.text += gpx.children(); works great with the new namespace.  Removing the namespace from the gpx makes the code above work great.  Any help would be great.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loocie</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1964</link>
		<dc:creator><![CDATA[Loocie]]></dc:creator>
		<pubDate>Tue, 16 Dec 2008 21:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1964</guid>
		<description><![CDATA[I had the same Problem too. I use the XML-Object as dataprovider in a datagrid. After including the namespace (topo), like in da&#039;s example it seams to work. But it is not possible to read elements inside the -elements like  or . Only the attributes @lon + @lat inside the  are readable.  When I remove the namespace declaration xmlns=&quot;http://www.topografix.com/GPX/1/0&quot; all sub elements are accessible.]]></description>
		<content:encoded><![CDATA[<p>I had the same Problem too. I use the XML-Object as dataprovider in a datagrid. After including the namespace (topo), like in da&#8217;s example it seams to work. But it is not possible to read elements inside the -elements like  or . Only the attributes @lon + @lat inside the  are readable.  When I remove the namespace declaration xmlns=&#8221;http://www.topografix.com/GPX/1/0&#8243; all sub elements are accessible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sj</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1593</link>
		<dc:creator><![CDATA[sj]]></dc:creator>
		<pubDate>Fri, 04 Apr 2008 07:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1593</guid>
		<description><![CDATA[Perfect. Thank you for the update.]]></description>
		<content:encoded><![CDATA[<p>Perfect. Thank you for the update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: da</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1592</link>
		<dc:creator><![CDATA[da]]></dc:creator>
		<pubDate>Fri, 04 Apr 2008 02:29:23 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1592</guid>
		<description><![CDATA[Defining the namespace does work, here&#039;s an example....

namespace topo = &quot;http://www.topografix.com/GPX/1/0&quot;;	      	
use namespace topo;
for each (var trkpt:XML in gpx..trkpt) {]]></description>
		<content:encoded><![CDATA[<p>Defining the namespace does work, here&#8217;s an example&#8230;.</p>
<p>namespace topo = &#8220;http://www.topografix.com/GPX/1/0&#8243;;<br />
use namespace topo;<br />
for each (var trkpt:XML in gpx..trkpt) {</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sj</title>
		<link>http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1520</link>
		<dc:creator><![CDATA[sj]]></dc:creator>
		<pubDate>Mon, 28 Jan 2008 17:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://note19.com/2007/11/19/processing-gpx-data-with-flex/#comment-1520</guid>
		<description><![CDATA[Defining the &lt;a href=&quot;http://livedocs.adobe.com/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Book_Parts&amp;file=13_Working_with_XML_169_09.html&quot; rel=&quot;nofollow&quot;&gt;namespace&lt;/a&gt; in ActionScript program, may help, but I&#039;ve not tried it.]]></description>
		<content:encoded><![CDATA[<p>Defining the <a href="http://livedocs.adobe.com/flex/201/html/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Book_Parts&amp;file=13_Working_with_XML_169_09.html" rel="nofollow">namespace</a> in ActionScript program, may help, but I&#8217;ve not tried it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

