<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The Geography Hemisphere Limitation</title><link>http://blogs.msdn.com/isaac/archive/2009/02/06/the-geography-hemisphere-limitation.aspx</link><description>Hi Folks, It occurs to me that I haven’t posted anything about the hemisphere limitation for the SQL Server geography type.&amp;#160; This limitation is a little confusing, and could probably use some clarification. It also occurs to me that I haven’t posted</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: The Geography Hemisphere Limitation</title><link>http://blogs.msdn.com/isaac/archive/2009/02/06/the-geography-hemisphere-limitation.aspx#9547799</link><pubDate>Tue, 14 Apr 2009 06:16:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9547799</guid><dc:creator>Pure Krome</dc:creator><description>&lt;p&gt;Hi Isaac :) Slightly off topic, would we be able to get a post about the priorities re: Sql Spatial, which you/the MS team are targetting .. at a high level, without breaking any NDA's?&lt;/p&gt;
&lt;p&gt;You mentioned at the end of this good post, that :-&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt; it’s an implementation artifact that the SQL Server team absolutely abhors&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt; removing the limit is high on everyone’s priorities&lt;/p&gt;
&lt;p&gt;cheers :)&lt;/p&gt;
</description></item></channel></rss>