{
  "title": "Geophysical survey line and seismic trace metadata for AI",
  "source_page": "https://fiund.com/industries/geophysical-profile-trace-metadata-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Overlapping trace numbers do not identify the survey line",
    "context": "Synthetic trace cards and original profile diagrams use abstract coordinates and timing units. No actual seismic signal, acreage, field operation or confidential interpretation is supplied.",
    "records": [
      [
        "GPF1",
        "Dummy line headers",
        "Line L1/day A traces 1–5, time unit U. Line L2/day B also traces 1–5, time unit V."
      ],
      [
        "GPF2",
        "Profile export P1",
        "Explicitly links L1 traces 1–3 under U; traces 4–5 omitted from the exported range."
      ],
      [
        "GPF3",
        "Unassigned profile P2",
        "Shows trace labels 1–3, but line, date and timing unit missing. No U-to-V equivalence supplied."
      ]
    ],
    "question": "What source and missing interval are documented for P1, and can P2 be assigned or compared by trace numbers alone?",
    "answer": "GPF2 traces P1 to L1/day A under U and explicitly leaves L1 traces 4–5 outside its export. GPF3's 1–3 labels also occur in L2, so they do not establish its line or date. Its missing timing basis additionally prevents a supported U/V comparison. Preserve line, acquisition date, trace range and units instead of treating a visually complete profile or repeated trace numbers as full source coverage.",
    "failureModes": [
      "Joining profiles across lines using trace number alone.",
      "Interpreting an omitted export interval as a missing physical observation or ignoring an unknown timing unit."
    ],
    "fields": [
      [
        "Line, date and trace key",
        "Disambiguates overlapping numbering."
      ],
      [
        "Export range versus source range",
        "Shows which records were actually included."
      ],
      [
        "Timing unit and convention",
        "Limits cross-profile comparison."
      ]
    ],
    "holdout": "Link P2 to L2 but leave its timing unit absent. Require identity to resolve while comparison basis remains incomplete.",
    "boundary": "Use original synthetic traces and abstract geometry. Exclude acreage, concessions, operational maps and client interpretation."
  }
}