Deliverable 5.5 Data models and code lists

Transcription

1 This document Steps creating valid M4EU, EURare and PROSUM WFS Features is a part of the official delivery in the ProSUM project: Deliverable 5.5 Data models and code lists Project Prospecting Secondary raw materials in the Urban mine and Mining waste Acronym ProSUM Grant Agreement Funding Scheme Horizon 2020 Webpage Work Package Work Package 5 Work Package Leader Daniel Cassard - BRGM Deliverable Title Data models and code lists Deliverable Number D 5.5 Deliverable Leader Frands Schjøth - GEUS Version: 6.0 Status Final for PMT review Author Tjerk Heijboer GEUS, Frands Schjøth GEUS, Martin Podboj Geo-ZS, Daniel Cassard BRGM, Francois Tertre BRGM & Anders Hallberg - SGU Reviewed by Project Management Team tch@geus.dk Scientific Coordinators Dr. Jaco Huisman, Scientific Advisor, UNU IAS SCYCLE Dr. Nikolaos Arvanitidis, Head of Unit, SGU Huisman@unu.edu Nikolaos.Arvanitidis@sgu.se This project has received funding from the European Union s Horizon 2020 research and innovation programme under grant agreement No

2 DOCUMENT CONTROL Project Coordinator: WEEE Forum Work Package Leader: BRGM Deliverable leader: GEUS Due date: M[N] 3 March 206 Date of submission: M[N] 2 May 206 Dissemination level: PU (Public) Version history Ver. no. Date Reason for release Responsible Initial Version Tjerk Heijboer Some changes Tjerk Heijboer Sarah Downes Merging mining waste into document Tjerk Heijboer Updating the text Frands Schjøth Some text changes and improvements Tjerk Heijboer Some text changes and improvements Frands Schjøth Merging DC and FT s comments, changing processtypecodevalue in urban mine to modified values from PC and AL Final for PMT review SD edit, modified how the class, table, column styles, and included SD suggested Definitions. Page formatting few corrections and code list corrections Removed old ProductKey-EEE list, added new list from Jaco. Daniel Cassard, Francois Tertre, Tjerk Heijboer Sarah Downes, Tjerk Heijboer Frands Schjøth, Daniel Cassard Tjerk Heijboer NOTICE The contents of this document are the copyright of the ProSUM consortium and shall not be copied in whole, in part, or otherwise reproduced (whether by photographic, reprographic or any other method), and the contents thereof shall not be divulged to any other person or organisation without prior written permission. Such consent is hereby automatically given to all members who have entered into the ProSUM Consortium Agreement, dated st December 204, and to the Research Executive Agency / European Commission to use and disseminate this information. The information and content of this report is the sole responsibility of the ProSUM Consortium members and does not necessarily represent the views expressed by the European Commission or its services. Whilst the information contained in the documents and webpages of the project is believed to be accurate, the author(s) or any other participant in the ProSUM consortium make no warranty of any kind with regard to this material. 2

3 TABLE OF CONTENTS TABLE OF CONTENTS... 3 List of Tables... 6 List of Figures... 7 PURPOSE... 8 EXECUTIVE SUMMARY Introduction Definitions/glossary of terms Conceptual data model Database, data models and data flow related terms ProSUM urban mine Introduction The unified conceptual model The database implementation Mapping CRM parameters to the unified data model Code list values ProductCategoryCodeValue ProductKeyCodeValue MaterialKeyCodeValue ElementKeyCodeValue CountryCodeValue ProcessTypeCodeValue EconomicSectorCodeValue EvaluationMethodCodeValue FlowTypeCodeValue DownstreamWasteFlowCodeValue WasteCategoryCodeValue UncertaintyTypeCodeValue UnitOfMeasureCodeValue PreferredQuantityTypeCodeValue Prosum Mining waste Conceptual model Database model Codelists Conclusions Recommendations and outlook

4 7. References Annexes Urban mine (WEEE, BATT, ELV) Code lists used in the unified database model All ProductKeyCodeValue values All MaterialKeyCodeValue values Steps creating valid M4EU, EURare and PROSUM WFS Features INSPIRE mr-core MiningFeatureOccurrence M4EU Mine_Extension: M4EU MiningActivity_Extension: M4EU MiningWaste_Extension: M4EU/PROSUM Product_Extension: M4EU/PROSUM Mineraloccurrence_Extension: PROSUM Mine_Extension: PROSUM ProcessingTransformationPlant: PROSUM ProcessingTransformationActivity: PROSUM MiningWaste: PROSUM MiningActivity: M4EU DocumentCitation: M4EU Commodity_Extension: M4EU RockMaterial: M4EU Mineral Valid WFS server request for M4EU, EURare and ProSUM All M4EU, EURare and ProSUM Mining Waste Codelist values AlterationDegreeType AlterationDistributionType AlterationTypeType AmountEstimationMethodType AnalyticalMethodTypeType AssociationTypeType ClassificationMethodUsedType CommodityType CompositionCategoryType CompositionEstimationMethodType ConsolidationDegreeType ConstituentPartRoleType ConventionType CountryType DepositGroupType DepositTypeType DeterminationMethodType

5 4.8 EndusePotentialType EnvironmentalDomainType EnvironmentalImpactType EventEnvironmentType EventProcessType ExplorationActivityTypeType ExplorationResultType ExpressionType ExtractionMethodType FormType GeneticCategoryType ImportanceType InstrumentTypetype LegislationLevelType LinearDirectedType LithologyType MaterialClassType MaterialRoleType MineralNameType MineStatusType MiningActivityTypeType NamedAgeType ObservedPropertyType OccurrenceTypeType PhysicalPropertyType PlanarPolarityType ProcessingActivityTypeType ProcessingTransformationPlantStatusType ProductType RawMaterialRoleType ReserveCategoryType ResourceCategoryType ResultQualityType SamplingMethodType ShapeType SpecialisedZoneTypeType SpecimenTypeType SupergeneProcessesTypeType UNFCategoryType UomAreaType

6 4.58 UomDensityType UomGeochemistryType UomLengthType UomPhysicalPropertyType UomVolumeType UomWeightType WasteStorageTypeType WasteTypeType ZoneTypeType List of Tables Table : Code list and sources for WEEE, ELV and BATT Table 2: List of types of CRM parameter data and how data is stored in the unified database Table 3: values derived from the product types stored in product key Table 4: Sub set of the Product codelist values used in the project Table 5: Example of material type code values Table 6: List of elements Table 7: Country codes that may be used in the frame of urban mine data Table 8: List of Processes types Table 9: Flow types Table 0: Materials present in down stream waste flow Table : Types of uncertainty defined in the project Table 2: Units of measure... 4 Table 3: Preferred quantity types... 4 Table 4: List of code lists and sources for the ProSUM mining waste extension Table 5: All product keys and codes for urban waste. Note in the portrayals EEE-007 and EEE- 00 are used, which have not yet been clearly defined Table 6: All material type code values as used in the database

7 List of Figures Figure : UML class diagram describing the unified conceptual data model for WEEE, ELV and BATT. A larger pdf version can be found here Figure 2: UML class diagram summarizing ProSUM modifications to the M4EU conceptual data model (green) a pdf version of this diagram can be found here... Figure 3: Relations between components of secondary raw materials (SRM) platforms Figure 4: Database model showing only the stock and flows tables and their relationships to the product table.a more detailed image can be found here Figure 5: Part of the unified database model showing only the product, component, material and element tables and their relationships and column names. A more detailed image can be found here Figure 6: Part of the database model for metadata related to the material, element and component measure tables. A more detailed image can be found here Figure 7: The EU-UMKDP architecture. The database models are used in the Provider DB in green, Harvesting DB and Diffusion DB Figure 8: the M4EU and EURare DB model version A pdf version can be found here Figure 9: Overview of tables added to the M4EU DB model in the context of Prosum. A pdf version can be found here Figure 0: ProSUM mining waste relation to the M4EU DB model. A pdf version can be found here Figure : ProSUM mining activity relation to the M4EU DB model. A pdf version can be found here Figure 2: ProSUM processing transformation plant relation to the M4EU DB model. A pdf version can be found here

8 4. Prosum Mining waste Figure 7: The EU-UMKDP architecture. The database models are used in the Provider DB in green, Harvesting DB and Diffusion DB. Figure 7 shows the system architecture describing the flow of data from Geological Surveys to the end user in the EU-UMKDP. The architecture in the ProSUM project is the same as for Minerals4EU and the EU-MKDP, but the structure of the databases and data formats has been modified. The basis of the Web services, and databases are a conceptual UML model, on which a database model and WFS xml schemas are created. TNO, BRGM, GEUS and GeoZS developed the M4EU conceptual UML model and the relational database model during the Minerals4EU project (-Sep-203 to 3-Aug-205) and the EURare project (-Jan-203 to 3-Dec-207) using expierences from EuroGeoSource project (0-Apr-200 to 3-Mar-203) and the ProMine project (0-May-2009 to 30-Apr-203). The final version from May 205 of the M4EU database model was v The needs expressed in the ProSUM project made it necessary to create new Feature and datatype classes as they were incompatible with v of the M4EU DB model. The ProSUM mining waste extension extends this M4EU DB model v without changing the former table names. However new attributes, constraints and new codes in code lists together with new tables are introduced in the ProSUM mining waste extension which currently has version v Conceptual model In Annex 2 of draft D5.7 on the specification of the EU-UMKDP, a modified ERML conceptual model is presented. D5.7 describes how these modifications are recreated in the conceptual model used in Minerals4EU (Figure 2). The Minerals4EU conceptual data model extends the INSPIRE Mineral resources conceptual model version 3. To remain compliant with the current INSPIRE data specifications the old implementation needed to be maintained so that a data provider still can deliver data that is compliant with INSPIRE, but also can deliver data with the 42

9 pkg Data Model - Overview Whole model Name: Data Model - Overview Whole model Author: waardenburgfde Version: Created: :39:33 Updated: :49:4 MineName *PK minenamedbk: bigserial *FK minedbk: bigint * name: varchar(50) Mine *PK minedbk: bigserial *FK miningfeatureoccurrencedbk: bigint beginlifespanversion: timestamp FK beginlifespanversionvoidreason: varchar(50) endlifespanversion: timestamp FK endlifespanversionvoidreason: varchar(50) * name: varchar(50) *FK status: varchar(50) startdate: timestamp FK startdatevoidreason: varchar(50) enddate: timestamp FK enddatevoidreason: varchar(50) *FK country: varchar(2) FK sourcereferencevoidreason: varchar(50) FK relatedminedbk: bigint FK relatedminevoidreason: varchar(50) 0.. MiningFeatureOccurrence *PK miningfeatureoccurrencedbk: bigserial * geometry: geometry * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) inspireversionidvoidreason: varchar(50) WasteStorage *PK wastestoragedbk: bigserial *FK miningwastedbk: bigint *FK wastestoragetype: varchar(50) EnvironmentalImpact MineRemark *PK mineremarkdbk: bigserial *FK minedbk: bigint * remark: text MiningWaste *PK miningwastedbk: bigserial *FK miningfeatureoccurrencedbk: bigint *FK miningactivitydbk: bigint *FK wastetype: varchar(50) storagetypevoidreason: varchar(50) FK materialvoidreason: varchar(50) FK wastemeasurevoidreason: varchar(50) volume: real FK uomvolume: varchar(50) FK volumevoidreason: varchar(50) density: real FK uomdensity: varchar(50) FK densityvoidreason: varchar(50) grade: real FK gradevoidreason: varchar(50) FK environmentalimpactvoidreason: varchar(50) *PK environmentalimpactdbk: bigserial *FK miningwastedbk: bigint *FK environmentalimpact: varchar(50) {XOR} 0.. MiningActivity *PK miningactivitydbk: bigserial *FK miningfeatureoccurrencedbk: bigint FK minedbk: bigint FK mineraloccurrencedbk: bigint mineralproducingcountrydbk: bigint begintime: timestamp endtime: timestamp *FK miningactivitytype: varchar(50) *FK processingactivitytype: varchar(50) oreprocessed: real FK uom: varchar(50) FK oreprocessedvoidreason: varchar(50) FK associatedminevoidreason: varchar(50) FK depositvoidreason: varchar(50) FK rawmaterialvoidreason: varchar(50) FK producedwastevoidreason: varchar(50) FK producedmaterialvoidreason: varchar(50) 0.. MinedMaterial *PK minedmaterialdbk: bigserial *FK miningactivitydbk: bigint *FK rawmaterialrole: varchar(50) minproportion: real maxproportion: real FK proportionvoidreason: varchar(50) 0.. {XOR} MineralProducingCountry *PK mineralproducingcountrydbk: bigserial * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) FK inspireversionidvoidreason: varchar(50) beginlifespanversion: timestamp FK beginlifespanversionvoidreason: varchar(50) endlifespanversion: timestamp FK endlifespanversionvoidreason: varchar(50) *FK country: varchar(2) * geometry: geometry resourceextractionvoidreason: varchar(50) oreamountvoidreason: varchar(50) Product *PK productdbk: bigserial *FK miningactivitydbk: bigint *FK product: varchar(50) grade: real FK gradevoidreason: varchar(50) production: real FK uomproduction: varchar(50) FK productionvoidreason: varchar(50) recovery: real FK recoveryvoidreason: varchar(50) commoditydbk: bigint FK sourcecommodityvoidreason: varchar(50) DocumentCitation *PK documentcitationdbk: bigserial FK mineraloccurrencedbk: bigint FK oremeasuredbk: bigint FK productdbk: bigint FK minedbk: bigint FK managementzonedbk: bigint FK analyticalprocessdbk: bigint * name: text shortname: varchar(50) FK shortnamevoidreason: varchar(0) date: timestamp FK datevoidreason: varchar(50) link: varchar(256) FK linkvoidreason: varchar(50) specificreference: text FK specificreferencevoidreason: varchar(50) Commodity 0.. *PK commoditydbk: bigserial EarthResourceMaterial EarthMaterial FK mineraloccurrencedbk: bigint FK mineralproducingcountrydbk: bigint *FK commodity: varchar(50) *PK earthresourcematerialdbk: bigserial *PK earthmaterialdbk: bigserial FK importance: varchar(50) *FK mineraloccurrencedbk: bigint FK earthresourcematerialdbk: bigint 0.. FK importancevoidreason: varchar(50) *FK materialrole: varchar(50) FK miningwastedbk: bigint rank: integer proportion: real FK minedmaterialdbk: bigint FK rankvoidreason: varchar(50) FK proportionvoidreason: varchar(50) FK supergeneprocessesdbk: bigint FK alterationdescriptiondbk: bigint FK constituentpartdbk: bigint FK physicalpropertyvoidreason: varchar(50) AnalyticalProcess *PK analyticalprocessdbk: bigserial *FK methodtype: varchar(50) operator: varchar(50) FK instrumenttype: varchar(50) Endow ment *PK endowmentdbk: bigserial *FK oremeasuredbk: bigint includesreserves: boolean includesreservesvoidreason: varchar(50) includesresources: boolean includesresourcesvoidreason: varchar(50) {XOR} Resource *PK resourcedbk: bigserial *FK oremeasuredbk: bigint *FK category: varchar(50) includesreserves: boolean includesreservesvoidreason: varchar(50) Reserve *PK reservedbk: bigserial *FK oremeasuredbk: bigint *FK category: varchar(50) Specimen *PK specimendbk: bigserial FK mineraloccurrencedbk: bigint FK miningwastedbk: bigint *FK materialclass: varchar(50) * samplingtime: timestamp FK samplingmethod: varchar(50) FK specimentype: varchar(50) samplinglocation: geometry Measurement *PK measurementdbk: bigserial *FK specimendbk: bigint FK analyticalprocessdbk: bigint *FK observedproperty: varchar(50) * result: real *FK uomresult: varchar(50) * resulttime: timestamp validtime: timestamp FK resultquality: varchar(50) OreMeasure *PK oremeasuredbk: bigserial FK mineraloccurrencedbk: bigint FK mineralproducingcountrydbk: bigint *FK classificationmethodused: varchar(50) calculationdate: timestamp * minquantity: real * maxquantity: real *FK uomquantity: varchar(50) FK dimensionvoidreason: varchar(50) minarea: real maxarea: real FK uomarea: varchar(50) FK areavoidreason: varchar(50) mindepth: real maxdepth: real FK uomdepth: varchar(50) FK depthvoidreason: varchar(50) minlength: real maxlength: real FK uomlength: varchar(50) FK lengthvoidreason: varchar(50) minwidth: real maxwidth: real FK uomwidth: varchar(50) FK widthvoidreason: varchar(50) FK proposedextractionmethod: varchar(50) proposedextractionmethodvoidreason: varchar(50) CommodityMeasure *pfk commoditymeasuredbk: bigserial * oremeasuredbk: bigint * commoditydbk: bigint minamount: real maxamount: real FK uomamount: varchar(50) FK amountvoidreason: varchar(50) cutoffgrade: real FK cutoffgradevoidreason: varchar(50) grade: real FK gradevoidreason: varchar(50) GeologicEvent *PK geologiceventdbk: bigserial *FK mineraloccurrencedbk: bigint name: varchar(50) FK namevoidreason: varchar(50) FK eventenvironment: varchar(50) FK eventenvironmentvoidreason: varchar(50) FK eventprocess: varchar(50) FK eventprocessvoidreason: varchar(50) FK oldernamedage: varchar(50) FK oldernamedagevoidreason: varchar(50) FK youngernamedage: varchar(50) FK youngernamedagevoidreason: varchar(50) UnfClassification *PK unfclassificationdbk: bigserial *FK oremeasuredbk: bigint *FK category: varchar(50) 0.. {XOR} {XOR} {XOR} 0.. MineralOccurrence ExplorationActivity *PK explorationactivitydbk: bigserial *FK mineraloccurrencedbk: bigint begintime: timestamp endtime: timestamp *FK activitytype: varchar(50) *PK mineraloccurrencedbk: bigserial * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) FK inspireversionidvoidreason: varchar(50) beginlifespanversion: timestamp FK beginlifespanversionvoidreason: varchar(50) endlifespanversion: timestamp FK endlifespanversionvoidreason: varchar(50) name: varchar(50) FK namevoidreason: varchar(50) FK dimensionvoidreason: varchar(50) minarea: real maxarea: real FK areavoidreason: varchar(50) FK uomarea: varchar(50) mindepth: real maxdepth: real FK uomdepth: varchar(50) FK depthvoidreason: varchar(50) minlength: real maxlength: real FK uomlength: varchar(50) FK lengthvoidreason: varchar(50) minwidth: real maxwidth: real FK uomwidth: varchar(50) FK widthvoidreason: varchar(50) FK expression: varchar(50) FK expressionvoidreason: varchar(50) FK classificationvoidreason: varchar(50) FK depositgroup: varchar(50) FK deposittype: varchar(50) FK deposittypevoidreason: varchar(50) *FK occurrencetype: varchar(50) FK associationtype: varchar(50) *FK country: varchar(2) * geometry: geometry FK geologichistoryvoidreason: varchar(50) FK formvoidreason: varchar(50) FK linearorientationvoidreason: varchar(50) FK planarorientationvoidreason: varchar(50) FK shapevoidreason: varchar(50) FK sourcereferencevoidreason: varchar(50) FK explorationhistoryvoidreason: varchar(50) FK resourceextractionvoidreason: varchar(50) FK oreamountvoidreason: varchar(50) FK endusepotentialvoidreason: varchar(50) geneticdescriptionvoidreason: varchar(50) FK compositionvoidreason: varchar(50)..* AlterationDistribution *PK alterationdistributiondbk: bigserial *FK alterationdescriptiondbk: bigint *FK alterationdistribution: varchar(50) 0.. A ExplorationResult *PK explorationresultdbk: bigserial *FK explorationactivitydbk: bigint *FK result: varchar(50) LinearOrientation *PK linearorientationdbk: bigserial *FK mineraloccurrencedbk: bigint *FK determinationmethod: varchar(50) descriptiveorientation: varchar(50) FK descriptiveorientationvoidreason: varchar(50) plunge: real FK plungevoidreason: varchar(50) trend: real FK trendvoidreason: varchar(50) FK directed: varchar(50) FK directedvoidreason: varchar(50) EndusePotential *PK endusepotentialdbk: bigserial *FK mineraloccurrencedbk: bigint *FK endusepotential: varchar(50) OccurrenceShape *PK occurrenceshapedbk: bigserial *FK mineraloccurrencedbk: bigint FK shape: varchar(50) OccurrenceName *PK occurrencenamedbk: bigserial *FK mineraloccurrencedbk: bigint * name: varchar(50) MineralDepositType *PK mineraldeposittypedbk: bigserial FK mineraloccurrencedbk: bigint FK deposittype: varchar(50) SupergeneProcesses *PK supergeneprocessesdbk: bigserial *FK mineraloccurrencedbk: bigint mindepth: real maxdepth: real FK uomdepth: varchar(50) FK depthvoidreason: varchar(50) FK materialvoidreason: varchar(50) FK type: varchar(50) FK typevoidreason: varchar(50) AlterationDescription 0.. *PK alterationdescriptiondbk: bigserial *FK rockmaterialdbk: bigint *FK alterationtype: varchar(50) FK alterationdegree: varchar(50) FK alterationdegreevoidreason: varchar(50) FK alterationproductvoidreason: varchar(50) FK alterationdistributionvoidreason: varchar(50) 0....* PlanarOrientation *PK planarorientationdbk: bigserial *FK mineraloccurrencedbk: bigint *FK determinationmethod: varchar(50) descriptiveorientation: varchar(50) FK descriptiveorientationvoidreason: varchar(50) *FK convention: varchar(50) azimuth: real FK azimuthvoidreason: varchar(50) dip: real FK dipvoidreason: varchar(50) FK polarity: varchar(50) FK polarityvoidreason: varchar(50) OccurrenceManagementZone *PK occurrencemanagementzonedbk: bigserial *FK mineraloccurrencedbk: bigint *FK managementzonedbk: bigint OccurrenceForm *PK occurrenceformdbk: bigserial *FK mineraloccurrencedbk: bigint *FK form: varchar(50) OccurrenceRemark *PK occurrenceremarkdbk: bigserial *FK mineraloccurrencedbk: bigint * remark: text MineralDepositGroup *PK mineraldepositgroupdbk: bigserial *FK mineraloccurrencedbk: bigint *FK depositgroup: varchar(50) * deposittypevoidreason: varchar(50) 0.. RockMaterial *PK rockmaterialdbk: bigserial *FK earthmaterialdbk: bigint color: varchar(50) FK colorvoidreason: varchar(50) FK compositioncategory: varchar(50) FK compositioncategoryvoidreason: varchar(50) FK geneticcategory: varchar(50) FK geneticcategoryvoidreason: varchar(50) FK consolidationdegree: varchar(50) FK consolidationdegreevoidreason: varchar(50) FK alterationpropertiesvoidreason: varchar(50) FK constituentvoidreason: varchar(50) RockMaterialLithology *PK rockmateriallithologydbk: bigserial *FK rockmaterialdbk: bigint *FK lithology: varchar(50)..* {XOR} EnvironmentalDomain *PK environmentaldomaindbk: bigserial *FK managementzonedbk: bigint *FK environmentaldomain: varchar(50) 0.. ThematicId *PK thematiciddbk: bigserial * managementzonedbk: bigint * identifier: varchar(50) * identifierscheme: varchar(50) Mineral *PK mineraldbk: bigserial *FK earthmaterialdbk: bigint color: varchar(50) FK colorvoidreason: varchar(50) *FK mineralname: varchar(50) ManagementZone *PK managementzonedbk: bigserial * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(25) FK inspireversionidvoidreason: varchar(50) beginlifespanversion: timestamp FK beginlifespanversionvoidreason: varchar(50) endlifespanversion: timestamp FK endlifespanversionvoidreason: varchar(50) *FK zonetype: varchar(50) name: varchar(50) FK namevoidreason: varchar(50) FK specialisedzonetype: varchar(50) FK specialisedzonetypevoidreason: varchar(50) beginvalid: timestamp endvalid: timestamp FK designatedperiodvoidreason: varchar(50) competentauthorityname: varchar(50) FK competentauthorityvoidreason: varchar(50) *FK country: varchar(50) FK relatedzonedbk: bigint FK relatedzonevoidreason: varchar(50) * geometry: geometry FK thematicidvoidreason: varchar(50) FK legalbasisvoidreason: varchar(50) FK planvoidreason: varchar(50) PhysicalDescription *PK physicaldescriptiondbk: bigserial FK earthmaterialdbk: bigint *FK physicalproperty: varchar(50) * value: real *FK uom: varchar(50) 0.. ConstituentPart..* *PK constituentpartdbk: bigserial *FK rockmaterialdbk: bigint FK role: varchar(50) minproportion: real maxproportion: real FK proportionvoidreason: varchar(50) 0.. ManagementZoneName *PK managementzonenamedbk: bigserial *FK managementzonedbk: bigint * name: varchar(50) LegislationCitation *PK legislationcitationdbk: bigserial *FK managementzonedbk: bigint * name: varchar(50) shortname: varchar(50) FK shortnamevoidreason: varchar(50) date: timestamp FK datevoidreason: varchar(50) link: varchar(255) FK linkvoidreason: varchar(50) specificreference: varchar(255) FK specificreferencevoidreason: varchar(50) identificationnumber: varchar(50) officialdocumentnumber: varchar(50) dateenteredintoforce: timestamp daterepealed: timestamp *FK level: varchar(50) officialjournalidentification: varchar(50) journalissn: varchar(50) journalisbn: varchar(50) linktojournal: varchar(255) ProSUM modifications. When a new version of the INSPIRE data specifications is released any deprecated classes in the model will be removed. 4.2 Database model Figure 8: the M4EU and EURare DB model version A pdf version can be found here 43

10 class ProSUM - Additions Name: ProSUM - Additions Author: tch, fsc Version:..2 Created: :00:00 Updated: :33:4 Tables::ProSUMMiningActiv itytype *PK prosumminingactivitytypedbk: bigserial *FK prosumminingactivitydbk: bigint *FK miningactivitytype: varchar(50) Tables::ProSUMMiningActiv ity *PK prosumminingactivitydbk: bigserial *FK miningfeatureoccurrencedbk: bigint FK minedbk: bigint FK mineraloccurrencedbk: bigint FK mineralproducingcountrydbk: bigint begintime: timestamp endtime: timestamp oreprocessed: real FK uom: varchar(50) FK oreprocessedvoidreason: varchar(50) FK associatedminevoidreason: varchar(50) FK depositvoidreason: varchar(50) FK rawmaterialvoidreason: varchar(50) FK producedwastevoidreason: varchar(50) FK producedmaterialvoidreason: varchar(50) Tables::ProcessingTransformationActivityType *PK processingtransformationactivitytypedbk: bigserial FK processingtransformationactivitytype: varchar(50) FK processingtransformationactivitydbk: bigint Tables::ProSUMWasteStorage Tables::ProSUMWasteDimension Tables::ProSUMMiningWasteMeasure *PK prosumwastestoragedbk: bigserial *PK wastedimensiondbk: bigserial *PK miningwastemeasuredbk: bigserial *FK prosumminingwastedbk: bigint FK miningwastemeasuredbk: bigint FK miningwastedbk: bigint *FK wastestoragetype: varchar(50) minarea: real *FK miningwasteclassificationmethodused: varchar(50) maxarea: real * date: date FK areauom: varchar(50) FK proposedextractionmethod: varchar(50) FK areavoidreason: varchar(50) FK proposedextractionmethodvoidreason: varchar(50) minvolume: real FK amountestimationmethodused: varchar(50) maxvolume: real FK amountestimationmethodusedvoidreason: varchar(50) FK volumeuom: varchar(50) Tables::ProSUMMiningWaste FK compositionestimationmethodused: varchar(50) FK volumevoidreason: varchar(50) FK compositionestimationmethodusedvoidreason: varchar(50) mindensity: real minwaste: real maxdensity: real *PK prosumminingwastedbk: bigserial maxwaste: real *FK miningfeatureoccurrencedbk: bigint FK densityuom: varchar(50) FK uomwaste: varchar(50) FK densityvoidreason: varchar(50) FK prosumminingactivitydbk: bigint FK wastevoidreason: varchar(50) FK processingtransformationactivitydbk: bigint FK dimensionvoidreason: varchar(50) *FK wastetype: varchar(00) FK storagetypevoidreason: varchar(50) FK materialvoidreason: varchar(50) Tables:: FK wastemeasurevoidreason: varchar(50) ProSUMWasteCommodityMeasure FK environmentalimpactvoidreason: varchar(50) Tables::ProSUMEnv ironmentalimpact *PK commoditymeasuredbk: bigserial *PK prosumenvironmentalimpactdbk: bigserial *FK miningwastemeasuredbk: bigint *FK prosumminingwastedbk: bigint *FK commoditydbk: bigint *FK environmentalimpact: varchar(50) minamount: real maxamount: real FK uomamount: varchar(50) FK amountvoidreason: varchar(50) mincutoffgrade: real maxcutoffgrade: real Tables::ProcessingTransformationActivity FK uomcutoffgrade: varchar(50) Tables::ProcessingTransformationPlant FK cutoffgradevoidreason: varchar(50) mingrade: real *PK processingtransformationactivitydbk: bigserial maxgrade: real *PK ProcessingTransformationPlantDbk: bigserial *FK miningfeatureoccurrencedbk: bigint FK uomgrade: varchar(50) *FK miningfeatureoccurrencedbk: bigint FK processingtransformationplantdbk: bigint FK gradevoidreason: varchar(50) beginlifespanversion: timestamp begintime: timestamp FK beginlifespanversionvoidreason: varchar(50) endtime: timestamp endlifespanversion: timestamp oreprocessed: real FK endlifespanversionvoidreason: varchar(50) FK uom: varchar(50) * name: varchar(50) Tables::ProcessingTransformationPlantName FK oreprocessedvoidreason: varchar(50) *FK status: varchar(50) FK associatedprocessingtransformationplantvoidreason: varchar(50) startdate: timestamp FK consumedmaterialvoidreason: varchar(50) FK startdatevoidreason: varchar(50) *PK ProcessingTransformationPlantNameDbk: bigserial FK producedwastevoidreason: varchar(50) enddate: timestamp *FK ProcessingTransformationPlantDbk: bigint FK producedproductvoidreason: varchar(50) FK enddatevoidreason: varchar(50) * name: varchar(50) FK consumedproductvoidreason: varchar(50) FK sourcereferencevoidreason: varchar(50) FK relatedminevoidreason: varchar(50) Types::ProcessingTransformationPlantStatusType *PK processingtransformationplantstatustype: varchar(50) name: text description: text url: text Figure 9: Overview of tables added to the M4EU DB model in the context of Prosum. A pdf version can be found here 44

11 class MiningWaste (ProSUM) Tables::MiningFeatureOccurrence Types::WasteTypeType *PK wastetype: varchar(00) name: text description: text url: text Name: MiningWaste (ProSUM) Author: tch, fsc Version:..2 Created: :00:00 Updated: :06:57 *PK miningfeatureoccurrencedbk: bigserial * geometry: geometry * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) FK inspireversionidvoidreason: varchar(50) 0.. Tables::EarthMaterial *PK earthmaterialdbk: bigserial FK earthresourcematerialdbk: bigint FK miningwastedbk: bigint FK prosumminingwastedbk: bigint FK minedmaterialdbk: bigint FK supergeneprocessesdbk: bigint FK alterationdescriptiondbk: bigint FK constituentpartdbk: bigint FK physicalpropertyvoidreason: varchar(50) Tables::ProSUMMiningWaste Tables::DocumentCitation Types::EnvironmentalImpactType *PK prosumminingwastedbk: bigserial Tables::ProSUMEnv ironmentalimpact *FK miningfeatureoccurrencedbk: bigint *PK documentcitationdbk: bigserial *PK environmentalimpact: varchar(50) FK prosumminingactivitydbk: bigint FK mineraloccurrencedbk: bigint name: text FK processingtransformationactivitydbk: bigint *PK prosumenvironmentalimpactdbk: bigserial FK oremeasuredbk: bigint description: text *FK wastetype: varchar(00) *FK prosumminingwastedbk: bigint FK productdbk: bigint url: text FK storagetypevoidreason: varchar(50) *FK environmentalimpact: varchar(50) FK minedbk: bigint FK materialvoidreason: varchar(50) FK managementzonedbk: bigint FK wastemeasurevoidreason: varchar(50) FK analyticalprocessdbk: bigint FK environmentalimpactvoidreason: varchar(50) FK ProcessingTransformationPlantDbk: bigint Types::WasteStorageTypeType Tables::ProSUMWasteStorage * name: text shortname: varchar(50) FK shortnamevoidreason: varchar(50) *PK wastestoragetype: varchar(50) *PK prosumwastestoragedbk: bigserial date: timestamp name: text *FK prosumminingwastedbk: bigint Tables::ProSUMMiningWasteMeasure FK datevoidreason: varchar(50) description: text *FK wastestoragetype: varchar(50) link: varchar(256) url: text FK linkvoidreason: varchar(50) *PK miningwastemeasuredbk: bigserial specificreference: text FK miningwastedbk: bigint FK miningwastemeasuredbk: bigint *FK miningwasteclassificationmethodused: varchar(50) FK specificreferencevoidreason: varchar(50) Types::ExtractionMethodType * date: date FK proposedextractionmethod: varchar(50) FK proposedextractionmethodvoidreason: varchar(50) *PK extractionmethod: varchar(50) FK amountestimationmethodused: varchar(50) Types::AmountEstimationMethodType name: text FK amountestimationmethodusedvoidreason: varchar(50) description: text FK compositionestimationmethodused: varchar(50) url: text FK compositionestimationmethodusedvoidreason: varchar(50) *PK amountestimationmethodtype: varchar(50) minwaste: real name: text maxwaste: real description: text FK uomwaste: varchar(50) url: text FK wastevoidreason: varchar(50) FK dimensionvoidreason: varchar(50) Types:: Tables::ProSUMWasteDimension UomAreaType Types::CompositionEstimationMethodType *PK wastedimensiondbk: bigserial *PK uom: varchar(50) FK miningwastemeasuredbk: bigint Tables:: name: text minarea: real *PK compositionestimationmethodtype: varchar(50) ProSUMWasteCommodityMeasure description: text maxarea: real name: text url: text FK areauom: varchar(50) description: text FK areavoidreason: varchar(50) url: text *PK commoditymeasuredbk: bigserial minvolume: real Types:: *FK miningwastemeasuredbk: bigint maxvolume: real UomWeightType *FK commoditydbk: bigint Types:: FK volumeuom: varchar(50) minamount: real UomVolumeType FK volumevoidreason: varchar(50) maxamount: real mindensity: real *PK uom: varchar(50) Types::ClassificationMethodUsedType FK uomamount: varchar(50) maxdensity: real name: text FK amountvoidreason: varchar(50) *PK uom: varchar(50) FK densityuom: varchar(50) description: text mincutoffgrade: real name: text FK densityvoidreason: varchar(50) url: text *PK classificationmethodused: varchar(50) maxcutoffgrade: real name: text description: text FK uomcutoffgrade: varchar(50) description: text url: text FK cutoffgradevoidreason: varchar(50) url: text mingrade: real maxgrade: real FK uomgrade: varchar(50) FK gradevoidreason: varchar(50) Tables::Commodity *PK commoditydbk: bigserial FK mineraloccurrencedbk: bigint Types:: Types:: FK mineralproducingcountrydbk: bigint UomDensityType UomGeochemistryType *FK commodity: varchar(50) FK importance: varchar(50) FK importancevoidreason: varchar(50) *PK uom: varchar(50) *PK uom: varchar(50) rank: integer name: text name: text FK rankvoidreason: varchar(50) description: text description: text url: text url: text Figure 0: ProSUM mining waste relation to the M4EU DB model. A pdf version can be found here 45

12 Figure : ProSUM mining activity relation to the M4EU DB model. A pdf version can be found here Figure 2: ProSUM processing transformation plant relation to the M4EU DB model. A pdf version can be found here Figure 8 shows the original M4EU database model version , while Figure 9 shows the tables that were added to the model. The ProSUMMiningWaste table and related tables allow a more detailed description of the amount of waste. In addition, the type and grade of commodities can be defined (see Figure 0). Multiple activity types can be associated to the ProSUMMiningActivity table, where only one activity type was available in v7.0.2 version (Figure 46

13 ). To describe the processing of products and mining waste, two new main tables were introduced: ProcessingTransformationPlant and ProcessingTransformationActivity, these were not present in v7.0.2 (Figure 2). Annex 2 gives a detailed overview of how to load data into the database so that error free and valid WFS requests can be generated using the Deegree framework for any of the features that are defined in the modified UML model (Figure 2). Care is required in following the steps described e.g. if some cells in tables are left blank or null, the Deegree framework may give unexpected errors. 4.3 Codelists The following codelists (Table 4) were updated and created in the context of ProSUM: Annex 4 of this deliverable gives an overview of all the existing code lists and their values that are associated with the extended M4EU database described in this report. Code list name Source AmountEstimationMethodType ProSUM 2 CompositionEstimationMethodType ProSUM 3 ProcessingActivityTypeType ProSUM merged with M4EU 4 ProcessingTransformationPlantStatusType ProSUM 5 WasteTypeType ProSUM merged with M4EU Table 4: List of code lists and sources for the ProSUM mining waste extension. The new codelists are required by the ProSUM modifications to the mining waste model. For more detailed descriptions of processing types and waste types new values were introduced in existing codelists. 47

14 7. References Daniel Cassard, François Tertre, Guillaume Bertrand, Agnès Tellez-Arenas (BRGM), Frands Schjøth, Jørgen Tulstrup, Tjerk Heijboer (GEUS), Jouni Vuollo (GTK), Dana Čápová (CGS), Jasna Šinigoj (Geo-ZS), Stephan Gruijters (TNO), Robert Tomas, Chris Schubert (JRC) (204) Minerals4EU-WP5: The EU-MKDP: specifications of the system. Deliverable D5.2 ( MKDP%20specifications%20of%20the%20system.%20Deliverable%20D5.2/) EarthResourceML (203). EURARE project: EuroGeoSource (203). EuroGeoSource homepage In the menu EuroGeoSource Deliverables: ) Publications and presentations: 2) Public Reports: INSPIRE Directive (2007). INSPIRE Thematic Working Group Mineral Resources (203). D2.8.III.2 Data Specification on Mineral Resources Technical Guidelines. 56 p. European Commission Joint research Center Publisher. _v3.0.pdf Minerals4EU project: Mining Waste directive (DIRECTIVE 2006/2/EC): Vuollo J., Cassard D., Tomas R., Schubert C. and WP5 Partners (204) Minerals Intelligence Network for Europe Minerals4EU: WP5: Code Lists Proposal for Minerals4EU. Minerals4EU Internal Report, 265 p. ( s4eu_v.0.pdf) Vuollo J., Cassard D., Simons B., Seymon A. (200). The Earth resource data exchange model (EarthResourceML) a tool for delivering INSPIRE and ProMine mineral resource data, 4 th INSPIRE Conference. Krakow, Poland, June. Vuollo J., Simons B., Laxton J., Cassard D., Seymon A. (202). EarthResourceML v.2.0 an upgrade of the CGI-IUGS Earth Resource Data Model due to INSPIRE Data Specification. 34 th International Geological Congress, Brisbane, August 202, Abstracts on CD-ROM. 49

15 2. Steps creating valid M4EU, EURare and PROSUM WFS Features M4EU application schema This guide assumes that you have installed a java webserver (tomcat) with the deegree.war file (see cookbooks in ), which has the M4EU workspace, together with the Postgres/Postgis database containing the 3 tables and 62 views that are part of the M4EU database model together with the PROSUM extensions. This guide will show you the order in which you need to insert data into tables in this database. Column names with voidreason ending should be either left blank or have a value of unknown, withheld, unpopulated from the voidreasontype codelist. Many columns in the database have an associated column with a voidreason postfix. Either column MUST be used unless the steps detailed below state otherwise. In some cases a voidreason column has no associated data column. These columns refer to reasons why no row in an associated table can be provided. To be INSPIRE compliant and to maintain the current Minerals4EU system, you as a provider must still put data in the tables that are related to M4EU features, if this type of data is available in your organization. The new PROSUM features extend and modify some of the Minerals4EU data types. ProSUM Mine and ProsSUM Mineraloccurrence features are an extension to the M4EU Mine and M4EU Mineraloccurrence features. They contain essentially the same information as their M4EU counterparts + some extra information and new associations. The ProSUM MiningActivity and ProSUM MiningWaste features have datatypes in common with their M4EU counterparts, but they also lack certain attributes that the M4EU features have and contain some other attributes that their M4EU counterparts do not have. They were therefore reimplemented and only extend the INSPIRE mr-core Mining Feature. In addition 2 new features have been created in the new version, to handle the processing of products of mining: ProSUM ProcessingTransformationPlant and ProSUM ProcessingTransformationActivity. These features extend the INSPIRE mr-core Mining Feature. Some of the database tables and certain column names are prefixed with ProSUM. These tables are only used to create ProSUM features and datatypes. If a table or column does not have this prefix it is used to create M4EU features or both ProSUM and M4EU features. All columns that are not further explained are either free text fields, numbers, dates or are associated to code lists that correspond to their names and commonly have comments associated to them in the database. Codelist values typically have a description and a url that links to an internet resource with more information about the value. 2. INSPIRE mr-core MiningFeatureOccurrence. Features described in and will automatically generate MiningFeatureOccurrences. 6

16 2.2 M4EU Mine_Extension:. Insert a row in MiningFeatureOccurrence. MiningFeatureOccurrence *PK miningfeatureoccurrencedbk: bigserial * geometry: geometry * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) FK inspireversionidvoidreason: varchar(50) inspireversionvoidreason voidreasontype 62

17 2. Insert a row in Mine Mine *PK minedbk: bigserial *FK miningfeatureoccurrencedbk: bigint beginlifespanversion: timestamp FK beginlifespanversionvoidreason: varchar(50) endlifespanversion: timestamp FK endlifespanversionvoidreason: varchar(50) * name: varchar(50) *FK status: varchar(50) startdate: timestamp FK startdatevoidreason: varchar(50) enddate: timestamp FK enddatevoidreason: varchar(50) *FK country: varchar(2) FK sourcereferencevoidreason: varchar(50) FK relatedminedbk: bigint FK relatedminevoidreason: varchar(50) FK relatedprocessingtransformationplantvoidreason: varchar(50) FK ProcessingTransformationPlantDbk: bigint beginlifespanversionvoidreason endlifespanversionvoidreason status MineStatusType startdatevoidreason enddatevoidreason sourcereferencevoidreason relatedminevoidreason relatedprocessingtransformation PlantVoidReason a. miningfeatureoccurrencedbk MUST be filled to link the Mine to a MiningfeatureOccurrence. b. See b c. If there is no DocumentCitation associated with a mine use sourcereferencevoidreason d. If there is no related Mine associated with a Mine use relatedminevoidreason (a related Mine is a row in the same Mine table) 63

18 3. Insert rows in MineRemark if this data is available MineRemark *PK mineremarkdbk: bigserial *FK minedbk: bigint * remark: text a. Use minedbk to link to Mine. 4. Insert rows in MineName if this data is available MineName *PK minenamedbk: bigserial *FK minedbk: bigint * name: varchar(50) a. Use minedbk to link to Mine. 64

19 5. Insert rows in DocumentCitation if this data is available. DocumentCitation *PK documentcitationdbk: bigserial FK mineraloccurrencedbk: bigint FK oremeasuredbk: bigint FK productdbk: bigint FK minedbk: bigint FK managementzonedbk: bigint FK analyticalprocessdbk: bigint FK ProcessingTransformationPlantDbk: bigint * name: text shortname: varchar(50) FK shortnamevoidreason: varchar(50) date: timestamp FK datevoidreason: varchar(50) link: varchar(256) FK linkvoidreason: varchar(50) specificreference: text FK miningwastemeasuredbk: bigint FK specificreferencevoidreason: varchar(50) shortnamevoidreason datevoidreason linkvoidreason specificreferencevoidreason a. Use minedbk to link to Mine. 65

20 2.3 M4EU MiningActivity_Extension:. Insert a row in MiningFeatureOccurrence. MiningFeatureOccurrence *PK miningfeatureoccurrencedbk: bigserial * geometry: geometry * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) FK inspireversionidvoidreason: varchar(50) inspireversionidvoidreason 66

21 2. Insert a row in MiningActivity. MiningActivity *PK miningactivitydbk: bigserial *FK miningfeatureoccurrencedbk: bigint FK minedbk: bigint FK mineraloccurrencedbk: bigint FK mineralproducingcountrydbk: bigint begintime: timestamp endtime: timestamp *FK miningactivitytype: varchar(50) *FK processingactivitytype: varchar(50) oreprocessed: real FK uom: varchar(50) FK oreprocessedvoidreason: varchar(50) associatedminevoidreason: varchar(50) FK depositvoidreason: varchar(50) FK rawmaterialvoidreason: varchar(50) FK producedwastevoidreason: varchar(50) producedmaterialvoidreason: varchar(50) miningactivitytype MiningActivityTypeType processingactivitytype ProcessingActivityTypeType uom UomWeightType oreproccessedvoidreason associatedminevoidreason depositvoidreason rawmaterialvoidreason ProducedWasteVoidReason ProducedMaterialVoidReason a. The miningfeatureoccurrencedbk MUST be filled to link the MiningActivity to a MiningFeatureOccurrence row. b. The minedbk column SHOULD be filled to link a Mine with a MiningActivity. If there is no link with a Mine use associatedminevoidreason. NOTE: Each row in Mine MUST have at least Miningactivity row linked to it. c. The mineraloccurrencedbk SHOULD be filled to link a MiningActivity with a row in MineralOccurrence. d. See b e. If no MinedMaterial is associated to the MiningActivity use rawmaterialvoidreason. 67

22 3. Insert a row in MinedMaterial if this data is available (otherwise e). MinedMaterial *PK minedmaterialdbk: bigserial FK miningactivitydbk: bigint FK prosumminingactivitydbk: bigint FK processingtransformationactivitydbk: bigint *FK rawmaterialrole: varchar(50) minproportion: real maxproportion: real FK proportionvoidreason: varchar(50) rawmaterialrole proportionvoidreason RawMaterialRoleType a. The miningactivitydbk MUST be filled to link a MiningActivity with a row in MinedMaterial. 68

23 2.4 M4EU MiningWaste_Extension:. Insert a row in MiningFeatureOccurrence. MiningFeatureOccurrence *PK miningfeatureoccurrencedbk: bigserial * geometry: geometry * inspireid: varchar(50) * inspirens: varchar(50) inspireversionid: varchar(50) FK inspireversionidvoidreason: varchar(50) inspireversionidvoidreason 69

24 2. Insert a row in MiningWaste. MiningWaste *PK miningwastedbk: bigserial *FK miningfeatureoccurrencedbk: bigint FK miningactivitydbk: bigint *FK wastetype: varchar(00) FK storagetypevoidreason: varchar(50) FK materialvoidreason: varchar(50) FK wastemeasurevoidreason: varchar(50) FK environmentalimpactvoidreason: varchar(50) volume: real FK uomvolume: varchar(50) FK volumevoidreason: varchar(50) density: real FK uomdensity: varchar(50) FK densityvoidreason: varchar(50) grade: real FK gradevoidreason: varchar(50) wastetype WasteTypeType storagetypevoidreason materialvoidreason wastemeasurevoidreason environmentalimpactvoidreason uomvolume UomVolumeType volumevoidreason uomdensity UomDensityType densityvoidreason gradevoidreason a. miningfeatureoccurrencedbk MUST be filled to link the MiningWaste to a MiningFeatureOccurrence row. b. miningactivitydbk SHOULD be filled to link a MiningWaste with a MiningActivity. If there is no link with a MiningActivity the producedwastevoidreason column in MiningActivity MUST be used. 70

25 2.5 M4EU/PROSUM Product_Extension:. Insert a row in Commodity or choose an existing row. Commodity *PK commoditydbk: bigserial FK mineraloccurrencedbk: bigint FK mineralproducingcountrydbk: bigint *FK commodity: varchar(50) FK importance: varchar(50) FK importancevoidreason: varchar(50) rank: integer FK rankvoidreason: varchar(50) commodity importance importancevoidreason rankvoidreason CommodityType ImportanceType 7

26 2. Insert a row in Product. Product *PK productdbk: bigserial FK miningactivitydbk: bigint FK prosumminingactivitydbk: bigint FK producedbyprocessingtransformationactivitydbk: bigint FK consumedbyprocessingtransformationactivitydbk: bigint *FK product: varchar(50) grade: real FK uomgrade: varchar(50) FK gradevoidreason: varchar(50) production: real FK uomproduction: varchar(50) FK productionvoidreason: varchar(50) recovery: real FK recoveryvoidreason: varchar(50) FK commoditydbk: bigint FK sourcecommodityvoidreason: varchar(50) product ProductType uomgrade UomGeochemistryType gradevoidreason uomproduction UomWeightType productionvoidreason recoveryvoidreason sourcecommodityvoidreason a. miningactivitydbk MUST be filled if it is a Product from an existing MiningActivity. b. prosumminingactivitydbk MUST be filled if it is a Product from an existing prosumminingactivity. c. producedbyprocessingtransformationactivitydbk MUST be filled if it is a Product from an existing ProcessingTransformationActivity d. consumedbyprocessingtransformationactivitydbk MUST be filled if the Product is consumed by a ProcessingTransformationActivity. e. The same Product row can be produced by activity and consumed by another. f. commoditydbk SHOULD be filled to link a Product row to a Commodity row. If there is no link with a Commodity row the sourcecommodityvoidreason MUST be used. 72