Object Data in Map / Civil 3D has much more potential than is used.
First, on the basis of OD, you can organize data collection in dwg no worse than Feature (Object) classes. Those. draw with the definition of graphic elements as objects and with the definition of their characteristics. As well as to convert graphic plans already created in dwg to object models.
Using excellent Feature classes ideas, better implementing them, adding unused features, you can create a powerful data collection tool for CAD.
Secondly, OD can be used as an internal database in dwg, if you add enough funds to work with them.
This allows you to return to Map 3D a large number of users who create maps that collect terrain data. Now they are forced to use other software. And it will allow better to prepare data for GIS, information systems.
We published in the Autodesk App Store two current, constantly used prototype plugins that solve these problems:
ODCLASS - data collection in dwg,
ODEDIT - work with data as a database in dwg.
We are talking about prototypes, because we always wanted such solutions to be made by Autodesk itself.
With these application prototypes, we want to show that this is realizable and how much the potential of Object Data is undervalued.
We also believe that the potential of Feature (Object) classes and Object Data is much broader than Map 3D tasks. And this idea is extrapolated, scaled to any modeling tasks, including basic AutoCAD.
In this case, instead of Object Data, you can use XRecord, available for any application to AutoCAD.
This would allow you to create object models that define characteristics in basic AutoCAD. And would give a common "language" for data exchange between any AutoCAD applications.
We are also preparing similar prototypes of plugins based on XRecord.
