Linked GeoRef

19
DATA LYSATOR web data solutions and training Linked GeoRef An Open Dataset and API for Improving Geographical Annotation and Finding of Public Sector Information Knud Möller (Datalysator), Florian Marienfeld (Willhöft IT) 2nd Open Data Dialog, 19 November 2013, Berlin, Germany

description

 

Transcript of Linked GeoRef

Page 1: Linked GeoRef

DATA LYSATORweb data solutions and training

Linked GeoRefAn Open Dataset and API for Improving GeographicalAnnotation and Finding of Public Sector Information

Knud Möller (Datalysator), Florian Marienfeld (Willhöft IT) 2nd Open Data Dialog, 19 November 2013, Berlin, Germany

Page 2: Linked GeoRef

D TALYSATORweb data solutions and training

The Challenge

•Most (Open (Government)) datasets refer to some location.

•Let’s declare that in the metadata!

2

http://www.opendata-hro.de

Page 3: Linked GeoRef

D TALYSATORweb data solutions and training

Which Standard?•There are plenty of options

• ISO authority: ISO 3166-1/2, Codes for the representation of names of countries and their subdivisions

• EU regulation: NUTS (Nomenclature of Units for Territorial Statistics)

• German elaboration: Amtlicher Gemeindeschlüssel (AGS) / Amtlicher Regionalschlüssel (ARS)

• Geometry: Geographical Bounding Boxes

3

Page 4: Linked GeoRef

D TALYSATORweb data solutions and training

Best fit for Germany?• AGS would work great

• From federal states down to boroughs:

• 05: Nordrhein-Westfalen

• 3: Regierungsbezirk Köln

• 82: Rhein-Sieg-Kreis

• 064: Gemeinde Swisttal

➡ 0538364

4

Page 5: Linked GeoRef

05: Nordrhein-Westfalen

053: Regierungsbezirk Köln

05382: Rhein-Sieg-Kreis

D TALYSATORweb data solutions and training 5

05382064: Gemeinde Swisttal

Map

s ta

ken

from

Wik

iped

ia

Page 6: Linked GeoRef

D TALYSATORweb data solutions and training

Problems with AGS

•only Germany

•not even all of it:

•no further detail for city-states like Berlin or Hamburg (no “Neukölln” in AGS)

• city states have their own local systems, e.g. “Lebensweltlich orientierte Räume” (LOR) in Berlin

6

Page 7: Linked GeoRef

D TALYSATORweb data solutions and training

Problems with others• NUTS and ISO:

• not as detailed as AGS

• not “at home” in administration

• bounding boxes

• not precise enough

• coordinates not so easy to read as text

• Everybody likes their own approach best...

7

Page 8: Linked GeoRef

D TALYSATORweb data solutions and training

Why Choose?

• Proposal: Linked Data solution

• combine all approaches in one dataset

• every code in every system gets unique identifier: a URI - dereference it (surf to it) and find out what it means!

8

• codes are linked: what is the same? what is contained in what (hierarchy)?

Page 9: Linked GeoRef

D TALYSATORweb data solutions and training

Linked GeoRef• http://lgeoref.org/nuts/DE (Germany)

• http://lgeoref.org/nuts/DEA (North Rhine-Westphalia)

• http://lgeoref.org/ags/05 (North Rhine-Westphalia)

• http://lgeoref.org/ags/12 (Brandenburg)

• http://lgeoref.org/ags/05/3/82 (Rhein-Sieg-Kreis)

• http://lgeoref.org/berlin/lor/08 (Neukölln)

• http://lgeoref.org/berlin/lor/02/02/02/06 (Graefekiez)

9

Page 10: Linked GeoRef

D TALYSATORweb data solutions and training

Integrate Reference Systems

10

DE

DEA DE3

Germany

NRW Berlin

Page 11: Linked GeoRef

D TALYSATORweb data solutions and training

Integrate Reference Systems

11

DE

DEA DE3

Germany

1105

05/3

05/3/82

05/3/82/064

NRW Berlin

Reg.-Bez. Köln

Rhein-Sieg-Kreis

Swisttal

Page 12: Linked GeoRef

D TALYSATORweb data solutions and training

Integrate Reference Systems

12

DE

DEA DE3

Germany

1105

05/3

05/3/82

05/3/82/064

NRW Berlin

Reg.-Bez. Köln

Rhein-Sieg-Kreis

Swisttal

02

02/02

02/02/02

02/02/02/08

08

Neukölln

Friedrichshain-Kreuzberg

Kreuzberg Süd

Tempelhofer Vorstadt

Graefekiez

Page 13: Linked GeoRef

D TALYSATORweb data solutions and training 13

Page 14: Linked GeoRef

D TALYSATORweb data solutions and training

Usecase: govdata.de

• geo-referencing data

• map-based search and filtering

• hard to enforce one scheme in metadata

• Linked GeoRef could help: spatial-uri field in addition to spatial (coordinates) and spatial-text (human-readable):

14

"spatial-uri": "http://lgeoref.org/berlin/lor/08"

Page 15: Linked GeoRef

D TALYSATORweb data solutions and training

Usecase: Code Converter

• convert between different reference systems

• “which AGS is this NUTS ‘DEE’”?

15

Page 16: Linked GeoRef

D TALYSATORweb data solutions and training

Collateral Usage

•central reference point for different code systems

•lookup for relations between codes (containment, identity, overlap, etc.)

•links to other widely-used reference datasets, e.g. DBpedia, GeoNames

16

Page 17: Linked GeoRef

D TALYSATORweb data solutions and training

Internals• data in various formats (mostly Excel) from various

sources converted to RDF

• interlinked, enriched and linked to external data (DBpedia, Geonames)

• each reference system in its own namespace

• http://lgeoref.org/ags/

• http://lgeoref.org/nuts/

• http://lgeoref.org/berlin/lor/

• etc.

• hosted in RDF store with SPARQL endpoint (dydra.com)

• simple Linked Data frontend with Pubby

17

Page 18: Linked GeoRef

D TALYSATORweb data solutions and training

Take-home• challenge: Open Data needs geographical

context

• many useful geo reference systems (AGS, NUTS, ...)

• but: everybody likes a different one

• so: don’t choose, use all of them together

• Linked GeoRef provides integrated, dereferenceable framework for this

18

Page 19: Linked GeoRef

D TALYSATORweb data solutions and training

References

• NUTS: http://epp.eurostat.ec.europa.eu/portal/page/portal/nuts_nomenclature/introduction

• AGS: http://de.wikipedia.org/wiki/Amtlicher_Gemeindeschlüssel

• LOR: http://www.stadtentwicklung.berlin.de/planen/basisdaten_stadtentwicklung/lor/

• Dydra: http://dydra.com

• Pubby: https://github.com/cygri/pubby

19