Jeff and fellow MI'ers
You are right about the file types but at least you can get that data in
easily/no problem. Creating the indexing/projection info is a no-brainer.
The legend has to be (re)generated with avenue - that's true - but can be
linked with in with a previously created APR. In the past it would have
been great for me in many projects to have been able to at least create the
ground geography (TAB,MAP files) without incurring extra cost to the
client. MFAL ain't been around that long! It certainly took awhile before
there was any sign of it here in the UK and the point still stands - open
format, open structure - stop hiding the structure MI so end-user has to pay
more to write a more efficient application! As someone putting solutions
together for clients, I just felt that so many other products (not just GIS
and ESRI) open their structure/publish it that they make their software more
customer-friendly. Using the MFAL line is simply another revenue stream for
MI which shows zero customer support. I fully appreciate MI is in business
to make money but perhaps a little give to the customer rather than take?
Doug
P.S. I would be interested to know what 'reasonable terms' are in the
States.
(Perhaps this thread no longer appropriate for the entire List)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Cole
Sent: 08 September 2000 20:40
To: [EMAIL PROTECTED]
Subject: re[2]: MI ESRI Shapefile and MapX Compatibility Question
Doug & the List,
It seems to be a common misconception that the ESRI Shape format is a public
format with a "published structure". Sure, the SHP, SHX and DBF formats are
documented. Where are the SBN, SBX, AVL, and PRJ file formats "publicly"
documented? These very important files contain important spatial indexing,
map projection, rendition, legend and other information that is critical in
order to support the format effectively.
As it has been said many times on this list - MapInfo offers their MFAL
dynamic link library on very reasonable terms for folks who need to support
TAB files directly in their application. We also offer a TAB Reader COM
library for the same reason. Both approaches are significantly less costly
then developing your own code, even around a published document.
Jeff
[EMAIL PROTECTED]
>> Richard
>> it's true (no proj. info etc.) - but perhaps a small price to pay for
>> published structure! Come on MI, open it up to all!
>> Anyway, ArcView also uses WOR or in their case APR. So all is set in
the
>> APR.
>> doug
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of
>> [EMAIL PROTECTED]
>> Sent: 01 September 2000 13:48
>> To: [EMAIL PROTECTED]
>> Subject: RE: MI ESRI Shapefile and MapX Compatibility Question
>> Hi Dennis,
>> How does ArcView know how to project the files and display the
entities -
>> is
>> the information stored in some higher order of file like a project or
>> theme
>> file or something?
>> Richard Burkmar.
>> -----Original Message-----
>> From: Waardenburg, Dennis [mailto:[EMAIL PROTECTED]]
>> Sent: 01 September 2000 13:39
>> To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED];
>> [EMAIL PROTECTED]
>> Subject: RE: MI ESRI Shapefile and MapX Compatibility Question
>> Richard,
>> The major drawbacks you describe are the result of shortcomings native
to
>> Shape files, not MapX. Shapefiles contain neither the
>> projection/coordinate
>> system nor the object style info for the layer, as Mapinfo TABs do.
MapX
>> can't read information that isn't there, so it's necessary for the
coder
>> to
>> provide it.
>> Dennis Waardenburg
>> GIS Specialist
>> The Environmental Company, Inc.
>> > -----Original Message-----
>> > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
>> > Sent: Friday, September 01, 2000 5:32 AM
>> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>> > Subject: RE: MI ESRI Shapefile and MapX Compatibility Question
>> >
>> > Dave,
>> >
>> > MapX 4.x can read & display native ESRI shape files using the
>> > 'Map.Layers.Add LayerInfoObject' method. There is a major drawback
>> though
>> > -
>> > you have to know the projection of the data and specify that in the
>> > 'LayerInfoObject' - MapX does not seem to be able to get the
projection
>> > from
>> > the shape file itself. MapX also renders the goemetry in the MapX
>> default
>> > styles.
>> >
>> > Richard Burkmar.
>> >
>> > -----Original Message-----
>> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>> > Sent: 31 August 2000 22:12
>> > To: [EMAIL PROTECTED]
>> > Subject: MI ESRI Shapefile and MapX Compatibility Question
>> >
>> >
>> >
>> >
>> > Does anybody out there know of any information regarding the reading
and
>> > editing
>> > of ESRI Shapefiles using the MapX language?
>> >
>> > Cheers
>> >
>> > Dave Williams
>> > Montgomery Watson
>> >
>> >
>>
> ----------------------------------------------------------------------
>> > To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and
put
>> > "unsubscribe MAPINFO-L" in the message body, or contact
[EMAIL PROTECTED]
>>
> ----------------------------------------------------------------------
>> > To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and
put
>> > "unsubscribe MAPINFO-L" in the message body, or contact
[EMAIL PROTECTED]
>> ----------------------------------------------------------------------
>> To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and
put
>> "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
>> ----------------------------------------------------------------------
>> To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and
put
>> "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
