Export Generalized Data (Topographic Production Tools)
Summary
Exports data generalized by the ArcGIS Topographic Mapping theme-based generalization models into a production schema using generalization rules defined in a Microsoft Excel spreadsheet.
Note:
A product file installer is available for ArcGIS Topographic Mapping. The product files contain predefined generalization XLSM rule files, but the tool supports both XLSX and XLSM formats.
Usage
The Input Geodatabase will contain the theme generalization feature classes created by the Import Generalization Data tool. Before running this tool, the Topographic Mapping generalization models for the data theme will be run on this database. The Target Geodatabase should be the same geodatabase that was used as the source for Input Geodatabase when the Import Generalization Data tool was run.
Before the generalized features are loaded into the Target Geodatabase, the source features are deleted to ensure that there are not multiple representations of the same real-world object in the target geodatabase.
The data theme determines which feature classes in the Input Geodatabase contain the features that will be loaded into the target geodatabase.
The Generalization Rule File contains the logic for mapping the generalized theme data back to your production schema.
Once a set of data is generalized, it can be used during the generalization of other datasets. This tool loads the generalized data back into the production geodatabase, so it can be used during different stages of the generalization process.
You can customize the generalization process using the spreadsheet without modifying the complex geoprocessing models that will perform the generalization.
While running the generalization models, some generalization tools assign a value of 1 to a visibility field to identify features that should be removed from the display at the output scale. The Export only visible features parameter can be used to specify whether only visible features will be exported, or all the features will be exported, regardless of their visibility. When running fully-automated generalization, you will most likely choose to export only visible features as this means fewer features will be included in the final database. If manual cartographic finishing is part of your generalization process, you can choose to keep the hidden features, so they can be made visible again at the discretion of the cartographer.
The Generalization Rule File parameter defines the visibility field used by the Export only visible features parameter.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input Geodatabase |
The geodatabase containing data in the generalization schema. |
Workspace |
|
Target Geodatabase |
The geodatabase where the generalized data will be loaded. |
Workspace |
|
Generalization Rule File |
The Excel file containing the generalization rules. This file defines features participating in the generalization process and determines the data that will be loaded and how it is organized. An example rule file is provided in the product file downloads for Topographic Mapping. |
File |
|
Data Theme |
A theme that specifies the type of data to be generalized. Available themes are automatically populated from the Generalization Rule File parameter. The values provided in the example rule file are as follows:
|
String |
|
Export only visible features (Optional) |
Specifies whether features with a value of 1 in the visibility field will be exported to the target database.
|
Boolean |
Derived output
| Label | Explanation | Data type |
|---|---|---|
|
Updated Geodatabase |
The updated target geodatabase. |
Workspace |
Environments
This tool does not use any geoprocessing environments.
Licensing information
- Basic: No
- Standard: Requires Topographic Mapping
- Advanced: Requires Topographic Mapping