SpecChecker - Why are so many elements rejected when they clearly have correct symbology?

SpecChecker - Why are so many elements rejected when they clearly have correct symbology?


By default SpecChecker checks against each element’s actual saved symbology, while ignoring how an element actually displays.

Let’s say you have a rule that rejects elements with color not equal to pink. You look at the elements, and they are displaying pink just as they should. No violation, right? Well.... take a look at the properties of one of those pink elements. What is the color? ByLevel. The ByLevel color may be pink, but that doesn’t mean the element color is pink. The color is ByLevel

If you are okay with the element being ByLevel and not pink, what you can do is tell SpecChecker to test against the elements displayed symbology, rather than the saved symbology.

Below are directions for saving that setting.

  1. Load SpecChecker.

  1. Go to Settings | Change Settings… | General.
  2. Locate the “Symbology:” field, and change the value to “As displayed”.

  1. Press <OK> to return to the main dialog box.
  2. To ensure SpecChecker retains the change, go to Settings | Save Settings.

Now when you process your files, the elements with correctly displayed symbology will not be flagged as violations for their symbology.