Enabling INSPIRE in Italy

Transcription

1 1

2 Enabling INSPIRE in Italy Some comments from the point of view of: - public administration - industry -research 2

3 Today everything is / shall / should / maybe is INSPIRE-compliant! What does it really mean in Italy? The legal mandate: Executive Decree n. 32 (DL 32) of 27 January 2010, enforcing the Directive 2007/2/CE 3

4 The DL 32/2010 The Decree 32/2010 explicitely refers to two already established infrastructures: - the network SINAnet, where the territorial data shall be integrated - the register RNDT, where the metadata are collected (made mandatory by DL 32/2010) 4

5 The SINAnet SINAnet is the network connecting many entities: - the national environmental agency (ISPRA) - the regional agencies - other relevant bodies SINAnet: - has been designed on the basis of EIONET - initially for reporting purposes, currently is extending its scope 5

6 The entities of SINAnet Each SINAnet entity exposes its information content and services in an agreed way (compliance to SEIS also to be enforced) Many entities many possible legacy problems, affecting the interoperability: - e.g. old databases, proprietary solutions - total transformations / evolutions not easily viable on the short / medium term 6

7 SINAnet and SPCoop SPCoop provides the framework of solutions for the interoperability of the Public Administration SINAnet has been designed according to the interoperability standards of SPCoop: - no hierarchies for the systems - federation of systems exchanging services - data maintained where they are produced 7

8 The domains in SPCoop SPCoop mandates that any organisational entity shall be seen as an individual domain Each domain can group many (pre-existent) IT systems Each domain has a logical gateway, as the access point to/from other domains 8

9 A graphic schema of SINAnet 9

10 The logical gateway in SPCoop - accepts and translates the incoming queries from outside - returns the results of the translated queries from inside the domain to the external users (both human or system) - resolves possible legacy problems of the pre-existent systems inside the domain 10

11 The global view According to SPCoop: - SINAnet is a federation of interoperable logical gateways - each logical gateways is deployed locally - a register stores the necessary support information Globally, strong similarities with the INSPIRE approach; however 11

12 At the implementation level Problems arising from the technology standards, e.g. for webservices : - OGC (and INSPIRE) allow SwA (SOAP with attachment) and MTOM (Message Transmission Optimisation Mechanism) - in SPCoop, SwA (SOAP with attachment) only is currently supported 12

13 The metadata in RNDT RNDT (Repertorio Nazionale dei Dati Territoriali) has been designed by CNIPA / DigitPA and published in 2009 RNDT is based upon ISO 19115, same as INSPIRE However: RNDT (2009) and INSPIRE are independent applications of ISO RNDT (2009) doesn t totally meet the indications of DL 32/2010 (lack of metadata for raster data etc.) Until a new release of RNDT, there is a problem of compliance with INSPIRE rules 13

14 The Hyerarchy level in RNDT - in RNDT: Hierarchy level (series; datasets; tiles) -In INSPIRE IR: Resource type (series; datasets) 14

15 The ISO19115 model 15

16 The registers In SINAnet: - services register required by SPCoop (being implemented) - data register included in FONTI (a database derived form CDR of EEA) - metadata register provided by RNDT (for territorial data and services) To be reshaped for INSPIRE. Which approach? 16

17 The possible approaches to deploy registers In general: - centralised register - federation of local registers - master/slaves copies (with constraints) 17

18 SPCoop basically requests (with exceptions) the federation of local registers 18

19 RNDT is a centralised register, supporting the Discovery services as per DL 32/

20 Back to SINAnet Registries are on the nodes Each node has: - a shared portion (for interoperability) - a private portion (domain specific) 20

21 The searches In SINAnet, a (geo)portal accesses directly the shared portions of the nodes This is strongly similar to the libraries national system (ISO 23950, with Z 3950 as access protocol and Dublin Core for metadata) Also similar to GBIF (inside GEOSS), with TAPIR as protocol and Darwin Core for metadata 21

22 Protocols and models In each of the mentioned contexts, the searches exploit: - one agreed harmonised data model - one agreed query protocol In SINAnet, GI-CAT as a super-protocol supporting many prototcols and many shared data models 22

23 The metadata on the SINAnet nodes Each node applies its own set of metadata BUT there is a subset mapping the agreed ones The gateway takes care of the translation from the local standard to the common standard, if and when necessary the above, as an already proven way of managing the transient 23

24 Conclusions Compliance to INSPIRE a snapshot of a moving target impacts also (and strongly) on related initiatives requires to carefully manage the transient can build upon some old solutions. 24

25 Thanks for your attention! 25