Description

As part of the investigation of #1587, we came across a feed to ~40M of shapes to validate. The current validator's implementation needs to be optimized to handle large feeds; see #1358. The recently merged #1553 introduced validation on shapes that expands resource usage on the validator. As a temporary solution until #1358 provides a better way to manage large files, we propose limiting the number of the shapes that trip_distance_exceeds_shape_distance's validator supports.

Tasks:

• Investigate an approximate higher number of shapes that trip_distance_exceeds_shape_distance can support.
• Implement logic to skip the validator when the shape count is above the limit and log why the validator is being skipped.
• Add the validator to the list of validators that didn't run due to limit