I just posted a new MITAB 1.5.0 release to the
http://mitab.maptools.org/ site.
This new release includes a few significant additions, the main one
being support for collection objects, thanks to funding from Comcast
(Andy Canfield) and an initial patch and analysis of collections by Jim
Hope of Innogistic Software. There is more, for instance lots of
improvements around the projection stuff, I have included the complete
list of changes since 1.4.0 below.
Note for those using the VB or .NET definition files in the contrib
directory that they have *not* been updated for this release. If I
receive updated headers from the users of these languages then I'll
include them and issue a 1.5.1 release. Only mitab_dyn.pas is up to date
in the contrib directory.
Thanks to everyone who contributed to this release!
Daniel
Version 1.5.0 (2006-02-16)
--------------------------
- Updated contrib/mitab_dyn.pas with new C API functions. Note that other
definition files for VB and .NET have *not* been updated for this
release.
- Fixed crash when attempting to write TABPolyline object with an invalid
geometry (GDAL bug 1059)
- cast strstr() results as per email from Charles Savage for VC8.
- Fixed build problem (link with -ldl not available) on MacOSX (bug 1167)
- Fixed problem with white space parsing in mitab_miffile.cpp (bug GDAL:954)
- layers with just regions can't be set as type wkbPolygon because they may
have multipolygons (bug GDAL:958)
http://bugzilla.remotesensing.org/show_bug.cgi?id=958
- Fixed support for multi character delimiters in .mid file (bug 1266)
- Fixed reading Mills.mif (TABPoint::ReadGeometryFromMIFFFile()), the check
for SYMBOL didn't check if pszLine was non-NULL.
- Fixed memory leak of m_pszDelimiter in mitab_middatafile.cpp.
- Fixed OGR problems with setting bounds on MIF files, and wrong bounds
on tab files (bug 1198)
Version 1.5.0-beta1 (2005-10-07)
--------------------------------
- Added read/write support for MapInfo Collections in MIF and TAB (bug 1126)
(Thanks to funding from Comcast (Andy Canfield) and an initial patch and
analysis of collections by Jim Hope of Innogistic Software)
- New C API methods to access collection members (bug 1126):
- mitab_c_get_collection_region_ref()
- mitab_c_get_collection_polyline_ref()
- mitab_c_get_collection_multipoint_ref()
- mitab_c_set_collection_region()
- mitab_c_set_collection_polyline()
- mitab_c_set_collection_multipoint()
- Support for writing affine projection params in .MAP header (AJD, bug
1155)
- New C API methods to get/set various projection parameters (AJD, bug
1155):
- mitab_c_get_projection_info()
- mitab_c_set_projection_info()
- mitab_c_get_datum_info()
- mitab_c_set_datum_info()
- mitab_c_get_affine_params()
- mitab_c_set_affine_params()
- All datum definitions in mitab_spatialref.cpp now have the correct
names (Anthony D, bug 1155)
- Added bounds entries for Finnish KKJ and Swedish projections (AJD, bug
1155)
- mitab_ogr_datasource.cpp: avoid leak of CPLReadDirectory() result.
- gcc4 related warnings in mitab_coordsys.cpp and mitab_utils.cpp avoided.
- Change the way \n and \ are handled internally. Now they are stored
unescaped in memory and escaped only when writing MIF files. (bug 1107)
- Improved handling of Danish modified TM proj#21-24 (HSS, bugs 976,1010)
- Upgraded CPL and OGR source from latest GDAL CVS (as of 2005-05-12)
- Produce a fatal error if creating an index of a size that exceeds the
.IND file format limitation (tree depth > 255) (OGR Bug 839)
- Added mitab_c_set_symbol_angle() and mitab_c_get_symbol_angle() for
point symbols of type TABFC_FontPoint (bug 1002)
- Added rule in cpl/GNUmakefile to copy cpl_config.h from
cpl_config.h.in. (FW)
- Changed to use OGRLayers spatial filtering support. (FW)
- A few fixes to support for modified TM projections #21-24 (AJD, bug 1155)
- Fixed missing initialization of default .MID file delimiter ("\t")
(Anthony D - bugs 1155 and 37)
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/mitab/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/