6DE THEMA ANNEX III "NUTSDIENSTEN EN OVERHEIDSDIENSTEN"

50 %
50 %
Information about 6DE THEMA ANNEX III "NUTSDIENSTEN EN OVERHEIDSDIENSTEN"
Technology

Published on February 21, 2014

Author: MaksimSestic

Source: slideshare.net

Description

Annex III definitie: Nutsvoorzieningen zoals riolering, afvalbeheer, energievoorziening, watervoorziening, bestuurlijke en maatschappelijke instanties van de overheid, zoals bestuurlijke overheden, civiele bescherming, scholen en ziekenhuizen.

6DE THEMA ANNEX III « NUTSDIENSTEN EN OVERHEIDSDIENSTEN » VERSIE 2.0 VAN SPECIFICATIE DOCUMENT Katleen Miserez, expert in TWG-US

Thema « Nutsdiensten en overheidsdiensten » Overzicht Annex III definitie: Nutsvoorzieningen zoals riolering, afvalbeheer, energievoorziening, watervoorziening, bestuurlijke en maatschappelijke instanties van de overheid, zoals bestuurlijke overheden, civiele bescherming, scholen en ziekenhuizen. Utility and Governmental Services 2 2

Thema « Nutsdiensten en overheidsdiensten » Overzicht • Definitie van nutsdienst en overheidsdienst: – Gelimiteerd tot diensten geleverd door publieke overheden (internationaal, nationaal, lokaal) – Maar ook “overheidsdiensten” geleverd door privé-ondernemingen (dienst ten behoeve van de bevolking) – 1ste criterium: de dienst wordt geleverd ten behoeve van de bevolking • Definitie van de term “milieu” in INSPIRE: – Betekenis van “milieu” is breed Het begrip milieu verwijst naar het geheel van natuurlijke en culturele/sociologische factoren die een invloed kunnen uitoefenen op levende organismen en op menselijke activiteiten. – Daaraan wordt ook de notie van duurzame ontwikkeling (ecologisch, sociaal en economisch) gekoppeld. – 2de criterium: de informatie draagt bij tot het oplossen van milieuproblemen 3 3

Thema « Nutsdiensten en overheidsdiensten » Overzicht • D2.3 Definition of Annex Themes and scope A very broad INSPIRE theme including different kinds of objects: Utility services/networks: Physical construction for transport of defined products: These may include pipelines for transport of oil, gas, water, sewage or other pipelines. Transmission lines may include electrical, phone, cable-TV or other networks. Transmission lines for both land and at sea/water (bottom) is important. All kinds of transmission systems have nodes and are linked to facilities for production and treatment of different kinds of products. Despite being heavily interlinked, the themes in INSPIRE are treated separately – the production and treatment facilties are treated mainly in the theme production and industrial facilities. Transmission systems may be of different kinds; • Oil and gas pipelines: Major lines from oil and gas fields/extraction areas and storage sites. Important production and treatment facilities of such resources is linked to a such a transport network, such as nuclear power stations, power stations, transformer stations and oil tanks. GISCO, Energy/ industry authorities, Companies • Water pipelines: Location of water pipelines – large and local network. Large transmission lines are of interest here. Linked to production facilities for water for consumption/processes. Irrigation lines treated separately under agricultural facilities. Water supply institutions, Utilities/ health • Sewage pipelines: Sewage network, linked to sewerage facilities. Major lines of interest here. Utilities • Transmission lines- electrical: Data set showing larger transmission lines for electricity, both at land and sea. The location of lines is important knowledge for the energy sector itself, land use planners, construction, fisheries for sea cables. Parts of the information important in low flight hindrance databases. Large: national energy/industry institutions. Local authorities, Companies • Transmission lines-phone/ data/cable-TV: Location of phone/ data: Rough data needed in land planning. Important transmission nodes, e.g. antennas, may be seen as part of the network. The cables placement can conflict other natural resource utilization activities, e.g. fisheries. Technical data accuracy for local level Companies Rough pipeline and utility service databases exist at European level, e.g. GISCO database with scale 1: 1.000.000. Data within countries is nonhomogenous. There are examples of national portals warning on construction, distributing maps/data on location of pipelines. At local and regional level the responsibility of government offices or different operators/ firms. In some countries there are national portals for information about cables etc in construction work. … (zie document voor volledige definitie en omschrijving) 4 4

Thema « Nutsdiensten en overheidsdiensten » Dispatching van TWG-US Name Surname Country Organization ES Brönnimann Frédéric Fundación Universitaria Iberoamericana SDIC FR Institut Géographique National (IGN-France) LMO González Pérez Pedro A. ES Working Group for-Enquiry on Local Infrastructures and Services (GT-EIEL) LMO Haugan Frank NO Asplan Viak Internet SDIC López Alós Angel - Joint Research Center (JRC) Miserez Katleen BE Flemish Environment Agency LMO Pfaffinger Norbert AT Austrian Federal Environment Agency LMO Ritschl Janine DE Schwarzbach Frank DE Šestić Maksim BH Proposed by Role Funiber: cross border SDIC between Europe and SouthAmerica IGN France LMO EuroGeographics IDEE Working Group of the Commission on Geomatics LMO left before beginning Expert National Mapping Agency Facilitator Territorial administration (A Coroña) Expert Plan4all SDIC Private company (Consultant in urban planning) Expert Research Center JRC’s Contact Point Environnemental Agency Expert Environnemental Agency Expert Drafting Team Data Specification DT DS GIS-Flanders SDIC Austrian Federal Environment Agency LMO Dresden University of Applied Sciences, Faculty of Geoinformation//gdi.initiative.sachsen LMO Lenkungsgremium GDI-DE (Steering Committee GDI-DE) LMO INOVA informaticki inzenjering, d.o.o. SDIC INOVA consortium SDIC Utility networks Type of organization University (during her PhD – joined lately) University (Professor Doctor Ing.) Private company (Consultant in utility networks) Admin. & Gvtal Services Expert Expert Editor 5 Waste Managt 5

Thema « Nutsdiensten en overheidsdiensten » Toelichting op totstandkoming • Het thema “nutsdiensten en overheidsdiensten” is zeer uitgebreid en werd daarom onderverdeeld in 3 sub-thema’s: – Utility services/networks – Administrative and social governmental services – Waste treatment facilities and waste storage • Elk sub-thema heeft een verschillend applicatie schema. Deze werden onafhankelijk van elkaar ontwikkeld. • Voor elk sub-thema werd uitgegaan van referentiemateriaal en enkele use cases. – Voor utility services/networks werd de documentatie van IMKL (Informatiemodel Kabels en Leidingen) gebruikt. 6 6

Thema « Nutsdiensten en overheidsdiensten » Belangrijke hoofdstukken • • • • Executive summary Hoofdstuk 2 Overview Hoofdstuk 3 Specification scopes Hoofdstukken 5.2, 5.3, 5.4 en 5.5 Application schemes 7 7

Thema « Nutsdiensten en overheidsdiensten » Utility networks submodel: Specific approach • Use of the Generic Network Model – Initially developed for the theme « Transport Networks » Annex I – Creation of an Abstract Application Schema for Utility Networks – Development of 5 application schemas: • • • • • Water Network Sewer Network Oil & Gas Network Electricity Network Telecommunications Network 8 8

Thema « Nutsdiensten en overheidsdiensten » Utility networks submodel: Abstract types Derived from the Generic Network model (node-arc-node) class Utility Netw orks - Abstract Types Generic Network Model (from GCM) «featureType» Network::NetworkProperty «featureType» UtilityProperty «voidable» + validFrom: DateTime + validTo: DateTime [0..1] constraints {All objects have inspireId} + inspireId: Identifier [0..1] «voidable, lifeCycleInfo» + beginLifespanVersion: DateTime + endLifespanVersion: DateTime [0..1] «featureType» Network::NetworkElement + +inNetwork «voidable» 0..* inspireId: Identifier [0..1] «lifeCycleInfo, voidable» + beginLifespanVersion: DateTime + endLifespanVersion: DateTime [0..1] +elements «featureType» Netw ork::Netw ork 1..* «voidable» + geographicalName: GeographicalName [0..*] «featureType» UtilityNetwork «voidable» + maintainer: MaintenanceAuthority + owner: OwnerAuthority «voidable» + networkRef: NetworkReference [1..*] «featureType» Network::LinkSet «featureType» +link Network::GeneralisedLink Notion of networks 1..* «featureType» Network::LinkSequence + +spokeStart 0..* «voidable» +startNode 0..1 centrelineGeometry: GM_Curve 0..* fictitious: Boolean = false +spokeEnd «voidable» 0..1 +endNode «featureType» Network::Link link: DirectedLink [1..*] {ordered} «featureType» UtilityLinkSet (identifier, name, owner, maintainer, etc.) + + «featureType» UtilityLinkSequence «featureType» UtilityLink «featureType» Network::Node + geometry: GM_Point «featureType» UtilityNode «featureType» UtilityNodeContainer «voidable» + elevation: ElevationLine + length: Length «voidable» + elevation: ElevationLine + length: Length «voidable» + elevation: ElevationLine + length: Length +nodes «voidable» «voidable» + elevation: ElevationPoint + heading: Angle 0..* «voidable» + elevation: ElevationPoint + heading: Angle constraints {All objects have inspireId} {All components belong to same utility network} constraints {All components belong to same utility network} {All objects have inspireId} constraints {All objects have inspireId} constraints {All objects have inspireId} constraints {All objects have inspireId} Line-based features (links, sequences, length, orientation, etc.) Point-based features «featureType» UtilityNetworkElement «voidable» + comment: PT_FreeText + currentStatus: ConditionOfFacilityValue + facilityReference: Facility + manufacturerCode: PT_FreeText + manufacturerName: PT_FreeText + objectName: UtilityName + reconstructionDate: DateTime + validFrom: DateTime + validTo: DateTime + verticalPosition: VerticalPositionValue «codeList» Base Types:: ConditionOfFacilityValue + + + + disused functional projected underConstruction «enumeration» Base Types:: VerticalPositionValue onGroundSurface suspendedOrElevated underground (nodes, direction) Feature (point or line-based) properties (name, manufacturer, vertical position, elevation, status, comment) 9 9

Thema « Nutsdiensten en overheidsdiensten » Utility networks submodel: Common types class Utility Netw orks - Common Types LinkSequence UtilityNetworkElement LinkSet UtilityNetworkElement «featureT ype» UtilityLinkSequence «voidable» + elevation: ElevationLine + length: Length Duct / Pipe (coating, material, diameter, casing, height, etc.) «voidable» + elevation: ElevationLine + length: Length «featureT ype» Pipe (cover, width, height, access, etc.) «codeList» PipeCoatingValue + + + + + + CPVC epoxy HDPE none other PVC «codeList» DuctCasingValue + + + «voidable» + elevation: ElevationPoint + heading: Angle +pipes 1..* «featureT ype» Manhole «featureT ype» Pole «voidable» + casing: DuctCasingValue + columns: Integer + hasWarningT ape: Boolean + height: Length + rows: Integer + spacer: Length + width: Length «voidable» + coverLength: Length + coverOpening: ManholeCoverOpeningValue + coverShape: ManholeCoverShapeValue + coverWidth: Length + height: Length + shaftAccess: ManholeShaftAccessValue + shaftLength: Length + shaftMaterial: ManholeShaftMaterialValue + shaftWidth: Length + type: ManholeT ypeValue «voidable» + diameter: Length + foundation: PoleFoundationValue + hasAnchorGuy: Boolean + hasPushBrace: Boolean + hasRiser: Boolean + height: Length + material: PoleMaterialValue + type: PoleT ypeValue +ducts «voidable» 0..* Pipe & Duct Enumerations Manhole Enumerations «codeList» PipeMaterialValue «codeList» PipeShapeValue arched circle cunette other oval rectangle square trapezoid «featureT ype» UtilityNodeContainer «featureT ype» Duct «voidable» + coating: PipeCoatingValue + diameter: Length + material: PipeMaterialValue + shape: PipeShapeValue + + + + + + + + Node UtilityNetworkElement Manhole «featureT ype» UtilityLinkSet + + + + + + + + + + + + + + + + + + + + + + + + Pole Enumerations «codeList» ManholeShaftAccessValue «codeList» ManholeCov erOpeningValue + + + + + + ABS asbestos blackIron blackSteel castIron clay compositeConcrete concrete CPVC FRP galvanizedSteel masonry other PB PE PEX PP prestressedReinforcedConcrete PVC reinforcedConcrete RPMP steel terracota wood + + + + + climbingIron ladder ladderFittings noAccess other stairs «codeList» ManholeShaftMaterialValue + + + + + + + + + cement concrete fiberglass masonry other plasteredMasonry plastic precastConcrete reinforcedPolyester «codeList» PoleTypeValue + + + + + circle composite grid other rectangle square hFrame other standard streetLight tower «codeList» PoleFoundationValue + + + + + extraDeepInEarth normallyInEarth normalWithConcreteBackfill onConcreteFoundation other (type, height, foundation, material, diameter, etc.) «codeList» PoleMaterialValue + + + + + + + aluminiuim composite concrete fiberglass other steel wood «codeList» ManholeTypeValue + + + concrete directBuried none bolts hooks lever other socket «codeList» ManholeCov erShapeValue + + + + + + Pole handhole manhole vault NetworkProperty «featureT ype» UtilityProperty «voidable» + validFrom: DateT ime + validT o: DateT ime [0..1] Network information «featureT ype» MaintenanceAuthority + authority: CI_ResponsibleParty «featureT ype» Ow nerAuthority + authority: CI_ResponsibleParty «featureT ype» UtilityName + name: GeographicalName (name, owner, 10 maintainer) 10

Thema « Nutsdiensten en overheidsdiensten » Application schema electricity network class Electricity Netw ork LinkSequence UtilityNetworkElement Node UtilityNetworkElement «featureT ype» Utility Networks:: UtilityLinkSequence «featureT ype» Utility Networks::UtilityNode «voidable» + elevation: ElevationPoint + heading: Angle «voidable» + elevation: ElevationLine + length: Length Network «featureT ype» Utility Networks::UtilityNetwork «voidable» + maintainer: MaintenanceAuthority + owner: OwnerAuthority «featureT ype» ElectricityCable Electricity cable (nominal or operating voltage, type  list of values) «featureT ype» ElectricityAppurtenance «featureT ype» ElectricityNetw ork «voidable» + conductorMaterial: ElectricityCableConductorMaterialValue + conductorSize: Length + nominalVoltage: UnitsList + operatingVoltage: Measure + type: ElectricityCableT ypeValue «voidable» + type: ElectricityAppurtenanceValue «voidable» + type: ElectricityNetworkT ypeValue «codeList» ElectricityCableTypeValue + + + + + + + + + + + other P_OH_Single P_OH_T hree P_OH_T wo P_UG_Single P_UG_T hree S_OH_Single S_OH_T hree S_UG_Single S_UG_T hree streetLightConductor «codeList» ElectricityCableConductorMaterialValue + + + aluminium copper steel «codeList» ElectricityAppurtenanceValue + + + + + + + + + + + + + + + + + + + + + + + + capacitorControl connectionBox correctingEquipment deliveryPoint dynamicProtectiveDevice fuse generator loadT apChanger mainStation netStation networkProtector openPoint primaryMeter recloserElectronicControl recloserHydraulicControl regulatorControl relayControl sectionalizerElectronicControl sectionalizerHydraulicControl streetLight subStation switch transformer voltageRegulator «codeList» ElectricityNetw orkTypeValue + + distribution transmission Electricity network (network type  list of values : distribution, transmission) Electricity appurtenance (type  list of values, Identifier) 11 11

Thema « Nutsdiensten en overheidsdiensten » Application schema telecommunications network class Telecommunications Netw ork Link UtilityNetworkElement LinkSequence UtilityNetworkElement «featureT ype» Utility Networks::UtilityLink «featureT ype» Utility Networks:: UtilityLinkSequence «featureT ype» TelecommunicationsCable «featureT ype» Utility Netw orks::Pipe «voidable» + material: T elecommunicationsCableMaterialValue + maxCapacity: Measure «voidable» + coating: PipeCoatingValue + diameter: Length + material: PipeMaterialValue + shape: PipeShapeValue «voidable» + elevation: ElevationPoint + heading: Angle «featureT ype» TelecommunicationsLink «voidable» + maintainer: MaintenanceAuthority + owner: OwnerAuthority «featureT ype» TelecommunicationsAppurtenance «featureT ype» TelecommunicationsNetw ork «voidable» + type: T elecommunicationsAppurtenanceValue «voidable» + type: T elecommunicationsNetworkTypeValue 0..* «codeList» TelecommunicationsCableMaterialValue + + + + Network «featureT ype» Utility Networks::UtilityNetwork «featureT ype» Utility Networks::UtilityNode «voidable» + elevation: ElevationLine + length: Length «voidable» + elevation: ElevationLine + length: Length +cables «voidable» Node UtilityNetworkElement coaxial opticalFiber other twistedPair Telecommunications cable (cable : max capacity, material  codelist: coaxial, optical fibre, etc.; + pipe : diameter, shape, material, etc.) «codeList» TelecommunicationsAppurtenanceValue «codeList» TelecommunicationsNetw orkTypeValue + + + + + + + + + + + + + + + + + + + + + + antenna copperMaintenanceLoop copperRepeater digitalCrossConnect digitalLoopCarrier exchange fiberInterconnect jointClosure loadCoil mainDistributionFrame multiplexer opticalMaintenanceLoop opticalRepeater patchPanel spliceClosure splitter terminal termination computer PST N radio television Telecommunications network (Type  codelist: computer, PSTN, radio, television, etc.) Telecommunications appurtenance (Type  codelist: antenna, terminal, multiplexer, etc.) 12 12

Thema « Nutsdiensten en overheidsdiensten » Application schema water network class Water Netw ork UtilityLinkSequence Node UtilityNetworkElement «featureType» Utility Netw orks::Pipe «featureType» Utility Networks::UtilityNode «voidable» + coating: PipeCoatingValue + diameter: Length + material: PipeMaterialValue + shape: PipeShapeValue «voidable» + elevation: ElevationPoint + heading: Angle «featureType» WaterPipe «featureType» WaterAppurtenance «voidable» + averageVolume: Volume + maxCapacity: Measure + type: WaterPipeTypeValue + waterType: WaterPipeWaterTypeValue Network «featureType» Utility Networks::UtilityNetwork «voidable» + maintainer: MaintenanceAuthority + owner: OwnerAuthority «featureType» WaterNetw ork «voidable» + type: WaterAppurtenanceValue Water network (no distinction) «codeList» WaterPipeTypeValue Water pipe + + + + + + + + + + + + + + + + + + + + + + «codeList» WaterPipeWaterTypeValue «codeList» WaterAppurtenanceValue LL LL_Commercial LL_Domestic LL_Fire LL_HydrantLaterals LL_Industrial LL_Irrigation ML ML_GM ML_GM_Carrier ML_GM_InLineStorage ML_GM_TransportPipe ML_PM ML_PM_AirRelease ML_PM_BlowOff ML_PM_Bypass ML_PM_ChemicalInjection ML_PM_DistributionMain ML_PM_Interconnect ML_PM_PipeBridge ML_PM_SamplingStation ML_PM_Transmiss ionMain + + + + + + + + + + + + + + + + + + + + + + + potable raw salt treated (water type value: potable, raw, salt, treated; pipe type value -> codelist) anode clearWell controlValve fitting hydrant junction lateralPoint meter pump pumpStation samplingStation scadaSensor storageBasin storageFacility surgeReliefTank systemValve thrustProtection treatmentPlant well Water appurtenance (codelist: anode, clear well, control valve, fitting, hydrant, pump, etc.) 13 13

Thema « Nutsdiensten en overheidsdiensten » Application schema sewer network class Sew er Netw ork UtilityLinkSequence Node UtilityNetworkElement «featureType» Utility Netw orks::Pipe Network «featureType» Utility Networks::UtilityNetwork «featureType» Utility Networks::UtilityNode «voidable» + coating: PipeCoatingValue + diameter: Length + material: PipeMaterialValue + shape: PipeShapeValue «voidable» + maintainer: MaintenanceAuthority + owner: OwnerAuthority «voidable» + elevation: ElevationPoint + heading: Angle «featureType» Sew erPipe «featureType» Sew erAppurtenance «voidable» + averageVolume: Volume + maxCapacity: Measure + type: SewerPipeTypeValue + waterType: SewerPipeWaterTypeValue «featureType» Sew erNetw ork «voidable» + type: SewerAppurtenanceValue Sewer network «codeList» Sew erPipeTypeValue + + + + + + + + + + + + + + + + + + + + + + LL LL_Combination LL_Commercial LL_Domestic LL_Irrigation LL_Storm ML ML_GM ML_GM_Collector ML_GM_Culvert ML_GM_InLineStorage ML_GM_Interceptor ML_GM_InvertedSiphon ML_GM_OpenChannel ML_GM_Outfall ML_GM_Overflow ML_GM_Tunnel ML_PM ML_PM_ForceMain ML_PM_PipeBridge ML_PM_Pressure ML_PM_Vacuum «codeList» Sew erPipeWaterTypeValue + + + + + + + + + + + + + + + + (no distinction) «codeList» Sew erAppurtenanceValue combined reclaimed sanitary storm anode barrel barScreen catchBasin cleanOut dischargeStructure meter pump regulator scadaSensor thrustProtection tideGate Sewer appurtenance (codelist: anode, barrel, pump, regulator, etc.) Sewer pipe (water type value: sanitary, storm, combined, …; pipe type  codelist) 14 14

Thema « Nutsdiensten en overheidsdiensten » Application schema oil&gas network • Model under development : class Oil & Gas Netw ork UtilityLinkSequence Node UtilityNetworkElement «featureType» Utility Netw orks::Pipe Network «featureType» Utility Networks::UtilityNetwork «featureType» Utility Networks::UtilityNode «voidable» + coating: PipeCoatingValue + diameter: Length + material: PipeMaterialValue + shape: PipeShapeValue «voidable» + maintainer: MaintenanceAuthority + owner: OwnerAuthority «voidable» + elevation: ElevationPoint + heading: Angle «featureType» OilAppurtenance «featureType» OilPipe «featureType» GasAppurtenance «voidable» + type: OilAppurtenanceValue «featureType» OilNetw ork «featureType» GasNetw ork «voidable» + type: GasAppurtenanceValue «voidable» + averageVolume: Volume + maxCapacity: Measure «featureType» GasPipe «codeList» OilAppurtenanceValue «codeList» GasAppurtenanceValue «voidable» + averageVolume: Volume + maxCapacity: Measure 15 15

Thema « Nutsdiensten en overheidsdiensten » Utility networks submodel: Open questions • Gebruik van het Generic Network model? • Andere applicatie schema’s? – heating netwerk – opsplitsen Oil & Gas • Level of development of modelization: – te ver? (voor data producers en netwerk beheerders) – niet ver genoeg? (voor gebruikers) • Managen van de 3de dimensie (vs Simple Feature spatial schema) • Validatie en verrijking van de codelijsten door testers 16 16

Thema « Nutsdiensten en overheidsdiensten » Governmental Services: Mandatory data class Administrativ e and Social Gov ernmental Serv ices • Slechts 1 feature type voor alle overheidsdiensten Verplichte attributen: – Identifier endLifespanVersion /* If set, the date endLifespanVersion shall be later than beginLifespanVersion. */ – Location self.endLifespanVersion .isAfter inv: • • • • Address (Annex I), or Building (Annex III), or Facility (Annex III), or GM_Object (Point of interest) (self.beginLifespanVersion) – ServicevalidTo the date validTo shall be equal or later type /* If set, «featureType» Gov ernmentalServ ice + + + inspireId: Identifier serviceLocation: ServiceLocationType serviceType: ServiceTypeValue «voidable» + additionalLocationDescription: PT_FreeText [0..1] + areaOfResponsibility: AreaOfResponsibilityType [0..1] + emergencyPlan: CI_Citation [0..*] + hoursOfService: PT_FreeText + name: GeographicalName [0..*] + note: PT_FreeText [0..1] + occupancy: OccupancyType [0..*] + resources: ResourceType [0..*] + responsiblePartyContact: CI_ResponsibleParty [1..*] + serviceLevel: ServiceLevelValue [0..*] + validFrom: DateTime + validTo: DateTime [0..1] + website: URL [0..1] than validFrom. */ Gebruik van codelijst gebaseerd op COFOG inv: self.validTo .isEqual(self.validFrom) or self.validTo .isAfter(self.validFrom) «lifeCycleInfo, voidable» • Hierarchische lijst (207 entries) + beginLifespanVersion: DateTime DateTime [0..1] Verrijkt met gedetailleerde sub-waarden endLifespanVersion: + naargelang de behoeften • Probleem/issue : onderhoudtovan de The attribute hoursOfService is consistent the ISO data type CI_Citation's attribute hoursOfService codelijsten constraints {endLifespanVersion} {validTo} 17 17

Thema « Nutsdiensten en overheidsdiensten » Governmental Services: Type of services • Codelijst gebaseerd op de COFOG lijst – = Classification of the Functions of Government (stabilized version 1999) – Ontwikkeld door de Organization for Economic Cooperation and Development (OECD) en gepubliceerd door de United Nations Statistical Division (UNSD) – Gebruikt door EUROSTAT sinds 2005 Code 01 Description Public administration office Code 08 Description Education ... ... 02 Public order and safety 08.1 08.2 Administration for education Pre-primary and primary education ... ... 03 Economic affairs 08.2.1 08.2.2 Pre-primary education (IS) Primary education (IS) ... ... 08.3 Secondary education 04 Environmental protection ... ... 08.3.1 08.3.2 Lower-secondary education (IS) Upper-secondary education (IS) 05 Health ... ... 08.4 08.5 Post-secondary non-tertiary education Tertiary education 06 Housing and community amenities ... ... 08.5.1 08.5.2 First stage of tertiary education (IS) Second stage of tertiary education (IS) 07 Recreation, culture and religion ... ... 08.6 08.7 Education not definable by level Subsidiary services to education 09 Social protection ... … – Abbreviations used: (CS) - collective services (IS) - individual services 18 18

Thema « Nutsdiensten en overheidsdiensten » Governmental Services: Voidable data class Administrativ e and Social Gov ernmental Serv ices • Slechts 1 feature type voor alle overheidsdiensten «featureType» Gov ernmentalServ ice Voidable of optionele attributen: – Additional location description endLifespanVersion /* If set, the date endLifespanVersion shall be – Area of responsibility later than beginLifespanVersion. */ • • • • – – – – inv: self.endLifespanVersion I) Administrative unit (Annex.isAfter (self.beginLifespanVersion) Named place (Annex I) Network reference (Annex I or III) GM_MultiSurface (to be digitized) Website Name validTo Occupancy set, the date validTo shall be equal or later /* If than validFrom. Resources self.validTo */ inv: .isEqual(self.validFrom) or self.validTo • Designation .isAfter(self.validFrom) • Quantity – Responsible – Hours of service The attribute hoursOfService is consistent to the ISO data type CI_Citation's – Service administrative level attribute + + + inspireId: Identifier serviceLocation: ServiceLocationType serviceType: ServiceTypeValue «voidable» + additionalLocationDescription: PT_FreeText [0..1] + areaOfResponsibility: AreaOfResponsibilityType [0..1] + emergencyPlan: CI_Citation [0..*] + hoursOfService: PT_FreeText + name: GeographicalName [0..*] + note: PT_FreeText [0..1] + occupancy: OccupancyType [0..*] + resources: ResourceType [0..*] + responsiblePartyContact: CI_ResponsibleParty [1..*] + serviceLevel: ServiceLevelValue [0..*] + validFrom: DateTime + validTo: DateTime [0..1] + website: URL [0..1] «lifeCycleInfo, voidable» + beginLifespanVersion: DateTime + endLifespanVersion: DateTime [0..1] constraints {endLifespanVersion} {validTo} hoursOfService • Global, European, national, regional, communal 19 19

Thema « Nutsdiensten en overheidsdiensten » Governmental Services: Open questions • Aanpak te generiek ?(1 feature type, occupancy en resources niet verplicht): – laat alle data producers/users toe om hun data in te brengen, maar – beperkt interoperabiliteit en bevragingen • Validatie en verrijking van de codelijsten – aantal waarden (te gedetailleerd, of nuttig?) – aantal hiërarchische sublevels • Managen en upgraden van de codelijsten 20 20

sition: GeographicPosition [1..*] able» ernativeIdentifier: CharacterString [0..1] tus: StatusValue [0..1] idFrom: DateTime idTo: DateTime [0..1] Thema « Nutsdiensten en overheidsdiensten » Waste management: Concept of Facility able, lifeCycleInfo» ginLifespanVersion: DateTime dLifespanVersion: DateTime [0..1] • Slechts 1 feature type « Facility » – – – – – Verschillende beschrijvende attributen +address Simple Geometry (GM_Object) «voidable» Name 0..* Description (PT_FreeText) Service hours «featureType» Facility constraints ssPosition} ssCountry} feSpanVersion} • Gemeenschappelijk concept  voorstel +building «voidable» 0..* voor GCM? +building «placeholder,feat... – Production & industrial«voidable» facilities Buildings::Abstract – Agricultural & aquaculture facilities – Governmental services submodel • +parcel «voidable» 0..* Kan gebruikt worden op verschillende +cadastralParcel niveau’s «featureType» «voidable» CadastralParcels::CadastralParcel – Facility / Site(s) / Installation(s) ometry: GM_Object spireId: Identifier bel: CharacterString – Cadastral parcels tionalCadastralReference: CharacterString • 0..* + inspireId: Identifier «voidable» + activity: ActivityType [1..*] + description: PT_FreeText [0..1] + geometry: GM_Object [0..1] + Id: IdentifierType [0..*] + name: PT_FreeText [0..1] + permission: PermissionType [0..*] + relatedParty: PartyRoleType [0..*] + serviceHours: ServiceHoursType [0..*] + status: FacilityStatusType [0..*] + type: FacilityListType [0..*] + validFrom: DateTime + validTo: DateTime [0..1] «voidable, lifeCycleInfo» + beginLifespanVersion: DateTime + endLifeSpanVersion: DateTime constraints {EndLifeSpanVersion} {validTo} Kan gerelateerd worden met able» – Addresses eaValue: Area [0..1] – [0..1] erencePoint: GM_Point Administratives idFrom: DateTime [0..1] – idTo: DateTime [0..1] Buildings units +parent 0..* «voidable» 21 21

Thema « Nutsdiensten en overheidsdiensten » Waste management: Sub-types & lists featureType» resses::Address Candidates for inclusion in Generic Conceptual Model cator [1..*] {ordered} icPosition [1..*] : CharacterString [0..1] [0..1] me [0..1] o» on: DateTime : DateTime [0..1] Datatypes Nieuwe datatypes: «dataType» Activ ityType + «featureType» Facility constraints +address «voidable» 0..* +building «voidable» 0..* +building «voidable» «placeholder,feat... Buildings::Abstract Activity Type - Capacity Type - Facility Status Type - Input Output Type - Party Role Type - Permission Type - Service Hours Type etc. - + inspireId: Identifier «voidable» + activity: ActivityType [1..*] + description: PT_FreeText [0..1] + geometry: GM_Object [0..1] + Id: IdentifierType [0..*] + name: PT_FreeText [0..1] + permission: PermissionType [0..*] + relatedParty: PartyRoleType [0..*] + serviceHours: ServiceHoursType [0..*] + status: FacilityStatusType [0..*] + type: FacilityListType [0..*] + validFrom: DateTime + validTo: DateTime [0..1] «voidable, lifeCycleInfo» + beginLifespanVersion: DateTime + endLifeSpanVersion: DateTime cel dable» 0..* +cadastralParcel «voidable» featureType» arcels::CadastralParcel ect 0..* ng eference: CharacterString «dataType» CapacityType + amount: Measure «voidable» + time: Time [0..1] constraints + + partyId: IdentifierType [0..1] roleType: RoleListType [1..*] «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + party: CI_ResponsibleParty [0..1] constraints «dataType» DayTimeType + + + day: DayListType timeFrom: TM_ClockTime timeTo: TM_ClockTime «dataType» PermissionType «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + description: PT_FreeText [0..1] + Id: IdentifierType [0..*] + relatedParty: PartyRoleType [0..*] «dataType» FacilityStatusType + statusType: StatusListType [0..1] «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + description: PT_FreeText [0..1] A «dataType» Serv iceHoursType + hours: DayTimeType [1..*] «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + serviceDescription: PT_FreeText [0..1] «dataType» IdentifierType ativeUnit 0..1 + featureType» eUnits::Administrativ eUnit Id: Identifier «voidable» + identificationSchemeDesignation: PT_FreeText + identificationSchemeId: Identifier de tiSurface Generic utility classes. 22 alName [1..*] racterString ministrativeHierarchyLevel o» inputOutputType: AbstractListType «voidable» + capacity: CapacityType [0..*] + designation: PT_FreeText [0..1] {PartyIdOrData} «voidable» e» on: DateTime : DateTime [0..1] + «dataType» PartyRoleType {EndLifeSpanVersion} {validTo} +parent 0..* ..1] M_Point [0..1] me [0..1] [0..1] activityType: AbstractListType «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + designation: PT_FreeText [0..1] + input: InputOutputType [0..*] + output: InputOutputType [0..*] «dataType» InputOutputType 22 +competentAdministrativeUnit

Thema « Nutsdiensten en overheidsdiensten » Waste management: Sub-types & lists Candidates for inclusion in Generic Conceptual Model Datatypes Codelists «dataType» Activ ityType Nieuwe codelijsten: + activityType: AbstractListType «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + designation: PT_FreeText [0..1] + input: InputOutputType [0..*] + output: InputOutputType [0..*] - + - amount: Measure «voidable» + time: Time [0..1] «dataType» InputOutputType + Activity List Input Output List Day List Facility List Activity Waste Treatment List etc. «dataType» PartyRoleType «dataType» CapacityType + + constraints {PartyIdOrData} day: DayListType timeFrom: TM_ClockTime timeTo: TM_ClockTime + + + + euRecoveryDisposalOperations eurostatNACE euWasteStatisticsActivities inspireWasteTreatmentActivities «dataType» PermissionType «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + description: PT_FreeText [0..1] + Id: IdentifierType [0..*] + relatedParty: PartyRoleType [0..*] statusType: StatusListType [0..1] «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + description: PT_FreeText [0..1] + + euListOfWastes eurostatCPA «codeList» InputOutputWasteListType Attributes + monday + tuesday + wednesday + thursday + friday + saturday + sunday «codeList» InputOutputProductListType «codeList» FacilityListType + + «codeList» RoleListType installation site + + + + hours: DayTimeType [1..*] «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + serviceDescription: PT_FreeText [0..1] Id: Identifier «voidable» + identificationSchemeDesignation: PT_FreeText + identificationSchemeId: Identifier authority contact operator owner «codeList» Activ ityWasteTreatmentListType + + + + + + disposal dumping incineration landfill recovery storage «dataType» IdentifierType + «codeList» Activ ityRecov eryDisposalListType «enumeration» DayListType «dataType» Serv iceHoursType + «codeList» Activ ityWasteStatisticsListType «codeList» InputOutputListSelType «dataType» FacilityStatusType + «codeList» Activ ityNACEListType partyId: IdentifierType [0..1] roleType: RoleListType [1..*] «voidable» + dateFrom: DateTime + dateTo: DateTime [0..1] + party: CI_ResponsibleParty [0..1] «dataType» DayTimeType + + + inputOutputType: AbstractListType «voidable» + capacity: CapacityType [0..*] + designation: PT_FreeText [0..1] «codeList» Activ ityListSelType «codeList,abstract» AbstractListType «codeList» StatusListType + + + + + + + + + abandoned active after-care illegal inactive, not monitored passive planned under construction under demolition Generic utility classes. 23 23

Thema « Nutsdiensten en overheidsdiensten » Waste management: Open questions • Concept « Facility » moet gefinaliseerd worden: – Harmonisatie met andere gebruikers (AF & PF) – Potentiële extensie naar andere thema’s (ER?) – Voorstel voor GCM versie 3 • Managen en upgraden van de codelijsten 24 24

Thema « Nutsdiensten en overheidsdiensten » Belangrijke issues Er is een overlap met heel wat andere thema’s –Hydrography –Buildings –Land use –Environmental monitoring facilities –Production and industrial facilities –Energy resources –Transport networks –Human health and safety –Natural risk zones –Addresses –... 25 25

Thema « Nutsdiensten en overheidsdiensten » Belangrijke issues Belangrijk discussiepunt: – Hoeveel detail moeten we opnemen in data specificatie (complexiteit van het model)? – Welke informatie is verplicht of optioneel? 26 26

Thema « Nutsdiensten en overheidsdiensten » Belangrijke issues Gebruikte use cases (in annex B van data specificaties): • Utility networks – Use case TWG_US_UN_KLIP (deze use case is gebaseerd op KLIP) • Administrative and social governmental services – Use case TWG_US_GS_Map_case – Use case TWG_US_GS_Data_case – Use case SITMAP – Territorial Information System of Málaga Province (Spain) • Waste management – Use case Waste Management Plans – Cross Thematic Data requirements Nieuwe en/of meer specifieke use cases zijn welkom ! 27 27

Thema « Nutsdiensten en overheidsdiensten » Vragen, opmerkingen, bedenkingen ??? Meld ze via de template ! 28 28

Thema « Nutsdiensten en overheidsdiensten » Reeds ontvangen vragen: INSPIRE data schema’s mogen worden uitgebreid met applicatiespecifieke zaken. Welk mechanisme moet hiervoor gebruikt worden ? In reference to extensions, you can check the Annex F (informative) Example for an extension to an INSPIRE application schema............. 128 in the Generic Conceptual Model (D2.5: Generic Conceptual Model, Version 3.2). Is er een mechanisme om codelijsten uit te breiden ? Regarding code lists, you should review also what is in the Regulation on interoperability of spatial data sets and services http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:3 23:0011:0102:EN:PDF, Article 6 1. And also to refer to the amendment of that Regulation http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:031:0013:01:EN:HT ML. 29 29

Thema « Nutsdiensten en overheidsdiensten » Dank u voor uw aandacht ! En veel succes bij het testen ! Katleen Miserez k.miserez@vmm.be +32 53 72 66 48 30 30

Add a comment

Related presentations

Related pages

6DE THEMA ANNEX III "NUTSDIENSTEN EN OVERHEIDSDIENSTEN ...

Annex III definitie: Nutsvoorzieningen zoals riolering, afvalbeheer, energievoorziening, watervoorziening, bestuurlijke en maatschappelijke instanties van ...
Read more

Thema | LinkedIn

View 94392 Thema posts, presentations, experts, and more. Get the professional knowledge you need on LinkedIn. LinkedIn Home What is LinkedIn? Join Today
Read more

Data Specifications - INSPIRE > Themes

European Commission > INSPIRE > Data Specifications About. Home About INSPIRE ... ANNEX 1. Addresses. ... Annex I,II and III
Read more

G.992.1 – Wikipedia

... entsprechend G.961 Appendix III) in einer angrenzenden Doppelader. ... Annex A und Annex B sind physikalisch unterschiedlich aufgebaut.
Read more

Open Data | Open.NRW

... Schutzgebiet, geregeltes Gebiet“ des INSPIRE Annex- Thema III "Bewirtschaftungsgebiete, Schutzgebiete, geregelte Gebiete und ...
Read more

Abfallverbringung in Deutschland und Europa

... Nr. 1418/2007 der Kommission über die Ausfuhr von bestimmten in Anhang III und IIIA der ... Themen. Klima · Energie; Atomenergie · Strahlenschutz;
Read more

Geoportal.de - Geodaten aus Deutschland - Zeitplan

... dass dieses Datum für die meisten Geodatensätze gilt, die unter die Themen der Anhänge II und III der INSPIRE-Richtlinien fallen. ...
Read more

Skamek Power > Home

6DE-18; 5DK-20e; 6DK-20e; 8DK-20e; ... Welcome to the SKAMEK Power AS website. ... Annex VI, tier II, and correspond to tier III - Certifications issued by
Read more