List of Contributions

Good eyes, James and Peter - thank you. When I am zoomed out enough that the oddity of the slice is not noticeable, you can select the one node at its tip and delete it. This will also fix the problem. I'll try the extended version idea. Is it likely that someone from Precisely will read this post ...

Thanks for looking! Unfortunately, that did not work for me. I saved the table with a new name "Reg.tab", closed Query2, opened the new table, and reran the query with the new table. I still got the popup error. Please keep in mind that the SELECT statement itself does not fail. I only get the error ...

We seem to have found a potential floating-point error in MIPro object operations. I've attached two MapInfo Pro vector tables, each of which has a single region object in it. One region object is entirely contained within the other, so there is a non-zero area overlap. However, when I run this query: ...

I see the same behavior! Thank you Eric. Next time, I will know better than to trust my minions when they tell me what the CoordSys is. ------------------------------ Matthew Katinsky Senior GIS Programmer SCHLOSSER GEOGRAPHIC SYSTEMS Montpelier VT ------------------------------

Sorry for the delay. I got a copy of the table from my coworker. It turns out that the table's native coordsys is UTM Zone 4, not Popular Mercator! Either I was misinformed or I wasn't paying attention. Regardless, we still seem to have a problem. I have uploaded the table so you can test this yourself. ...

I can see how TableInfo() bounds might exceed actual object bounds over time due to deletions. Thanks for that explanation. As for the bounds in the coordsys clause, the table itself was defined using that very bounded coordsys clause. However we did try the code again setting the current coordsys ...

(Apologies if this has been answered before. I couldn't find it in a search) We have a MapInfo vector table with Region objects in EPSG 3857. We want to know the min and max x and y extent over all objects in the table. But we get different answers depending on how we ask for the data. Set CoordSys ...