Defining the aeronautical properties

Once the product library and production database are created, your client machine needs to be set to point to these databases on the Production Properties dialog box, and other properties need to be set.

Setting the product library workspace

The product library is a geodatabase that allows multiuser environments to centralize information and behavior for cartographic and digital data production.

Steps:

1. Start ArcMap.
2. On the main menu, click Customize > Production > Production Properties.

   The Production Properties dialog box appears.

3. If necessary, click Data Management.
4. Click the cell next to Workspace in the Product Library section and click the ellipsis (...) that appears.

   The Please browse to the location of the Product Library Workspace dialog box appears.

5. Navigate to the product library database.
6. Click Open.
   Note:

   The Upgrade Workspace dialog box appears if the geodatabase does not have all the components necessary to perform as a product library. Click OK if you want to upgrade the geodatabase you want to use as the product library and click OK once the upgrade completes.

   Tip:

   If this is not a new product library, and if an error appears when you choose a geodatabase as the product library, it may need to be compacted or compressed to restore its integrity. Compacting applies to personal and file geodatabases, and compressing applies to ArcSDE geodatabases.

   The path to the product library appears in the cell next to Workspace, and the Privileges and Workspace Type fields are automatically populated.

   Note:

   The product library workspace can be unset by deleting the path to the workspace out of the cell next to Workspace.

Setting the production database workspace

The production database is the primary database that contains the geographic data that can be used directly or to create and maintain the charts, maps, and cells for production.

Steps:

1. If necessary, click the cell next to Auto Update.
2. If necessary, click the drop-down arrow that appears and choose False.
3. Click the plus sign (+) next to Production Database.
4. Click the cell next to Workspace in the Production Database section and click the ellipsis (...) that appears.

   The Please browse to the location of the production database Workspace dialog box appears.

5. Navigate to the database that contains the data for your map or chart.
6. Click Open.
   Tip:

   The Upgrade Workspace dialog box appears if the geodatabase does not have all the components necessary to perform as a production database. Click OK if you want to upgrade the geodatabase you want to use as the production database and click OK once the upgrade completes.

   The path to the production database appears in the cell next to Workspace, and the Privileges and Workspace Type fields are automatically populated.

Setting the data model versions

Depending on the project or projects your organization is working on, you may have a product library that supports several different data models. The data models contain different structures that can be applied to your database for the type of data you want to create or with which you are working.

Steps:

1. Click the plus sign (+) next to Data Model Version.
2. Click the cell next to Set Data Model Versions and click the ellipsis (...) that appears.

   The Choose Data Model Versions dialog box appears.
3. Check the check boxes next to the database schemas you want to associate with a production database.
4. Click OK.
5. Click the Current Model Version drop-down arrow and choose the model version you want to use.
   Note:

   All model versions supported appear in the drop-down options, but if the model is not installed, you will receive a message saying the model is not installed.

Setting the product class version

Product classes are types of geographic products designed for a particular use, typically unique groups of maps, charts, or digital data that share common properties. There can be several product classes associated with each solution. Product class versions can be created to accommodate different versions of a product class with which you are working.

Steps:

1. Click the plus sign (+) next to Product Class Version.
2. Click the cell next to Product Class Versions and click the ellipsis (...) that appears.

   The Choose Product Class Versions dialog box appears.
3. Check the check boxes next to the product classes you can produce in your production database.
4. Click OK.

   The Production Properties dialog box appears.

5. Click the cell next to Current Product Class Version.
6. Click the drop-down arrow and choose the product class that matches the data you are currently using.
7. Click Apply to set the properties.

Setting the instances maintained

The instances maintained are a configurable list of charts maintained at that location or database. This allows databases to avoid filling up by only maintaining cartographic features for charts maintained at a particular facility or by a specific group.

Steps:

1. Click the cell next to Set Tool Options.
2. Click the drop-down arrow that appears.
3. Click the ellipsis (...) next to Instances Maintained.

   The Instances Maintained dialog box appears.

   
Tip:

You can also open the Instances Maintained dialog box if you navigate to an instance in the product library tree, right-click, then choose Set Instances Maintained.

4. Navigate to the product instances you want to associate with the production database in the Select Instances tree view.

   This is the last level of the tree view.

5. Check the check box next to the product instance you want to associate with the production database.
6. Repeat steps 4–5 for each product instance you want to associate with the production database.
7. To automatically expand the tree view to the instances you have selected, check the Expand to saved instances automatically check box.
8. Click OK when you are finished.

   The Data Management pane appears.

9. Click OK.
   Tip:

   You can associate each product instance with the map document data frame to allow the map document to open the instance with the corresponding production database.