Stratigraphy and WellboreMarkerSet - questions and concerns
Refer to this excellent documentation (worked example) https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/blob/master/Examples/WorkedExamples/Reservoir%20Data/Stratigraphy/README.md
For wellbore 15/3-7,
Top of Viking (group, rank=1) = 4049.0 m Top of Draupne (formation, rank=2) is 4049.0 m. Top of Heather (formation, rank=2) is 4049.0 m.
Looking at populated WellboreMarkerSet record in https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Examples/work-product-component/WellboreMarkerSet.1.2.1.json
For populated load manifest of sample data (TNO marker data) does not utilize adequate number of properties from Marker array. https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/4-instances/TNO/work-products/markers_1_1_0/load_top_1.1.0_1001_csv.json
"Markers": [
{
"MarkerName": "QUATER. UNDIFF.",
"MarkerMeasuredDepth": 0.0
},
{
"MarkerName": "Breda Formation",
"MarkerMeasuredDepth": 282.0
},
{
"MarkerName": "Veldhoven Clay Member",
"MarkerMeasuredDepth": 501.0
},
It would be nice to get suitable sample data, JSON files/load-manifests (for related entities) that actually match with this excellent documentation. Some hints are in the worked example. Such as- for "Gudrun" Stratigraphic Column - https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/blob/master/Examples/WorkedExamples/Reservoir%20Data/Stratigraphy/README.md#stratigraphic-column So, it is necessary to convert this information in a complete (loadable) package so as to get a proper reference.
My concerns - Markers.MarkerName is "free text". Open to human error. When Data Loader is populating data from many wells from this NPD field, he/she uses "Top of Draupne" for one well and uses "Top - Draupne" for another well. Use case - for obtaining contour map of "Top of Draupne", it becomes necessary to get MD (or TVD-SS), X, Y from all wellbores.
Question -
- FeatureTypeID and FeatureName. FeatureType can be "Top", "Base". The values are clear. FeatureName - why is this left as "free text" rather than link to existing record in some other parent entity?
https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/E-R/reference-data/FeatureType.1.0.0.md Description = Used to describe the type of features. Common values being Top, Base, OWC, Fault etc.
Is the property name unambiguous? Is this more "Contact type"? In any case, what would be typical value of FeatureName in NPD example when we have to build Markers array for NPD Wellbore 15-3/7?
Top of Viking (group, rank=1) = 4049.0 m Top of Draupne (formation, rank=2) is 4049.0 m. Top of Heather (formation, rank=2) is 4049.0 m.
- In Markers array, there are some properties. Such as MarkerTypeID, Missing. Being array, we can populate information of several markers within one specific Wellbore.
Now, there is also provision of new property/block.
AvailableMarkerProperties such as MissingThickness. Not obvious how this will be used for multiple elements as present in markers array.
- For WellboreMarkerSet, it is linked to one StraigraphicColumn. The link is from overall record and not individual array element.
In any case, what would be typical value of StraigraphicColumn in NPD example when we have to build Markers array for NPD Wellbore 15-3/7? Leave that as "Gudrun" for Column overall?
Top of Viking (group, rank=1) = 4049.0 m Top of Draupne (formation, rank=2) is 4049.0 m. Top of Heather (formation, rank=2) is 4049.0 m.
cc - @gehrmann and @Keith_Wall for information