At this point, I’ve covered what I think are the majority of the "core" feature upgrades. One final thing I did want to cover on the issue was general productivity. Although I don’t have any numbers to quote, here are a few of the productivity enhancements that have been highlighted:
- Updated Oracle data server – With this new data server, graphics are supposed to draw much faster
- Updated spatial filter command – Filtering performance has gone up dramatically
- A new selection tool – Where before you could only select in a square/rectangular fashion, you now have a polygonal select option as well
- Geocoding tools – They’ve rolled the geocoding engine into the core product (no longer an expansion pack)
- New Construction Aid – You can now place a deflection angle construction aid
Additionally, the move command now supports construction aids as well - Picklists – Picklists can now be used in the data window
- Categories – Categories have been implemented throughout the application. As opposed to 6.0 where Categories where in most of the product but were still missing from certain area
- Keyboard navigation with the QuickPick command
- The define symbol utility can now be used in batch
I haven’t had a chance to use the beta in quite sometime. However I believe I’ve covered the majority of the key points on 6.1 that I’ve read about or personally experienced. We’ll be organizing a GeoMedia Pro 6.1 product launch through NCIGUC once 6.1 is released to manufacturing (hopefully sometime soon). Once we have the launch, I’ll be able to provide additional information.
We observed a much decreased performance in loading oracle Feature classes with 6.01.00.52 up to more then 500% time.
Are there any more experiences in this point?
Oliver – I had heard (but not tested) the exact opposite. It is supposed to be MUCH faster. Have you filed this with Intergraph at all?
Hi Jeff. not yet – I will do that after some more tests today. I’ll keep you up with information on that point.
Jeff, I confirmed this bad times today in a second test series. The bad times refers both to steps with graphically display and to steps with exlusively showing or analyzing attributive data (like range thematic analyze of the thematic legend entry).
(cont.) I posted this issue today to Intergraph Switzerland and will keep you up with information if there are news or hints.
I wrote to a couple of folks in Huntsville, AL, USA to see if they have any ideas/feedback on the issue. Will post any update that I receive.
I suppose (and hope) that this is just a beta issue. I post any hints I will get.
I heard back from Huntsville, they are saying its only faster. Is this through a custom command or just Legend > Add Feature Class?
A follow-up from Huntsville, AL:
“The actual report from the blog says the performance hit is on graphical displays and thematics. My performance numbers show a 40% improvement in data retrieval which is what we expected with the new OCI. Thematics and general display is client side.” So the degradation in performance may be display, rather than Oracle. We have in the process of performance reviews this week, so I’ll look at this further from that point of view.
We’ll see what comes out of the Q&A.
Thoughts?