Finally Bentley Map is here. But it still the same program (or actually half the same program for the moment). I got the impression that with Bentley CONNECT Bentley products would move towards a common attribute format, i.e. Item Types/EC attributes. Will that be the case with Bentley Map in the future?
CONNECT has great tools for analyzing, thematizing and reporting on Item Types and it's a shame that you should be required to have Bentley Map to review attributes.
I realize that it's a big challange to rewrite old code but if not now, when? Will Bentley Map ever be a modern, integrated software that adds new functionality in a seamless way letting MicroStation users use/view the result?
/Krister
" I got the impression that with Bentley CONNECT Bentley products would move towards a common attribute format, i.e. Item Types/EC attributes."
From all of the Bentley sessions I attended on the lead up to the release of the CONNECT Edition products (MicroStation, OpenRoads, etc.) I got the same impression. Every session talked about a move to a common data structure where the vertical applications could recognize each other's objects. For example a pipe object in OpenRoads will be able to be read and processed as a pipe object in Aecosim.
Based on that I was expecting that Bentley Map CONNECT was making that kind of move away from XFM. I was also looking for a move similar to OpenRoads where the MicroStation Element Template structure would be used as the basis for defining features. Revamping the GSA to use dgnlib's for storing extended map feature definitions instead of creating custom workset structures would also have been a welcome change.
For as long as it took to get the first release of Bentley Map CONNECT out the door I have to say I am very disappointed with the lack of progress in these areas.
As Krister said - "But it still the same program (or actually half the same program for the moment)"
Rod WingSenior Systems Analyst