How is well spacing calculated?

Overview

Well spacing — the lateral distance between a subject wellbore and its nearest neighboring wellbores — is one of the most practically significant metrics in modern unconventional resource development.

• Tighter spacing can drive interference and pressure depletion between wells
• Wider spacing may leave recoverable resource behind

Computing accurate spacing depends less on mathematical complexity and more on the quality, completeness, and consistency of the underlying well data.

What We Measure

Spacing is represented through multiple calculated relationships. For each horizontal well, we compute up to eight distinct spacing relationships, each answering a different operational question:

• Closest Offset Well: Nearest lateral wellbore in any formation on either side of the subject well
• Closest Inverse Offset Well: Nearest lateral on the opposite side of the subject well
• Closest Offset Well in Formation: Nearest lateral targeting the same formation
• Closest Inverse Offset Well in Formation: Opposite-side equivalent within the same formation
• Closest Vertical Well: Nearest vertical wellbore by surface location
• Closest Disposal/Injection Well: Nearest injection or disposal well
• Closest Logged Well: Nearest well with wireline log data

All lateral-to-lateral distances are reported in feet, using straight-line geodetic distances between subsurface points.

How It Is Computed

Step 1 — Directional Survey Foundation
Spacing calculations require directional survey data.

• Survey defines 3D wellbore path (lat, long, MD, TVD, inclination, azimuth)
• Only points with inclination > 60° are used (horizontal section)

Key dependency: If no directional survey exists → no spacing can be computed

Step 2 — Offset Candidate Search
For each survey point:
• Search nearby wells (~0.05° bounding box ≈ ~3 miles)
• Filter to other lateral wells (inclination > 60°)
• Rank by distance using geography: STDistance

Directional filter applied:
• Offset azimuth must be within ±30°
• Or within ±30° of reciprocal (180°)

Fallback:
• If no matches → run azimuth-agnostic search (logged, not silent)

Step 3 — Cross-State Boundary Search
Spacing calculations are not limited by state boundaries.
• If no in-state result or distance > 1,320 ft (¼ mile)
• Search neighboring state datasets

Final result = closest offset across all states

Step 4 — Survey Station Roll-Up
Station-level results are aggregated to the well level:
• Winning offset = most frequently closest across stations
• Tie-breaker = ln cases of a tie, the offset with the lowest average distance is selected.

Final spacing = average distance across winning stations

This approach reduces reliance on single-point minimum distances.

Step 5 — Well Relationship Classification
Primary offsets are classified based on production timing:
• Parent → Offset produces >1 year before subject
• Child → Offset produces >1 year after subject
• Co-Developed → Within ±1 year
• None → Missing data or outside 1,320 ft threshold

Data Quality Caveats and Limitations

Directional Survey Coverage
• Not all wells have surveys
• Formats vary widely (PDF, text, XML, CSV)
• Some cannot be parsed

Result: Missing or unusable surveys → no spacing computed

Formation Name Standardization
Formation naming is inconsistent, examples:
• “Wolfcamp A”
• “WCAMP-A”
• “WCA”

The system applies formation normalization logic; however, results depend on the consistency of source formation naming and may not align in all cases.

Coordinate Accuracy
Issues include:
• Mixed datums (NAD27 vs NAD83 vs WGS84)
• Missing datum metadata

Handling approach:  Coordinates are converted to WGS84 when the source datum is provided.
If the source datum is not specified, coordinates are assumed to be WGS84.

Potential impact: Positional differences may vary by up to several hundred feet depending on source data quality and datum consistency.

Missing or Incorrect TVD and Azimuth
Common problems:
• TVD missing or zero-filled
• Azimuth incorrect or absent

Fallback behavior:
• No TVD → formation match = name-only
• No azimuth → no directional filtering

Production Date Reliability
Used for Parent/Child classification, but:
• Often reflects first reported month, not actual production
• May be updated retroactively
• Sometimes missing entirely

Result: “None” classification often = missing data, not true absence

Inter-State Data Awareness
Cross-state logic depends on data availability:
• If neighboring state data is delayed or incomplete
• Spacing near borders may be overstated

Summary

Spacing represents the most precise figure derivable from available data.

The methodology:
• Anchored in directional survey geometry
• Uses spatial indexing for scale
• Applies fallback logic for incomplete data

Even with advanced methodology, results remain dependent on the completeness and accuracy of the underlying source data.

Explore additional articles by searching the topics on the left. If you have any questions, feel free to email support@welldatabase.com