Hi: Unfortunately MapInfo does not enforce topology (Maptitude does) and can create nonsense boundary lines. In this case the edge may be so garbled that Maptitude cannot fix it when importing. Maptitude Mapping Software <http://www.caliper.com> Group Moderator
--- In [email protected], "ivanmf_iimf" <ivan.marcelo.ferreira@...> wrote: > > Hi, > > I've tried to convert .tab to .dbd file like was suggested but I've got an error and a message window saying to look at the log file for more information. > > At the log file I found the following message > "Area ID 4982: Error at coordinate (-46469552,-5751102) > ERROR: Deleting area ID #4982." > > What can I do? > > --- In [email protected], "dr_haspel" mhaspel@ wrote: > > > > > > > > Ivan, > > > > The reason you're seeing a performance difference is that the .cdf format is optimized for Maptitude's underlying database, while .tab (MapInfo's format) is not. > > > > Once you've opened the .tab file in Maptitude, you should be able to export it to .cdf format using Tools... export. You'll probably have to do this in two steps: > > > > Step #1: convert .tab to .dbd (editable, but not optimized Mapt format) > > Step #2: convert .dbd to .cdf (optimized, but not editable Mapt format) > > > > Good luck! > > > > P.S. If you need to automate this process in GISDK, look at the AddMITABLayer() and ExportGeography() commands. > > > > > > > > > > > > --- In [email protected], Ivan Marcelo Ferreira <ivan.marcelo.ferreira@> wrote: > > > > > > Hi, > > > > > > We have a map in a .tab file and the same map in a .cdf file. Why is .tab > > > file slower than .cdf file? > > > When we're using the .tab file, Maptitude takes a few seconds more then > > > when we're using the .cdf file. > > > Can I convert the .tab file in a .cdf file? > > > > > > The .tab file is attached. > > > > > > Thanks, > > > Ivan > > > > > >
