Overview

Depending on the source data and how you define the helper maps, it is very easy to add vehicle attributes to mapped applications that are not necessary. For example, you might have an Engine on an application where that is the only Engine available for that model year. AceMapper Compression is used to remove these unnecessary attributes.

Note that the compression process can be reversed by “rolling back” or by dropping all mapped applications and re-creating them.

Compression Logic:

The following describes how AceMapper removes redundant attributes and re-writes mapped applications.

1. Build a cross product, based on the attribute families on applications in a group of basevehicle/part type/position and mfrlabel.

2. Look for a single family that keeps all the applications distinct (for each attribute in the family, all applications have the same part, notes, qualifiers and mfrlabel and no other attribute in the family has the same part, notes and qualifiers).

3. If no single family is found, it looks for combinations of two families and so on.

In some cases, a single family is sufficient for one application, but not for all. In that case, that single family is locked in for all applications on the basevehicle/part type/position and mfrlabel.