Skip to content
GeoEQ · Geotechnical software research lab · University of Utah

Documentation / Reference

The .sbl project file format: JSON structure and row layout

Applies to 1.0 and later · current 1.2 3 min read

Short answer

A GeoEQ SPT Logs project file (.sbl) is plain UTF-8 JSON: a top-level object with a version and a list of projects, each holding boreholes, and each borehole holding a header, spt rows (12 cells), strata rows (3 cells) and optional core rows (7 cells). You can read it directly with any JSON library.

12 / 3 / 7
cells per spt / strata / core row
UTF-8 JSON
plain text, no export step needed

What is in a .sbl file?

A .sbl file is plain UTF-8 JSON. It is documented so you can read your own data, for a QA script, a bulk check across boreholes, or to hand a profile to the geoeq Python package, without exporting anything first. By default project files are kept in Documents\GeoEQ SPT Logs\Projects; see Updates and where your data lives.

What is the overall shape?

{
  "version": 2,
  "projects": [
    {
      "id": "b5191c21",
      "name": "ABC Site Investigation",
      "client": "ABC Development",
      "location": "Salt Lake City, Utah, USA",
      "about": "...",

      // presentation choices, all optional
      "units": "metric",            // or "imperial", labels only, never a conversion
      "coord_display": "both",      // "xy" | "latlong" | "both"
      "water_marker": "classic_line",
      "spt_interval": 1.5,          // test spacing used by Generate depths
      "spt_start": 1.5,             // first test depth
      "ruler_interval": 0.0,        // 0 = Auto (follows spt_interval)
      "n_scale": "fixed",           // or "auto"
      "n_scale_max": 70.0,
      "n_overflow": "clamp",        // "clamp" | "refusal" | "extend"
      "refusal_text": "asrec",      // "asrec" | "gt" | "Ref" | "R"

      "boreholes": [
        {
          "id": "9b1aed49",
          "name": "BH-02",
          "depth": 15.0,            // total depth
          "gwt": 2.5,               // groundwater depth below EGL
          "borelog": {
            "header": {
              "coord_x": "424715", "coord_y": "4512390",
              "coord_lat": "40.7615", "coord_long": "-111.8896",
              "date_started": "2026-05-15", "date_completed": "2026-05-16",
              "method": "Hollow Stem Auger", "water_rl": "(-) 2.5",
              "dia": "100", "standard": "ASTM D-2487 & D-2488",
              "egl_rl": 0.0
            },
            "page_depth": 15.0,     // depth printed per sheet
            "spt": [ /* rows, see below */ ],
            "strata": [ /* rows, see below */ ],
            "core": [ /* core runs, see below; omitted if none */ ]
          }
        }
      ]
    }
  ]
}

One file can hold several projects. Each project carries the shared settings, and each borehole carries its own header and tables. The project-level choices match the options in Project settings, and absent fields mean the default behaviour.

How are table rows stored?

Table rows are arrays of strings in column order. Empty cells are "".

spt rows have 12 cells:

CellContentNotes
0depth
1 to 315 cm increments, 1st, 2nd, 3rd"50/75" means refusal: 50 blows for 75 mm
4NOptional. Blank means N is taken as 2nd + 3rd
5sample ID
6sample typeD or UD
7 to 11fines %, LL, PI, qu, moisture %

strata rows have 3 cells: bottom depth, description, and soil letter (C clay, S sand, M silt, G gravel, F fill, O organic, R rock).

core rows have 7 cells, and the list is present only where there is coring: run top, run bottom, TCR %, SCR %, RQD %, core size, and fractures per metre. Run number, run length and the rock quality word are derived, not stored. See Rock coring.

How do I read a file with Python?

import json

with open("ABC Site Investigation.sbl", encoding="utf-8") as f:
    doc = json.load(f)

for project in doc["projects"]:
    for bh in project["boreholes"]:
        print(f"\n{bh['name']}: {bh['depth']} m, water {bh['gwt']} m")
        for row in bh["borelog"]["spt"]:
            depth, b1, b2, b3, n = row[0], row[1], row[2], row[3], row[4]
            if "/" in b3:                       # refusal, e.g. 50/75
                print(f"  {depth:>6}  refusal {b3}")
            elif n or (b2 and b3):
                print(f"  {depth:>6}  N = {n or int(b2) + int(b3)}")

The script prints the water depth for each borehole, then each test as either a refusal or its N-value, where N is the stored value or the 2nd plus 3rd increment.

Will files stay compatible across versions?

New fields are added, never repurposed, and every one is optional. A reader that ignores what it does not recognise keeps working across versions. Files written by earlier versions open unchanged and are upgraded in memory when saved.

Edit a file by hand only on a copy. The app is the safest place to change data, and with version 1.3 the Connect AI server writes files with a backup and a dry run.

Frequently asked questions

What is a .sbl file?

It is the project file of GeoEQ SPT Logs. It is plain UTF-8 JSON that can hold one or more projects, each with its boreholes, SPT data, strata, header and optional rock core runs.

Can I read a .sbl file without the app?

Yes. Open it with any JSON library, for example Python's json module. The format is documented so you can run a QA script, a bulk check across boreholes, or hand a profile to the geoeq Python package without exporting anything.

Will files from earlier versions still open?

Yes. New fields are added, never repurposed, and every one is optional. Files written by earlier versions open unchanged and are upgraded in memory when saved.

What does 50/75 mean in a blow count cell?

It is refusal notation: 50 blows for 75 mm of penetration. It is stored as the text 50/75 in the 15 cm increment cell.