Troubleshooting and FAQ
Common error messages and what to do about them, getting data out of Excel, and other questions.
Error messages
Errors are listed under the text box on the web page (click one to jump to it), or returned by the API. Each one has a path saying where the problem is: /layers/2/uscs means the uscs field of the third layer, because counting starts at 0.
| Message | What it means and how to fix it |
|---|---|
| Invalid JSON: Expected double-quoted property name… (line 1 column 55) | A punctuation problem at that position. Most often a comma after the last item in a list, a missing comma between items, single quotes instead of double quotes, or a missing } or ]. See JSON rules. |
| unknown property "descripton" | A field name the viewer doesn't know, usually a typo. Check the spelling in the data format reference. Names are lower case, with underscores (water_content, not Water Content). |
| bottom (0) must be greater than top (5) | The top and bottom depths are the wrong way round, or equal. |
| is not a recognized USCS symbol (e.g. SM, CL, SP-SM) | The uscs field takes USCS group symbols and pairs of them. Put anything else (such as "FILL") in the description, or use hatch for a material such as FILL. |
| unknown sampler type "SHELBY": use a built-in type or define it in patterns | The sample type isn't one of the sampler codes. Codes are case-sensitive: Shelby, not SHELBY. |
| must be number | A number was written in quotes ("top": "4"), or contains units or text ("water_content": "12%"). Write just the number: "top": 4. |
| must be "1.0" | If you give schema_version, it must be exactly "1.0", in quotes. You can also leave it out. |
| must have required property 'bottom' | Every layer and sample needs both top and bottom. |
Warnings
Warnings don't stop the log being drawn; they point out things that might be mistakes.
- "CL" doesn't match the description, which reads as CL-ML: the recorded USCS symbol disagrees with the description. The log shows both. Check which is right. See checking recorded symbols.
- "GP-GW" is not a possible USCS symbol: it isn't one of the ASTM D2487 dual symbols. Use a real dual symbol, or "/" for a borderline soil (e.g. CL/CH).
- lab results on the sample (water_content) are shown level with the sample, without a specimen box: the data is in the older format. Move the results into a
specimenslist; see results on the sample. - samples have remarks, not a description: rename the sample's
descriptiontoremarks. - "NoRecovery" is not a sampler type (or "No Recovery" is not a sample number): give the sampler that was tried as
type, and"recovery_percent": 0. See recovery. - specimen (3–3.2) is outside its sample (1–2): check the specimen's depths.
- gap between 5 and 6 (no layer described): there's no layer from 5 to 6. It's left blank on the log. If the gap is real (e.g. no recovery), add a layer for it, perhaps with
"hatch": "NO_RECOVERY". - overlaps layer 1 (4–12): two layers cover the same depths. Check the depths.
Questions
Is my data sent anywhere?
Not by the web page: it draws the log in your browser, and keeps your open logs in your browser's storage so they're still there next time. Opening an AGS4 or DIGGS file on the page doesn't upload it either. The only things the page loads from elsewhere are map pictures, from OpenStreetMap or Esri, and your data isn't sent with them. The API does receive the data you send it, but doesn't store or log it.
Can I edit the drawing afterwards?
Yes. Download it as SVG and open it in Inkscape (free), Adobe Illustrator or another vector editor. Text stays as text, and each part is a separate object.
How do I put a log in a Word report?
Recent versions of Word and PowerPoint accept SVG directly (Insert → Pictures), and it stays sharp when printed. Otherwise use a PNG at 2× or 3×. For a full-page log, Print / PDF and insert the PDF, or add it as an appendix.
My log is very tall. Can I split it over pages?
The web page draws one continuous log. To split it, draw it in parts with the depth_range option (in the JavaScript module), or print to PDF and let the browser break it over pages. Making the drawing wider, or turning off Fit text, also makes it shorter.
Why are my layers stretched unevenly?
They aren't: the depth scale is always uniform. With Fit text on, the whole scale is stretched until sample rows and descriptions fit, so a log with many closely spaced samples gets taller. See why the depth scale stretches.
The graphic log shows the wrong symbol
Give the layer a uscs (or a hatch, which always wins). A layer whose description doesn't determine a soil type, such as "clayey SILT", is left blank until you do. If a material such as fill or a rock is being picked out of the description when you don't want it, set uscs and turn off infer_materials, or set hatch directly. How the symbol is chosen explains the order.
Why is the USCS symbol in parentheses?
It was inferred from the description, not recorded in the data. The legend says so too. Add uscs to the layer to show it without parentheses, or turn off infer_uscs to hide inferred symbols.
Can I log rock cores?
Yes: there are hatches for over 40 rock types, plus weathered rock and intermediate geomaterial, and sampler types for rock core and triple-tube core with recovery_percent. There aren't dedicated RQD or fracture-frequency columns yet; put RQD in remarks.
Can it draw CPT soundings?
No, it draws boring logs only. CPT soundings in a DIGGS file are skipped.
How should I cite it?
Please cite the software, which is published on DesignSafe:
Sahin, A., and S. J. Brandenberg (2026). Boring Log Viewer (version 1.0.0). DesignSafe-CI. https://doi.org/10.17603/ds2-rnc6-7323
The DesignSafe page also offers the citation as BibTeX, RIS and DataCite XML. Please also list the source of your boring data in the log's references, so it appears on the drawing.
I found a bug, or need a feature
Please open an issue on GitHub. Include the JSON (or file) that shows the problem, with any confidential information removed.