NVCL Infrastructure Tracker

Harvest. On — the NVCL pipeline queried every participating node’s public services: the WFS gsmlp:BoreholeView layer (filtered to nvclCollection='true') for registered boreholes, then each node’s NVCLDataServices getDatasetCollection for every borehole’s dataset records. Nothing on this page comes from a private database — the same services are public, and the Live check button and source links query them directly.

Scanned km — three tiers, in strict order (merged-v1.2). The atom is the scan interval (start–end depth), and per borehole overlapping intervals are merged so rescans never double-count — the headline is unique core imaged by a spectral scanner, which differs from metres drilled (the same holes total — km drilled). Evidence is taken in this precedence and never blended:

1. API interval — measured. The depth range the node’s own getDatasetCollection publishes, per dataset.
2. TSG interval — measured. When a node publishes none (WA and NT publish none at all), the interval is read from the Depth (m) field in the TSG file’s own header on NCI THREDDS — the AuScope NVCL mirror collection, DOI 10.25914/bztg-rg43. That is the instrument’s own record of what it scanned, so it counts as measured, tracked separately as TSG-measured. Only the ZIP index and the header are downloaded — about 0.1% of each archive.
3. Drilled-length estimate — not measured. A borehole with neither an API interval nor a TSG one is estimated once at its drilled length (never per dataset, so rescans cannot inflate it). The headline “≈” is measured + estimated with the split always shown. Blending them silently was the retired method’s flaw.

Scan dates vs ingest dates. A node’s createdDate records when a record was loaded into its database, not when the core was scanned — which is why whole states appear to arrive in a single month under it. Where the TSG mirror has been read, dates come from the TSG header’s own scan date and those clusters disappear. Any node still relying on API dates whose busiest month holds more than 15% of its records is flagged in the table below and its freshness badge reads ingest date, not a scan date. Full rules: METHODOLOGY.md ↗.

Instruments. HyLogger units are identified from instrument fields in dataset metadata (— of — datasets carry instrument data). — boreholes hold more than one scan (up to —).

Live check. Your browser fetches each node’s WFS resultType=hits URL — the same endpoints cited in the Verify column — and reads numberMatched from the XML. Some government servers do not send CORS headers, so a browser fetch can be blocked even while the service is up; the source link always works because it opens the server’s answer directly.