MapInfo Developers,

Blue Marble Geographics is announcing a new product that many MapInfo developers may 
be interested in.  

The MapInfo TAB format has become a very popular, defacto standard, map file format.  
Do you want to support the native MapInfo TAB file format directly within your app 
without conversion?  

Are you building your own application and want to handle native MapInfo map data (TAB 
files) directly?
 
Does your application currently handle MIF (MapInfo Interchange Format) files? Would 
you rather be handling native MapInfo map data directly?

You may not want to add a full-blown mapping OCX into your application in order to 
simply support the MapInfo map format. You already have your app and it's framework 
and you simply want to be able to read TAB files directly so that you can use your 
existing code to display, query, or otherwise manipulate the data, without rewriting 
your application or altering it's architecture. You don't want to compromise 
performance and you don't want the reader to "throw information away".

Wouldn't it be nice if you could add support for reading native MapInfo map files into 
your application without engineering, writing, and testing the low level code that 
actually reads the files? Did you know that the TAB file specification is proprietary 
and not publicly available?

Our FormatX TAB Reader is a 32-bit DLL (dynamic link library) that provides a COM 
object library interfact for reading the native, proprietary MapInfo file format.

You can get more details about our FormatX TAB Reader at 
http://www.bluemarblegeo.com/devformatxtab.htm

Thanks,

Jeff Cole
[EMAIL PROTECTED]

Blue Marble Geographics
"The Geographic Software Component Company."
www.bluemarblegeo.com
261 Water Street, Gardiner, Maine 04345 USA
Voice: 207-582-6747  Fax: 207-582-7001
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]

Reply via email to