Bio of Me Graduated Undergrad and MSc in GIS at Edinburgh Now a GIS consultant with ESRI (UK) Became interested in this when I was a student delegate at the AGI conference in 2007 Bio of Bruce Member of the GIS group with Edinburgh Earth Observatory As well as teaching GIS at Edinburgh Steering committee of GISRUK as well as Vice Chairman of Scottish RGS and founder member of AGI Scotland Introduce Talk Result of MSc Take you through the reasons for choice Implications of design & implementation Finally findings and future BUT want to sprinkle in issues, problems and troubles along the way
R.Groot 1997 described Silo mentality Why Silos exists Plethora of HIGH QUALITY independent information sources Organisations compete against each other for information exposure and so there are many different proprietary solutions Independent standards, delivery mechanisms and unique idiosyncracies Break down the silos: How? Secure, standardised and Simple (to start) No silver bullet. No Top down approach. Need grass roots Define SDI as UMBRELLA OF POLICIES AND PROCEEDURES WHICH AIMS TO PROVIDE THE OPPORTUINITY TO CONNECT INFORMATION THROUGH THE CONTEXT OF GEOGRAPHICAL LOCATION
LIGHTWEIGHT: Allows people to plug into their own systems – extend upon it SCALABLE No use in creating a mega silo with a single proprietary interface Standards driven Has to comply with Geographical standards AND IT infrastructure standards Aims affected design - they forced functionality
Lightweight – Middleware solution Single port of entry Minimal requirement of overhead by the stakeholders. Reduce their buy in Varying levels of information required Don’t need to change the data sources but instead focus on interoperability. Make the convertor, not the change at the base system Keep the data separate to data delivered and method of consumption Scalable Designed in a manner that would allow component driven development Coordinate conversion Chose KML as it was able to support different geographical representations, text, media etc etc Output in various formats to allow development off Standards driven Why not use OGC? WMS -> Only handles images WFS -> No support for Text KML Lightweight Doesn’t come with 500 page standard De Facto standard Free NEGATIVES: - Only WGS 84, not the same geographical descriptive as OGC RESULTING SYSTEM EVOLVED INTO TWO TIERS......
Emphasise that URL sharing is the first step to linking information through geographical location Served through GEOGRAPHICAL GLUE OF LOCATION Provides a method of systematic searching - provides robust a discrete framework THE PROCESS WORKFLOWS OF THIS SYSTEM ARE BEST VISUALISED WITH THE DIAGRAM.....
Allows Forms of Data Contains the features Through the use of CYGnus, several issues have been raised and would suggest that they are research areas.......
Handling data for same feature TROON – Same thing different data Hierachy of data EDINBURGH – Need to order the data Textual issues: Same thing different name – Balmoral Hotel = North British Hotel Same thing two functions – House of Falkland = Falkland House School Gaelic names – Stornoway = Steòrnabhagh Spatial Issues Same thing, different locations GLASGOW – Centre not of the PO but of the Cathedral but this is 12 th century and so it is East of modern city centre. This used to be the post offices but now they are moving out to the suburbs Areal of city units Newbigging – There are 5 Newbiggings in Scotland! Three of which are within a few miles of eachother!
Scotland’s places NAS and RCAHMS partnership is building a de facto for use of parish names into location. Agreed format and agreed version of Parishes END: Fills a gap for single delivery mechanism for delivering textual information Recognises and supports SDI – Aids the SDI by providing initial solution for TEXTUAL delivery Support for current OGC services Ease of scale and extension
Niall Carter: Breaking down the Silos
Breaking down the silos CYGnus Data Delivery Framework Niall Carter & Bruce M. Gittings University of Edinburgh
Aim <ul><li>“ Develop a lightweight, scalable and standards-compliant geographical information delivery system for Scotland” </li></ul>
Requirements <ul><li>Minimal buy in by providers </li></ul><ul><li>Separate delivery mechanism and method of consumption </li></ul><ul><li>Easy to develop off </li></ul><ul><li>Interoperability </li></ul>
CYGnet - CYGnus <ul><li>CYGnet </li></ul><ul><ul><li>Data discovery and deep linking system </li></ul></ul><ul><ul><li>Connects users or more usually other systems to data sources </li></ul></ul><ul><li>CYGnus </li></ul><ul><ul><li>Data delivery system </li></ul></ul><ul><ul><li>Delivers data to end users or occasionally other systems for further processing </li></ul></ul><ul><li>Based on a variety of locational identifiers (EN, LL, Bbox, placename, potentially admin geography, address, postcode etc.) </li></ul>
CYGnus Server Middleware Converts Geographies URL API KML Converts Geographies & compiles documents into one User URL API XML, GML, KML Information Provider Information Provider Information Provider Client Gazetteer
CYGnus <ul><li>Forms of Data </li></ul><ul><li>Textual </li></ul><ul><li>Photos </li></ul><ul><li>Point, lines & polygons </li></ul><ul><li>WMS – provides map background </li></ul><ul><li>Features </li></ul><ul><li>Expandable </li></ul><ul><li>Accessible </li></ul><ul><li>Simple </li></ul><ul><li>Coordinate conversion </li></ul><ul><li>Standards (KML, XML, GML etc. </li></ul>
Issues <ul><li>Handling data for same feature derived from multiple providers </li></ul><ul><ul><li>Troon </li></ul></ul><ul><li>Hierarchy of data </li></ul><ul><ul><li>Edinburgh </li></ul></ul><ul><li>Textual Issues </li></ul><ul><li>Spatial Issues </li></ul><ul><ul><li>Glasgow </li></ul></ul>
This is not a demonstration… <ul><li>… it uses real data </li></ul><ul><li>… from real organisations </li></ul><ul><li>… data is not cut down or simplified in any way </li></ul><ul><li>… data is provided live and in real time </li></ul>
Future <ul><li>Scotland's Places </li></ul><ul><ul><li>NAS and RCAHMS, making connection on parish names </li></ul></ul><ul><li>Part of Scotland's SDI </li></ul><ul><ul><li>Could provide the place name part of SDI without place names; geography instead </li></ul></ul><ul><ul><li>Linking text-based resource </li></ul></ul>
The rise of the mega Silo? <ul><li>CYGnus </li></ul>User Information Provider Information Provider Information Provider