Advanced Data Source Management

Idea created by duri on Dec 15, 2010
    Reviewed
    Score830

    The worst nightmare for every ArcGIS user is broken data links. ArcMap and ArcCatalog should provide robust, intelligent and automated data source management which continually maintains integrity of project’s data structure and maximally assists user in its preservation. This would bring more freedom to the work process and establish more user comfortable environment.

    • Active and permanent source data surveillance – monitoring of current projects and linked data locations throughout the work process. User is warned before the change with direct impact on project’s integrity (add, delete, move or rename). Approved changes are immediately reflected in the map document (sources are automatically updated).
    • Node-based data source manager – intuitive and interactive management of all externally referenced map data (geo, database, layout) and their relationship visualization (like Autodesk Flame, The Foundry Nuke).
    • Broken data links manager – report layers, databases and layout elements with missing data links on MXD open or LYR add. Provide possibility for automatic or manual repair.
    • Intelligent evaluation of the loss of data connection – identify whole or partial loss due to moved/renamed data sources or base folders (absolute/relative mode) or change of map document location (relative mode) when the project is opened or previewed.
    • Automatic search for moved or renamed layers or folders – finds original or similar sources in the neighborhood of missing data with identification and comparison of best matches according to pre-recorded file, geographic, database and metadata properties.
    • Automatic re-creation of entire broken data structure – recover automatically all missing sources according to pre-recorded information about map document and data sources (path, size, date, name…) or by user specified new data position.
    • Layer data source replacement assistant – to help properly update database dependent layer properties (symbology, definition query, labels and joins/relates) and provide smooth transition during the layer source exchange with emphasis on preserving as many layer settings as possible.