Day 3 Design of the COCONET data Model for Geodatabase implementation (Chair Richard Lisovsky and Oleksandr Neprokin)

[Richard Lisovskyi]

• Define the COCONET data model and the COCONET UML diagram following the first conceptual phase of the Geodatabase architecture design assessed during the GIS technical meeting.
• Starting from the ArcMarine data model the partners will revise the common data type during the workshop and the UML schema in order to asses the COCONET UML.

Dear all,

I welcome you to the continuation of our  first COCONET Virtual Workshop about “Existing EU protocols and standards for data and metadata sharing, rules for dataflow between partners and design of COCONET Data Model” our third day.

Here in the attachments  I am sending you The UML diagram for WP10 (as example) and  the UML diagram for the COCONET Project including the WP2,WP4, WP5, WP6.

Please have a look and in the morning session we will start our discussions.What do you think about it. We are asking you to revise the schemas during our two days. The Diagram's

will be posted on our forum in the morning.

I wish all of you  successful continuation of our work during our workshop and am shure that working together we will support  the COCONET  Project and create perfect products for the 

European Commission.

I  also welcome the quest participants of the workshop who agreed to join and contribute to our discussions:

Paola Carrara CNR-IREA ,Alessandro Oggioni CNR-IREA,  Sarretta CNR-ISMAR and JRC,Peter Thijsse MARIS .

I am wishing everybody good cooperation and all the best.

Richard Lisovsky

[Oleksandr Neprokin]

Dear Colleagues,

Please view the UML diagrames prepared on the basis of the COCONET layers list developed and presented at the previous workshop. We ask you to define the attributes for the existing layers. You are free to make corrections to the UML. Finally we need to get something like INSPIRE Consolidated UML Model. In addition we need to finalize our existing COCONET layers list. Please, make your suggestions. In the attachments you will find all the necessary documents.

[Federica Foglini]

I want to thanks Richard and Olexandr for their good jog in preparing the UML for COCONET. This is a fundamental step in the design of our Geodatabase so we need your collaboration these two days to work actively in revising and finalizing the UML for COCONET. I ask Oltion, who is a database expert to help us in the formal revision of the UML

 Please use the .xls template to populate with attributes the Object in the data model and send back to the Group workshop.

I kindly ask to the following GIS representatives to revise the UML in particular:

Vivi please revise the UML for WP5, adding attributes for each layer specifying the data type (Point, polygon, line)  taking into account the ISNPIRE data model in terms of attributes looking at the energy resource themes

Melanie and Tom revise the UML for WP6 looking the INSPIRE diagram

Antoni please revise the WP4 and add attributes

Me, Francesco, Giulio, Gabriel, Alina will revise the WP2

 We still need the UML for WP3, Please Aurore and Serge can you give us some input about that?

Alessandro Sarretta will help us with the UML of INSPIRE, if you need any explanation please ask him.

Many thanks and have a good day

[Richard Lisovskyi]

I would like to thank Federica for these warm words and add that our young GIS specialists Artem Kryglov

and Oleksandr Lepioshkin are activly working in preparing the UML Diagram's.

Richard

[Federica Foglini]

Please have a look to this link: http://help.arcgis.com/en/arcgis_inspire/1.0/help/index.html#//014m000000p0000000

Here there are some interesting info about the interaction between ArcGIS and INSPIRE!

Artem and Oleksandr can you please explore it and see if it can be useful for our UML

Thanks

Federica

[Oleksandr Neprokin]

Dear Federika

We have downloaded INSPIRE GDB template and now we payed close attention to it. We shall give the feedback as soon as possible.

[Federica Foglini]

Many thanks Oleksandr,

in the mean time we are revising the uml for Habitat adding attributes and related tables with a list of code.

[Antoni García Rubies]

Dear Federica,

The attributes for WP4 are OK. At least all of the most obvious human induced threats are here, but what happens with the ocean circulation-climate interactions and sea-level rise, wave storminess, wind farm location and coastal risks? I think that our partners from the University of Cantabria have a lot of information about these topics. Let me know what they think about how they want to integrate their data.

Yours

Toni

[Federica Foglini]

Dear Antoni,

about the attributes for WP4, can you please try to implement the .xls file adding the proper rows for the threats layers.
Please have a look to the .xls file and if you can try to add some attributes, Maybe aurore can help you.

About the University of cantabira, can you maybe contact them and ask if they have info and wants a gis layer

[alessandro.sarretta]

Hi everybody,
first of all I'd like to highlight that I'm not an UML expert so please consider this reading my comments.
I've been working on the INSPIRE Data Specifications for 2 years and I've only used UML for creating class diagrams. I had a very quick look at the UML models you've shared in the group.
I'll try here to list some considerations, please excuse me if there are not in a logical order and probably a bit confused...
If you have any clarification or question, I hope we have time to discuss them during this virtual workshop.

I'd like to highlight here a couple of elements that I think are fundamental for your discussion:

• if you have time, the reading of some of the INSPIRE data specifications might be valuable, at least to include some common attributes described there, that could be used also in the future for a more detailed mapping to INSPIRE rules and requirements.
• The current version of the data specifications for the Annex I, II and III of the INSPIRE Directive can be found here:
• http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2
• the links in the data models web page (http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2/list/datamodels) refer to old versions of the models: please don't consider them for a detailed study and have a look at the pdfs from the link above
• the link Federica sent on ArcGIS for INSPIRE (http://help.arcgis.com/en/arcgis_inspire/1.0/help/index.html#//014m000000p0000000) is quite useful to understand connections between the INSPIRE conceptual approach and an ESRI GeoDB approach;
• I think the example file "Featureclass_examplefor Habitat.xls" Federica shared via mail is a good example to replicate for all the layers. Then all the Fields should be also reported in the UML model

Some general informations on data specifications in INSPIRE:

• INSPIRE is "only" about "the establishment of the Infrastructure for Spatial Information in the European Community, for the purposes of Community environmental policies and policies or activities which may have an impact on the environment."
• I'd like to highlight that INSPIRE is not about all data that are collected, managed and analysed for research purposes
• for this reason INSPIRE Data Specification are containing spatial object and attributes that are at a "general" level
• the level of detail among the data models in INSPIRE is very different
• one of the most important things to consider is that objects and attributes that are of interest for the CoCoNet project are (or might be) usually described in different Data Themes
• vice versa, some other objects might not be included in any of the INSPIRE Data Specification, exactly because they are domain specific or they have different goals than the INSPIRE Directive

Specifically on UML models:

• UML data models in INSPIRE seem to be at a different level of abstraction
• INSPIRE UML models are conceptual
• ArcMarine (and I guess also CoCoNet) seems to be already an physical implementation software oriented
• in INSPIRE the classes described in the class diagrams have "stereotypes" that are different types of objects
• FeatureTypes are spatial objects; DataType; Code Lists
• in ArcMarine there are various "Common Marine Data Types", that in INSPIRE are instead described using attributes in the classes
• e.g. a Shoreline in ArcMarine is a Data Type per se; in INSPIRE there is a Shoreline spatial object described in the "Sea Regions" data specifications
• from a quick view I think that there are a number of data specifications of your interest:
• "Elevation" for bathymetric data
• "Geology"
• "Human Health and Safety", "Population Distribution" and "Demography" maybe for some of the Threats and Socio Economic
• "Sea Regions" for the delineation of the seas and for coastlines
• "Atmospheric Conditions and Meteorological Geographical Features" for air temperature, pressure, wind, ...
• "Environmental Monitoring Facilities" for locations and info related to sensors, stations, etc.
• "Habitats and Biotopes"
• "Species Distribution"
• "Energy Resources" for wind farms
• "Oceanographic geographical features" for all data related to ocean
• the guideline for the application of "Observations and Measurements" ISO standard to INSPIRE for all the measurements
  

I have some questions on the CoCoNet UML models, just for my understanding.

• should the CoCoNet model be the "sum" of all the WPs' models?
• I only see classes in the diagrams:
• are the classes representing always layers?
• what is a layer in the CoCoNet context?
• are layers representing always spatial objects?
• It's not clear to me what the Classes are representing in the model:
• I see different "types" of classes
• a representation of a measured property (via a number of points, a raster, ...)
• "documentation" information (Policy_options, Case_studies, ...)
• There are some repetitions in the models of different WPs (habitats is both in Habitats, Geology and Wind; waves is both in Physical and Wind)
• is it expected?
• Measured properties (temp, wind, ...), especially when there are many (e.g. all the layers in the "Wind" diagram) in the INSPIRE DSs are frequently described via code lists, referring to international agreed ones, with the purpose to maintain semantic
  

Ok, for the time being  that's all :-)
Sorry for the lenght of this e-mail...
HTH
Ale

[catia.chiappini]

I can't open the WP10_UML.pdf file

[Federica Foglini]

Alessandro,

Many Thanks for your long and useful email, I think Oleksandr can give more answers to your questions helping us thinking about this issues
Please find some answers here below

The GIS layers represents  feature classes  that are homogeneous collections of common features, each having the same spatial representation, such as points, lines, or polygons, and a common set of attribute columns.

The Object class represent the tables storing multiples attributes that can be related to the features classes usingh a spatial relationship.

The COCONET Model will be the sum off al WPs model, at this stage we are trying to divide the UML for WPs in order to work on it in different group. It is easier for partners at the beginning of the project to think as WPs.

Each WP will produce different data and can be as the INSPIRE THEME. For example WP2 is about Habitat, WP5 about Wind farm ecc.

I have some questions:

We are dividing HABITATS in different feature class because the "habitat people" prefer this kind of division. What do you think about in terms of INSPIRE Directive?

[Aurore Chassanite]

Hello everyone,

we are working on an UML for the WP3. I let you know as soon as I have more information from my team.

Sincerely
Aurore

[Oleksandr Neprokin]

Dear Alessandro

Thank you for your very valuable input. We will try to add to the answers of Federica our views on this matter.

• In the COCONET model the same layer can be represented by different data types (Feature Point/line/polygon or rastr - see attached xls file), it is assumed that «Higher Layers” express the parent class (this is the layer group united by common properties), and the “Layer” - this is the classes that can be represented by different data types (Feature Class).
• Because different WPs intersect each other and share parent classes, so we found repetition.

Federica, we noticed that in our table “Higher Layers” represented similar Classes, e. g. “Basic Layer”, “Base Layer”, “Basemap (boundaries, HWL etc.)”, “Base” - are these different Classes or the same?

With regard to the applicability of the INSPIRE for our COCONET model, as we understand we need to create a model based on the Marine Data Model, but the description of the basic data types must correspond mostly to INSPIRE for further interoperability. We want to implement this model in ArcGIS SDE 10. Today we hope to review the work of ArcGIS for INSPIRE Geodatabase Template and receive an example of the geodatabase structure. The advantage of this Template is that it focuses on the use of SDE while Marine Data Model is a personal geodatabase.

GIS team, UkrSCES

[Oleksandr Neprokin]

Dear Catia

Please find in the attechment WP10_UML.jpg

[alessandro.sarretta]

Hi Federica,
thanks for your reply.
This morning I don't have much time to work on this, I hope to find more time this afternoon...
As a general suggestion, when revising INSPIRE data specs, if you want to have a look at the "attributes" required, have a deep look at Chapter 5, containing the data model diagrams and the feature catalogue, with all the definitions.
Concerning the Habitats and Biotops data specs (http://inspire.jrc.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_HB_v3.0rc2.pdf), you can have a general picture of the model at page 17, with the class diagram and the code lists.
Federica, could you explain better why there is a nees to have different feature classes for habitats with some examples?
Thank you
Ale

[Federica Foglini]

Dear Oleksadr,


I agree the INSPIRE data model  is better for our purpose, for interadoperability and for the creation of a SDE. The update UML of INSPIRE have been pubblished very recently, so we are now able to focus on it instead of the Marine data Model. I think we are going towards the best solution, thanks Oleksandr to revise the ArcGIS for INSPIRE, I am really looking forward to see how it works.
In the mean time the Habitat team is revising the INSPIRE UML and filling the .xls files. I am also try to revise the Geology UML that is really complicated and need to symplify it for the purposes of the projects

About your questions, "base map", "basic layer" they are the same.
 We need to revise the GIS layer list because it comes from the the assemblage of different WPs done duing the GIS meeting in Lecce. I am realizing now that bathymetry for example is repeated many times.

[Federica Foglini]

Hi Alessandro and all

the habitat team  would like to keep separated the Biogenic habitat, the seagrass, the barrens, and the sandy habitat because they need more details about these habitats  that are not in the Eunis and in the habitat directive. In the Mediterraneand and the Black Sea there are different habitats from the Atlantic and the North Sea.
Anyway I asked them to analyse the INSPIRE Schema and I think we can use a unique layer (that means a unique feature class, or feature type) with different "data type" and "code list".
They will send soon a proposal for Habitats!

I am also revising the Geology and I think we mainly need the Geomorphological features (adding some types). Have you suggestion for the seafloor lithology?
I ask to geologists in this group to try revise the schema you can find here: http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2

Many thanks

[Oleksandr Neprokin]

Dear All

We have successfully installed ArcGIS for INSPIRE Geodatabase Template 1.0 SP2. This GeoDataBase contains 48 Feature Class and 228 SDE Tables (table with info watch in attachment). 

[francescodeleo]

Dear all

I am sending you  the file attached FEATURE CLASSES  together with the relative objects classes, relevant for WP2. We followed, where possible, the annexes of the Habitats Directive, INSPIRE and EUNIS classification.

We added two new FEATURE CLASSES:

·      Overgrazing facies with incrustant algaes and sea urchins (Eunis Cod. A3.131)

·      Deep-sea bioherms  (Eunis Cod. A6.6)

Our idea is to change Sandy Habitat  FEATURE CLASSES with Sublittoral sediment (Eunis Cod. A5). This change could allow to include all the levels inside this one, in case misht be of interest.

[alessandro.sarretta]

Dear Oleksandr,
could you please confirm that the ArcGIS for INSPIRE GeoDataBase template contains only Annex I INSPIRE themes?
Thanks
Ale

[Oleksandr Neprokin]

Dear Alessandro

Now on the site of ESRI available the only one template for INSPIRE Annex I. Please find attached screenshot from their site.

Cheers

Oleksandr

[alessandro.sarretta]

Hi,
regarding the Geomorphological feature in INSPIRE, in the Geology data specs, there is a feature class NaturalGeomorphologicFeature described by the NaturalGeomorphologicFeatureTypeValue code list. It contains a quite generic "marineLittoralCoastalWetland" value (pag. 301) that could be maybe specialised in something more detailed and useful for your purposes.
Regarding the seafloor lithology,the feature type "GeologicUnit" is a composition of the data type "CompositionPart" (pag. 17), having as an attribute "material", that takes its values from the "LithologyValue" code list (pag. 256 and following ones...). Mayne you can find here something useful.
HTH
Ale

[Federica Foglini]

Dear All,

 after this productive day please fine below my observations, summary and proposal for next steps. I think the UML model is the most important step to define in order to start to collect and harmonize data from partners.

Summary

1. Thanks to Alessandro,  and the excellent job of Olexander and his team we are now aware about  the INSPIRE Geodatabase.  It is only for Annex I so we need to build the UML based on Annex II and III for our purposes.
2. We need to base our UML INSPIRE data mode instead of the Marine Data Model, in order to ensure interadoperability adapting INSPIRE schemas to our needs.
3. we received the .xls file with attribute for the Habitat WP2.
4. we are waiting input from WP3 WP4 WP5 and WP6 revising INSPIRE and filling the .xls file.

 Proposal for Next Ste: 

1. Assembling all input from partners (.xls files with attributes) and analyse their needs and see if it is possible to avoid the creating of duplicate layers (for example can we create only one layer for habitat with different data type instead of 5 different layers??) 

2. Revise the GIS layer list and eliminate the duplicate layers (for example base map,  habitats, bathymetry)

3. Create the UML for each WP2-3-4-5-6 with attributes and relationships based on the INSPIRE Directive and the INSPIRE Geodatabase. I want to remind you that the layers for these WPs are at the scale of Mediterranean and Black sea

4. Derive an :xml template for each UML in order to create the empty SDE Geodatabase. In this way we are sure that people in charge of creating the Geodatabase will use exactly the same UML model

Here the list of people in charge of managing the Geodatabase as agreed in Lecce. Please make comments

 

GeoDB1	CONISMA	Francesco De Leo
GeoDB2	CNRS	Aurore Chassanite and ?
GeoDB3	HCMR	VIVi' Drakopoulou
GeoDB4	INCDM	Alina Spinu
GeoDB5	CNR ISMAR	Federica Foglini
Central GeoDB for Piltot project	UkrSCES	Richard Lisovsky and his team
Central GeoDB Mediterranean and Black Sea	CNR ISMAR	Federica Foglini and his team

 

Please find attached the work flow Schema and make comments to the next steps

[Vivi Drakopoulou]

Dear all
we are working on UML for WP5.
Tomorrow you'll have our input.
Vivi

[Federica Foglini]

Dear All,

here the .UML for WP6 by Tom and Melanie,

Tom, here I can't see the attributs, but again the layers,
Can you produce a .xls sheet for each layer with the attributes you want to include revising the INSPIRE data Model.

Please have a look the WP2 .xls file and to the Annex I II and III as suggested by Alessandro Sarretta

Federica

[Aurore Chassanite]

Dear all,

 

This is a proposal of WP3 layers, I've tried to link with Inspire Annex but it was difficult. I haven't found anything concerning genetic connectivity in Inspire data model.

 

I have also added some details about the genetic layer on the general excel file for all Coconet.

 

As we haven't decided exactly the genetic data we will use, more details will probably be added later. Concerning the beta diversity part of the WP3, I cannot tell you now the layer in details, this will be decided during the workshop in Italy next October.

Let me know if it is ok for you and what you think about the file

 

Sincerely

Aurore

 

 

[Federica Foglini]

Thanks Aurore for your effort,

we will try to integrate this info in the data model and we will have the opportunity to integrate the UML with new attributes if necessary.
I know it is not so easy to integrate with the INSPIRE directive to be compliant, we will try to do our best but we have also to be aware to the limitation of the INSPIRE data schema and try to focus on our need.

[Aurore Chassanite]

Dear all,

 

here is a proposal of UML for the WP3. For the moment this is the genetic part, as I am not sure how to include the beta diversity and propagules parts. To realise the sampling for genetic analysis we will need the map of the habitat and the physical data (like curents, temperature, etc.).

The second WP3 workshop concerning the betadiversity will occur in mid October. We will be able to obtain more information about the data and metadata available for beta diversity after this workshop.

 I hope this is OK

 

Sincerely

Aurore

 

[Federica Foglini]

Please find attached the Schema for the WP6 sent by Melanie and Tom

Federica

[Vivi Drakopoulou]

Dear Federica, Dear all

These are the revised draft of UML and WP5 layers tried to link with Inspire Annex III.
Let me know what do you think about this proposal.

Vivi

[Federica Foglini]

Dear Vivi,

thanks for your Schema, I think it is a good proposal and we will include it in the final report.

Federica