Where is Ed?

After a rather lengthy hiatus, I’m back to blogging once again.  I was awakened from my reverie by an old friend who noted that a few folks had wondered if I was still alive and kicking.  Not to worry, I’m still busy with SQL Server Spatial.  But back to the central question: Where is Ed? …

2

Working with Invalid Data and the SQL Server 2008 Geography Data Type, Part 1b

"Fixing" Polygon Ring Orientation in SQL Server 2008 using T-SQL In the last installment, I promised to try and correct invalid Geography data using FME.  While I am making progress on that front, I decided to take a small detour and discuss an interesting but little known behavior of the SQL Server Geometry type, polygons…

19

GeoWeb 2008 Conference Dinner Cruise Photos (and SQL Server 2008 Spatial ;-)

On the Wednesday night GeoWeb 2008 dinner cruise around Vancouver harbor, several folks who had forgotten their cameras (and 1 who had broken their camera) noted that I was busy taking photos and asked if they could be made available. I am happy to report that I have successfully uploaded the photos to my Skydrive…

0

WORKING WITH INVALID DATA AND THE SQL SERVER 2008 GEOGRAPHY DATA TYPE, PART 1

As many of you have already discovered, the Geography data type in SQL Server 2008 is very strict about the structure of the spatial data which it will accept. The Geometry data type, on the other hand, is much more forgiving about spatial data which does not conform to the rules defined in the OGC…

2

GETTING YOUR PROGRAMS READY FOR THE UPCOMING GEOGRAPHY COORDINATE ORDER SWAP

For those of you who have programs which work with November CTP (CTP-5) and February CTP (CTP-6) and use the Geography data type, you should already be aware of Isaac’s posts on this subject: Latitude-Longitude Ordering and The Upcoming Geography Coordinate Order Swap—A FAQ. The next CTP, most likely called the May CTP (CTP-6 Refresh),…

1

TRAVELING WITH SQL SERVER 2008 SPATIAL

I travel quite a bit and have the need to carry a bit of equipment with me. This includes a laptop with the latest version of SQL Server 2008 (spatially-enabled, of course) and a geospatial data capture device – a Nikon D300 equipped with a special GPS receiver (di-GPS, described later). As many of you…

0

CHANGING THE BLOG NAME…

By popular request (well, at least the request of Abe on Spatially Adjusted…), I’ve changed the name of the blog from “Ed on Spatial” to “Spatial Ed”.  This should cause some interesting confusion…

2

SQL SERVER SPATIAL BUGS…

As part of the Microsoft SQL Server 2008 February CTP Bug Bash Contest, we are looking for spatial bugs!  The entrant with the largest number of reproducible non-duplicate SQL Server 2008 Spatial bugs submitted during the entry period will win an Xbox Elite.  At last check, we had 1 entrant with 1 bug – surely…

0

Introduction

Welcome to my first blog effort. Many of you in the spatial world may already know me.  For everyone else, I am the Spatial Program Manager for SQL Server.  I’ve been working in the spatial/GIS field much longer than I wish to admit, with prior engagements at Informix Software and IBM in the recent past….

2

NEW SPATIAL FEATURES IN The SQL SERVER 2008 FEBRUARY CTP

Now that the February CTP (CTP-6) for SQL Server 2008 is available, it’s time to let folks know what new spatial features have been added or updated since the November CTP (CTP-5). Before I get into the new and updated features, I want to make sure that it is clear that the latitude-longitude coordinate ordering…

12