OneDZ: A Global Detrital Zircon Database and Implications for Constructing Giant Geoscience Database

We strongly recommend that users who need fast relational queries download the original SQL dump in version 1 of this record. If you prefer to work without SQL, the raw CSV tables provided in version 2 are the simplest alternative. In addition, version 3 (current) adds a relational table in which every zircon record is keyed by a Harbin-algorithm-generated unique ID, incorporates all new contributions received up to 1 August 2025, and summarises the most common encoding artefacts (Chinese, Latin and Arabic characters mis-rendered during prior UTF-8/ANSI conversions). When importing, please ensure that the primary-key column is preserved and that your client is set to UTF-8. | Correct character | Typical mis-rendered sequence | Language/script | Affected contexts\* || --------------- | ----------------------------- | --------------- | -------------------------- || 岩 | 丠, 岩, 岩? | Chinese | 地层名称, 岩性描述 || 锆 | é’„, 镶, 锆? | Chinese | 锆石, 锆石U-Pb || 喜 | å–œ, å–œ?, 喜? | Chinese | 喜山期, 喜马拉雅 || 世 | 世, 世? | Chinese | 地质年代, 上新世 || ñ | ñ, ñ | Latin | Mañicaragua Fm, Peña Negra || ç | ç, ç | Latin | Maçacará Gp, Curaçá Fm || é | é, é | Latin | Precambriérien, Jurássico || ã | ã, ã | Latin | Serra ão, Triãngulo || ﻩ | ?, ØŸ, 问号 | Arabic | جبل (Jebel), حجر (rock) || ﻙ | ?, Ùƒ | Arabic | كربونيفيري (Carboniferous) || ﺔ | ?, Ø© | Arabic | ﺔﻘﺒﻄ (Taqabat Fm) | Due to the departure of several graduate students who originally compiled the database, and because our remaining resources are fully committed to web-platform development, the table above lists representative errors only; we do not have the personnel to exhaustively catalogue every encoding artefact. All records have since been automatically rectified with GeoGPT, and the entire dataset is now provided in English, yet—because local encoding settings differ across PCs—we cannot guarantee that every user will be entirely free of garbled text. Both the v1 SQL dump and all CSV/XLSX files in v2 are encoded in UTF-8; please ensure your client is likewise configured before import. The GeoGPT-based repair and translation modules are under active development and testing, and we expect a future web release to resolve these issues definitively.