Well profiles, in open format.
Free editor to create, visualize, and export geological and construction profiles. A simple JSON, versioned, readable by any language.
One JSON.
Three purposes.
Today, well data lives in PDFs that don't talk to each other. The .well file is a simple, versioned format to change that — a single JSON that fully describes a well, designed as an international standard.
Visualization
Free D3.js library to render and export geological and construction profiles at real scale.
Record
Predictable structure to archive and version well data, ready for submission and auditing.
Research
Organized metric fields allow cross-referencing and comparing wells across aquifers, regions, and eras.
Open
Human-readable JSON, public specification, and permissive license — free to use, extend, and contribute.
Today, a water well's data exists in many places: in the driller's notebook, in the consultant's spreadsheet, in the PDF report submitted to the licensing authority. Each in its own format, each unreadable to the other. welldot and the .well format were created to solve this.
Live editor
Tables linked to the drawing. Edit a layer, see the profile redrawn at real scale.
Open format
Human-readable JSON, public specification, and Apache 2.0 license. Implement in any language.
Submission-ready
A4 PDFs at real scale, with header, metadata, and multi-page drawing.
Standard inside,
flexible outside.
A single human-readable text file: archivable in folders, versionable in git, indexable in databases, analyzable by AI. The core is strict where it matters — SI metrics, WGS84, English keys — and flexible everywhere else.
The repository includes a ready-made welldot.skill: point any agent to github.com/rafaeelneto/welldot and it operates the format natively.
The future.
v1 covers geological and construction profiles. The specification evolves openly to embrace the full lifecycle of a well.
Native .las
Import and storage of LAS geophysical profiles, side by side with the lithological profile.
Pump tests
Pump tests, recovery, specific flow, and hydrodynamic parameters as time series.
Operational history
Event log: maintenance, pump replacement, static level, shutdowns — dated and attributable.
Water quality
Physical-chemical and bacteriological analyses linked to sampling, depth, and date.
Extended metadata
Water rights, owner, usage regime, cadastral references, and links to regulatory databases.
Community extensions
Namespaces for fields specific to agencies and regions, without breaking the standardized core.