Hi all,
MapInfo stores coordinates in 32 bit integers (binary tab format), and
converts them back into floating point when loading data. The conversion
is done taking the boundary into account. The greater the boundary, the
lower the precision. That's why lat/lon coordinates are stored with
great
Murali,
The mapinfo driver is not known for creating datasets with good precision.
Projected coordinates can have an error of up to 0.02
http://www.gdal.org/ogr/drv_mitab.html
http://trac.osgeo.org/gdal/browser/trunk/autotest/ogr/ogr_mitab.py#L106
On Sat, May 26, 2012 at 9:24 AM, Murali Krishna
I'm trying to create a MapInfo file using gdal ogr java bindings (version
1.9.0) with some point geometries.
However the geometries in the created MapInfo file doesn't actually match
with the values which i have used in creation.
For example, I create a MapInfo feature with a point geometry and wi