Applications of Smart Points Of Interest Otakar Čerba University of West Bohemia, Plzeň, Czech Republic Outline I About Smart Points of Interest (SPOI) I Examples of applications – map client I Future steps of SPOI development Motivation – Why did we start to develop SPOI 1. Request for open data for tourism, including promotion of services or regions → data focused on interesting places or features (points of interest) 2. Need to interconnect this data with existing data, but also non-structured information (photos, maps, text documents, records. ) → Linked Data approach 3. Demand on seamless data (without state borders) → one global dataset enabling any type of data querying (GeoSPARQL) 4. Low costs on data production and management → data from various existing resources, but published in the uniform data model and with use standards 5. Possibility of an attractive visualization (maps), integration to external application and simple editing → support by independent simple tools based on standards Smart Points of Interest (SPOI) I ~27 000 000 points published as 5* Linked Open Data I Data access I Map client (within editing) I SPARQL endpoint (results exported to JSON, CSV, RDF. ) I Web page: gis.zcu.cz/spoi I SPOI description I Links to map client and SPARQL endpoint I Data model, harmonization scheme, list of changes, metadata DOAP a VoID SPOI Populating I 49 external data resources I Global datasets – OpenStreetMap, Natural Earth, GeoNames.org I Local data from Citadel on the Move project I Local data – small regions from Italy, Belgium, Czechia or Latvia I Harmonization process (automated / semi-automated – various tools) I Filtering I Format conversion I Data models conversion I Coordinates transformation I Adding links, metadata Vocabularies I RDF, RDFS – basic framework for SPOI data stored as RDF triple I OWL, SKOS – identity links I FOAF – attributes with contact information I ISA Programme Location Core Vocabulary – addresses I GeoSPARQL – topological relation I Dublin Core, DOAP, VoID – metadata Links I Sematical / vocabulary links → SPOI Ontology (→ GEMET, Eurovoc, OpenStreetMap) I Identity links → LinkedGeoData / OpenStreetMap, GeoNames.org I Topological links → DBpedia, GeoNames.org I Extension / relationship links → non-structured data (photos, Wikipedia, maps. ) SPOI Visualization By J. Kellar (as testing of Big Spatial Data visualization) Map client I HS Layers – libraries OpenLayers a ExtJS, open source pod GNU/GPL license I Functions – zooming, paning, layer switcher, various background maps, searching, change of visual properties of layers. I Relation to Open Weather Map I Sharing – providing of HTML code to integrate SPOI to any web page I Editing – adding new points, editing attributes of existing points Map client (Nicolosi, Italy) Tourism Applications I Smart Tourism Guide (by J. Macura) I SPOI searching based on coordinates or GeoNames.org objects without a need of SPARQL or GeoSPARQL experince I Data export to KML or GPX I Local guides (Peregrinus project, farms) I Generating web pages with information on interesting places Smart Tourism Guide (Plzeň, Czech Republic) – map Local Guide (Týnec, Czech Republic) – web page Local Guide (Týnec, Czech Republic) WebGlayer vizualization I Experimental spatial Big Data visualization (by Jáchym Kellar supervised by Jan Ježek) I Rigu, Latvia I Heat map I Real-time madification of the map (filtering, selection by area. ) WebGLayer (Riga) Future Steps I Data collecting and uploading optimization I Data model & metadata → exchange format I Massive linking I New data & new data resources (Wikidata, DBpedia) I Errors & duplicities eliminating I Update procedure I Better map client (visual hierarchy, clustering. ) I New application and services based on SPOI (AR with SPOIs) I Promotions and consultations Conclusions – Benefits of SPOI I Common data model I Re-using existing standards I Linked Open Data I SPARQL endpoint I Community (students, locals, projects – SDI4Apps, Peregrinus, OTN. ) Thank you for attention and questions Otakar Čerba (https://cz.linkedin.com/in/otakarcerba) gis.zcu.cz/spoi.