Skip to content

§20 family: Polylines, vertices and meshes (§20.4.11 to §20.4.17, §20.4.33, §20.4.34, §20.4.85) #142

Open
2 of 2 issues completed

Description

@DrunkOnJava

Spec: ODA Open Design Specification for .dwg files v5.4.1, §20.4.11, §20.4.12, §20.4.13, §20.4.14, §20.4.15, §20.4.16, §20.4.17, §20.4.33, §20.4.34, §20.4.85.

Sections and their state on main (2026-10-21)

Section State Code Note
§20.4.11 VERTEX (2D) (10) (p. 114) closes src/entities/vertex.rs
§20.4.12 VERTEX (3D) (11) (p. 115) closes src/entities/vertex.rs
§20.4.13 VERTEX (MESH) (12) (p. 115) closes src/entities/vertex.rs
§20.4.14 VERTEX (PFACE) (13) (p. 116) closes src/entities/vertex.rs
§20.4.15 VERTEX (PFACE FACE) (14) (p. 116) closes src/entities/vertex.rs
§20.4.16 2D POLYLINE (15) (p. 116) closes src/entities/polyline.rs
§20.4.17 3D POLYLINE (16) (p. 117) closes src/entities/polyline.rs
§20.4.33 POLYLINE (PFACE) (29) (p. 129) closes src/entities/polyface_mesh.rs
§20.4.34 POLYLINE (MESH) (30) (p. 130) closes src/entities/polygon_mesh.rs
§20.4.85 LWPLINE (p. 204) closes src/entities/lwpolyline.rs

closes comes from the boundary checks on the local 19-file corpus (STATUS.md, 2026-08-30). It is re-measured on the public corpus in CI by the 0.2.0 measurement epic, and no section is complete until its values equal AutoCAD's own DXF export.

Acceptance, for every section above

  • Every field of its prescription is read, with every version branch the section names
  • Where the section prints an example, its bytes are a committed fixture and decode to the values printed
  • The field list ends on the record's exact data-stream boundary (and string/handle-stream boundaries on R2007+) on every corpus record of the type, on every release band
  • Every value equals AutoCAD's DXF export of the same drawing, matched by handle (DXF group 5), with the scorer from the oracle epic
  • The corpus holds at least one record of the type on each release band, R13 to R2018; a band without one is recorded on the corpus epic, not assumed
  • Its row in docs/spec-coverage.md moves to complete, with the evidence linked

Subtasks

  • §20.4.11 VERTEX (2D) (10)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.12 VERTEX (3D) (11)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.13 VERTEX (MESH) (12)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.14 VERTEX (PFACE) (13)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.15 VERTEX (PFACE FACE) (14)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.16 2D POLYLINE (15)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.17 3D POLYLINE (16)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.33 POLYLINE (PFACE) (29)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.34 POLYLINE (MESH) (30)
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018
  • §20.4.85 LWPLINE
    • R13
    • R14
    • R2000
    • R2004
    • R2007
    • R2010
    • R2013
    • R2018

A subtask becomes its own issue when someone picks it up; that issue quotes the section's field list and names the corpus records it is measured on.

Parent: #138

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:entitiesEntity prescriptions in spec §20.4priority:P1On the path of the current milestonetype:specImplements or verifies a numbered section of ODA spec v5.4.1

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions