When can we expect MapInfo Pro to take full use of multiple core processing?
The benefits & drawback of collecting data using the grid tool provided in MapInfo. Is it better than just using blockgroups??
@Corey Graft?, from my experience GRID is much better as you do not have to the normalize any of the data based on area. Plus, to the end user, they see something that they do not have to mentally try to adjust on the fly that this block group looks like it has more or fewer widgets than the neighboring one without accounting for the differences in area.
@Steve Wallace?, good point. As you know some of the Object Processing tools in Pro already do suWe are also looking into taking advantage of the new MapInfo Data Access Library to start creating tools that can run in the back ground and support multi cores.
Over the years I have done a couple of tools that start multiple instances of Pro to be able to split the data processing in that way.
@Steve Wallace?, sorry, I also meant to ask if you had specific request for multi core right now?
I work with lots of data open at the same time, so anything I do takes a lot of redraw time even with multiple SSD's for storage. Then when I need to compute anything spatial, it can take a long time to calculate. Outside your direct control, but RouteFinder takes almost 4 minutes just to create drive distances for a couple dozen fire stations. I'm just impatient!
Oh, you mean like every E**I web map we've ever seen? Roads, aerials, terrain, color vs grey... yeah -- great idea!
Thanks. Nice interaction
@Andrew Bailey?, we try to support the common spatial database systems out there, SQL Server, Oracle, PostGIS...
For auditing we support Oracle Workspaces out of the box in MapInfo Pro
Terms of UseLegalPrivacy NoticesTrademarks Your Privacy ChoicesCalifornia Privacy NoticesCookie Settings