FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-70401

Point classification against a polygon with holes: vertex crossing rule · case 01

Points level with a polygon vertex flip between inside and outside.

GIS polygon topology● Open access↗
FA-70402

Point classification against a polygon with holes: vertex crossing rule · case 02

Points level with a polygon vertex flip between inside and outside.

GIS polygon topology◈ Members↗
FA-70403

Point classification against a polygon with holes: vertex crossing rule · case 03

Points level with a polygon vertex flip between inside and outside.

GIS polygon topology◈ Members↗
FA-70404

Point classification against a polygon with holes: vertex crossing rule · case 04

Points level with a polygon vertex flip between inside and outside.

GIS polygon topology◈ Members↗
FA-70405

Point classification against a polygon with holes: vertex crossing rule · case 05

Points level with a polygon vertex flip between inside and outside.

GIS polygon topology◈ Members↗
FA-70406

Point classification against a polygon with holes: segment extent test · case 01

Points on axis-parallel edges and on vertices are not reported as boundary.

GIS polygon topology● Open access↗
FA-70407

Point classification against a polygon with holes: segment extent test · case 02

Points on axis-parallel edges and on vertices are not reported as boundary.

GIS polygon topology◈ Members↗
FA-70408

Point classification against a polygon with holes: segment extent test · case 03

Points on axis-parallel edges and on vertices are not reported as boundary.

GIS polygon topology◈ Members↗
FA-70409

Point classification against a polygon with holes: segment extent test · case 04

Points on axis-parallel edges and on vertices are not reported as boundary.

GIS polygon topology◈ Members↗
FA-70410

Point classification against a polygon with holes: segment extent test · case 05

Points on axis-parallel edges and on vertices are not reported as boundary.

GIS polygon topology◈ Members↗
FA-70411

DE-9IM matrix named predicate evaluation: T wildcard meaning · case 01

Line and point interactions never satisfy predicates that require a non-empty intersection.

GIS polygon topology● Open access↗
FA-70412

DE-9IM matrix named predicate evaluation: T wildcard meaning · case 02

Line and point interactions never satisfy predicates that require a non-empty intersection.

GIS polygon topology◈ Members↗
FA-70413

DE-9IM matrix named predicate evaluation: T wildcard meaning · case 03

Line and point interactions never satisfy predicates that require a non-empty intersection.

GIS polygon topology◈ Members↗
FA-70414

DE-9IM matrix named predicate evaluation: T wildcard meaning · case 04

Line and point interactions never satisfy predicates that require a non-empty intersection.

GIS polygon topology◈ Members↗
FA-70415

DE-9IM matrix named predicate evaluation: T wildcard meaning · case 05

Line and point interactions never satisfy predicates that require a non-empty intersection.

GIS polygon topology◈ Members↗
FA-70416

DE-9IM matrix named predicate evaluation: touches alternatives · case 01

Geometries that meet only boundary-to-boundary are not reported as touching.

GIS polygon topology● Open access↗
FA-70417

DE-9IM matrix named predicate evaluation: touches alternatives · case 02

Geometries that meet only boundary-to-boundary are not reported as touching.

GIS polygon topology◈ Members↗
FA-70418

DE-9IM matrix named predicate evaluation: touches alternatives · case 03

Geometries that meet only boundary-to-boundary are not reported as touching.

GIS polygon topology◈ Members↗
FA-70419

DE-9IM matrix named predicate evaluation: touches alternatives · case 04

Geometries that meet only boundary-to-boundary are not reported as touching.

GIS polygon topology◈ Members↗
FA-70420

DE-9IM matrix named predicate evaluation: touches alternatives · case 05

Geometries that meet only boundary-to-boundary are not reported as touching.

GIS polygon topology◈ Members↗
FA-70421

DE-9IM matrix named predicate evaluation: touches point pair exclusion · case 01

Two points are reported as touching.

GIS polygon topology● Open access↗
FA-70422

DE-9IM matrix named predicate evaluation: touches point pair exclusion · case 02

Two points are reported as touching.

GIS polygon topology◈ Members↗
FA-70423

DE-9IM matrix named predicate evaluation: touches point pair exclusion · case 03

Two points are reported as touching.

GIS polygon topology◈ Members↗
FA-70424

DE-9IM matrix named predicate evaluation: touches point pair exclusion · case 04

Two points are reported as touching.

GIS polygon topology◈ Members↗
FA-70425

DE-9IM matrix named predicate evaluation: touches point pair exclusion · case 05

Two points are reported as touching.

GIS polygon topology◈ Members↗
FA-70426

DE-9IM matrix named predicate evaluation: overlaps dimension pattern · case 01

Lines that meet at a single crossing point are reported as overlapping.

GIS polygon topology● Open access↗
FA-70427

DE-9IM matrix named predicate evaluation: overlaps dimension pattern · case 02

Lines that meet at a single crossing point are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70428

DE-9IM matrix named predicate evaluation: overlaps dimension pattern · case 03

Lines that meet at a single crossing point are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70429

DE-9IM matrix named predicate evaluation: overlaps dimension pattern · case 04

Lines that meet at a single crossing point are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70430

DE-9IM matrix named predicate evaluation: overlaps dimension pattern · case 05

Lines that meet at a single crossing point are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70431

DE-9IM matrix named predicate evaluation: overlaps equal dimension guard · case 01

A line lying partly inside a polygon is reported as overlapping it.

GIS polygon topology● Open access↗
FA-70432

DE-9IM matrix named predicate evaluation: overlaps equal dimension guard · case 02

A line lying partly inside a polygon is reported as overlapping it.

GIS polygon topology◈ Members↗
FA-70433

DE-9IM matrix named predicate evaluation: overlaps equal dimension guard · case 03

A line lying partly inside a polygon is reported as overlapping it.

GIS polygon topology◈ Members↗
FA-70434

DE-9IM matrix named predicate evaluation: overlaps equal dimension guard · case 04

A line lying partly inside a polygon is reported as overlapping it.

GIS polygon topology◈ Members↗
FA-70435

DE-9IM matrix named predicate evaluation: overlaps equal dimension guard · case 05

A line lying partly inside a polygon is reported as overlapping it.

GIS polygon topology◈ Members↗
FA-70436

DE-9IM matrix named predicate evaluation: covers alternatives · case 01

A polygon does not cover a line that lies on its boundary.

GIS polygon topology● Open access↗
FA-70437

DE-9IM matrix named predicate evaluation: covers alternatives · case 02

A polygon does not cover a line that lies on its boundary.

GIS polygon topology◈ Members↗
FA-70438

DE-9IM matrix named predicate evaluation: covers alternatives · case 03

A polygon does not cover a line that lies on its boundary.

GIS polygon topology◈ Members↗
FA-70439

DE-9IM matrix named predicate evaluation: covers alternatives · case 04

A polygon does not cover a line that lies on its boundary.

GIS polygon topology◈ Members↗
FA-70440

DE-9IM matrix named predicate evaluation: covers alternatives · case 05

A polygon does not cover a line that lies on its boundary.

GIS polygon topology◈ Members↗
FA-70441

Bounding box topological relation: equality test · case 01

Boxes that merely share a lower-left corner are reported as equal.

GIS polygon topology● Open access↗
FA-70442

Bounding box topological relation: equality test · case 02

Boxes that merely share a lower-left corner are reported as equal.

GIS polygon topology◈ Members↗
FA-70443

Bounding box topological relation: equality test · case 03

Boxes that merely share a lower-left corner are reported as equal.

GIS polygon topology◈ Members↗
FA-70444

Bounding box topological relation: equality test · case 04

Boxes that merely share a lower-left corner are reported as equal.

GIS polygon topology◈ Members↗
FA-70445

Bounding box topological relation: equality test · case 05

Boxes that merely share a lower-left corner are reported as equal.

GIS polygon topology◈ Members↗
FA-70446

Bounding box topological relation: separation strictness · case 01

Boxes sharing an edge or corner are reported as disjoint.

GIS polygon topology● Open access↗
FA-70447

Bounding box topological relation: separation strictness · case 02

Boxes sharing an edge or corner are reported as disjoint.

GIS polygon topology◈ Members↗
FA-70448

Bounding box topological relation: separation strictness · case 03

Boxes sharing an edge or corner are reported as disjoint.

GIS polygon topology◈ Members↗
FA-70449

Bounding box topological relation: separation strictness · case 04

Boxes sharing an edge or corner are reported as disjoint.

GIS polygon topology◈ Members↗
FA-70450

Bounding box topological relation: separation strictness · case 05

Boxes sharing an edge or corner are reported as disjoint.

GIS polygon topology◈ Members↗
FA-70451

Bounding box topological relation: containment with shared edges · case 01

A box flush against the inside of another is not reported as contained.

GIS polygon topology● Open access↗
FA-70452

Bounding box topological relation: containment with shared edges · case 02

A box flush against the inside of another is not reported as contained.

GIS polygon topology◈ Members↗
FA-70453

Bounding box topological relation: containment with shared edges · case 03

A box flush against the inside of another is not reported as contained.

GIS polygon topology◈ Members↗
FA-70454

Bounding box topological relation: containment with shared edges · case 04

A box flush against the inside of another is not reported as contained.

GIS polygon topology◈ Members↗
FA-70455

Bounding box topological relation: containment with shared edges · case 05

A box flush against the inside of another is not reported as contained.

GIS polygon topology◈ Members↗
FA-70456

Bounding box topological relation: within operand completeness · case 01

A box poking out of the top of another is reported as within.

GIS polygon topology● Open access↗
FA-70457

Bounding box topological relation: within operand completeness · case 02

A box poking out of the top of another is reported as within.

GIS polygon topology◈ Members↗
FA-70458

Bounding box topological relation: within operand completeness · case 03

A box poking out of the top of another is reported as within.

GIS polygon topology◈ Members↗
FA-70459

Bounding box topological relation: within operand completeness · case 04

A box poking out of the top of another is reported as within.

GIS polygon topology◈ Members↗
FA-70460

Bounding box topological relation: within operand completeness · case 05

A box poking out of the top of another is reported as within.

GIS polygon topology◈ Members↗
FA-70461

Bounding box topological relation: touching sides · case 01

Boxes stacked vertically are reported as overlapping.

GIS polygon topology● Open access↗
FA-70462

Bounding box topological relation: touching sides · case 02

Boxes stacked vertically are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70463

Bounding box topological relation: touching sides · case 03

Boxes stacked vertically are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70464

Bounding box topological relation: touching sides · case 04

Boxes stacked vertically are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70465

Bounding box topological relation: touching sides · case 05

Boxes stacked vertically are reported as overlapping.

GIS polygon topology◈ Members↗
FA-70466

TopoJSON arc stitching into rings: reversed arc index · case 01

Reversed arcs pull in the neighbouring arc.

GIS polygon topology● Open access↗
FA-70467

TopoJSON arc stitching into rings: reversed arc index · case 02

Reversed arcs pull in the neighbouring arc.

GIS polygon topology◈ Members↗
FA-70468

TopoJSON arc stitching into rings: reversed arc index · case 03

Reversed arcs pull in the neighbouring arc.

GIS polygon topology◈ Members↗
FA-70469

TopoJSON arc stitching into rings: reversed arc index · case 04

Reversed arcs pull in the neighbouring arc.

GIS polygon topology◈ Members↗
FA-70470

TopoJSON arc stitching into rings: reversed arc index · case 05

Reversed arcs pull in the neighbouring arc.

GIS polygon topology◈ Members↗
FA-70471

TopoJSON arc stitching into rings: reversal application · case 01

Rings that use an arc backwards jump across the shape.

GIS polygon topology● Open access↗
FA-70472

TopoJSON arc stitching into rings: reversal application · case 02

Rings that use an arc backwards jump across the shape.

GIS polygon topology◈ Members↗
FA-70473

TopoJSON arc stitching into rings: reversal application · case 03

Rings that use an arc backwards jump across the shape.

GIS polygon topology◈ Members↗
FA-70474

TopoJSON arc stitching into rings: reversal application · case 04

Rings that use an arc backwards jump across the shape.

GIS polygon topology◈ Members↗
FA-70475

TopoJSON arc stitching into rings: reversal application · case 05

Rings that use an arc backwards jump across the shape.

GIS polygon topology◈ Members↗
FA-70476

TopoJSON arc stitching into rings: delta accumulation · case 01

Decoded arcs collapse around the origin.

GIS polygon topology● Open access↗
FA-70477

TopoJSON arc stitching into rings: delta accumulation · case 02

Decoded arcs collapse around the origin.

GIS polygon topology◈ Members↗
FA-70478

TopoJSON arc stitching into rings: delta accumulation · case 03

Decoded arcs collapse around the origin.

GIS polygon topology◈ Members↗
FA-70479

TopoJSON arc stitching into rings: delta accumulation · case 04

Decoded arcs collapse around the origin.

GIS polygon topology◈ Members↗
FA-70480

TopoJSON arc stitching into rings: delta accumulation · case 05

Decoded arcs collapse around the origin.

GIS polygon topology◈ Members↗
FA-70481

TopoJSON arc stitching into rings: transform order · case 01

Decoded coordinates are offset by the translate times the scale.

GIS polygon topology● Open access↗
FA-70482

TopoJSON arc stitching into rings: transform order · case 02

Decoded coordinates are offset by the translate times the scale.

GIS polygon topology◈ Members↗
FA-70483

TopoJSON arc stitching into rings: transform order · case 03

Decoded coordinates are offset by the translate times the scale.

GIS polygon topology◈ Members↗
FA-70484

TopoJSON arc stitching into rings: transform order · case 04

Decoded coordinates are offset by the translate times the scale.

GIS polygon topology◈ Members↗
FA-70485

TopoJSON arc stitching into rings: transform order · case 05

Decoded coordinates are offset by the translate times the scale.

GIS polygon topology◈ Members↗
FA-70486

TopoJSON arc stitching into rings: identity transform default · case 01

Unquantized topologies decode every position to the origin.

GIS polygon topology● Open access↗
FA-70487

TopoJSON arc stitching into rings: identity transform default · case 02

Unquantized topologies decode every position to the origin.

GIS polygon topology◈ Members↗
FA-70488

TopoJSON arc stitching into rings: identity transform default · case 03

Unquantized topologies decode every position to the origin.

GIS polygon topology◈ Members↗
FA-70489

TopoJSON arc stitching into rings: identity transform default · case 04

Unquantized topologies decode every position to the origin.

GIS polygon topology◈ Members↗
FA-70490

TopoJSON arc stitching into rings: identity transform default · case 05

Unquantized topologies decode every position to the origin.

GIS polygon topology◈ Members↗
FA-70491

TopoJSON arc stitching into rings: junction de-duplication · case 01

Stitched rings lose their closing vertex and contain doubled junctions.

GIS polygon topology● Open access↗
FA-70492

TopoJSON arc stitching into rings: junction de-duplication · case 02

Stitched rings lose their closing vertex and contain doubled junctions.

GIS polygon topology◈ Members↗
FA-70493

TopoJSON arc stitching into rings: junction de-duplication · case 03

Stitched rings lose their closing vertex and contain doubled junctions.

GIS polygon topology◈ Members↗
FA-70494

TopoJSON arc stitching into rings: junction de-duplication · case 04

Stitched rings lose their closing vertex and contain doubled junctions.

GIS polygon topology◈ Members↗
FA-70495

TopoJSON arc stitching into rings: junction de-duplication · case 05

Stitched rings lose their closing vertex and contain doubled junctions.

GIS polygon topology◈ Members↗
FA-70496

Rook and queen polygon adjacency: edge direction normalisation · case 01

Neighbouring polygons with the same winding are never rook-adjacent.

GIS polygon topology● Open access↗
FA-70497

Rook and queen polygon adjacency: edge direction normalisation · case 02

Neighbouring polygons with the same winding are never rook-adjacent.

GIS polygon topology◈ Members↗
FA-70498

Rook and queen polygon adjacency: edge direction normalisation · case 03

Neighbouring polygons with the same winding are never rook-adjacent.

GIS polygon topology◈ Members↗
FA-70499

Rook and queen polygon adjacency: edge direction normalisation · case 04

Neighbouring polygons with the same winding are never rook-adjacent.

GIS polygon topology◈ Members↗
FA-70500

Rook and queen polygon adjacency: edge direction normalisation · case 05

Neighbouring polygons with the same winding are never rook-adjacent.

GIS polygon topology◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗