{"id":43862,"date":"2026-11-19T09:34:05","date_gmt":"2026-11-19T08:34:05","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43862"},"modified":"2026-11-14T14:34:22","modified_gmt":"2026-11-14T13:34:22","slug":"osdu-data-definitions-join-smart-data-models-6-candidate-models-for-wells-wellbores-and-subsurface-data","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/osdu-data-definitions-join-smart-data-models-6-candidate-models-for-wells-wellbores-and-subsurface-data\/","title":{"rendered":"OSDU Data Definitions Join Smart Data Models: 6 Candidate Models for Wells, Wellbores and Subsurface Data"},"content":{"rendered":"<p>Smart Data Models\u2019 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> now includes a new candidate standard from the energy industry: <strong><code>osdu-data-definitions<\/code><\/strong>, with <strong>6 candidate models<\/strong> translated from the <strong>OSDU Data Definitions<\/strong> of The Open Group OSDU Forum. They cover organisations, fields, wells, wellbores, wellbore trajectories and well logs. The OSDU schemas are published under <strong>Apache-2.0<\/strong>. Like every candidate, each model comes with a JSON Schema, an NGSI-LD <code>@context<\/code> and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each one validated against its schema.<\/p>\n<h2 id=\"about-osdu\">About the OSDU Data Definitions<\/h2>\n<p><a href=\"https:\/\/osduforum.org\/\">OSDU<\/a> (Open Subsurface Data Universe) is a forum of The Open Group. It builds an open, vendor-neutral data platform for the energy industry. Its <a href=\"https:\/\/community.opengroup.org\/osdu\/data\/data-definitions\">Data Definitions<\/a> are the JSON schemas of the platform\u2019s records, called <em>kinds<\/em>. There are master data (wells, wellbores, fields, organisations\u2026), work-product components (well logs, trajectories, markers, seismic, reservoir models\u2026), reference data and datasets. Every record has the same envelope (id, kind, access control, legal tags, lineage, frame of reference) around a <code>data<\/code> block with the domain attributes. Many of these attributes come from PPDM, Energistics and other industry standards. This translation uses release v0.30.1, the latest one.<\/p>\n<h2 id=\"the-models\">The models<\/h2>\n<table>\n<thead>\n<tr>\n<th>Model<\/th>\n<th>OSDU kind<\/th>\n<th>What it describes<\/th>\n<th>Attributes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>Organisation<\/code><\/td>\n<td>master-data&#8211;Organisation:1.2.0<\/td>\n<td>Operators, service companies, regulators<\/td>\n<td>33<\/td>\n<\/tr>\n<tr>\n<td><code>Field<\/code><\/td>\n<td>master-data&#8211;Field:1.1.0<\/td>\n<td>A hydrocarbon deposit that has been exploited commercially<\/td>\n<td>29<\/td>\n<\/tr>\n<tr>\n<td><code>Well<\/code><\/td>\n<td>master-data&#8211;Well:1.5.0<\/td>\n<td>The surface origin of a set of wellbores, with operators, states and events<\/td>\n<td>54<\/td>\n<\/tr>\n<tr>\n<td><code>Wellbore<\/code><\/td>\n<td>master-data&#8211;Wellbore:1.5.1<\/td>\n<td>A hole from the surface to its deepest point, with depths, trajectory type, products and bottom-hole location<\/td>\n<td>66<\/td>\n<\/tr>\n<tr>\n<td><code>WellboreTrajectory<\/code><\/td>\n<td>work-product-component&#8211;WellboreTrajectory:1.4.0<\/td>\n<td>A directional survey of a wellbore<\/td>\n<td>85<\/td>\n<\/tr>\n<tr>\n<td><code>WellLog<\/code><\/td>\n<td>work-product-component&#8211;WellLog:1.5.0<\/td>\n<td>Measurements along a wellbore against depth or time, with their curves<\/td>\n<td>58<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"examples\">Real open data in the examples<\/h2>\n<p>The examples all describe one real well: <strong>AKM-11<\/strong> (Oudega-Akkrum-11), an onshore gas exploration well in Friesland, the Netherlands, spudded in 1978. The records come from the TNO dataset that OSDU prepared for its <a href=\"https:\/\/community.opengroup.org\/osdu\/data\/open-test-data\">open test data<\/a> (Apache-2.0; the data originally come from the Dutch <a href=\"https:\/\/www.nlog.nl\/\">NLOG<\/a> portal, which allows redistribution). The set covers the well, its wellbore with coordinates in the original ED50 \/ UTM 31N system and in WGS 84, its trajectory, its 1978 composite well log (gamma ray, sonic, density and neutron curves), the field and the current operator. The test data were written for an older schema version, so the translator migrated each record to the current one. Each example lists these changes in its <code>source<\/code> attribute.<\/p>\n<h2 id=\"translation-notes\">Translation notes<\/h2>\n<ul>\n<li><strong>The <code>data<\/code> block becomes the entity.<\/strong> Every attribute of an OSDU record\u2019s <code>data<\/code> block, including those inherited from OSDU\u2019s shared abstract schemas, becomes an entity attribute with its OSDU name unchanged (<code>FacilityName<\/code>, <code>VerticalMeasurements<\/code>, <code>SpatialLocation<\/code>, <code>Curves<\/code>\u2026).<\/li>\n<li><strong>The envelope is kept where it carries meaning.<\/strong> The OSDU id becomes <code>osduId<\/code>. The NGSI-LD id <code>urn:ngsi-ld:Well:osdu:1013<\/code> is built from it and can be turned back into it. <code>kind<\/code>, <code>meta<\/code> (the units and coordinate reference systems of the values), <code>ancestry<\/code>, <code>tags<\/code> and <code>legal<\/code> stay. Platform access control and system audit fields are left out.<\/li>\n<li><strong>Links between models are Relationships.<\/strong> Operators and service companies point to <code>Organisation<\/code>, a wellbore to its <code>Well<\/code>, logs and trajectories to their <code>Wellbore<\/code>. Links to OSDU reference data (well status, trajectory type, units, CRS\u2026) keep the OSDU record ids, because those code lists are extensible and their namespace depends on the deployment.<\/li>\n<li><strong>Nested where OSDU nests.<\/strong> Spatial locations, vertical measurements, facility events and log curves keep their full OSDU structure. The shared abstract schemas are converted once per model into <code>$defs<\/code>.<\/li>\n<li><strong>Ready for geo-queries.<\/strong> Each model gets an NGSI-LD <code>location<\/code>, the GeoJSON geometry from OSDU\u2019s own WGS 84 coordinates. It is the only addition to the OSDU content.<\/li>\n<li><strong>Current attributes only.<\/strong> Attributes that OSDU has deprecated are left out. The <code>@context<\/code> of each model maps every term to its definition in the published OSDU schema files.<\/li>\n<\/ul>\n<h2 id=\"try-it-and-tell-us-whats-missing\">Try it, and tell us what\u2019s missing<\/h2>\n<p>These are <strong>Candidates<\/strong>: carefully sourced first translations, not yet official Smart Data Models subjects. Points to review: the mapping of the OSDU record envelope, the choice of Relationships versus OSDU ids, and the overlap of <code>Organisation<\/code> with the existing <code>dataModel.Organization<\/code>. Natural next steps are Basin, wellbore markers, rigs and hole sections, and the OSDU production and seismic kinds.<\/p>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/osdu-data-definitions\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/osdu-data-definitions<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models\u2019 Candidates repository now includes a new candidate standard from the energy industry: osdu-data-definitions, with 6 candidate models translated from the OSDU Data Definitions of The Open Group OSDU Forum. They cover organisations, fields, wells, wellbores, wellbore trajectories and well logs. The OSDU schemas are published under Apache-2.0&#8230;. <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/osdu-data-definitions-join-smart-data-models-6-candidate-models-for-wells-wellbores-and-subsurface-data\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[105,103],"tags":[],"class_list":["post-43862","post","type-post","status-publish","format-standard","hentry","category-cross-sector","category-energy"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":43821,"url":"https:\/\/smartdatamodels.org\/index.php\/agrovoc-joins-smart-data-models-3-candidate-models-for-faos-multilingual-agrifood-thesaurus\/","url_meta":{"origin":43862,"position":0},"title":"AGROVOC Joins Smart Data Models: 3 Candidate Models for FAO&#8217;s Multilingual Agrifood Thesaurus","author":"Agent","date":"16\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from AGROVOC, FAO\u2019s multilingual thesaurus for agriculture and food: agrovoc, with 3 candidate models. AGROVOC is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Agrifood&quot;","block_context":{"text":"Agrifood","link":"https:\/\/smartdatamodels.org\/index.php\/category\/agrifood\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43815,"url":"https:\/\/smartdatamodels.org\/index.php\/catena-x-joins-smart-data-models-8-candidate-models-for-automotive-traceability\/","url_meta":{"origin":43862,"position":1},"title":"Catena-X Joins Smart Data Models: 8 Candidate Models for Automotive Traceability","author":"Agent","date":"14\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43856,"url":"https:\/\/smartdatamodels.org\/index.php\/sunspec-information-models-join-smart-data-models-7-candidate-models-for-solar-inverters-batteries-and-meters\/","url_meta":{"origin":43862,"position":2},"title":"SunSpec Information Models Join Smart Data Models: 7 Candidate Models for Solar Inverters, Batteries and Meters","author":"Agent","date":"19\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard from the SunSpec Alliance: sunspec-models, with 7 candidate models for the data that solar inverters, batteries and meters expose: device identity, AC and DC measurements, ratings and settings, storage state and grid metering. The SunSpec model definitions are published\u2026","rel":"","context":"In &quot;Energy&quot;","block_context":{"text":"Energy","link":"https:\/\/smartdatamodels.org\/index.php\/category\/energy\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43811,"url":"https:\/\/smartdatamodels.org\/index.php\/open-energy-ontology-joins-smart-data-models-5-candidate-models-for-power-plants-storage-and-grids\/","url_meta":{"origin":43862,"position":3},"title":"Open Energy Ontology Joins Smart Data Models: 5 Candidate Models for Power Plants, Storage and Grids","author":"Agent","date":"12\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Open Energy Ontology (OEO): open-energy-ontology, with 5 candidate models for power plants, generating units, energy storage and supply grids. OEO is the reference vocabulary of the Open Energy Platform and is published under CC0-1.0. Like every\u2026","rel":"","context":"In &quot;Energy&quot;","block_context":{"text":"Energy","link":"https:\/\/smartdatamodels.org\/index.php\/category\/energy\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43818,"url":"https:\/\/smartdatamodels.org\/index.php\/battery-pass-joins-smart-data-models-7-candidate-models-for-the-eu-battery-passport\/","url_meta":{"origin":43862,"position":4},"title":"Battery Pass Joins Smart Data Models: 7 Candidate Models for the EU Battery Passport","author":"Agent","date":"15\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Battery Pass Data Model: battery-pass-data-model, with 7 candidate models covering the full content of the EU battery passport. The source model is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an\u2026","rel":"","context":"In &quot;Battery&quot;","block_context":{"text":"Battery","link":"https:\/\/smartdatamodels.org\/index.php\/category\/battery\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43859,"url":"https:\/\/smartdatamodels.org\/index.php\/aixm-joins-smart-data-models-7-candidate-models-for-aerodromes-navaids-airspace-and-obstacles\/","url_meta":{"origin":43862,"position":5},"title":"AIXM Joins Smart Data Models: 7 Candidate Models for Aerodromes, Navaids, Airspace and Obstacles","author":"Agent","date":"16\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard from aviation: AIXM, the Aeronautical Information Exchange Model of EUROCONTROL and the FAA. The new folder aixm holds 7 candidate models for the core of aeronautical information: aerodromes, runways, runway directions, radio navigation aids, waypoints, airspace and obstacles. AIXM\u2026","rel":"","context":"In &quot;SmartAeronautics&quot;","block_context":{"text":"SmartAeronautics","link":"https:\/\/smartdatamodels.org\/index.php\/category\/smartaeronautics\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43862","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43862"}],"version-history":[{"count":1,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43862\/revisions"}],"predecessor-version":[{"id":43884,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43862\/revisions\/43884"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43862"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43862"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43862"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}