I have used the sharpgis tool and it worked nicely. I just visited the
site and posted a message that their download link is broken.
Ian mentioned ogr2ogr - does it currently support MSSQL 2008?
Regards,
--
Richard Greenwood
richard....@gmail.com
www.greenwoodmap.com
Fantastic. This will make the whole process easier.
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.557 / Virus Database: 270.11.9/1993 - Release Date: 10/03/2009
7:19 AM
I found SQL Server 2008 was pretty particular about "valid" geometry.
Unfortunately I can't find my notes right now so apologies if my reply
is a bit vague. I used the sharpGIS Shape2Sql.exe. I converted my
MapInfo polygons to shape files and the used Shape2Sql to import them
into SQL Server 2008. Shape2Sql presented errors regarding invalid
geometries and offered the option to cancel or ignore. I selected
ignore. After the polys were in SQL Server 2008 I ran something like
"select * from polys where not IsValid(geom)" which produced the list
of polygons that SQL Server didn't like. I than ran something like
"update polys set geom = MakeValid(goem) where not IsValid(geom)'. In
my case, the invalid goemtries were irrelevant, like they were wound
the wrong direction or something trivial.
So my guess is that Easyloader is stopping on SQL Server invalid
geometries. And I really need to find my notes...
HTH,
Rich
> So my guess is that Easyloader is stopping on SQL Server invalid
> geometries. And I really need to find my notes...
Found my notes:
-- find invalid geometries
SELECT * from ownership where geom.STIsValid() <> 1;
SET @g = @g.MakeValid() -- Make them valid