RE: Bug in MapInfo 5.5 Yes / No??
I have exported a point in a test layer which generates the following MIF/MID
files.
(MapInfo 5.5, NT4 sp4, P3 500)
Version 300
Charset "WindowsLatin1"
Delimiter ","
CoordSys Earth Projection 1, 12 Bounds (148.5, -36) (149.5, -35)
Columns 4
X_flt Float
Y_flt Float
X_dec Decimal(14, 8)
Y_dec Decimal(14, 8)
Data
Point 148.9817073 -35.44214178
Symbol (77,16711680,7,"MapInfo Cartographic",0,0)
__________________
_____
Please note the 7 decimal places on the Long (X) and 8 decimal places on the Lat
(Y) value in the MIF file above. Now the MID file looks like,
148.982 , -35.4421 , 148.98170700 , -35.44214200
The value in the last column {Decimal (14,8)} was generated using the following
command
Update TabName Set col4 = objectgeography(obj,2)
Please note that the last 2 numbers in the MID have been set to zero or 178 (MIF
value) is now 200 (MID value).
It would appear that despite the fact that the original layer was bounded to
improve the number of decimal places we can not use objectgeography to access
all 7 and 8 decimal places.
PRINT commands with FORMAT$ statements also appear to round the 7th and 8th
decimal places on the Lats (Y) and longs (X).
Using [F7] on the selected object does give the correct number of significant
figures (see diagram below).
(Embedded image moved to file: pic28392.pcx)
How do we update a browser in MapInfo using MapBasic commands with all 7 and 8
significant figures using a Lat Long projection??
(MapInfo USA) Is this a recognised bug and is there a plan to fix the problem?
Please supply details if available.
If you have any questions or solutions on this bug or if I have done something
wrong, please email me direct.
Steve Smith
Australian Bureau of Statistics
[EMAIL PROTECTED]
GIS Innovations
[EMAIL PROTECTED]
pic28392.pcx
