Site bore reference (v1)
Site bore reference is one of Demiton's published registers for Australian civil construction. Borehole records referenced for a site. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
Part of Projects in the register catalog.
- Register ID
site_bore_referenceUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- A stateThe current value of something, replaced when it changes.
- Status
- DeclaredDefined, and fills when a source produces its first record.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.1)Superseded by v2.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- AHD / AUSGeoid2020Australian Height Datum with AUSGeoid2020 separation model
- AS 1289 seriesMethods of testing soils for engineering purposes
- AS 1726:2017Geotechnical site investigations
- AS 5488.1:2022Classification of Subsurface Utility Information (SUI)
- ISO 19650Information management using BIM (identical to ISO 19650-1/-2:2018)
- GDA2020 / MGA2020Geocentric Datum of Australia 2020 and Map Grid of Australia 2020
- National Measurement (Recognized-Value Standard of Measurement of Position) Determination 2017Legal definition of GDA2020 under National Measurement Act 1960 (Cth) s 8A
- INSPIRE Data Specification on Coordinate Reference Systems (D2.8.I.1)INSPIRE CRS Technical Guidelines: ETRS89 horizontal, EVRS vertical
- EPSG Geodetic Parameter DatasetIOGP CRS registry (EPSG:7844 GDA2020, EPSG:7855 MGA zone 55, EPSG:4326 WGS 84 ensemble)
- ISO 14688-1:2017 / ISO 14688-2:2017Geotechnical investigation and testing - Identification and classification of soil
- ISO 22475-1:2021Geotechnical investigation and testing - Sampling methods and groundwater measurements - Part 1: Technical principles for the sampling of soil, rock and groundwater
- RFC 7946The GeoJSON Format
- NZGD2000 / NZTM2000 / NZVD2016New Zealand Geodetic Datum 2000, NZ Transverse Mercator 2000, NZ Vertical Datum 2016 (NZGeoid2016)
- AGS 4.2Electronic Transfer of Geotechnical and Geoenvironmental Data
- BS 5930:2015+A1:2020Code of practice for ground investigations
- OSGB36 / ETRS89 / OSTN15 / OSGM15 (ODN)Ordnance Survey National Grid, ETRS89 and the definitive transformations
- PAS 128:2022Underground utility detection
- ASCE/UESI/CI 38-22Investigating and Documenting Existing Utilities
- ASTM D2487-17(2025)Classification of Soils for Engineering Purposes (USCS)
- ASTM D2488Description and Identification of Soils (Visual-Manual Procedures)
- DIGGSData Interchange for Geotechnical and Geoenvironmental Specialists
- NAD 83(2011) / NAVD 88 (NSRS)US official horizontal and vertical datums, being replaced by NATRF2022 et al.
Connectors
Connected today
Demiton keeps this register current from these systems now.
No system fills this register yet.
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
None planned yet.
Fields
18 fields: 9 required, 9 optional.
Required
Every record carries these fields.
- sourceText
The register and vintage the answer was resolved from (e.g. the NGIS NSW extract)
Example:
Queensland Groundwater Database- contentText
One sentence stating the resolved answer.
Example:
3 registered bores within 500 m of the Cherbourg Water Tr…- projectText
The tenant project whose site coordinate the answer is about.
Example:
BWG-2025-003- radius_mWhole number
The search radius the counts and distances were computed at.
Example:
500- horizontal_datumText
The horizontal datum (and, where frame-based, the realisation) the site coordinate was expressed in.
Example:
GDA2020- bores_within_radiusWhole number
Number of registered bores inside
radius_mExample:
3- nearest_bore_distance_mDecimal number
Distance from the project site coordinate to the nearest registered bore within the radius.
Example:
210.5- nearest_bore_rock_depth_mDecimal number
Shallowest
depth_top_mof an interval whoseMajorLithCodeis in the rock allowlist, in the nearest logged bore; null means no rock evidenced, and null is a first-class answer.Example:
18.2- logged_bores_within_radiusWhole number
How many of those carry a lithology log.
Example:
1
Optional
Present when the source system records them.
- datum_epochText
The epoch where the horizontal datum is frame-based.
- resolved_atDate and time
When the answer was resolved.
Example:
2026-06-10T09:00:00+10:00- register_stateText
The state register the answer came from.
Example:
QLD- rock_lith_codeText
The
MajorLithCodethat evidenced rock.- resolver_versionText
Which resolver/method version produced the answer.
Example:
geo-resolver-v2- rock_lith_schemeText
The code list/edition the lithology code belongs to (NGIS
MajorLithCode; AS 1726:2017 / AGS 4.2 / DIGGS for other sources)- nearest_logged_bore_idWhole number
The source register's
bore_idfor the nearest logged bore.Example:
142207- nearest_bore_drilled_depth_mDecimal number
Total drilled depth of the nearest logged bore.
- nearest_logged_bore_distance_mDecimal number
Distance to the nearest bore that carries a log.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "bores_within_radius": 3, "content": "3 registered bores within 500 m of the Cherbourg Water Treatment Plant site; nearest logged bore RN142207 at 210.5 m, rock at 18.2 m depth.", "horizontal_datum": "GDA2020", "logged_bores_within_radius": 1, "nearest_bore_distance_m": 210.5, "nearest_bore_rock_depth_m": 18.2, "nearest_logged_bore_id": 142207, "project": "BWG-2025-003", "radius_m": 500, "register_state": "QLD", "resolved_at": "2026-06-10T09:00:00+10:00", "resolver_version": "geo-resolver-v2", "source": "Queensland Groundwater Database"}Version history
- v2 (current)
- v1
Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/site_bore_reference/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.