Scotland's Environment Web Data Journey Dave Watson, Duncan Taylor
Session Outline SEWeb data journey –What has been encountered on that journey SEWeb as a data consumer –What do we do with the data? Five Star/Linked Data SEWeb Data – what next?
SEWeb Data Journey
SEWeb Brand – Daughter Web Sites
Data at Source
Dataset Progress ‘Data at Source’ – 55 WMS consumed by Map Viewer -> 239 Data Layers – 9 Rest Services consumed by Land Information Search (LIS) -> 39 Data Layers – 10+?? Non spatial data consumed by Visualisation Tools Five Star /Linked Data – 68 SESO Data, 12 Water (SEPA WFD), 1 Site Conditioning (SNH) Data Holdings – Soils/Aquaculture Daughter Sites – Project Finder
What do we do with the data? Themed spatial maps Advanced Maps Visualisation Applications Task Specific Applications Linked Data Repository
Themed/Advanced Maps
Task Specific Maps – Land Information Search
Visualisation/Discover Data
# Available on the web (whatever format) but with an open licence, to be Open Data # Available as machine-readable structured data (e.g. excel instead of image scan of a table) # # # as (2) plus non-proprietary format (e.g. CSV instead of excel) # # All the above plus, Use open standards from W3C (RDF and SPARQL) to identify things, so that people can point at your stuff # # # # # All the above, plus: Link your data to other people’s data to provide context Why Linked Data? - 5 Star Model of Open Data
Linked Data Four Principles 1.Use URIs as names for things 2.Use HTTP URIs so that people can look up those names. 3.When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL) 4.Include links to other URIs so that they can discover more things.
State of Environment (SOE) – Linked Data Model
SOE – Implementation Vocabulary/concept scheme Trial data
SOE Data Linkages ChapterTopicDataset SEWEB SOE Data Linkages
ChapterTopic = national indicator Dataset European Indicator (SOE) EEA SEWEB relates to SOE Data Linkages
ChapterTopicDataset Data view and download services Data Provider links to Metadata EEA SEWEB relates to publishes feeds European Indicator (SOE)
SEWeb Data - What Next? Continued Addition of Datasets What’s in my Area? – Local Datasets/SEWeb Local Scottish Government Digital Strategy – Data Portals Graphical Data Models to support ‘State of Environment’ Links to European Data Initiatives
Useful Links –SEWeb –Scottish Soils –Aquaculture –Linked Data Lab –SSDI –INSPIRE –Water Classification Visualisation a_visualisation/water_body_classification.aspx
End of Presentation – Workshop Support Slides Follow
Useful Links –SEWeb –Scottish Soils –Aquaculture –Linked Data Lab –SSDI –INSPIRE –Water Classification Visualisation a_visualisation/water_body_classification.aspx
SENSE 3 – Schema Relationships
State of Environment Reporting Defined by chapters (air, water, land, etc) Chapters divided into topics, each with a summary quality assessment Datasets support and inform the assessment of the topic A dataset may be related to more than one topic Currently published as static pages
State of Environment Reporting Remodel as linked data Enable publication of metadata on datasets Link to data visualisation and download where available Provide contact details where data not yet published on line Provide support and examples of best practice to assist publication
SEPA as Data Provider
SEPA Reporting Requirements Information required at many levels Internal – SEPA corporate systems National – State of Environment; SEWeb European – Directive Reports; INSPIRE
Where we were… Many applications Many formats Many versions SEPA Database Reports GIS Applications Publications Website Information Requests EU Reporting
What we decided to do Focus on data – not applications Identify key reporting datasets Define them once Use them many times… …in many formats
Where we’ve got to Operational Database Reporting Database Publish Externally Defined data “products” Consistent metadata GIS Intranet Reports & Analysis SEWeb SEPA Website EU Reporting Consistent data
Where we’re getting to Operational Database Reporting Database Publish as WMS; WFS; Linked data Defined data “products” Consistent metadata GIS Intranet Reports & Analysis EU Reporting Consistent data Websites (SEPA, SEWeb,…) Partners Public EU
What’s helped Scotland’s Spatial Data Infrastructure – provided framework and standards for metadata SEWeb – prioritisation of datasets Government direction – “digital by default“ EU reporting frameworks – SEIS, SENSE
What we need now Agree to use existing standards and vocabularies Define new ones where appropriate Encourage use of common reference systems Encourage others to use the data
What we get out of it Wider (and cleverer) use of data Less bespoke development Fewer information requests to deal with Publish data once – let everyone else get on with it
Data Architecture
Linked Data
# Available on the web (whatever format) but with an open licence, to be Open Data # Available as machine-readable structured data (e.g. excel instead of image scan of a table) # # # as (2) plus non-proprietary format (e.g. CSV instead of excel) # # All the above plus, Use open standards from W3C (RDF and SPARQL) to identify things, so that people can point at your stuff # # # # # All the above, plus: Link your data to other people’s data to provide context 5 Star Model of Open Data
What is Linked Data? Data in which real-world things are given addresses on the web (URIs), and data is published about them in machine-readable formats. Describes a method of publishing structured data so that it can be interlinked and become more useful. Builds upon standard Web technologies such as HTTP, RDF and URIs, but rather than using them to serve web pages for human readers, it extends them to share information in a way that can be read automatically by computers. HTTPRDFURIs Enables data from different sources to be connected and queried.
Linked Data Four Principles 1.Use URIs as names for things 2.Use HTTP URIs so that people can look up those names. 3.When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL) 4.Include links to other URIs so that they can discover more things. ml
Operational System
Typical Relational Data Table Surface Water Bodies COLUMN NAMEDATA TYPEMANDATORY IDNumberY NAMEVarchar2(30)Y CATEGORYVarchar2(15)N SUB_BASINVarchar2(30)N CATCHMENTNumberN STATUSVarchar2(30)N
Typical Relational Data IDNAMECATEGORYSUB_BASINCATCHMENTSTATUS 3001River Almond (Breich Water confluence to Maitland Bridge) RiverForth61Poor 3809River North Esk (Source to Penicuik House) RiverForth63High Loch ShielLakeArgyll117Good South ArranCoastalClydeGood
As Linked Data Surface Water Body 3001is of categoryRiver Surface Water Body 3001is calledRiver Almond (Breich Water confluence to Maitland Bridge) Surface Water Body 3001is in sub-basinForth Surface Water Body 3001is in catchment61 Surface Water Body 3001has statusPoor Surface Water Body is of categoryCoastal Surface Water Body is calledSouth Arran Surface Water Body is in sub-basinClyde Surface Water Body has statusGood
As Linked Data Surface Water Body 3001is of categoryRiver Surface Water Body 3001is calledRiver Almond (Breich Water confluence to Maitland Bridge) Surface Water Body 3001is in sub-basinForth Surface Water Body 3001is in catchment61 Surface Water Body 3001has statusPoor Surface Water Body is of categoryCoastal Surface Water Body is calledSouth Arran Surface Water Body is in sub-basinClyde Surface Water Body has statusGood Surface Water Body 3001is in local authorityWest Lothian Surface Water Body 3001is in local authorityCity of Edinburgh Surface Water Body is in postcode districtKA27
RDF/Triplestore SubjectPredicateObject ewaterbody/3001 rdf:type ewaterbody/3001 rdf:type erBody ewaterbody/3001 rdf:type Body ewaterbody/3001 rdfs:label “ River Almond (Breich Water confluence to Maitland Bridge) ” ewaterbody/ /currentOverallClassification “ Overall status – Poor ” ewaterbody/ /inCatchment ent/61 /surfaceArea ent/61 /catchmentType “ Main River ” indistrict/3 rdfs:label “ Forth ”
Non SEPA-SEWeb Linked Data Examples Data.gov.uk. EA Bathing Waters Ordnance Survey Winnipeg Legislation