@welldot/core 0.4.0 → 0.5.0

package/docs/spec/v2/overview.md

@@ -1,9 +1,91 @@
-# `.well` File Format Specification — Version 2.3: Overview
+# `.well` File Format Specification — Version 2.4: Overview
 
-**Version:** 2.3 **Extension:** `.well` **Encoding:** UTF-8 **Base format:** JSON **MIME type:** `application/vnd.well+json` **JSON Schema:** `https://welldot.org/schema/v2/well.schema.json` **JSON Schema draft:** 2020-12 **JSON-LD Context (optional):** `https://welldot.org/context/v2.jsonld` **Status:** v2.0 ratified — shipped in `@welldot/core` v0.2.0 · v2.1 shipped in `@welldot/core` v0.3.0 · v2.3 shipped in `@welldot/core` v0.4.0
+**Version:** 2.4 **Extension:** `.well` **Encoding:** UTF-8 **Base format:** JSON **MIME type:** `application/vnd.well+json` **JSON Schema:** `https://welldot.org/schema/v2/well.schema.json` **JSON Schema draft:** 2020-12 **JSON-LD Context (optional):** `https://welldot.org/context/v2.jsonld` **Status:** v2.0 ratified — shipped in `@welldot/core` v0.2.0 · v2.1 shipped in `@welldot/core` v0.3.0 · v2.3 shipped in `@welldot/core` v0.4.0 · v2.4 shipped in `@welldot/core` v0.5.0
 
 **See also:** [format-reference.md](./format-reference.md) · [object-schemas.md](./object-schemas.md) · [interoperability.md](./interoperability.md) · [water-quality.md](./water-quality.md)
 
+## Overview
+
+The `.well` v2 specification is split into five documents. This one gives the context: what changed in each revision (v2.4, v2.3, v2.1 and from v1), why the format exists, the design principles the other parts follow, and the known limitations. The other four are:
+
+- [format-reference.md](./format-reference.md) — the top-level fields, versioning and deprecation, datetimes, recommended vocabularies, `well_id`, `location`, units, profiles, extensibility, cross-reference rules and precision.
+- [object-schemas.md](./object-schemas.md) — every object schema, the `hydrodynamic_events` ledger, `aquifer_analysis`, `history_logs`, the operational blocks (pumps, permits, meters, production, operating regime) and a complete example.
+- [water-quality.md](./water-quality.md) — water samples and results, their units, the parameter vocabulary and regulatory profiles.
+- [interoperability.md](./interoperability.md) — the JSON-LD context, the relationship to GWML2 and JSON Schema validation.
+
+## Table of contents
+
+- [Changes in v2.4](#changes-in-v24)
+  - [Deprecations](#deprecations)
+- [Changes in v2.3](#changes-in-v23)
+- [Changes in v2.1](#changes-in-v21)
+  - [Deprecations](#deprecations-1)
+- [Changes from v1](#changes-from-v1)
+- [Purpose](#purpose)
+- [Design Principles](#design-principles)
+- [Known Limitations of v2](#known-limitations-of-v2)
+
+---
+
+## Changes in v2.4
+
+v2.4 files write `"version": "2.4"`; parsers up to `@welldot/core` 0.4.0 reject them. Beyond that, v2.4 is an additive revision: every valid v2.3 document stays valid when its `version` is rewritten, and the integer `2` still means "v2.0 to v2.3, revision unknown".
+
+```
+v2.4 additions:
+- version is the string "M.m" (^\d+\.\d+$), compared as two integers,
+  never as text; patch levels are not allowed; readers accept 1, 2 and
+  "M.m"
+- location.properties.timezone (optional, IANA name): the local date of
+  an instant is its date converted to this zone; a missing timezone in
+  a file with condition fulfillments emits the warning missing_timezone
+- logger_series (hydrodynamic event type): a continuous level series
+  recorded by an installed sensor, with sensor_depth, interval,
+  barometric_compensation and aggregation (none, hourly, daily with
+  depth_min / depth_max); not a controlled test, not a static level
+- LevelReading.datetime: the instant of a reading, required in a
+  logger_series, where elapsed is absent
+- Offline packaging: an optional ZIP (.wellz) with the .well file at
+  the root and attachments at relative paths; relative uri allowed and
+  sha256 required only inside the package
+- Application extensions: x-<vendor>-<name> is RECOMMENDED
+  (e.g. x-welldot-custom)
+
+v2.4 clarifications:
+- A known hydrodynamic event type is validated against its own schema
+  and no longer falls back to the open x- rule; step counts per type
+  are SHOULD (a free count is valid), and steps must be valid
+  PumpingStep entries
+- An optional field without a value is omitted, never written as null
+  (storativity is no longer nullable); v2 integer files that still
+  carry it are tolerated on read
+- Ledgers MAY be edited in place; editing is NOT RECOMMENDED after a
+  record has been exported, and corrects remains the way to retract a
+  measurement. Result.validation is editable too
+- Repeated records (collective permits, campaign blanks) share the
+  same id and SHOULD have identical content; consumers MAY merge them
+  by id. A fulfillment event_id or sample_id resolves only in the file
+  of the well that produced it
+- Unresolved references MUST be preserved when a file is re-exported,
+  never silently removed
+- A duplicated operating_regime.effective_from and an
+  estimated_volume period_end not after period_start are warnings
+- daily_operating_time above 24 is normalized to 24 with a warning
+  (the stored value stays as written); a negative value is an error
+- Attachment.document_type condition_evidence is typically found in
+  permits[].conditions[].fulfillments
+- The attachment lists (id uniqueness, "root is not an aggregate",
+  where attachments are allowed) name the same set of records
+- history_logs updated_at may be earlier than datetime for a pre-dated
+  entry; neither ordering emits a warning
+- well_id: producers SHOULD mark exactly one entry primary: true; "the
+  first entry is canonical" is only the fallback
+```
+
+### Deprecations
+
+None.
+
 ---
 
 ## Changes in v2.3
@@ -28,13 +110,14 @@ v2.3 additions:
   its identifier and/or request_identifier (verbatim, any format), a
   closed administrative status (requested, granted, suspended,
   revoked, denied, withdrawn), an administrative history (filing,
-  process, notifications, fees, with done/due_date) and, on each
-  condition, a responsible and the fulfillments of its deadlines
-  (datetime, due_date, author, event_id, sample_id)
+  process, notifications, fees, with done/due_date and attachments)
+  and, on each condition, a responsible and the fulfillments of its
+  deadlines (datetime, due_date, author, event_id, sample_id,
+  attachments)
 - meters (optional Meter[]): totalizer (hidrômetro) installation
   history; device facts only (type, serial, nominal diameter,
   max_reading for rollover)
-- production (optional ProductionEntry[]): append-only ledger of
+- production (optional ProductionEntry[]): ledger of
   meter_reading entries (register values in m³) and estimated_volume
   entries (volumes estimated for a period without a meter); volumes
   are derived from consecutive readings, never stored as totals.
@@ -152,7 +235,7 @@ v2.0 additions:
 - well_id (array of authority-scoped identifiers)
 - profiles (JSON Schema URLs for regulatory and domain-specific constraints)
 - texture object (multi-vocabulary, replaces v1 fgdc_texture string)
-- hydrodynamic_events (append-only ledger of water-level observations)
+- hydrodynamic_events (ledger of water-level observations)
 - aquifer_analysis (interpreted aquifer parameter sets)
 - history_logs (operational log of interventions and incidents,
   with updated_at edit timestamp)
@@ -201,7 +284,7 @@ The `.well` format is an open standard for representing water well data. It is d
 - **Ground level as zero** — all depth values are measured from ground level (0); elevation above the WGS84 ellipsoid (or declared datum) is stored separately in `location.elevation`. Water levels above ground are negative.
 - **Geographic north** — all azimuth values are referenced to geographic north.
 - **Three block kinds** — every top-level array is one of three kinds, and the kind decides how records are corrected:
-  - **Ledger** (`hydrodynamic_events`, `production`, `water_samples`) — append-only. An error is corrected by appending a new entry whose `corrects` points to the retracted entry; existing entries are never edited in place. A retracted entry stays in the file but is excluded from every derivation. This is enforced by authoring tools in the welldot stack, not by the file format itself. The format provides `id`, `datetime`, `sequence` and `corrects` to support this discipline.
+  - **Ledger** (`hydrodynamic_events`, `production`, `water_samples`) — grows by appending. Entries MAY be edited in place, but editing is NOT RECOMMENDED after an entry has been exported. A measurement correction (a re-measurement, a revised laboratory report) is best written as a new entry whose `corrects` points to the retracted entry; a retracted entry stays in the file but is excluded from every derivation. The format provides `id`, `datetime`, `sequence` and `corrects` to support this discipline; it does not enforce it.
   - **Mutable record** (`history_logs`, `permits`, `operating_regime`) — edited in place; `updated_at` records the last edit.
   - **Installation** (`pump_installations`, `meters`) — equipment present in the well for a period (`installed_at` / `removed_at`); edited in place with `updated_at`.
 - **Derived values are never stored raw** — `s/Q`, `Q/s`, drawdown `s`, and any other value computable from stored fields must not appear as stored fields. Applications compute them on demand.
@@ -225,4 +308,4 @@ The following are recognized limitations of this version, reserved for future ve
 
 ---
 
-_`.well` Format Specification v2.3_
+_`.well` Format Specification v2.4_

package/docs/spec/v2/water-quality.md

@@ -1,22 +1,45 @@
-# `.well` File Format Specification — Version 2.3: Water Quality
+# `.well` File Format Specification — Version 2.4: Water Quality
 
 **See also:** [overview.md](./overview.md) · [format-reference.md](./format-reference.md) · [object-schemas.md](./object-schemas.md) · [interoperability.md](./interoperability.md)
 
+## Overview
+
 This document specifies the `water_samples` block _(since v2.3)_: the sample and result schemas, the recommended values, the unit rules, the `welldot` parameter vocabulary and how jurisdiction requirements are expressed. Cross-cutting rules that also cover water samples stay in their general sections: datetimes and the `_resolution: "day"` convention, canonical units and field bindings, cross-references, uniqueness and precision in [format-reference.md](format-reference.md); attachments, ledger corrections and `history_logs` links in [object-schemas.md](object-schemas.md). The Complete Example in object-schemas.md includes water samples.
 
-## Contents
+## Table of contents
 
 - [`water_samples[]`](#water_samples)
+  - [`WaterSample`](#watersample)
+  - [`SamplingPoint`](#samplingpoint)
+  - [`Purge`](#purge)
+  - [`PurgeReading`](#purgereading)
+  - [`Laboratory`](#laboratory)
+  - [`Result`](#result)
+  - [`Parameter`](#parameter)
+  - [`Filtration`](#filtration)
+  - [`Validation`](#validation)
+  - [Result rules](#result-rules)
+  - [Malformed (rejected)](#malformed-rejected)
+  - [Validation (warnings, never rejection)](#validation-warnings-never-rejection)
+  - [Derived values](#derived-values)
+  - [History log links](#history-log-links)
 - [Recommended values](#recommended-values)
+  - [`water_samples[].sample_type` — Recommended values _(since v2.3)_](#water_samplessample_type--recommended-values-since-v23)
+  - [`water_samples[].sampling_method` — Recommended values _(since v2.3)_](#water_samplessampling_method--recommended-values-since-v23)
+  - [`water_samples[].sampling_point.type` — Recommended values _(since v2.3)_](#water_samplessampling_pointtype--recommended-values-since-v23)
+  - [`water_samples[].sampling_point.device` — Recommended values _(since v2.3)_](#water_samplessampling_pointdevice--recommended-values-since-v23)
 - [Units](#units)
 - [Parameter vocabulary](#parameter-vocabulary)
+  - [Vocabulary rules](#vocabulary-rules)
+  - [Core vocabulary](#core-vocabulary)
+  - [Limit sets are not part of the file](#limit-sets-are-not-part-of-the-file)
 - [Regulatory profiles](#regulatory-profiles)
 
 ---
 
 ## `water_samples[]`
 
-A ledger: each entry is one collection of water from the well, with the results measured on it in the field and in the laboratory. Entries are never edited in place. A corrected laboratory report, or a revalidation of data already recorded, is a new sample whose `corrects` holds the id of the retracted sample, following object-schemas.md § `hydrodynamic_events[]` — Corrections (retracted samples stay in the file and are excluded from every derivation; chains are allowed; a cycle emits a warning).
+A ledger: each entry is one collection of water from the well, with the results measured on it in the field and in the laboratory. Entries MAY be edited in place, but editing is NOT RECOMMENDED after the entry has been exported. A revalidation of data already recorded is an edit of `Result.validation` in place. A corrected laboratory report is best written as a new sample whose `corrects` holds the id of the retracted sample, following object-schemas.md § `hydrodynamic_events[]` — Corrections (retracted samples stay in the file and are excluded from every derivation; chains are allowed; a cycle emits a warning).
 
 The block serves drinking-water compliance, environmental and mining monitoring under licence, and hydrochemistry, in any jurisdiction. It follows the rigor of audited monitoring (chain of custody, field QA/QC, filtration, lab flags, data validation) with almost every field optional. It is jurisdiction-neutral: limits, exceedances and national rules are never stored; see § Parameter vocabulary — Limit sets are not part of the file.
 

package/examples/README.md

@@ -1,9 +1,21 @@
 # `.well` example wells
 
+## Overview
+
 Nineteen complete `.well` v2.3 files that serve as a reference for the format. Each one stays valid and covers a different situation. The profiler offers them in its "New well" dialog, which opens when the editor starts empty, and serves them at `https://welldot.org/examples/<file>`. They also ship with `@welldot/core` (`@welldot/core/examples/<file>`).
 
 `src/examples.test.ts` checks that every file passes `WellSchema`, round-trips through `deserializeWell` / `serializeWell`, and matches `index.json`, and that every category lists at least three examples.
 
+This README covers where the data comes from, the list of examples, how the thumbnails are generated, the rules used to map SIAGAS records onto the physical base, and how to add an example.
+
+## Table of contents
+
+- [Data provenance](#data-provenance)
+- [The examples](#the-examples)
+- [Thumbnails](#thumbnails)
+- [Mapping rules used for the physical base](#mapping-rules-used-for-the-physical-base)
+- [Adding an example](#adding-an-example)
+
 ## Data provenance
 
 Each example is **illustrative**. It is built on a real well from SIAGAS (Serviço Geológico do Brasil), but it is not that well's record.

package/examples/belem-pa-condominio-outorga.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500013505"
@@ -29,6 +29,7 @@
     "lng": -48.47917,
     "elevation": 12,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.0001,
       "lng_precision": 0.0001,

package/examples/belem-pa-monitoramento-posto.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500002024"
@@ -29,6 +29,7 @@
     "lng": -48.485,
     "elevation": 11,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.00005,
       "lng_precision": 0.00005,

package/examples/belem-pa-pirabas-abastecimento.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500002050"
@@ -33,6 +33,7 @@
     "lng": -48.48083,
     "elevation": 14,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,
@@ -1031,7 +1032,6 @@
       "max_flow_rate_basis": "step_drawdown",
       "specific_capacity": 12.712,
       "transmissivity": 881.7,
-      "storativity": null,
       "jacob_b": 0.062,
       "jacob_c": 0.000139,
       "well_efficiency_pct": 79,

package/examples/belem-pa-poco-colmatado.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500001046"
@@ -25,6 +25,7 @@
     "lng": -48.47639,
     "elevation": 9,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/belem-pa-poco-raso-abandonado.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500001090"
@@ -25,6 +25,7 @@
     "lng": -48.44083,
     "elevation": 5,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/belem-pa-qualidade-agua-acida.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500001109"
@@ -25,6 +25,7 @@
     "lng": -48.44806,
     "elevation": 10,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/colatina-es-gnaisse-rural.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3100007879"
@@ -33,6 +33,7 @@
     "lng": -40.51389,
     "elevation": 71,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,
@@ -490,7 +491,6 @@
       "flow_rate": 7.2,
       "specific_capacity": 0.141,
       "transmissivity": 0.0000385,
-      "storativity": null,
       "notes": "Uma única fratura produtora; rebaixamento quase até a entrada d’água. Vazão recomendada: 4 m³/h."
     }
   ],

package/examples/coluna-mg-cristalino-abastecimento.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3100020129"
@@ -33,6 +33,7 @@
     "lng": -42.83861,
     "elevation": 655,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,
@@ -489,7 +490,6 @@
       "flow_rate": 14.76,
       "specific_capacity": 0.291,
       "transmissivity": 9,
-      "storativity": null,
       "notes": "Meio fissural sob manto de alteração: transmissividade aparente. Rebaixamento elevado na primeira hora indica perdas de carga no poço."
     }
   ],

package/examples/estrela-doeste-sp-bauru-serra-geral.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3500000898"
@@ -29,6 +29,7 @@
     "lng": -50.40361,
     "elevation": 430,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/extremoz-rn-barreiras-raso.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=2600055664"
@@ -29,6 +29,7 @@
     "lng": -35.325,
     "elevation": 9,
     "properties": {
+      "timezone": "America/Fortaleza",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/gastao-vidigal-sp-dados-inconsistentes.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3500001375"
@@ -25,6 +25,7 @@
     "lng": -50.18028,
     "elevation": 380,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/irece-ba-carste-bambui.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=2900000278"
@@ -29,6 +29,7 @@
     "lng": -41.88639,
     "elevation": 765,
     "properties": {
+      "timezone": "America/Bahia",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/lagoa-santa-mg-carste-abastecimento.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3100003115"
@@ -32,6 +32,7 @@
     "lat": -19.63972,
     "lng": -43.90083,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,
@@ -437,7 +438,6 @@
       "flow_rate": 110,
       "specific_capacity": 35.48,
       "transmissivity": 0.00621,
-      "storativity": null,
       "notes": "Transmissividade alta, controlada pelo conduto. O nível estático caiu 4,3 m desde 1987, acompanhando o rebaixamento regional."
     }
   ],

package/examples/minas-novas-mg-cadastro-incompleto.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3100020670"
@@ -21,6 +21,7 @@
     "lat": -17.33306,
     "lng": -42.48694,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.001,
       "lng_precision": 0.001,

package/examples/quixeramobim-ce-cristalino-salobro.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=2300021772"
@@ -28,6 +28,7 @@
     "lat": -5.43222,
     "lng": -39.46444,
     "properties": {
+      "timezone": "America/Fortaleza",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,
@@ -476,7 +477,6 @@
       "flow_rate": 12.3,
       "specific_capacity": 0.724,
       "transmissivity": 0.000149,
-      "storativity": null,
       "notes": "Transmissividade aparente do meio fissural. A vazão de exploração recomendada é de 6 m³/h, metade da vazão de teste, por causa do rebaixamento e da salinidade."
     }
   ],

package/examples/rinopolis-sp-estratigrafico-guarani.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3500000010"
@@ -25,6 +25,7 @@
     "lng": -50.79306,
     "elevation": 408,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/santarem-pa-jorrante-alter-do-chao.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=1500000136"
@@ -25,6 +25,7 @@
     "lng": -54.73722,
     "elevation": 22,
     "properties": {
+      "timezone": "America/Belem",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/examples/sao-gabriel-rs-cacimba.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=4300001500"
@@ -25,6 +25,7 @@
     "lng": -54.42194,
     "elevation": 150,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.001,
       "lng_precision": 0.001,

package/examples/sete-lagoas-mg-carste-industrial.well

@@ -1,6 +1,6 @@
 {
   "$schema": "https://welldot.org/schema/v2/well.schema.json",
-  "version": 2,
+  "version": "2.4",
   "x-welldot-example": {
     "illustrative": true,
     "based_on": "https://siagasweb.sgb.gov.br/layout/detalhe.php?ponto=3100003295"
@@ -29,6 +29,7 @@
     "lng": -44.29556,
     "elevation": 765,
     "properties": {
+      "timezone": "America/Sao_Paulo",
       "crs": "EPSG:4326",
       "lat_precision": 0.0003,
       "lng_precision": 0.0003,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@welldot/core",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "type": "module",
   "description": "TypeScript types, Zod validators, and serialization utilities for the .well open format — a JSON standard for water well data.",
   "keywords": [