[Gdal-dev] Problem creating MapInfo tab files using C# (via theC API)

[Christian Ratliff]

  I was able to build under VC 2003 (7.1) without a problem.

christian
DeLorme

-----Original Message-----
From: Richard Matsunaga [mailto:richard at waypointinfo.com] 
Sent: Thursday, March 23, 2006 11:26 AM
To: gdal-dev at lists.maptools.org
Subject: RE: [Gdal-dev] Problem creating MapInfo tab files using C# (via
theC API)

 
After hours of struggling to compile in Visual Studio 2005, I may have
to go back to VSC++ 6. Does anyone have updated instructions on how to
get GDAL building in the latest Visual Studio?

I continue to experience odd behaviour when using the MapInfo driver. On
the suggestion of a list member, I ran ogrinfo on two of my layers - a
working one and a corrupt one. There was nothing amiss according to
ogrinfo. All features are contained within the extents and there are no
other differences reported (I assume the -al switch is the most detailed
version of the outputs?).

Now when I try to create the MapInfo datasource, I get a .NET exception
indicating memory corruption. If I try to open it again (immediately in
the next line of code), it will work. This only happens with the MapInfo
driver, although I haven't tried many drivers.

I also generated ESRI Shapefile outputs, then used ogr2ogr to convert to
MapInfo tab format. This is the strange part: the same MI files were
corrupt as when I directly write them from my code. There's obviously
something in there that MapInfo doesn't like.

I then tried ogr2ogr from ESRI Shapefiles generated by a C++ version of
my app and those were all correct.

Richard


-----Original Message-----
From: gdal-dev-bounces at lists.maptools.org
[mailto:gdal-dev-bounces at lists.maptools.org] On Behalf Of Daniel
Morissette

Frank Warmerdam wrote:
> 
> This might be worth taking up on the mitab list - this issue sounds 
> vaguely familiar.  I wonder if it might already have been fixed. Are 
> you using GDAL CVS?
> 

Frank,

Are you thinking of the problem with the #ifdef MITAB_AFFINE_PARAMS in
MITAB that causes unreadable files?
http://bugzilla.maptools.org/show_bug.cgi?id=1319

Richard: perhaps you could try recompiling GDAL after adding
-DMITAB_AFFINE_PARAMS to the CPPFLAGS variable in GDALmake.opt and let
us know if that solves the issue.

Daniel
--
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
Gdal-dev mailing list
Gdal-dev at lists.maptools.org
http://lists.maptools.org/mailman/listinfo/gdal-dev


_______________________________________________
Gdal-dev mailing list
Gdal-dev at lists.maptools.org
http://lists.maptools.org/mailman/listinfo/gdal-dev