Validating Soil Landscapes of Canada (SLC) version 2.2

The following validation procedures were applied prior to the release of SLC version 2.2.

Polygons
Type Description Process
completeness coverage must be all of Canada
  • map and visual check
lineage polygon boundaries must be similar to previous versions
  • map SL differences and spot check

PAT
Type Description Process
completeness SL must exist for every record in the PAT
  • frequency
logical consistency polygons should have the correct SL code
  • map SL numbers and spot check

LAT
Type Description Process
completeness there must be 1 record in the LAT for every SL in the PAT
  • join LAT to PAT
  • join PAT to LAT
logical consistency percent totals correct
  • sum percentages by SL
attribute accuracy sum of areas must be area of polygon
  • check area with PAT area
attribute accuracy total areas must be reasonable
  • compare totals with published totals

CMP
Type Description Process
completeness there must be a record in the CMP for every SL which is not 100% water
  • join CMP to PAT
  • join PAT to CMP
attribute coding Check that all items contain only valid codes
  • link valid field contents (from CAN001) to each record
logical consistency CMP percentages must total 100% for each SL
  • frequency
logical consistency attributes for each record must be able to co-exist For each item,
  • manual check
  • link valid field associations (CAN002) to each record
attribute accuracy derived maps should be similar to previous versions For each item,
  • map dominant attributes
  • random manual spot check comparison to previous versions
  • spot check areas where problems were known or changes were made

CLYR
Type Description Process
completeness there must be a record in the CLYR for every soil component
  • identify soil components (KINDMAT = SO or OR), then check linkage to CMP
  • check linkage in reverse
attribute coding Check that all items contain only valid codes
  • link valid field contents (from CAN001) to each record
logical consistency attributes for each record must be able to co-exist For each item,
  • manual check
  • link valid field associations (CAN002) to each record
logical consistency depth must total less than 1.2m
  • frequency
attribute accuracy derived maps should be similar to previous versions For each item,
  • map dominant attributes
  • random manual spot check comparison to previous versions
  • spot check areas where problems were known or changes were made

Documentation
Type Description Process
completenessall tables and items are documented
  • manual check