The impacts of Open Government initiatives on SDIs

Transcription

1 The impacts of Open Government initiatives on SDIs Martin Seiler Coordination Office SDI Germany INSPIRE Conference 2013 Florence, 27 June 2013

2 Outline (Open) Government in Germany GDI-DE-architecture govdata.de architecture Providing geospatial metadata to govdata.de Conclusion & Outlook

3 Administrative structure federation 16 federal states ( Bundesländer ) GeoBasis-DE / BKG 2013

4 Administrative structure federation 16 federal states ( Bundesländer ) ~ municipalities GeoBasis-DE / BKG 2013

5 Administrative structure federation 16 federal states ( Bundesländer ) ~ municipalities They all own data! GeoBasis-DE / BKG 2013

6 Open Government Common Drivers: public discourse about transparency in politics revision of PSI directive governmental data as public good economic potential through innovation

7 Open Government But diverse: laws cultures mindsets implementations GeoBasis-DE / BKG 2013

8 What is open data? Open Knowledge Foundation: defines 11 criteria: / (e.g. access/technological restriction, reuse/attribution, integrity, details about licenses, statements regarding discrimination, )

9 What is open data? Open Knowledge Foundation: defines 11 criteria: / (e.g. access/technological restriction, reuse/attribution, integrity, details about licenses, statements regarding discrimination, ) govdata.de is less demanding clear license statement license considered open data available for download data available in a machine readable format

10 SDI architecture

11 SDI architecture

12 SDI architecture

13 SDI architecture > 30 Discovery Services connected

14 Govdata.de portal on federal level nation-wide, harmonized access to open data search and access through a single website harmonized categories, metadata prototype online since 03/2013 large share of data in administrations is spatial data!

15 Govdata.de portal on federal level nation-wide, harmonized access to open data search and access through a single website harmonized categories, metadata prototype online since 03/2013 large share of data in administrations is spatial data! We have an application for your SDI!!

16 Govdata.de

17 Govdata.de architecture Source: Marienfeld (2012)

18 Govdata.de architecture Source: Marienfeld (2012)

19 GDI-DE vs. govdata.de GDI-DE Govdata.de Interface ISO AP CKAN-APIs Format XML JSON Data model ISO CKAN-Profil Complexity high low Standard license no yes

20 GDI-DE vs. govdata.de GDI-DE Govdata.de Interface ISO AP CKAN-APIs Format XML JSON Data model ISO CKAN-Profile Complexity high low Standard license no yes

21 Challenges identifying open data in the central

22 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts

23 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts

24 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling

25 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use

26 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use additional agreements on metadata in GDI-DE

27 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use additional agreements on metadata in GDI-DE Keyword:

28 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use additional agreements on metadata in GDI-DE {name: Name of License URL: Attribution: Attribution Text }

29 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use additional agreements on metadata in GDI-DE resolve data-service coupling

30 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use additional agreements on metadata in GDI-DE resolve data-service coupling json export

31 Challenges identifying open data in the central mapping ISO to CKAN-Profile, e.g. Point of Contacts Data Service Coupling Restrictions on access and use promote common licenses keeping the infrastructures in sync identification of resources

32 Challenges GDI-DE central local

33 Challenges GDI-DE central local (local, regional, thematic)

34 Challenges GDI-DE central (central) ISO local (local, regional, thematic) Source: Weichand (2013), edited

35 Challenges GDI-DE central (central) ISO local (local, regional, thematic) (local, regional, thematic) Source: Weichand (2013), edited

36 Challenges GDI-DE central (central) ISO local (local, regional, thematic) (local, regional, thematic) Source: Weichand (2013), edited

37 Challenges GDI-DE central (central) ISO local (local, regional, thematic) ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

38 Challenges GDI-DE central (central) Govdata.de (central) ISO local (local, regional, thematic) ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

39 Challenges GDI-DE central (central) Govdata.de (central) ISO CKAN local (local, regional, thematic) ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

40 Challenges GDI-DE central (central) Govdata.de (central) ISO CKAN local (local, regional, thematic) ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

41 Challenges GDI-DE central (central) ISO CKAN Govdata.de (central) ISO CKAN local (local, regional, thematic) ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

42 Challenges GDI-DE Transformation A: central (central) ISO CKAN Govdata.de (central) Transformation A!= Transformation B ISO CKAN local (local, regional, thematic) Transformation B: ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

43 Challenges GDI-DE Transformation A: central (central) ISO CKAN Govdata.de (central) Transformation A!= Transformation B ISO CKAN - Duplicates? - Priorities? local (local, regional, thematic) Transformation B: ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

44 Challenges SDI Europe central (central) Transformation A: ISO CKAN Govdata.de (central) ISO CKAN local (local, regional, thematic) Transformation B: ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

45 Challenges SDI Europe (INSPIRE) ISO CKAN DCAT central (central) Transformation A: ISO CKAN Govdata.de (central) ISO CKAN local (local, regional, thematic) Transformation B: ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

46 Challenges SDI Transformation C: Europe (INSPIRE) ISO ISO DCAT Transformation D: CKAN DCAT central (central) Transformation A: ISO CKAN Govdata.de (central) ISO CKAN local (local, regional, thematic) Transformation B: ISO CKAN (local, regional, thematic) Source: Weichand (2013), edited

47 Conclusion lessons learned about usefulness of the infrastructure for others

48 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity

49 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users

50 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users open up

51 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users open up high quality metadata is crucial (automatisms, editors)

52 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users open up high quality metadata is crucial (automatisms, editors) INSPIRE metadata IR/TG need improvement

53 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users open up high quality metadata is crucial (automatisms, editors) INSPIRE metadata IR/TG need improvement clear license statements are essential

54 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users open up high quality metadata is crucial (automatisms, editors) INSPIRE metadata IR/TG need improvement clear license statements are essential centralized architecture is adjusting slowly

55 Conclusion lessons learned about usefulness of the infrastructure for others reduce complexity care about requirements of potential/new users open up high quality metadata is crucial (automatisms, editors) INSPIRE metadata IR/TG need improvement clear license statements are essential centralized architecture is adjusting slowly is a challenge and a chance

56 Thank you Questions?