Strange behaviour in web cartographic application

Question

Hi group,
I have noticed a strange behaviour with the overview tool of my web application with MapInfo data uploaded in Oracle 10g with EasyLoader. When I put the cursor near the limit of some polygons but outside of its surface, the overview tool shows the info of this polygon when it should show the info of the neighbor polygon. It's like if the boundary of the polygon is outside of its limit but visually the borders are looking good.
After many tests, I think the problem may be related with the tolerance precision and the table bounds in sdo_metadata. The table is in lat/long (8307) and the tolerance setted by Easyloader is X: 7.9013E-6 and Y:1.01201E-5
In MapInfo I gave this bounds to the table: min x: -82.0483359 min y: 43.2322719 max x: -54.6521931 max y: 64.3415211 but when loaded in Oracle the bounds are automatically set to -180/180 and -90/90
I tried to change the tolerance and the bounds in Oracle and create a new spatial index without success. Changing the bounds in MapInfo prior uploading to Oracle was unsuccessfull as well.
Anything else could be tryed?
Thank you
Maxime D.

Answer 1

Maxime,
Didn't you contact me privately about something like this? No matter.
the tolerance setted by Easyloader is X: 7.9013E-6 and Y:1.01201E-5These tolerances are not what Oracle says should be set for geodetic (8307) data. From the documentation...
The tolerance value for geodetic data should not be smaller than 0.05 (5 centimeters)You can do one of two things:
1. If you have SQL Developer, install GeoRaptor and then right mouse click on the table in the connect pane and select Metadata Manager. Then calculate XY values and if GeoRaptor doesn't set the tolerances to 0.05 do it manually. Then press Update.
2. Using SQLPlus or SQL Developer's SQL Worksheet, do this:
update user_sdo_geom_metadata
set diminfo = SDO_DIM_ARRAY(SDO_DIM_ELEMENT(-82.0483359,-54.6521931,0.05),
                            SDO_DIM_ELEMENT(43.2322719,64.3415211,0.05)),
       SRID = 8307
where table_name = YOUR TABLE
  and column_name = YOUR SDO_GEOMETRY COLUMN NAME;
commit;NOTE: It is OK to have ordinate ranges different from -180..180, -90..90.
Drop your index and rebuild.
Should now be OK.
If it starts to misbehave again (and the metadata has been changed) then all one could say is that perhaps the MapInfo software is modifying the metadata some how. Perhaps this is related to the MAPINFO_MAPCATALOG?
Any MapInfo gurus know?
regards
Simon