The data model schemas used with ArcGIS for Aviation: Charting contain the feature classes, tables, and relationships for primary data storage as well as tables and feature classes to support cartography.
The schema is stored in a configuration file with the extension .xml—AIS_GX_WGS84.xml. The XML file is applied to the geodatabase using the Create Aviation Geodatabase geoprocessing tool. The tables and feature classes for storing the cartographic information are named with the suffix _C. Cartographic feature classes contain attribution needed for cartography on a particular chart. A master feature may be associated with one or many cartographic features depending on how many charts the feature will appear.
Setting up the AIS entails the procedures described below.
Creating the product library
The product library stores and manages configuration components of the software and is referenced by many tools in Aviation Charting. You, or a database administrator, should create the product library.
Included in the product library database are the masking rules tables, rules for applying visual specifications, views, and more. The product library stores information about the charts, including the extents, that will be produced and are accessed from a tree structure.
The product library is a series of tables for a given product class (for example, Enroute) that allows the organizational setup of a production environment and/or hard-copy map production.
To establish a product library, you or a database administrator must first create a new product class in the Product Library tree. At a minimum, the name field should be populated. Upon creating the product class, a series of tables and feature classes (PL_<name>_Series, PL_<name>_Product, PL_<name>_Instance, and PL_<name>_AOI) are created.
In each of the PL tables, a PARENTID field exists that must contain the GFID of its parent. This parent/child relationship must be maintained throughout the product library table structure down to the Area of Interest (AOI) level.
Creating the production database
The production database is the basic data storage or production database and is central to all users. You or a database administrator should create the production database using the Create Aviation Geodatabase tool.
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. It is built from a valid Aviation Charting data model.
The geoprocessing tool enables versioning and geodatabase archiving on the production database. Geodatabase archiving is ArcGIS functionality to maintain an archive of all changes to a geodatabase. Through archiving, it is possible to view data as it existed at any point in the past.
The Change Reporter tool within Aviation Charting reads the archive tables and allows you to specify a date range and view a list of all changes made between those dates. It is beneficial in chart maintenance to view the changes made since the last chart production cycle.
Defining the 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.
Configuring validation
ArcGIS Data Reviewer for Desktop can be used for data control and quality management that helps identify where geometric corrections, extraneous feature edits, and feature attribution changes must be made to the spatial data and its attributes, as well as digitize the locations of missing features.