The discrepancy is introduced by the projection that is used. If you set the
coordsys to a non-projected longitude/latitude the results show no such
differences. This will happen if you open your map and run the select; the
MI will then use the default non-projected system. If your table is in a
projected system, set coordsys table to your table, run the select and you
will find discrepancies. Works as expected!
Jacques PARIS
e-mail [EMAIL PROTECTED]
For MapInfo support, see the Paris PC Consult enr. site at
http://www.total.net/~rparis/gisproducts.htm
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Leduc, Yannick
Sent: August 2, 2000 9:51 AM
To: 'MapInfo-L'
Subject: MI MBR or not
Hello to you,
I was answering the request of Sebastian Hudson about polygons
attribute when I found out something I can't explain to myself. What is the
difference between querying the MinX of an object and querying the MinX of
the MBR's object. To me, it was the same thing, but I obtain different
value. I tought MBR was based on Min and Max value of the object. Now I
found it's different. Someone care to explain?
Here's the query:
Select ObjectGeography(obj, 1) "MinX", ObjectGeography(MBR(obj), 1)
"MinXmbr", ObjectGeography(obj, 3) "MaxX",ObjectGeography(MBR(obj), 3)
"MaxXmbr", ObjectGeography(obj, 2) "MinY", ObjectGeography(MBR(obj), 2)
"MinYmbr", ObjectGeography(obj, 4) "MaxY", ObjectGeography(MBR(obj), 4)
"MaxYmbr" from Municipalités_DTMCQ Where Left$(code_munic, 2) ="32" into
InfoBox
Here's an extract of my query's result:
"MinX" "MinXmbr" "MaxX" "MaxXmbr" "MinY"
"MinYmbr" "MaxY" "MaxYmbr"
667471.92 667231.92 677843.03 678063.86 226552.59
226331.4 237344.29 237565.95
677400.54 677337.92 679832.76 679894.06 234335.18
234285.66 237378.1 237427.62
670638.53 670359.25 683360.19 683611.49 231531.9
231269.52 244381.18 244644.03
659609.21 659251 674021.56 674342.26 233601.98
233280.08 248778.71 249101.45
653932.29 653823.25 655784.05 655891.66 240164.59
240119.47 244610.58 244655.7
646826.6 646244.35 661147.04 661672.98 234878.14
234527.44 257458.31 257810.33
661718.22 661638.7 664618.76 664696.5 247036.25
246969.58 250453.56 250520.35
655857.02 655402.98 672300.28 672701.34 240529.82
240154.59 259233.75 259610.18
670280.91 670010.32 682541.75 682786.27 240905.89
240651.49 253302.44 253557.43
674759.64 674331.43 694261.29 694621.64 241743.61
241365.28 262030.25 262409.77
666066.95 665719.93 688366.52 688655.09 258601.27
258140.08 273947.4 274409.78
662393.92 662029.76 677591.37 677914.46 250076.79
249744.53 265770.77 266103.86
654782.52 654414.67 665299.1 665639.45 251802.59
251554.97 266825.28 267073.49
648200.38 647832.89 662414.4 662746.77 259959.69
259613.27 274300.49 274647.75
Weird, isn't it?
Yannick Leduc, géog.
DTMCQ - SIP
Mailto:[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]
