I want to convert numerous in-development surface files from Civil 3D to GIS data that can be published and accessed via Portal. However, I am not sure on the best methods for storing this data in our Enterprise DB.
It seems that terrain datasets have a lot of functionality but that mosaic raster datasets do as well. These surface files will be, ideally, conglomerated from multiple DWG's and compiled into a single dataset that is continually updated to reflect all active projects. The data will be published primarily for display purposes where popups on elevation/slope/etc would be beneficial to have (which both mosaics and terrain datasets seem to support on Portal).
What is the main pros & cons for having the Civil 3D data stored in one format vs the other? I'm a bit confused on what exactly a terrain dataset offers.
