<?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: Which Maps API Should I Use?</title>
	<atom:link href="http://mapscripting.com/which-maps-api-should-i-use/feed" rel="self" type="application/rss+xml" />
	<link>http://mapscripting.com/which-maps-api-should-i-use</link>
	<description>Create Location-based Web Applications</description>
	<lastBuildDate>Wed, 29 Jun 2011 21:13:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Happy 5th Birthday, Google Maps API - Map Scripting</title>
		<link>http://mapscripting.com/which-maps-api-should-i-use/comment-page-1#comment-497</link>
		<dc:creator>Happy 5th Birthday, Google Maps API - Map Scripting</dc:creator>
		<pubDate>Tue, 29 Jun 2010 07:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://mapscripting.com/?p=5#comment-497</guid>
		<description>[...] Maps. And since then, it&#8217;s gone from fun little toy to extremely useful tool. And while I appreciate all mapping APIs, it&#8217;s important to note this milestone for the influential platform. Let&#8217;s look where [...]</description>
		<content:encoded><![CDATA[<p>[...] Maps. And since then, it&#8217;s gone from fun little toy to extremely useful tool. And while I appreciate all mapping APIs, it&#8217;s important to note this milestone for the influential platform. Let&#8217;s look where [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Way Cool Map Scripting - Map Scripting</title>
		<link>http://mapscripting.com/which-maps-api-should-i-use/comment-page-1#comment-386</link>
		<dc:creator>Way Cool Map Scripting - Map Scripting</dc:creator>
		<pubDate>Tue, 16 Mar 2010 21:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://mapscripting.com/?p=5#comment-386</guid>
		<description>[...] today at SXSW Interactive in Austin. In it, I showed some simple ways to improve your maps, from using Mapstraction to custom map markers to changing the entire map [...]</description>
		<content:encoded><![CDATA[<p>[...] today at SXSW Interactive in Austin. In it, I showed some simple ways to improve your maps, from using Mapstraction to custom map markers to changing the entire map [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mapstraction V2 In The Wild - Map Scripting</title>
		<link>http://mapscripting.com/which-maps-api-should-i-use/comment-page-1#comment-366</link>
		<dc:creator>Mapstraction V2 In The Wild - Map Scripting</dc:creator>
		<pubDate>Fri, 22 Jan 2010 17:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://mapscripting.com/?p=5#comment-366</guid>
		<description>[...] Mapstraction started working on a new, improved version of the open source wrapper library. This is the mapping API I recommend because it allows developers to write code once that works on any mapping provider. Also, I use [...]</description>
		<content:encoded><![CDATA[<p>[...] Mapstraction started working on a new, improved version of the open source wrapper library. This is the mapping API I recommend because it allows developers to write code once that works on any mapping provider. Also, I use [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Open Should Mapping APIs Be? - Map Scripting</title>
		<link>http://mapscripting.com/which-maps-api-should-i-use/comment-page-1#comment-190</link>
		<dc:creator>How Open Should Mapping APIs Be? - Map Scripting</dc:creator>
		<pubDate>Fri, 29 May 2009 06:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://mapscripting.com/?p=5#comment-190</guid>
		<description>[...] for a particular project, but something else might be better for another project. With mapping APIs Mapstraction fixes this issue, but shouldn&#8217;t providers get together and standardize on their own? Watch my presentation [...]</description>
		<content:encoded><![CDATA[<p>[...] for a particular project, but something else might be better for another project. With mapping APIs Mapstraction fixes this issue, but shouldn&#8217;t providers get together and standardize on their own? Watch my presentation [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

