Group activity
Thanks Stefania you have been very helpfull!!!
I have an other problem with the transformation on hale, I finished the mapping setting up all the relation between source schema and target schema but when i try to exporting as gml it doesn´t allow me and also on the workbench 'transformation' it doesn´t appear anything, I mean this:
I´ve checked out an example training and I could see this:
I don´t what I am doing wrong.
Thank you in advance!
Hi Beatriz,
I can see that you have loaded your source and target schemas. Have you loaded your source data?
You should see the number of loaded features beside the feature type. Please see the following screenshot:
The feature type HydroNode has data loaded. The feature type WatercourseLink does not.
Once you have loaded your source data and enabled live transformation, you should be able to export your gml file.
Kind regards,
Kate Lyndegaard
wetransform Gmbh
www.wetransform.to
Hi Miroslaw,
the water supply zones are "areas managed" under the Drinking Water Directive and well fit the scope of the Area Management / restriction / regulation zones & reporting units INSPIRE data theme.
Regarding the geometry representation, the AM Data Specification state that "Typically the representation of the geometry of a ManagementRestrictionOrRegulationZone shall be either a GM_Surface or GM_MultiSurface. However, it has been recognised that at some levels of detail the geometry may be represented as either a GM_Point or GM_Curve.Consequently, any constraints on the geometry representation have been removed".
This means that point geometry can be used because in this case it corresponds to the level of detail of the source data set .
Regarding the Zone Type code, the http://inspire.ec.europa.eu/codelist/ZoneTypeCode/drinkingWaterProtectionArea is the value to use.
To further specify that the source data set contains water supply zones under the Drinking Water Directive, the specialisedZoneType attribute (optional attribute) could be used. In fact, this attribute is meant to provide an additional value to further specialise the type of zone specified in the zoneType element.
The specialisedZoneType can contain any value defined by data provider (as long as it is made available in a public register – ref. Article 6(3) of the Implementing Rules).
More specifically, the http://inspire.ec.europa.eu/codelist/SpecialisedZoneTypeCode does not contain any value (empty code list). The AM Data Specification state that the values for the specialisedZoneType “should be derived from relevant domain-specific controlled vocabulary, where available". An extension of the INSPIRE code list SpecialisedZoneTypeCode is provided in the Eionet Data Dictionary, but currently it does not contain any value for water supply zones under DWD (read more on the specialisedZoneTypeCode in this Thematic Cluster post.).
Regarding the WMS layer, follow what specified in Sec 11.1 of the Data Specification for the layer AM.DrinkingWaterProtectionArea and in Sec 11.2.7 for the style relevant to abovementioned layer (for points, the geometry is rendered as a square with a size of 6 pixels, with a light blue(#BED2FF) fill and a black outline).
Hope this helps
Stefania
Dear Stefania,
thank you very much for your prompt reply.
Concerning Zone Type Code attribute, using of suggested "drinkingWaterProtectionArea" codelist item could be considered as problematic from the first point of view, because meaning of the drinking water protection area (= area from which the drinking water is taken) is different from the water supply zone (= area supplied by drinking water). On the other hand, if appropriate clarification is provided in the specialisedZoneType attribute (for example: "water supply zone (DWD)") and if we consider, that no more suitable value is available in the ZoneType codelist, then suggested solution is OK.
I have just one additional question (which could be relevant also for other Area management topics) - if polygon dataset is provided by country within this theme, is it allowed to use overlapping polygons?
Example: agglomerations A, B and C are served by drinking water sources 1 and 2. Out of this, agglomeration A is served by source 1 only, agglomeration C is served by source 2 only and agglomeration B is served by water mixed from both sources 1 + 2. In such case, water supply zone relevant for drinking water source 1 includes agglomerations A + B and water supply zone relevant for drinking water source 2 includes agglomerations B + C. If the water supply zones are represented by polygons, these polygons will overlapp in the area of agglomeration B. Is such solution acceptable?
Miroslav
Hi Beatriz,
you can connect hale studio directly to PostGis Database ... no need to use csv or any other format.
You might find it useful to follow the tutorials on the INSPIRE Knowledge Base (https://inspire.ec.europa.eu/portfolio/training-library). More specifically you can reference the module on Examples of data transformation (though it is for AU data theme, it gives an overview on how to use hale studio - aka HALE)
Hope this helps
Stefania
Hi Stefania! yes i understood what you´ve said but my only doubt is that in the species I am looking for It doesn´t appear a proper code so I mean this : (http://www.eu-nomen.eu/portal/taxon.php?GUID=F3C17C56-71C1-47E0-BB0F-BF9B8B569CD6) just appear in the end of the url the guid,so is that enough?
Thank you very much! have a nive day!
Yes Beatriz ,
you could also provide the label of the code list value in the <xlink: title> element.
In your case , this means that in the GML dataset you have
<hb:referenceSpeciesId
xlink:href=" http://www.eu-nomen.eu/portal/taxon.php?GUID=F3C17C56-71C1-47E0-BB0F-BF9B8B569CD6"
xlink:title=" Pinus halepensis Mill"/>
Hope this clarifies your doubts,
Stefania
I have some serious objections to establish the parallel data provision in terms of a "Linked Approach" within or connected to the theme Protected Sites.
The DS for PS had foreseen an extension for the delivery of CDDA data using the "full profile", therefore the INSPIRE-community should urgently claim for the re-establishment of a data model extension to serve this use case.
The same is true of a Natura2000-extension, clipped out of an early version of the DS, and yet waiting to be replaced by a revised extension.
Parallel data provision via a "linked approach" leads us away from INSPIRE and thus lacks any legal obligation for the Member States.
Dear Enrico,
it is a good encoding to provide codelist extension. Thank you for providing.
So in your case an extended value for the 'zoneType' field would be encoded as e.g. :
http://daten-hamburg.de/inspire/codelist/ZoneTypeCode_Extension.xml#waterfrontArea
Having a look at the values you provided, anyway, I noticed that you also provide the value "aircraftNoiseRestrictionZone" .This is indeed a specialization of the http://inspire.ec.europa.eu/codelist/ZoneTypeCode/noiseRestrictionZone value, therefore should be provided as new value for the specialisedZoneTypeCode codelist ( http://inspire.ec.europa.eu/codelist/SpecialisedZoneTypeCode. )
You may find it useful having a look at the TC discussion Using the specialisedZoneType attribute .
which provides also a relevant extended code list example from EEA.
I take this opportunity to point to 'How to extend INSPIRE code lists' dedicated page and to the Best Practices for registers and registries & Technical Guidelines for the INSPIRE register federation, describing how to set up registers for INSPIRE, including registers for extended INSPIRE code lists.
Best,
Stefania