The impacts of Open Government initiatives on SDIs

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

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

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

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

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

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

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

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

What is open data? Open Knowledge Foundation: defines 11 criteria: http://opendefinition.org/okd / (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

SDI architecture

SDI architecture

SDI architecture

SDI architecture > 30 Discovery Services connected

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!

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!!

Govdata.de

Govdata.de architecture Source: Marienfeld (2012)

Govdata.de architecture Source: Marienfeld (2012)

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

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

Challenges identifying open data in the central

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

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

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

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

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

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

Challenges identifying open data in the central mapping ISO 19115 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: http://www.licenseurl Attribution: Attribution Text }

Challenges identifying open data in the central mapping ISO 19115 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

Challenges identifying open data in the central mapping ISO 19115 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

Challenges identifying open data in the central mapping ISO 19115 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

Challenges GDI-DE central local

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Conclusion lessons learned about usefulness of the infrastructure for others

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

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

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

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)

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

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

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

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

Thank you Questions? martin.seiler@bkg.bund.de