Upon generating analytics for the 4.2 release, we found that several datasets failed to run, and we assume that's because of the new trip_distance_exceeds_shape_distance error.
These datasets failed with the message The configured memory limit was reached:
In the memory reduction design & analysis document, it's mentioned that there's a significant amount of memory usage from the TripAndShapeDistanceValidator. This should be further investigated.
Describe the bug
Upon generating analytics for the 4.2 release, we found that several datasets failed to run, and we assume that's because of the new
trip_distance_exceeds_shape_distance
error.These datasets failed with the message
The configured memory limit was reached
:These datasets failed with the message
Timeout of 1800 seconds exceeded
:This dataset failed with the message
connection broken
:We should further investigate and identify possible performance improvements to this notice. Relates to #1589
Steps/Code to Reproduce
Expected Results
Actual Results
Feed fails to parse.
Screenshots
No response
Files used
No response
Validator version
4.2
Operating system
MacOS
Java version
No response
Additional notes
No response