View schema

Schema URL	http://dd.eionet.europa.eu/schemas/Floods/GML_UoM.xsd
File name	GML_UoM.xsd
Schema set	Floods
Name	GML_UoM
There are 3 QA scripts and 0 conversion scripts registered for this schema.
Link to the schema page on XMLCONV
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fd="http://dd.eionet.europa.eu/schemas/Floods/CFDGML" elementFormDefault="qualified" targetNamespace="http://dd.eionet.europa.eu/schemas/Floods/FDGML"
xmlns="http://dd.eionet.europa.eu/schemas/Floods/FDGML">
	<xs:import namespace="http://dd.eionet.europa.eu/schemas/Floods/CFDGML" schemaLocation="http://dd.eionet.europa.eu/schemas/Floods/GML_FDcommon.xsd"/>
	<xs:import namespace="http://www.opengis.net/gml/3.2" schemaLocation="http://schemas.opengis.net/gml/3.2.1/deprecatedTypes.xsd"/>
	<xs:element name="FeatureCollection" type="FeatureCollectionType" substitutionGroup="gml:AbstractFeature"/>
	<xs:complexType name="FeatureCollectionType">
		<xs:complexContent>
			<xs:extension base="gml:AbstractFeatureType">
				<xs:sequence>
					<xs:element name="featureMember" type="UoMPropertyType" minOccurs="1" maxOccurs="unbounded"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:complexType name="FeatureCollectionPropertyType">
		<xs:sequence minOccurs="0">
			<xs:element ref="FeatureCollection"/>
		</xs:sequence>
		<xs:attributeGroup ref="gml:AssociationAttributeGroup"/>
		<xs:attributeGroup ref="gml:OwnershipAttributeGroup"/>
	</xs:complexType>
	<xs:complexType name="UoMPropertyType">
		<xs:sequence minOccurs="0">
				<xs:element name="UnitsOfManagement" type="UnitsOfManagement">
		<xs:annotation>
			<xs:documentation>-- Name --
sub unit

-- Definition --
[Operational definition. Not in the WFD] Reporting unit. River basin districts larger than 50000 square kilometers should be divided into comparable sub-units with an area between 5000 and 50000 square kilometers. The sub-units can be created using river basins (if more than one river basin exists in the RBD) or sub-basins, for example. If the RBD area is less then 50000 square kilometers, the RBD itself can be used as a sub-unit.</xs:documentation>
		</xs:annotation>
	</xs:element>
		</xs:sequence>
		<xs:attributeGroup ref="gml:AssociationAttributeGroup"/>
		<xs:attributeGroup ref="gml:OwnershipAttributeGroup"/>
	</xs:complexType>

	<xs:complexType name="UnitsOfManagement">
		<xs:annotation>
			<xs:documentation>-- Definition --The Floods Directive (Article 3.2) allows Member States to identify units of management different from the river basin districts used for the Water Framework Directive. Units of management may be individual river basins and/or certain coastal areas, and may be entirely within national borders or may be part of an international unit of management or international river basin district.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="inspireId" type="fd:Identifier" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>-- Definition --External object identifier of the spatial object.

-- Description -- An external object identifier is a unique object identifier published by the responsible body, which may be used by external application to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon.

NOTE: ManagementRestrictionOrRegulationZone spatial objects commonly perform the role/function of "Reporting Unit" for non-spatial reported data. The reported data shall contain object references to ManagementRestrictionOrRegulationZones. Therefore, all spatial objects shall be assigned an inspireID. 

--Guidance-- An inspireId is an external object identifier published by the responsible data provider with the intention that they may be used by third parties for referencing. Also as zones are typically ?Reporting Units?, they also require external object identifiers to enable them to be referenced by non-spatial reported data. </xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="geometry" type="gml:MultiSurfacePropertyType" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>-- Definition -- The geometry representing the spatial extent of the spatial object.

-- Description -- The geometry of a Unit of management can be defined using any geometry representation. Typically this shall be either a GM_Surface or GM_MultiSurface.
However, there may be zone that are represented as either point or a line. 
NOTE: Where a UoM forms as a polygon, this should be encoded as a GM_Surface or GM_MultiSurface not a GM_Curve or a GMPoint.

--Guidance-- The geometry shall be the same as the geometry used for reporting obligations under the Water Framework Directive [2000/60/EC] </xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="zoneType" type="fd:ZoneTypeCode" minOccurs="1" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>-- Definition --High level classification defining the type of management, restriction or regulation zone. 

-- Guidance – Data Providers reporting under Floods Directive must use the default value unitOfManagement for the zoneType attribute.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="environmentalDomain" type="fd:EnvironmentalDomain" minOccurs="1" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>-- Definition --Classification of the environment domain(s) for which, through the establishment of the zone, certain environmental objectives shall be reached.

-- Description --A zone may be established within one environmental domain (e.g. water) or may to cover a wide range of environmental objectives that cross-cut several domains. For example, Marine Regions may relate to water,  land use, sustainable development.

--Guidance-- This has been included to enable users to retrieve multiple types of zone that exist within a domain as it was recognised that some users may not know what zone types exist. </xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="relatedZone" type="fd:relatedZone" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>-- Definition -- Reference to one or more related ManagementRestrictionOrRegulationZones. The related zone may either be a sub zone or a zone of different type.

-- Description – EXAMPLE 1: River basin districts (RBD) exist at three levels: 
1) International River Basin District 
2) National River Basin District 
3) River Basin District Sub units. An international RBD may contain one or more national RBD and/or River Basin Sub Units. A national RBD may be related to an International RBD and one or more RBD sub-units. 
EXAMPLE 2: A WFDWaterBody may be related to a River Basin District.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="featureOfInterest" type="fd:featureOfInterest" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>-- Definition --This feature is the real-world object whose properties are under observation, or is a feature intended to sample the real-world object.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="thematicId" type="fd:ThematicIdentifier" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>-- Definition --Descriptive unique object identifier applied to spatial objects in a defined information theme. 

-- Description -- Some spatial objects may be assigned multiple unique identifiers.
These may have been established to meet data exchange requirements of different reporting obligations at International, European or national levels and/or internal data maintenance requirements.
Where multiple thematicIDs exist all should be provided. This shall allow any external dataset that uses thematicIDs to referencing to the zone to continue to be linked to the spatial object.

-- Guidance – voidable.. thematic object identifier are additional identifiers that have been assigned to the zone. Multiple thematic object identifiers may be assigned to a zone where different data exchange requirements (e.g. national vs European reporting) have defined different lexical rules for thematic object identifiers. Where multiple thematic object identifiers exist all should be provided. This shall allows external datasets that use these thematic object identifiers for referencing to link to the INSPIRE spatial object.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="name" minOccurs="0" maxOccurs="unbounded" nillable="true">
				<xs:annotation>
					<xs:documentation>-- Definition --A geographical name that is used to identify the management, restriction or  regulation zone in the real world. It provides a 'key' for implicitly associating different representations of the object.

- Guidance -- Voidable. Each NamedPlace is associated with one or several geographical names, i.e. proper nouns applied to the spatial object, modelled with the data type GeographicalName. The different geographical names of one given spatial object may be for example the names in different languages or in different forms (e.g. complete and short forms of country and administrative unit names).
Each GeographicalName may have one or several spellings, i.e. proper ways of writing it, in one or several scripts like the Latin/Roman, Greek and Cyrillic scripts, modelled with the data type SpellingOfName.</xs:documentation>
				</xs:annotation>
				<xs:complexType>
                     <xs:complexContent>
                      <xs:extension base="fd:GeographicalName">
                          <xs:attribute name="nilReason" type="gml:NilReasonType"/>
                      </xs:extension>
                    </xs:complexContent>
                   </xs:complexType>
			</xs:element>
			<xs:element name="specialisedZoneType" minOccurs="0" maxOccurs="1" nillable="true">
				<xs:annotation>
					<xs:documentation>-- Definition --Additional classification value which further specialises the type of management, regulation or restriction zone relevant to the domain. 

-- Description -- NOTE: This value should be derived from a relevant domain-specific controlled vocabulary, where available.

- Guidance – Voidable. This allows more specific classification of the zone. This shall be a relevant zone type defined from an externally governed domain or community code list, where available. If no code list exists then this shall be the commonly used name assigned to the zone within the domain or community (preferably in English). 
The allowed values for this code list comprise any values defined by data provider.</xs:documentation>
				</xs:annotation>
				<xs:complexType>
                     <xs:simpleContent>
                      <xs:extension base="fd:SpecialisedZoneTypeCode">
                          <xs:attribute name="nilReason" type="gml:NilReasonType"/>
                      </xs:extension>
                    </xs:simpleContent>
                   </xs:complexType>
			</xs:element>
			<xs:element name="designationPeriod" minOccurs="1" maxOccurs="1" nillable="true">
				<xs:annotation>
					<xs:documentation>-- Definition --Time period defining when the management, restriction or regulation zone was legally designated or became effective in the real world.

-- Description --NOTE: designationPeriod uses the ISO 19108 TM_Period which is comprised of two properties - gml:beginPosition and gml:endPosition. 
If the zone shall remain in force for an indeterminate period of time then the endPosition/indeterminatePosition="unknown" can be used to state that the zone is still effective.

- Guidance – Voidable.. TM_Period is implemented using the gml:TimePeriodType. </xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:complexContent>
                      <xs:extension base="fd:TM_Period">
                          <xs:attribute name="nilReason" type="gml:NilReasonType"/>
                      </xs:extension>
                    </xs:complexContent>
                   </xs:complexType>
			</xs:element>
			<xs:element name="competentAuthority" minOccurs="1" maxOccurs="unbounded" nillable="true">
				<xs:annotation>
					<xs:documentation>-- Definition --
Description of the organisation(s) responsible for managing, restricting or regulating measures or activities within the zone. 

-- Description -- NOTE 1 A party, typically an individual person, acting as a general point of contact for a resource can be specified without providing any particular role.

- Guidance -- Voidable.</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:complexContent>
                      <xs:extension base="fd:RelatedParty">
                          <xs:attribute name="nilReason" type="gml:NilReasonType"/>
                      </xs:extension>
                    </xs:complexContent>
                   </xs:complexType>
			</xs:element>
			<xs:element name="beginLifespanVersion" minOccurs="1" maxOccurs="1" nillable="true">
				<xs:annotation>
					<xs:documentation>-- Definition --
Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

 -- Description -- NOTE This date is recorded to enable the generation of change only update files.

--Guidance-- Voidable. Data Providers should report this information, if available.</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:complexContent>
                      <xs:extension base="fd:DateTime">
                          <xs:attribute name="nilReason" type="gml:NilReasonType"/>
                      </xs:extension>
                    </xs:complexContent>
                   </xs:complexType>
			</xs:element>
			<xs:element name="endLifespanVersion" minOccurs="0" maxOccurs="1" nillable="true">
				<xs:annotation>
					<xs:documentation>-- Definition --Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

-- Description -- The value of endLifespanVersion shall not be before the value of beginLifespanVersion.

--Guidance-- Voidable. Changes to the attribute "endLifespanVersion" does not trigger a change in the attribute "beginLifespanVersion".</xs:documentation>
				</xs:annotation>
				<xs:complexType>
					<xs:complexContent>
                      <xs:extension base="fd:DateTime">
                          <xs:attribute name="nilReason" type="gml:NilReasonType"/>
                      </xs:extension>
                    </xs:complexContent>
                   </xs:complexType>
			</xs:element>
			<xs:element name="plan" type="fd:DocumentCitation" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>-- Definition --
Reference to, or citation of a plan (management or action plan) that describes the environmental objectives and measures that shall be undertaken in the zone to protect the environment.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="legalBasis" type="fd:LegislationCitation" minOccurs="1" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>-- Definition --
Reference to, or citation of the legal instrument or document that required the establishment of the zone.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
</xs:schema>