Essential product library vocabulary
AOI
AOI stands for Area of Interest. See Area of interest.
Area of interest
A polygon feature that represents the specific geographic extent of the instance. This could be an index feature from a feature class that contains all the chart or map extents for a region or the world. Examples include a country, region, or area based on an index of map extents. Area of interest is abbreviated as AOI.
For the Nautical Solution, an AOI represents the geometry that defines the area of data coverage and no coverage for a particular ENC product, or the extent of a particular panel for a chart product.
 |
AOI 1 and AOI 2 come together to form an ENC product. |
 |
AOI 1 and AOI 2 come together to form a Chart product. |
Associated batch job
A collection of database validation rules that will be applied to the production database when features are created or edited.
Conflict
When you check a product back into the product library, there can be occasions where there are conflicts between the properties of the map document being checked in and the values stored in the product library for the product's instance and area of interest properties.
Learn more about conflicts with the product library and how to resolve them
Data model
An Extensible Markup Language (XML) workspace document that contains the structure that can be applied to your database for the type of data or map/chart you want to create or with which you are working.
The structure is a theoretical schema constructed of feature classes and attributes used to codify real-world phenomena in a consistent fashion, such as polygons that represent states, points that represent cities, and lines that represent roads. Learn more about data model.
 |
Nautical data model |
Data Model Version
A data model contains the structure of your database for the type of data with which you are working. When changes occur to your data model or you have a new type of data, a new version of the data model should be created. Many tools that interact with product library use the data model version set as the default data model version to determine how they should behave.
Extraction query
A SQL statement where clause that allows you to determine which features are extracted into products, instances, or areas of interest, which are going to be included on your products. Extraction queries are only available with the Nautical Solution and the Aeronautical Solution.
During the Populate Instance(s) process, data is extracted from the central database repository (NIS) to a production database using the parameters set by the where clauses.
 |
Field configuration
Defines custom Production Mapping properties about your fields. This can be how the field is displayed in tool dialog boxes such as Feature Manager, what type of control is used to edit the field, or if the field is considered feature-level metadata. Field configuration can also be used to determine which attributes will be used when dissolving features with the Production Dissolve tool and how the other attributes will be populated. Field configurations are created using Field Configuration Manager and are stored in the product library.
Implement Instance(s)
The action described when clicking the Implement Instance(s) command in Product Library. The Nautical Solution creates a SQL Express database with the schema that is found in the XML file.
 |
Implement Instance |
Instance
A geographic extent on a product. An instance is associated with a data frame on the map document. A product can have one or more instances on it, which means it can also have more than one data frame (one for each instance). The instance can contain the main map data or be used as an inset.
Populate Instance(s)
The action described when clicking the Populate Instance(s) command in product library. In the Nautical Solution, it extracts data from the production database, cleans the data, sets up versions on the product database, and creates the replica definitions.
Product
One of the individual maps, charts, or cells of geographic data being created (the map document, or .mxd file). Products are the primary deliverable from the production system. They are represented as individual map documents and the data they display. A product is part of both a product class and series and can consist of one or more product instances.
For example, a nautical chart can consist of many panels (data frames).
Product class
A type of geographic product designed for a particular use, typically unique types of maps, charts, or digital data that share common properties.
Examples include Topographic Line Maps (TLMs), AP1B, and Electronic Navigational Charts (ENCs).
The complete grouping of all individual products that fulfill a single navigation/orientation purpose. All products within a class share rules and features that define how and what type of data will be produced to meet the defined specific navigation/orientation need. Product classes are made up of one or more series.
Product Class Version
A product class is a type of geographic product designed for a particular use. When changes occur to the product class or to the data that is used to create a product, a new version of the product class may need to be created. Many tools that interact with the product library use the product class version set as the default product class version to determine how they should behave.
Production database
A production database contains the data you are using for production tasks such as creating and updating features. Depending on the data model you are using, data in a production database can be used to create a digital or hard-copy map or chart or a specific type of data. The data in a production database usually corresponds with a data model and product class in the product library.
For the Nautical Solution, a production database is the instance database that contains a replica of the data for a specific instance.
Product library
Geodatabase that allows multiuser environments to centralize information and behavior for cartographic and digital data production. Production business rules, documents, and spatial information are stored inside the product library, allowing an organization to enforce and standardize production. Data model information, data validation rules, geographic extents, symbology rules, and map documents can all be managed inside product library as examples of production business rules.
Series
A subgrouping of a product class based on a common geographic area or presentation style. A series is useful for subdividing product classes that have a large number of products. Some common geographic series can be based on a state, country, or any part thereof. A series could also be defined based on appearance such as a common page size or layout for a product class that produces maps.
Solution
The name of the specific projects or industry grouping that corresponds with the products being created. This could also match the name of one of the ESRI mapping and charting solutions that is installed or a project.
Update Instance(s)
A command in the product library. In the Nautical Solution, this creates a disconnected sync file for the CM and URGENT replicas that are stored in the product library.
XML workspace
The XML document that can be imported into a geodatabase. It contains one or more geodatabase feature datasets, feature classes, and tables. It can include schema and data or just the schema.
It serves as the template geodatabase for the NIS, ENC, AML, and Chart databases. These XML files are either manually or automatically imported, using the implement process in the product library, prior to populating a database.