Creating an ArcInfo coverage using a mapping table

Cette rubrique concerne exclusivement ArcInfo.

Geodatabase feature classes can be exported to coverages thematically using a mapping table. This allows you to export line and polygon features to the same coverage in predefined groups, rather than manually creating the coverages based on selectable feature layers. For instance, the mapping table can specify that the roads, railroads, and trails are in a transportation coverage; the coastal water and lakes are in a hydrography coverage, and so forth.

You can also specify the workspace in which the coverages are created as well as a cluster tolerance for creating the coverages.

D’origineD’origine :

In previous releases, the coverage mapping file was stored in the DBS_FC_VVT table in your production geodatabase. However the knowledge base is no longer used in Production Mapping.

The coverage mapping table can be a table in any geodatabase, however, it must have the following structure. One row in the table should be created for each feature class in the geodatabase you are exporting. The row must also include the name of the coverage that will be created from that feature class. Feature classes with the same coverage name will be exported to the same coverage.

Étapes :
  1. Start ArcMap.
    ConseilConseil :

    If the ArcMap - Getting Started dialog box appears, you can open a new or existing map document. You can also check the Do not show this dialog box in the future check box and click Open.

  2. If necessary, load data in the map.
  3. If you need to create a mapping table to create the coverages, do the following:
    1. Create a table in the Catalog window or in ArcCatalog.
    2. Add the following fields to the table.

      Field Name

      Field Type

      Description

      OBJECTID

      Object Id

      A unique number that is automatically generated by the database. This identifier is used to reference the source dataset in the DatasetMapping and SourceFields tables.

      FEATURECLASS

      Text

      The name of the feature class in the source geodatabase.

      COVERAGENAME

      Text

      The name of the coverage that will be created when the feature class is exported.

      ConseilConseil :

      Multiple line and polygon feature classes can be exported to the same coverage, but ensure that only one point or annotation feature class is mapped to the same coverage.

  4. On the main menu, click Customize > Toolbars > Production Editing.
  5. On the Production Editing toolbar, click Production Editing > Geodatabase to Coverage.

    The Production Mapping GDBToCoverage: Data Input Mode dialog box appears.

    Production Mapping GDBToCoverage: Data Input Mode dialog box

  6. Choose the Mapping Table option.
  7. Click the ellipsis (...) next to the Mapping Table text box and navigate to the mapping table for the geodatabase you want to export.
  8. Choose the file and click Select.

    The Mapping Table text box is populated with your selection.

  9. Click OK.

    The Please select coverages to create dialog box appears.

    Please select coverages to create

  10. Check the check boxes next to the feature classes and coverages you want to export.

    The names of the feature classes associated with the coverage are displayed in the Feature classes in list.

  11. Click a coverage or feature class name in the list to view its available feature classes.
  12. Click the ellipsis (...) next to the Workspace text box.
  13. Navigate to the workspace to which you want to export the coverages.
  14. Click OK.
  15. Type a value in the Tolerance text box.

    The tolerance is the minimum distance between coordinates before they are considered equal. The value can be higher for data that has less precision and lower for data with high precision.

  16. Click OK.
  17. View the log file.
  18. ConseilConseil :

    Geodatabase line and area feature classes can be exported to a single ArcInfo coverage. The output coverage stores these individual feature classes in route and region subclasses, respectively.

    ConseilConseil :

    Geodatabase point and annotation feature classes must be exported to individual ArcInfo coverages; one coverage per feature class.

Rubriques associées


10/2/2010